usecix 1.0.6__py3-none-any.whl

cix/__init__.py

@@ -0,0 +1 @@
+"""cix — code index for AI coding tools."""

cix/_indexed_extensions.py

@@ -0,0 +1,68 @@
+"""Canonical map of indexed file extensions → cix language labels.
+
+This is **documentation infrastructure** — the client never parses files.
+The authoritative parser surface lives in cix-api per
+docs/ship_boundary.md §2. This constant exists so generated docs
+(CLAUDE.md / AGENTS.md / GEMINI.md sections from cix.integrations.docs),
+hook messages, and inline comments can quote one source of truth instead
+of pointing readers at ``cix/lib/parser.py:EXTENSION_MAP`` — that module
+was deleted on 2026-05-14 when parsing moved cloud-side.
+
+When cix-api gains parser support for a new extension, add the entry
+here and let the docs regenerate. The list is informational; cix-api is
+the runtime authority and may diverge before this catches up.
+"""
+from __future__ import annotations
+
+# (extension, language-label) pairs in stable display order. Order is the
+# order they appear in generated CLAUDE.md/AGENTS.md/GEMINI.md sections,
+# so keep popular languages first.
+INDEXED_EXTENSIONS: tuple[tuple[str, str], ...] = (
+    ('.py', 'python'),
+    ('.js', 'javascript'),
+    ('.ts', 'typescript'),
+    ('.jsx', 'javascript'),
+    ('.tsx', 'tsx'),
+    ('.vue', 'vue'),
+    ('.php', 'php'),
+    ('.go', 'go'),
+    ('.java', 'java'),
+    ('.cpp', 'cpp'),
+    ('.c', 'c'),
+    ('.cs', 'csharp'),
+    ('.rb', 'ruby'),
+    ('.swift', 'swift'),
+    ('.kt', 'kotlin'),
+    ('.rs', 'rust'),
+    ('.scala', 'scala'),
+    ('.sql', 'sql'),
+    ('.html', 'html'),
+    ('.css', 'css'),
+    ('.scss', 'scss'),
+    ('.md', 'markdown'),
+)
+
+
+def indexed_extensions() -> tuple[str, ...]:
+    """Just the extension strings (e.g. ``.py``), in display order."""
+    return tuple(ext for ext, _ in INDEXED_EXTENSIONS)
+
+
+def indexed_languages() -> tuple[str, ...]:
+    """Just the language labels, deduplicated, in first-seen order."""
+    seen: set[str] = set()
+    out: list[str] = []
+    for _, lang in INDEXED_EXTENSIONS:
+        if lang not in seen:
+            seen.add(lang)
+            out.append(lang)
+    return tuple(out)
+
+
+def render_extensions_inline() -> str:
+    """Render the extension list as a single line of backtick-quoted entries.
+
+    Used by ``cix.integrations.docs`` to populate the "Indexed file types"
+    section in CLAUDE.md / AGENTS.md / GEMINI.md.
+    """
+    return ' '.join(f'`{ext}`' for ext, _ in INDEXED_EXTENSIONS)

cix/_ip_boundary.py

@@ -0,0 +1,97 @@
+"""IP boundary — modules that must NOT ship in the user's binary.
+
+Phase 2c constant. The Nuitka build (Phase 2d) reads this list and
+configures ``--nofollow-import-to`` for each entry, so the produced
+binary fails fast if any client-side code path tries to import a
+restricted module. The thin-mode tests in
+``tests/test_thin_client_boundary.py`` simulate that absence at import
+time and verify MCP advertisement + cloud dispatch keep working.
+
+What's restricted: every cix.core.* module whose tools have a router
+in ``cix.cloud.dispatch._ROUTERS`` (the set is exposed as
+``CLOUD_ROUTED_TOOLS``). Those tools are served cloud-side; their
+Python source is the IP. Modules NOT in this list are local-only
+handlers (refactor, audit, reindex, registry, diagnostics, notes —
+see PHASE_2_STATUS.md "Stays local by nature") or shared
+infrastructure that the thin client needs.
+
+Updating: when a new tool's handler module joins the cloud-routed
+set, add the module here AND verify the boundary tests in
+``tests/py/test_thin_client_boundary.py`` still pass. The reverse —
+moving a tool's handling back to local —
+is a deliberate IP-leakage event that requires a code-review pause;
+removing a module from this list should never be incidental.
+"""
+from __future__ import annotations
+
+# Modules excluded from the user's binary in Phase 2d. All entries are
+# tool-bearing thin router-shells (TOOL_DEFS + cloud_unreachable handler);
+# their full local implementations were ripped on 2026-05-15 under
+# clean-and-ship s3. Each ships only as a manifest-advertisement surface
+# the binary doesn't need to carry.
+#
+# Removed 2026-05-15: cix.core.coverage and cix.core.workspaces — these
+# were support-only helpers for impact / navigation / orientation. With
+# the shadow code gone, nothing client-side imports them, so they no
+# longer have to be enumerated here.
+#
+# Alphabetical for stable diff readability; runtime behavior doesn't
+# depend on order.
+# Full IP-boundary tracking set (18 entries). This is what the Nuitka
+# build excludes via --nofollow-import-to and what the thin-client
+# boundary tests + tool-manifest sync test iterate over. Every entry is
+# a tool-bearing module whose tool stays advertised via the frozen
+# cix._tool_manifest and routes cloud-side via cix.cloud.dispatch.
+# Alphabetical for stable diffs; runtime behavior is order-independent.
+IP_BOUNDARY_TRACKED: tuple[str, ...] = (
+    'cix.core.audit',
+    'cix.core.catchup',
+    'cix.core.counterfactual',
+    'cix.core.coverage_map',
+    'cix.core.diagnostics',
+    'cix.core.impact',
+    'cix.core.last_diff',
+    'cix.core.navigation',
+    'cix.core.orientation',
+    'cix.core.read_stale',
+    'cix.core.refactor',
+    'cix.core.refresh_stale',
+    'cix.core.reindex',
+    'cix.core.renames',
+    'cix.core.search',
+    'cix.core.stale',
+    'cix.core.team_index',
+    'cix.core.vital_sign',
+)
+
+# Strict subset that must NOT appear as a source module inside the built
+# wheel. This is the grep input for forbidden-path verification
+# (tools/build/verify_wheel.py). It is IP_BOUNDARY_TRACKED minus
+# 'cix.core.diagnostics': those 17 shadow modules were deleted from disk
+# 2026-05-19 (clean-and-ship s3), so a clean wheel contains none of them
+# and the grep returns []. diagnostics is deliberately EXCLUDED here:
+# cix/core/diagnostics.py is a real, present source module that
+# legitimately ships (referenced by cix._tool_manifest), so grepping for
+# it would false-positive on a clean wheel (final-launch-design
+# decision #41 / risk #600). diagnostics is still IP-boundary-tracked
+# (Nuitka excludes it from the binary) — it is just not forbidden in the
+# pip wheel.
+SHADOWS_FORBIDDEN_IN_WHEEL: tuple[str, ...] = tuple(
+    m for m in IP_BOUNDARY_TRACKED if m != 'cix.core.diagnostics'
+)
+
+# Backwards-compatible alias. Existing consumers — the thin-client
+# boundary tests, the tool-manifest sync test, and scripts/build_binary.py
+# (Nuitka excludes) — want the full tracking set, which is now
+# IP_BOUNDARY_TRACKED. Keep this name so those imports don't break.
+IP_RESTRICTED_MODULES: tuple[str, ...] = IP_BOUNDARY_TRACKED
+
+
+def is_ip_restricted(module_name: str) -> bool:
+    """True when ``module_name`` is in the restricted set.
+
+    Used by Nuitka config (Phase 2d) and by the manifest-walker in
+    ``cix.mcp_server.main`` to decide whether a missing module is the
+    intentional thin-client cut or an actual install error.
+    """
+    return module_name in IP_RESTRICTED_MODULES