Sync ctx 03af985

GitHub commit: 03af985401f8dd95b559ecb86c10322a86d14af5

.gitattributes

@@ -1,2 +1,4 @@
 graph/wiki-graph.tar.gz filter=lfs diff=lfs merge=lfs -text
 graph/wiki-graph-runtime.tar.gz filter=lfs diff=lfs merge=lfs -text
+graph/skills-sh-catalog.json.gz filter=lfs diff=lfs merge=lfs -text
+graph/skillspector-audit.jsonl.gz filter=lfs diff=lfs merge=lfs -text

.github/pull_request_template.md

@@ -10,6 +10,7 @@
 
 - [ ] Existing tests pass (`pytest -q`)
 - [ ] New tests added for changed behaviour
+- [ ] MkDocs nav page changes update `docs/qa/feature-user-story-status.csv`
 - [ ] `ruff check src/` passes
 - [ ] `mypy src/` passes
 - [ ] Integration tests checked if embedding code was touched (`pytest -q -m integration`)

.github/workflows/docs.yml

@@ -51,25 +51,11 @@ jobs:
         run: |
           python -m mkdocs build --strict
 
-      - name: Archive Pages artifact
-        run: |
-          tar \
-            --dereference --hard-dereference \
-            --directory site \
-            -cvf "$RUNNER_TEMP/artifact.tar" \
-            --exclude=.git \
-            --exclude=.github \
-            --exclude=.[^/]* \
-            .
-
       - name: Upload Pages artifact
-        uses: actions/upload-artifact@v4
+        uses: actions/upload-pages-artifact@v5
         with:
-          name: github-pages
-          path: ${{ runner.temp }}/artifact.tar
+          path: site
           retention-days: 1
-          if-no-files-found: error
-          overwrite: true
 
   deploy:
     name: Deploy to GitHub Pages

.github/workflows/huggingface-sync.yml

@@ -19,12 +19,14 @@ concurrency:
 
 jobs:
   sync:
-    name: Sync dataset
+    name: Sync dataset repo
     runs-on: ubuntu-latest
+    timeout-minutes: 60
     steps:
       - name: Checkout
         uses: actions/checkout@v5
         with:
+          fetch-depth: 0
           lfs: false
 
       - name: Skip when HF_TOKEN is not configured
@@ -32,17 +34,162 @@ jobs:
         run: |
           echo "::notice title=Hugging Face sync skipped::Set the HF_TOKEN repository secret to publish Stevesolun/ctx automatically."
 
-      - name: Hydrate required graph artifacts from release assets
+      - name: Classify sync scope
+        id: scope
         if: ${{ env.HF_TOKEN != '' }}
+        shell: bash
+        env:
+          BEFORE_SHA: ${{ github.event.before }}
+          EVENT_NAME: ${{ github.event_name }}
+          HEAD_SHA: ${{ github.sha }}
+        run: |
+          set -euo pipefail
+          if [[ "$EVENT_NAME" == "workflow_dispatch" ]]; then
+            echo "sync_mode=full" >> "$GITHUB_OUTPUT"
+            exit 0
+          fi
+          BASE="$BEFORE_SHA"
+          if [[ -z "$BASE" || "$BASE" =~ ^0+$ ]] || ! git cat-file -e "$BASE^{commit}" 2>/dev/null; then
+            BASE="$(git rev-parse "$HEAD_SHA^")"
+          fi
+          git diff --name-only "$BASE" "$HEAD_SHA" > changed-files.txt
+          python - <<'PY' >> "$GITHUB_OUTPUT"
+          from pathlib import Path
+
+          files = [
+              line.strip().replace("\\", "/")
+              for line in Path("changed-files.txt").read_text(encoding="utf-8").splitlines()
+              if line.strip()
+          ]
+          card_only_prefixes = (".github/", "docs/", "src/tests/")
+          card_only_files = {"README.md", "CHANGELOG.md"}
+          card_only = bool(files) and all(
+              path in card_only_files or path.startswith(card_only_prefixes)
+              for path in files
+          )
+          print(f"sync_mode={'card' if card_only else 'full'}")
+          PY
+
+      - name: Hydrate required graph artifacts from release assets
+        if: ${{ env.HF_TOKEN != '' && steps.scope.outputs.sync_mode == 'full' }}
         env:
           GH_TOKEN: ${{ github.token }}
         run: |
-          latest_tag="$(gh release view --repo "$GITHUB_REPOSITORY" --json tagName --jq .tagName)"
-          echo "Hydrating graph artifacts from release ${latest_tag}"
-          rm -f graph/wiki-graph.tar.gz graph/wiki-graph-runtime.tar.gz graph/skills-sh-catalog.json.gz
-          gh release download "$latest_tag" --repo "$GITHUB_REPOSITORY" --dir graph --pattern wiki-graph.tar.gz
-          gh release download "$latest_tag" --repo "$GITHUB_REPOSITORY" --dir graph --pattern wiki-graph-runtime.tar.gz
-          gh release download "$latest_tag" --repo "$GITHUB_REPOSITORY" --dir graph --pattern skills-sh-catalog.json.gz
+          set -euo pipefail
+          echo "Resolving graph artifacts from matching release assets to avoid Git LFS bandwidth."
+          python - <<'PY'
+          import hashlib
+          import json
+          import os
+          from pathlib import Path
+          import subprocess
+          import time
+          import urllib.request
+
+          repo = os.environ["GITHUB_REPOSITORY"]
+          release_asset_wait_seconds = 300
+          release_asset_poll_seconds = 10
+          expected_graph_assets = {
+              "graph/wiki-graph.tar.gz": {
+                  "sha256": "d051d4f21208abe3e73975a9c30650150138d88919c27979d725be936a6ea10a",
+                  "size": 296113770,
+              },
+              "graph/wiki-graph-runtime.tar.gz": {
+                  "sha256": "993fc08377fdb09edcff4414c59b10fc121189b4a161bf796e3f8f6600907bb1",
+                  "size": 122141091,
+              },
+              "graph/skills-sh-catalog.json.gz": {
+                  "sha256": "d1bb927e93d65ef86cdbc6d68c7f57511d64c8f13026e8193287a9c4ca6f5815",
+                  "size": 10763626,
+              },
+          }
+
+          def load_releases() -> list[dict]:
+              return json.loads(subprocess.check_output(
+                  ["gh", "api", f"repos/{repo}/releases?per_page=50"],
+                  text=True,
+              ))
+
+          def hydrate_from_release(path_name: str, hydrated_min_size: int) -> None:
+              artifact = Path(path_name)
+              fallback = expected_graph_assets[path_name]
+              expected_oid = fallback["sha256"]
+              expected_size = int(fallback["size"])
+              if artifact.exists():
+                  pointer = artifact.read_text(encoding="utf-8", errors="replace")
+                  for line in pointer.splitlines():
+                      if line.startswith("oid sha256:"):
+                          expected_oid = line.split(":", 1)[1].strip()
+                      elif line.startswith("size "):
+                          expected_size = int(line.split(" ", 1)[1].strip())
+                  if not pointer.startswith("version https://git-lfs.github.com/spec/v1") and artifact.stat().st_size > hydrated_min_size:
+                      print(f"{artifact} is already hydrated")
+                      return
+
+              deadline = time.monotonic() + release_asset_wait_seconds
+              while True:
+                  candidates = []
+                  for release in load_releases():
+                      tag_name = str(release.get("tag_name") or "")
+                      is_graph_cache = tag_name.startswith("graph-artifacts-")
+                      if release.get("draft") or (
+                          release.get("prerelease") and not is_graph_cache
+                      ):
+                          continue
+                      for asset in release.get("assets", []):
+                          if asset.get("name") != artifact.name:
+                              continue
+                          digest = str(asset.get("digest") or "")
+                          size = int(asset.get("size") or 0)
+                          if size != expected_size:
+                              continue
+                          if digest and digest != f"sha256:{expected_oid}":
+                              continue
+                          candidates.append((tag_name, asset))
+
+                  if candidates:
+                      break
+                  if time.monotonic() >= deadline:
+                      raise SystemExit(
+                          f"No release asset matches {path_name} "
+                          f"sha256:{expected_oid} size:{expected_size}"
+                      )
+                  print(
+                      f"Waiting for matching release asset {artifact.name} "
+                      f"sha256:{expected_oid} size:{expected_size}"
+                  )
+                  time.sleep(release_asset_poll_seconds)
+
+              source_tag, asset = candidates[0]
+              tmp = artifact.with_name(f"{artifact.name}.download")
+              sha = hashlib.sha256()
+              total = 0
+              with urllib.request.urlopen(asset["browser_download_url"], timeout=300) as resp:  # noqa: S310
+                  with tmp.open("wb") as fh:
+                      while True:
+                          chunk = resp.read(1024 * 1024)
+                          if not chunk:
+                              break
+                          sha.update(chunk)
+                          total += len(chunk)
+                          fh.write(chunk)
+              actual_oid = sha.hexdigest()
+              if actual_oid != expected_oid or total != expected_size:
+                  tmp.unlink(missing_ok=True)
+                  raise SystemExit(
+                      f"Downloaded {path_name} does not match expected artifact: "
+                      f"sha256:{actual_oid} size:{total}"
+                  )
+              tmp.replace(artifact)
+              print(
+                  f"Hydrated {path_name} from {source_tag} release asset "
+                  f"sha256:{actual_oid} size:{total}"
+              )
+
+          hydrate_from_release("graph/wiki-graph.tar.gz", 100_000_000)
+          hydrate_from_release("graph/wiki-graph-runtime.tar.gz", 10_000_000)
+          hydrate_from_release("graph/skills-sh-catalog.json.gz", 1_000_000)
+          PY
 
       - name: Set up Python
         if: ${{ env.HF_TOKEN != '' }}
@@ -58,7 +205,13 @@ jobs:
           python -m pip install --upgrade pip
           python -m pip install -e ".[dev]" huggingface_hub
 
-      - name: Sync Hugging Face dataset
+      - name: Sync Hugging Face dataset repo
         if: ${{ env.HF_TOKEN != '' }}
+        env:
+          SYNC_MODE: ${{ steps.scope.outputs.sync_mode }}
         run: |
-          python scripts/sync_huggingface.py --repo . --repo-id Stevesolun/ctx --repo-type dataset
+          if [[ "$SYNC_MODE" == "card" ]]; then
+            python scripts/sync_huggingface.py --repo . --repo-id Stevesolun/ctx --repo-type dataset --card-only
+          else
+            python scripts/sync_huggingface.py --repo . --repo-id Stevesolun/ctx --repo-type dataset
+          fi

.github/workflows/publish.yml

@@ -47,7 +47,7 @@ jobs:
       - name: Set up Python
         uses: actions/setup-python@v6
         with:
-          python-version: "3.12"
+          python-version: "3.11"
 
       - name: Install release tooling
         run: |
@@ -155,12 +155,12 @@ jobs:
           release_asset_poll_seconds = 10
           expected_graph_assets = {
               "graph/wiki-graph.tar.gz": {
-                  "sha256": "91b30795e7d200cf31a62a8749969d12658f5f74636d2de06d6b2b24b393c12f",
-                  "size": 457545675,
+                  "sha256": "e487ec2109803e3c05cb2ca6906e8a0bae681f32a4fe79f3fb2f168fbea2c947",
+                  "size": 329276669,
               },
               "graph/wiki-graph-runtime.tar.gz": {
-                  "sha256": "334fb19bace3fd6e4b92087850f17297fb248032957d123f3f1432dfde2e36c0",
-                  "size": 175773376,
+                  "sha256": "993fc08377fdb09edcff4414c59b10fc121189b4a161bf796e3f8f6600907bb1",
+                  "size": 122141091,
               },
           }
 
@@ -258,18 +258,18 @@ jobs:
           python src/validate_graph_artifacts.py \
             --graph-dir graph \
             --deep \
-            --min-nodes 100000 \
-            --min-edges 2000000 \
-            --min-skills-sh-nodes 89000 \
+            --min-nodes 79000 \
+            --min-edges 1700000 \
+            --min-skills-sh-nodes 67000 \
             --min-semantic-edges 1000000 \
-            --expected-nodes 102928 \
-            --expected-edges 2913960 \
-            --expected-semantic-edges 1683193 \
+            --expected-nodes 79958 \
+            --expected-edges 1778069 \
+            --expected-semantic-edges 1088763 \
             --expected-harness-nodes 207 \
-            --expected-skills-sh-nodes 89471 \
-            --expected-skills-sh-catalog-entries 89465 \
-            --expected-skills-sh-converted 89465 \
-            --expected-skill-pages 91464 \
+            --expected-skills-sh-nodes 67028 \
+            --expected-skills-sh-catalog-entries 67024 \
+            --expected-skills-sh-converted 67024 \
+            --expected-skill-pages 68494 \
             --expected-agent-pages 467 \
             --expected-mcp-pages 10790 \
             --expected-harness-pages 207 \
@@ -392,6 +392,38 @@ jobs:
             echo "help smoke: $cmd"
             "$cmd" --help >/dev/null
           done < ctx-console-help.txt
+          echo "Telemetry release smoke"
+          export HOME="$PWD/.telemetry-home"
+          export CTX_TELEMETRY_HASH_SALT="release-smoke-salt"
+          mkdir -p "$HOME"
+          python - <<'PY'
+          from ctx.telemetry import record_counter, record_event
+
+          record_event(
+              "ctx.release.smoke",
+              source="publish-workflow",
+              payload={"query": "raw-release-telemetry-sentinel"},
+          )
+          record_counter(
+              "ctx.release.smoke",
+              attributes={"query": "raw-release-telemetry-sentinel"},
+          )
+          PY
+          ctx-telemetry-export --dry-run --json
+          ctx-telemetry-export \
+            --sink local_jsonl \
+            --output telemetry-events.jsonl \
+            --json
+          ctx-telemetry-export \
+            --signal metrics \
+            --sink local_jsonl \
+            --output telemetry-metrics.jsonl \
+            --json
+          ctx-telemetry-retention plan --signal all --json
+          if grep -R "raw-release-telemetry-sentinel" telemetry-events.jsonl telemetry-metrics.jsonl; then
+            echo "raw telemetry sentinel leaked into exported telemetry" >&2
+            exit 1
+          fi
           python -m pip install "${wheel}[harness]"
           python - <<'PY'
           import litellm

.github/workflows/test.yml

@@ -31,6 +31,7 @@ jobs:
       package_changed: ${{ steps.classify.outputs.package_changed }}
       similarity_changed: ${{ steps.classify.outputs.similarity_changed }}
       source_changed: ${{ steps.classify.outputs.source_changed }}
+      telemetry_changed: ${{ steps.classify.outputs.telemetry_changed }}
     steps:
       - name: Checkout with full history
         uses: actions/checkout@v5
@@ -149,6 +150,33 @@ jobs:
           python -m pip install --upgrade pip
           python -m pip install ".[dev,embeddings]"
 
+      - name: Cache MiniLM model
+        uses: actions/cache@v5
+        with:
+          path: ~/.cache/huggingface
+          key: hf-sentence-transformers-all-MiniLM-L6-v2-v1
+
+      - name: Pre-download MiniLM model
+        env:
+          HF_TOKEN: ${{ secrets.HF_TOKEN }}
+        run: |
+          python - <<'PY'
+          import time
+          from sentence_transformers import SentenceTransformer
+
+          model = "sentence-transformers/all-MiniLM-L6-v2"
+          for attempt in range(1, 5):
+              try:
+                  SentenceTransformer(model)
+                  print(f"ready: {model}")
+                  break
+              except Exception as exc:
+                  print(f"attempt {attempt} failed: {exc}", flush=True)
+                  if attempt == 4:
+                      raise
+                  time.sleep(15 * attempt)
+          PY
+
       - name: Run similarity precision/recall gate
         env:
           CTX_REQUIRE_SIMILARITY_EVAL: "1"
@@ -326,12 +354,12 @@ jobs:
           release_asset_poll_seconds = 10
           expected_graph_assets = {
               "graph/wiki-graph.tar.gz": {
-                  "sha256": "91b30795e7d200cf31a62a8749969d12658f5f74636d2de06d6b2b24b393c12f",
-                  "size": 457545675,
+                  "sha256": "e487ec2109803e3c05cb2ca6906e8a0bae681f32a4fe79f3fb2f168fbea2c947",
+                  "size": 329276669,
               },
               "graph/wiki-graph-runtime.tar.gz": {
-                  "sha256": "334fb19bace3fd6e4b92087850f17297fb248032957d123f3f1432dfde2e36c0",
-                  "size": 175773376,
+                  "sha256": "993fc08377fdb09edcff4414c59b10fc121189b4a161bf796e3f8f6600907bb1",
+                  "size": 122141091,
               },
           }
 
@@ -426,18 +454,18 @@ jobs:
           python src/validate_graph_artifacts.py \
             --graph-dir graph \
             --deep \
-            --min-nodes 100000 \
-            --min-edges 2000000 \
-            --min-skills-sh-nodes 89000 \
+            --min-nodes 79000 \
+            --min-edges 1700000 \
+            --min-skills-sh-nodes 67000 \
             --min-semantic-edges 1000000 \
-            --expected-nodes 102928 \
-            --expected-edges 2913960 \
-            --expected-semantic-edges 1683193 \
+            --expected-nodes 79958 \
+            --expected-edges 1778069 \
+            --expected-semantic-edges 1088763 \
             --expected-harness-nodes 207 \
-            --expected-skills-sh-nodes 89471 \
-            --expected-skills-sh-catalog-entries 89465 \
-            --expected-skills-sh-converted 89465 \
-            --expected-skill-pages 91464 \
+            --expected-skills-sh-nodes 67028 \
+            --expected-skills-sh-catalog-entries 67024 \
+            --expected-skills-sh-converted 67024 \
+            --expected-skill-pages 68494 \
             --expected-agent-pages 467 \
             --expected-mcp-pages 10790 \
             --expected-harness-pages 207 \
@@ -480,7 +508,7 @@ jobs:
           PY
 
       - name: Cache Playwright browsers
-        uses: actions/cache@v4
+        uses: actions/cache@v5
         with:
           path: ~/.cache/ms-playwright
           key: playwright-${{ runner.os }}-${{ steps.playwright.outputs.version }}
@@ -493,6 +521,36 @@ jobs:
       - name: Run browser security tests
         run: pytest -q --no-cov -m browser src/tests/test_ctx_monitor_browser.py
 
+  telemetry-enterprise:
+    name: "Telemetry enterprise gate"
+    needs: classify
+    if: ${{ github.event_name == 'push' || needs.classify.outputs.telemetry_changed == 'true' }}
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v5
+        with:
+          lfs: false
+
+      - name: Set up Python 3.12
+        uses: actions/setup-python@v6
+        with:
+          python-version: "3.12"
+          cache: pip
+          cache-dependency-path: pyproject.toml
+
+      - name: Install telemetry test dependencies
+        run: |
+          python -m pip install --upgrade pip
+          python -m pip install ".[dev]"
+
+      - name: Run telemetry privacy and export tests
+        run: |
+          python -m pytest -q --no-cov \
+            src/tests/test_enterprise_telemetry.py \
+            src/tests/test_harness_cli_run.py \
+            -k "telemetry or runtime_lifecycle"
+
   package-build:
     name: "Build wheel package"
     needs: classify
@@ -709,6 +767,7 @@ jobs:
       - package-build
       - clean-host-contract
       - no-test-no-merge
+      - telemetry-enterprise
     if: ${{ always() }}
     steps:
       - name: Checkout

CHANGELOG.md

@@ -5,7 +5,134 @@ Format loosely follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
-- No unreleased changes yet.
+### Added
+
+- Added enterprise OpenTelemetry-ready telemetry across API, MCP, CLI/runtime,
+  ctx-core tool, skill lifecycle, and CI classifier boundaries, with local
+  NDJSON collection plus ready-to-use OTLP export configuration.
+- Added telemetry retention, governance, collector, dashboard, alert, and
+  release-gate runbook assets so enterprise installs can operate telemetry
+  without leaking payloads by default.
+
+### Fixed
+
+- Hardened structured exception telemetry with hashed messages/stacks and
+  deterministic nested salt handling for privacy-preserving correlation.
+
+## [1.0.19] - 2026-06-23
+
+### Fixed
+
+- Hardened the dashboard smoke contract so it now checks the `/live` alias and
+  the local catalog page, not only the older `/events` and JSON catalog search
+  paths.
+- Added monitor API regressions for typed sidecar JSON reads and the real
+  `/api/unload` agent path without mocking the runtime unload implementation.
+
+## [1.0.18] - 2026-06-22
+
+### Fixed
+
+- Fixed the PyPI publish workflow static gate by aligning it with the
+  canonical Python 3.11 mypy target used by main CI. This supersedes the
+  failed `v1.0.17` publish attempt, whose tag used Python 3.12 for the
+  release static gate while mypy parsed the package as Python 3.11.
+- Removed the remaining dashboard-entity test dependency on private
+  `ctx.monitor.compat._*` helpers by routing it through the stable
+  `ctx.monitor.testing` facade.
+
+## [1.0.17] - 2026-06-22
+
+### Changed
+
+- Split more of `ctx-monitor` into focused modules: graph artifact/index
+  helpers, wiki entity/Markdown renderers, and the graph page client script.
+- Kept the flat `ctx.monitor.compat` layer as the tested backcompat surface
+  while normalizing its source encoding for standard AST tooling.
+- Added a stable `ctx.monitor.testing` facade so monitor tests no longer
+  depend directly on private `compat._*` names.
+
+## [1.0.16] - 2026-06-20
+
+### Fixed
+
+- Fixed `ctx-init --graph` for the large runtime graph artifact shipped in
+  `v1.0.15`. The installer now scans large `graph.json` files for required
+  node-link keys without parsing the whole graph, so first-time PyPI installs
+  can validate and install the released runtime graph.
+- Supersedes `v1.0.15` for public install flows because `v1.0.15` published
+  successfully but the public smoke exposed a runtime graph validation false
+  negative.
+
+## [1.0.15] - 2026-06-20
+
+### Added
+
+- Added modular graph and wiki pack manifests with immutable base packs,
+  overlay packs, tombstones, and compaction/promotion validation so normal
+  entity updates no longer require treating one monolithic graph/wiki tarball
+  as the only source of truth.
+- Added the SQLite graph-store fast path for dashboard/search/neighborhood
+  reads, plus queue-driven pack compaction and status reporting in the local
+  monitor.
+- Added Skillspector release artifacts and audit/remediation services so the
+  shipped catalog can surface stale, low-quality, or oversized skill records
+  with explicit evidence.
+
+### Fixed
+
+- Fixed the post-merge dashboard pack-compaction status typing so the full
+  package mypy gate passes on the modular graph release branch.
+
+## [1.0.14] - 2026-06-17
+
+### Fixed
+
+- Fixed the local dashboard `/catalog` and `/catalog/` routes so README and
+  docs catalog links open the searchable entity catalog instead of returning
+  404.
+- Fixed graph export/load compatibility with NetworkX versions that do not
+  accept the `edges=` keyword on `node_link_data()` and `node_link_graph()`,
+  while preserving ctx's canonical on-disk `edges` JSON key.
+
+## [1.0.13] - 2026-06-17
+
+### Fixed
+
+- Fixed custom/API/local model harness recommendations in runtime-only graph
+  installs by scoring harness page body text, including graph-connection
+  sections, instead of frontmatter alone.
+- Stopped conversational filler such as "compatible", "across", "own", and
+  "coding" from counting as hard harness fit requirements.
+
+## [1.0.12] - 2026-06-16
+
+### Added
+
+- Added first-class `ctx-skill-unload` and `ctx-agent-unload` console
+  scripts so skill and agent lifecycle cleanup has the same public CLI shape
+  as MCP uninstall flows.
+- Added browser A-Z dashboard coverage for Manage CRUD, Config save, Harness
+  Setup, Sessions, KPI, Runtime, graph/wiki/docs, live events, and mutation
+  security paths.
+
+### Changed
+
+- Made custom/API/local model harness recommendations fast enough for the
+  interactive wizard by using the harness-only catalog path before falling
+  back to the full graph.
+- Added Hugging Face to the dashboard Harness Setup provider list and carried
+  `--api-key-env` consistently through `ctx-init` and
+  `ctx-harness-install --recommend`.
+
+### Fixed
+
+- Fixed Windows UTF-8 BOM JSON parsing in repo scans so PowerShell-created
+  `package.json` files do not degrade stack detection.
+- Fixed dashboard Config saves so unchanged boolean defaults are not written
+  as accidental user overrides.
+- Suppressed the expected empty-graph warning in clean-host fast mode while
+  preserving warnings for real graph corruption.
 
 ## [1.0.11] - 2026-05-28
 
@@ -196,7 +323,7 @@ Format loosely follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 ### Fixed
 
 - Published the post-0.7.16 hardening fixes with release metadata that matches
-  the CI runner's collected test count.
+  the CI runner's test inventory count.
 
 ## [0.7.17] - 2026-05-09
 
@@ -261,7 +388,7 @@ Format loosely follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 - Kept the graph artifact CI check useful when GitHub LFS budget is
   exhausted by validating the committed LFS pointer and running full deep
   artifact validation locally before release.
-- Refreshed README and docs collected-test counts after the CI classifier
+- Refreshed README and docs test inventory counts after the CI classifier
   regression tests were added.
 
 ## [0.7.7] - 2026-05-05
@@ -276,7 +403,7 @@ Format loosely follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
   catalog matches through the same fit/provider gates.
 - Propagated incremental semantic top-K contamination to a fixed point so
   larger catalog updates do not preserve second-order stale neighbors.
-- Synced README and docs collected-test counts with the current suite.
+- Synced README and docs test inventory counts with the current suite.
 
 ## [0.7.6] - 2026-05-05
 
@@ -1608,6 +1735,14 @@ pass. Full test suite: **1316 passed, 2 skipped**.
 - 5 dead imports removed (`os`, `Mapping`, `timedelta` from
   `ctx_lifecycle`; `Path` from `intake_gate`, `intake_pipeline`).
 
+[1.0.19]: https://github.com/stevesolun/ctx/releases/tag/v1.0.19
+[1.0.18]: https://github.com/stevesolun/ctx/releases/tag/v1.0.18
+[1.0.17]: https://github.com/stevesolun/ctx/releases/tag/v1.0.17
+[1.0.16]: https://github.com/stevesolun/ctx/releases/tag/v1.0.16
+[1.0.15]: https://github.com/stevesolun/ctx/releases/tag/v1.0.15
+[1.0.14]: https://github.com/stevesolun/ctx/releases/tag/v1.0.14
+[1.0.13]: https://github.com/stevesolun/ctx/releases/tag/v1.0.13
+[1.0.12]: https://github.com/stevesolun/ctx/releases/tag/v1.0.12
 [1.0.11]: https://github.com/stevesolun/ctx/releases/tag/v1.0.11
 [1.0.10]: https://github.com/stevesolun/ctx/releases/tag/v1.0.10
 [1.0.9]: https://github.com/stevesolun/ctx/releases/tag/v1.0.9

CONTRIBUTING.md

@@ -26,6 +26,17 @@ pytest -q -m integration           # embedding precision/recall tests
 pytest --cov=src -q                # with coverage report
 ```
 
+## Documentation changes
+
+Public MkDocs nav pages are release-tracked in
+`docs/qa/feature-user-story-status.csv`. If you add, remove, or move a `.md`
+entry under `mkdocs.yml` `nav`, update the canonical feature tracker with the
+exact `docs/...md` `entrypoint_or_route` and run:
+
+```bash
+python -m pytest src/tests/test_feature_user_story_tracker.py -q
+```
+
 ## Code style
 
 Both **ruff** and **mypy** must pass before a PR is merged.

README.md

@@ -18,16 +18,23 @@ tags:
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
 [![Python 3.11+](https://img.shields.io/badge/Python-3.11+-green.svg)](https://python.org)
 [![PyPI](https://img.shields.io/pypi/v/claude-ctx.svg)](https://pypi.org/project/claude-ctx/)
-[![Tests](https://img.shields.io/badge/Tests-4043_collected-brightgreen.svg)](https://github.com/stevesolun/ctx/actions/workflows/test.yml)
-[![Graph](https://img.shields.io/badge/Graph-102%2C928_nodes_/_2.9M_edges-red.svg)](https://stevesolun.github.io/ctx/knowledge-graph/)
-[![Skills](https://img.shields.io/badge/Skills-91%2C464-blue.svg)](https://stevesolun.github.io/ctx/catalog/?type=skill)
+[![Tests](https://img.shields.io/badge/Tests-4400_inventory-brightgreen.svg)](https://github.com/stevesolun/ctx/actions/workflows/test.yml)
+[![Graph](https://img.shields.io/badge/Graph-79%2C958_nodes_/_1%2C778%2C069_edges-red.svg)](https://stevesolun.github.io/ctx/knowledge-graph/)
+[![Skills](https://img.shields.io/badge/Skills-68%2C494-blue.svg)](https://stevesolun.github.io/ctx/catalog/?type=skill)
 [![Agents](https://img.shields.io/badge/Agents-467-purple.svg)](https://stevesolun.github.io/ctx/catalog/?type=agent)
 [![MCPs](https://img.shields.io/badge/MCPs-10%2C790-pink.svg)](https://stevesolun.github.io/ctx/catalog/?type=mcp-server)
 [![Harnesses](https://img.shields.io/badge/Harnesses-207-orange.svg)](https://stevesolun.github.io/ctx/catalog/?type=harness)
 [![Docs](https://img.shields.io/badge/docs-MkDocs_Material-blue.svg)](https://stevesolun.github.io/ctx/)
 [![Repo views](https://hits.sh/github.com/stevesolun/ctx.svg?label=repo%20views)](https://hits.sh/github.com/stevesolun/ctx/)
 
-ctx watches what you are building, walks a **102,928-node** graph, and
+**ctx is not an Amazon-style catalog of skills, MCPs, agents, tools, or
+harnesses. It is a recommendation layer.** Point it at your organization's own
+tools, or use the pre-built graph, and ctx recommends the smallest useful bundle
+for the current development window. The goal is to load the right skills,
+agents, MCP servers, and optional harness at the right moment so hosted LLMs
+burn fewer tokens and local models waste less CPU/GPU work.
+
+ctx watches what you are building, walks a **79,958-node** graph, and
 recommends a small, top-scored bundle of skills, agents, and MCP servers for
 the current task. If you use your own local/API model instead of Claude Code,
 ctx has a separate harness setup flow: tell it the model and goal, review the
@@ -35,18 +42,37 @@ recommended harness, then install with dry-run/update/uninstall controls.
 
 Current shipped snapshot:
 
-- **91,464 skill entity pages**, with **89,465** hydrated installable `SKILL.md` bodies.
+- **68,494 skill entity pages**, with **67,024** hydrated installable `SKILL.md` bodies.
 - **467 agents**, **10,790 MCP servers**, and **207 harnesses**.
-- **2.9M graph edges** across semantic similarity, tags, slug tokens, source overlap, direct links, quality, usage, type affinity, and graph structure.
+- **1,778,069 graph edges** across semantic similarity, tags, slug tokens, source overlap, direct links, quality, usage, type affinity, and graph structure.
 - **28,612 long skill bodies** converted through the micro-skill gate instead of shipping raw long prompts.
 - Entity updates for skills, agents, MCPs, and harnesses print benefits/risks and skip replacement unless you explicitly approve the update.
 
 ## Why it exists
 
-- **Discovery** — with 91K+ skill pages, 460+ agents, 10K+ MCP servers, and 207 harnesses, you can't possibly know which exist or which apply to your current work.
+- **Discovery** — with 68,494 skill pages, 467 agents, 10,790 MCP servers, and 207 harnesses, you can't possibly know which exist or which apply to your current work.
 - **Context budget** — loading everything wastes tokens and degrades quality. You need the right 10–15 per session.
 - **Skill rot** — skills you installed months ago and never used are cluttering context. Stale ones should be flagged automatically.
 
+## Example user stories
+
+The canonical QA tracker is
+[`docs/qa/feature-user-story-status.csv`](docs/qa/feature-user-story-status.csv).
+The dashboard-specific tracker
+[`docs/qa/dashboard-user-story-status.csv`](docs/qa/dashboard-user-story-status.csv)
+is a supporting detail ledger; canonical status and release readiness stay in the
+feature tracker.
+Rows for public MkDocs pages use the exact `docs/...md` path from `mkdocs.yml`
+as `entrypoint_or_route`, so adding a nav page also means adding or updating
+the matching feature-tracker row.
+Examples from that tracker:
+
+| Tracker row | User story | Expected ctx behavior |
+| --- | --- | --- |
+| `CLI-002` | As a user I can ask ctx for current repo recommendations. | `ctx-recommend` returns a capped, graph-scored bundle of relevant skills, agents, and MCP servers from the shared recommendation engine. |
+| `CLI-026` | As a local/API model user I can get harness recommendations and install one. | `ctx-harness-install --dry-run` interviews model/goals/tools/privacy, recommends a fitting harness above threshold, or emits a no-fit custom harness PRD. |
+| `API-011` | As a dashboard user I can manually add, edit, or delete entities. | `/api/entity/upsert` and `/api/entity/delete` validate type, slug, and body, then queue safe graph/wiki updates instead of mutating blindly. |
+
 ## Install
 
 ```bash
@@ -81,7 +107,7 @@ ctx-init --graph --graph-install-mode full
 ```
 
 The full `wiki-graph.tar.gz` includes the shipped skill index,
-91,464 skill entity pages under `entities/skills/`, 89,465 hydrated
+68,494 skill entity pages under `entities/skills/`, 67,024 hydrated
 installable `SKILL.md` files under `converted/`,
 and 207 harness pages under
 `entities/harnesses/`.
@@ -109,6 +135,7 @@ ctx-skill-quality list     # four-signal quality score for every skill
 ctx-skill-quality explain python-patterns   # drill into a single skill
 ctx-skill-health dashboard # structural health + drift detection
 ctx-toolbox run --event pre-commit          # run a council on the current diff
+ctx-telemetry-export --dry-run --json       # inspect privacy-redacted telemetry spool
 ctx-monitor serve          # local dashboard: http://127.0.0.1:8765/
 ```
 

docs/catalog.md

@@ -44,10 +44,11 @@ It is public and always reachable. The full live catalog runs locally inside
   <p id="ctx-catalog-count" class="ctx-catalog-muted"></p>
 
   <div id="ctx-catalog-grid" class="ctx-catalog-grid">
+<!-- ctx-catalog:begin -->
     <article class="ctx-catalog-card" data-type="skill" data-search="skill prompt workflow testing code review frontend backend security research">
       <span class="ctx-catalog-pill">Skills</span>
       <h3>Skills</h3>
-      <p class="ctx-catalog-muted">91,464 entities</p>
+      <p class="ctx-catalog-muted">68,494 entities</p>
       <a class="md-button" href="./?type=skill">Filter tiles</a>
       <a class="md-button" href="../dashboard/#catalog-badge-links">Open full catalog locally</a>
     </article>
@@ -149,6 +150,7 @@ It is public and always reachable. The full live catalog runs locally inside
       <a class="md-button" href="./?type=harness&q=tool+access">Filter tiles</a>
       <a class="md-button" href="../dashboard/#catalog-badge-links">Open full catalog locally</a>
     </article>
+<!-- ctx-catalog:end -->
   </div>
 </div>
 

docs/dashboard.md

@@ -16,7 +16,8 @@ ctx-monitor serve --host 0.0.0.0 --port 8888  # LAN read-only with startup token
 Zero Python dependencies added by the dashboard. Everything runs on
 stdlib `http.server`, using daemon request threads so a live
 `/api/events.stream` client cannot block normal dashboard or JSON API
-requests. The graph page uses a built-in list renderer and does not load
+requests. The graph page uses a built-in dependency-free SVG neighborhood
+renderer with zoom, drag, hover details, and a list fallback. It does not load
 third-party JavaScript.
 
 ## Usage
@@ -31,6 +32,25 @@ Generic/API/local harnesses that call ctx-core validation tools write to
 the runtime lifecycle ledger. The dashboard exposes that ledger at
 `/runtime` and as JSON at `/api/runtime.json`.
 
+### Smoke-test the dashboard
+
+Use the repo smoke check after dashboard changes or before screenshots. It uses
+only stdlib HTTP calls against a running `ctx-monitor` instance and checks the
+core pages plus graph/wiki/catalog APIs.
+
+```bash
+ctx-monitor serve
+python scripts/dashboard_smoke.py --warm
+```
+
+To make latency regressions fail the command, add named thresholds:
+
+```bash
+python scripts/dashboard_smoke.py --warm \
+  --fail-on-slow graph-api-warm=1.0 \
+  --fail-on-slow kpi-warm=3.0
+```
+
 ### Check queue and artifact state - `/status`
 
 The status tab shows the durable wiki/graph maintenance queue and the
@@ -111,10 +131,12 @@ frontmatter values are visibly marked as truncated.
 
 ### Explore the knowledge graph — `/graph`
 
-The graph tab is a built-in list view over the dashboard-supported
-skill/agent/MCP/harness graph. Imported skills are normal `skill`
-nodes in the graph. Harness nodes are browsable and filterable here;
-install/update actions remain in `ctx-harness-install`.
+The graph tab is a dependency-free interactive SVG view over the
+dashboard-supported skill/agent/MCP/harness graph. Imported skills are normal
+`skill` nodes in the graph. Harness nodes are browsable and filterable here;
+install/update actions remain in `ctx-harness-install`. If the SVG renderer
+cannot initialize, the dashboard falls back to a list view over the same graph
+payload.
 When you arrive with no
 slug selected, the page shows:
 
@@ -127,9 +149,9 @@ slug selected, the page shows:
 - the graph list panel itself, which activates as soon as you pick a
   seed
 
-Inside the graph list view, entity pills identify the node type. The
-focus row has `depth=0` in the page data, and neighbor rows are filterable
-by entity type and shared tag/token text.
+Inside the graph view, entity pills identify the node type. The focus node has
+`depth=0` in the page data, and neighbor rows remain filterable by entity type
+and shared tag/token text.
 
 The JSON endpoint still includes blended graph edge weights, combining
 semantic similarity, explicit tag overlap, and slug-token overlap where
@@ -196,7 +218,7 @@ per-process monitor token injected into the rendered page.
 | `/wiki/<slug>?type=<entity>` | Dashboard-supported wiki entity page rendered: markdown body + full frontmatter table + grade banner + deep links to sidecar and graph-neighborhood views. The optional `type` query disambiguates duplicate slugs such as `langgraph`. |
 | `/graph` | **Graph explorer landing page** - node/edge count header, a "Popular seed slugs" block (18 highest-degree skill/agent/MCP/harness entities as clickable chips), search box for any skill/agent/MCP/harness slug, and the built-in graph list panel. Clicking a seed chip navigates to `/graph?slug=<slug>&type=<entity>`. |
 | `/graph?slug=<slug>&type=<entity>` | **Built-in** 1-hop neighborhood around the target skill/agent/MCP/harness slug. Entity pills identify skill, agent, MCP server, and harness rows. Tap any node to navigate to that entity's typed wiki page. Type and tag filters run client-side. |
-| `/manage` | Search, inspect, edit, delete, and manually import skill/agent/MCP/harness wiki entities through the same safe-name and mutation-token checks as live load/unload. |
+| `/manage` | Search, inspect, edit, delete, and manually import skill/agent/MCP/harness wiki entities through the same safe-name and mutation-token checks as live load/unload. Manual skill upserts run the required static SkillSpector gate before the wiki page is written or queued for graph refresh. |
 | `/harness` | Harness Setup wizard for non-Claude/custom API/local model users: collects model, goals, tool needs, safety constraints, and shows the harness recommendation/install path. |
 | `/docs` | Local repo docs rendered inside the dashboard with MkDocs-like tabs, sidebar table of contents, in-dashboard search, and source links. |
 | `/config` | Effective ctx config with defaults, required markers, field explanations, and editable user overrides where supported. |

docs/entity-onboarding.md

@@ -19,11 +19,14 @@ ctx-scan-repo --repo . --recommend
 ```
 
 If a persisted semantic vector index exists, that worker pass also runs a
-best-effort incremental attach into `graphify-out/entity-overlays.jsonl` so the
-new entity can connect to existing graph nodes without a full all-pairs
-semantic rebuild. The wiki page remains the source of truth; if incremental
-attach is skipped or fails, the worker still queues the normal incremental
-graph export job.
+best-effort incremental attach into `graphify-out/entity-overlays.jsonl` and,
+when active graph packs exist, writes a small graph overlay pack for the
+changed entity. If the vector index is missing, the worker can still write a
+node-only graph overlay pack and refresh `graph-store.sqlite3`, so local
+dashboard/search/recommendation reads see the merged base+overlay graph without
+a full all-pairs semantic rebuild. The wiki page remains the source of truth;
+only legacy installs without active graph packs fall back to the normal
+incremental graph export job.
 
 ## Updating the Graph and LLM Wiki
 
@@ -43,8 +46,9 @@ the update is treated like a release step.
    still changing.
 5. Drain the wiki queue for local runtime use:
    `ctx-wiki-worker --wiki ~/.claude/skill-wiki --limit 1`. This updates the
-   wiki index, attempts incremental ANN graph attach when a vector index exists,
-   and queues the normal incremental graph export.
+   wiki index, writes wiki overlay packs, attempts incremental ANN graph attach
+   when a vector index exists, writes graph overlay packs when active packs are
+   present, and queues a graph-store refresh so local reads see the merged view.
 6. Rebuild the curated wiki graph with `ctx-wiki-graphify` before shipping
    release artifacts or when you need a full graph/export reconciliation.
 7. Repack `graph/wiki-graph.tar.gz` through the artifact promotion path:
@@ -239,10 +243,13 @@ ctx-skill-add \
 What happens:
 
 1. The name is validated.
-2. Intake checks run against the markdown.
-3. The skill is copied into `~/.claude/skills/`.
-4. A wiki page is created under `entities/skills/`.
-5. The wiki index and log are updated.
+2. NVIDIA SkillSpector runs in static `--no-llm` mode by default; the add
+   fails unless the scan passes. Use `--no-security-scan` only for a deliberate
+   local exception.
+3. Intake checks run against the markdown.
+4. The skill is copied into `~/.claude/skills/`.
+5. A wiki page is created under `entities/skills/`.
+6. The wiki index and log are updated.
 
 ## Add an Agent
 

docs/huggingface-publish.md

@@ -1,8 +1,8 @@
 # Hugging Face Publish
 
-ctx publishes the GitHub repository as the public Hugging Face dataset
+ctx publishes the GitHub repository as the public Hugging Face dataset repo
 [`Stevesolun/ctx`](https://huggingface.co/datasets/Stevesolun/ctx). The
-dataset is a clean `git ls-files` snapshot, including the shipped graph
+dataset repo is a clean `git ls-files` snapshot, including the shipped graph
 tarball and catalog artifacts, not local review reports or ignored caches.
 
 ## What gets uploaded

docs/index.md

@@ -7,7 +7,14 @@ hide:
 
 [![Repo views](https://hits.sh/github.com/stevesolun/ctx.svg?label=repo%20views)](https://hits.sh/github.com/stevesolun/ctx/)
 
-Watches what you develop, walks a knowledge graph of **91,464 skill pages, 467 agents, 10,790 MCP servers, and 207 cataloged harnesses**, and recommends the
+**ctx is not an Amazon-style catalog of skills, MCPs, agents, tools, or
+harnesses. It is a recommendation layer.** Point it at your organization's own
+tools, or use the pre-built graph, and ctx recommends the smallest useful bundle
+for the current development window. The goal is to load the right skills,
+agents, MCP servers, and optional harness at the right moment so hosted LLMs
+burn fewer tokens and local models waste less CPU/GPU work.
+
+Watches what you develop, walks a knowledge graph of **68,494 skill pages, 467 agents, 10,790 MCP servers, and 207 cataloged harnesses**, and recommends the
 right execution bundle on the fly. The live execution bundle is skills,
 agents, and MCP servers only; custom/API/local model users get a separate
 harness recommendation based on model choice and task goal. You decide
@@ -48,15 +55,17 @@ memory that gets smarter every session.
     check, unit coverage, canaries, package build, twine, docs, graph
     validation, browser, and similarity checks as needed. Use `--profile full`
     before release work to force the source/package gates even for docs-only or
-    graph-only changes.
+    graph-only changes. Public MkDocs nav pages are release-tracked: when
+    `mkdocs.yml` adds, removes, or moves a `.md` page, update
+    `docs/qa/feature-user-story-status.csv` with the exact `docs/...md`
+    `entrypoint_or_route`.
 
 ## Why this exists
 
 Claude Code skills, agents, MCP servers, and model harness profiles are
 powerful, but at scale they become unmanageable:
 
-- **Discovery problem** — with 91K+ skill pages, 460+ agents, 10,000+
-  MCP servers, and 207 harnesses, how do you know which
+- **Discovery problem** — with 68,494 skill pages, 467 agents, 10,790 MCP servers, and 207 harnesses, how do you know which
   ones exist and which are relevant to your current project?
 - **Context budget** — loading every installable entity wastes tokens and
   degrades quality. You need exactly the right skills, agents, and MCP
@@ -90,14 +99,14 @@ graph-based discovery:
 
 - A Karpathy 3-layer wiki at `~/.claude/skill-wiki/` is the single source
   of truth.
-- **102,928 graph nodes** for the shipped skill/agent/MCP/harness
-  inventory, including 91,464 skill pages
+- **79,958 graph nodes** for the shipped skill/agent/MCP/harness
+  inventory, including 68,494 skill pages
   and 207 harness pages under `entities/harnesses/`.
   Each page tracks tags, status, provenance, and usage where it applies.
-- A **knowledge graph** (102,928 nodes, 2,913,960 edges) built from a
-  13,463-node core plus 89,465 body-backed skill nodes.
+- A **knowledge graph** (79,958 nodes, 1,778,069 edges) built from a
+  12,934-node core plus 67,024 body-backed skill nodes.
   The graph has 52 Louvain communities and blends semantic cosine,
-  tag overlap, and slug-token overlap; 89,465 skill bodies are
+  tag overlap, and slug-token overlap; 67,024 skill bodies are
   shipped as installable `SKILL.md` files. Entries over the configured line
   threshold are converted to gated micro-skill orchestrators. Full source
   bodies were used for semantic graphing before packaging; `SKILL.md.original`
@@ -131,8 +140,8 @@ ones are flagged. New ones self-ingest.
 
     ---
 
-    102,928 shipped graph nodes: 13,463 curated skill/agent/MCP/harness nodes plus 89,465 body-backed skill nodes. The graph has
-    2,913,960 weighted edges and 52 Louvain communities.
+    79,958 shipped graph nodes: 12,934 curated skill/agent/MCP/harness nodes plus 67,024 body-backed skill nodes. The graph has
+    1,778,069 weighted edges and 52 Louvain communities.
     Ships pre-built in `graph/wiki-graph.tar.gz` and powers the
     graph-aware recommendations + the pre-ship `ctx-dedup-check` gate.
 
@@ -197,18 +206,19 @@ ones are flagged. New ones self-ingest.
     [Memory anchoring](memory-anchor.md) ·
     [Lifecycle dashboard](skill-lifecycle-and-dashboard.md)
 
--   **Releases**
+-   **Source snapshot**
 
     ---
 
-    **v1.0.11** — MIT, CI-matrixed (Ubuntu 3.12 plus Windows/macOS 3.11/3.12),
-    4,043 tests collected. Ships console scripts including `ctx-init`,
+    Current main is **v1.0.20** — MIT, CI-matrixed (Ubuntu 3.12 plus Windows/macOS 3.11/3.12),
+    4,400 test inventory. Adds enterprise OpenTelemetry-ready telemetry and
+    ships console scripts including `ctx-init`,
     `ctx-monitor` (local dashboard with graph + wiki + load/unload for
     skills, agents, and MCP servers, plus Harness Setup for user-owned LLMs),
     `ctx-incremental-attach`, `ctx-incremental-shadow`, `ctx-dedup-check`
     (pre-ship near-duplicate gate), and
     `ctx-tag-backfill` (entity hygiene), plus a fast runtime graph artifact
-    and the full ~439 MiB wiki tarball with **102,928 nodes / 2,913,960 edges / 52 Louvain communities**.
+    and the full ~282 MiB wiki tarball with **79,958 nodes / 1,778,069 edges / 52 Louvain communities**.
 
     [:octicons-arrow-right-24: CHANGELOG](https://github.com/stevesolun/ctx/blob/main/CHANGELOG.md) ·
     [Repository](https://github.com/stevesolun/ctx)

docs/knowledge-graph.md

@@ -13,9 +13,9 @@ agents, and MCP servers.
 ## What's in it
 
 Authoritative numbers from the shipped tarball. The curated-core snapshot
-is **13,463 nodes** (1,999 curated skills + 467 agents + 10,790 MCP servers + 207 harnesses). Harness pages under `entities/harnesses/` are ingested into
+is **12,934 nodes** (1,470 curated skills + 467 agents + 10,790 MCP servers + 207 harnesses). Harness pages under `entities/harnesses/` are ingested into
 local rebuilds and the separate harness recommendation path. The
-tarball also carries **91,464 skill pages**; **89,465**
+tarball also carries **68,494 skill pages**; **67,024**
 skill bodies are hydrated as installable `SKILL.md` files under
 `converted/`; the **28,612** entries over the configured line
 limit were converted to gated micro-skill orchestrators. Full original bodies
@@ -25,19 +25,19 @@ are omitted from the shipped tarball.
 
 | | Count |
 |---|---:|
-| Total nodes | **102,928** |
-| Curated core nodes | **13,463** (1,999 skills + 467 agents + 10,790 MCP servers + 207 harnesses) |
-| Body-backed skill nodes | **89,465** hydrated installable skill entries |
-| Total edges | **2,913,960** |
-| Hydrated skill incident edges | **2,605,721** |
-| Hydrated skill semantic incident edges | **1,500,648** |
+| Total nodes | **79,958** |
+| Curated core nodes | **12,934** (1,470 skills + 467 agents + 10,790 MCP servers + 207 harnesses) |
+| Body-backed skill nodes | **67,024** hydrated installable skill entries |
+| Total edges | **1,778,069** |
+| Hydrated skill incident edges | **1,516,298** |
+| Hydrated skill semantic incident edges | **911,922** |
 | Communities | **52** (Louvain) |
-| Edge sources (overlap-deduped) | semantic 1,683,193 - tag 897,784 - token 433,245 |
-| Cross-type edges (skill <-> agent) | ~66,799 |
-| Cross-type edges (skill <-> MCP) | ~41,521 |
+| Edge sources (overlap-deduped) | semantic 1,088,763 - tag 474,837 - token 280,275 |
+| Cross-type edges (skill <-> agent) | ~52,382 |
+| Cross-type edges (skill <-> MCP) | ~30,295 |
 | Cross-type edges (agent <-> MCP) | ~229 |
-| Harness edges | **6,576** |
-| Shipped skill index | **89,465** observed body-backed skill entries |
+| Harness edges | **5,063** |
+| Shipped skill index | **67,024** observed body-backed skill entries |
 
 ## Install
 
@@ -148,8 +148,8 @@ quality clusters for the recommendation use case.
 ctx-monitor serve              # http://127.0.0.1:8765
 ```
 
-Then open `/graph?slug=<entity-slug>&type=<entity-type>` for a
-cytoscape neighborhood view, or
+Then open `/graph?slug=<entity-slug>&type=<entity-type>` for the
+dashboard's interactive SVG neighborhood view, or
 `/api/graph/<slug>.json?type=<entity-type>&hops=1&limit=40` for the
 dashboard-shaped JSON. The `type` query is optional for unique slugs and
 recommended for duplicate slugs such as `langgraph`. See the
@@ -168,7 +168,7 @@ raw = json.loads(
 edges_key = "links" if "links" in raw else "edges"
 G = node_link_graph(raw, edges=edges_key)
 
-# 102,928 nodes, 2,913,960 edges
+# 79,958 nodes, 1,778,069 edges
 print(G.number_of_nodes(), G.number_of_edges())
 
 # Find entities related to 'fastapi-pro' by edge weight
@@ -217,6 +217,101 @@ This split is intentional: execution surfaces need identical ranking and a
 small top-K, while harness choice changes the model runtime itself and belongs
 in an explicit onboarding/install flow.
 
+## Modular graph and wiki packs
+
+ctx is moving the graph and LLM-wiki from "one huge tarball is the mutable
+truth" to this operational model:
+
+```text
+immutable base graph pack
+  + small graph overlay packs
+  + tombstones for deletes
+  + immutable base wiki pack
+  + small wiki overlay packs
+  -> merged reader for dashboard, search, recommendations, and repair tools
+```
+
+The user-facing behavior is intended to stay the same: recommendations,
+dashboard graph views, wiki pages, and harness setup still read the merged
+graph/wiki as one catalog. The difference is how updates are stored. Adding or
+updating one skill, agent, MCP server, or harness can write a small overlay pack
+instead of forcing a full graph and wiki rebuild.
+
+This makes normal updates faster and safer:
+
+- **Faster adds/updates** - the worker writes a page overlay and, when the
+  vector index exists, attaches ANN-based graph edges for the changed entity.
+- **Efficient deletes** - deletes become tombstones in graph/wiki overlays, so
+  removed entities disappear from merged reads without rewriting the base pack.
+- **Crash isolation** - overlay packs and compaction manifests are written
+  atomically; a failed update does not corrupt the base snapshot.
+- **Same recommendation contract** - merged graph reads preserve edge metadata,
+  scores, provenance, and tombstones before resolver/dashboard code sees the
+  graph.
+
+Pack directories live inside the installed wiki:
+
+```text
+~/.claude/skill-wiki/
+  graphify-out/packs/base-<export-id>/
+  graphify-out/packs/overlay-<id>/
+  wiki-packs/base-<export-id>/
+  wiki-packs/overlay-<id>/
+```
+
+Overlay packs are the normal local-update path. Full rebuilds are still needed
+when you intentionally refresh the release artifact, change global scoring
+configuration, rebuild communities, or compact a long chain of overlays into a
+new base snapshot.
+
+To stage a coordinated graph+wiki compaction without mutating the active wiki:
+
+```bash
+ctx-pack-compact compact \
+  --wiki-path ~/.claude/skill-wiki \
+  --base-export-id <new-export-id> \
+  --staging-dir /tmp/ctx-pack-stage \
+  --json
+```
+
+The staging directory contains a top-level `pack-compaction-manifest.json` plus
+staged graph and wiki base packs. Promotion validates the top-level manifest,
+graph pack manifest, wiki pack manifest, checksums, matching export IDs, and
+graph/wiki entity consistency before replacing active packs:
+
+```bash
+ctx-pack-compact validate \
+  --staged-graph-packs-dir /tmp/ctx-pack-stage/graph-packs \
+  --staged-wiki-packs-dir /tmp/ctx-pack-stage/wiki-packs \
+  --require-compaction-manifest \
+  --json
+```
+
+```bash
+ctx-pack-compact promote \
+  --wiki-path ~/.claude/skill-wiki \
+  --staged-graph-packs-dir /tmp/ctx-pack-stage/graph-packs \
+  --staged-wiki-packs-dir /tmp/ctx-pack-stage/wiki-packs \
+  --json
+```
+
+Promotion refreshes the SQLite dashboard/recommendation graph store by default.
+Use `--graph-store-db <path>` to refresh a non-default store, or
+`--no-graph-store-refresh` only when you plan to rebuild it separately:
+
+```bash
+ctx-pack-compact validate \
+  --wiki-path ~/.claude/skill-wiki \
+  --json
+
+ctx-graph-store build \
+  --graph-dir ~/.claude/skill-wiki/graphify-out \
+  --db ~/.claude/skill-wiki/graphify-out/graph-store.sqlite3
+
+ctx-graph-store validate \
+  --db ~/.claude/skill-wiki/graphify-out/graph-store.sqlite3
+```
+
 ### LLM-wiki design references
 
 ctx follows Karpathy's LLM-wiki pattern. We also reviewed
@@ -238,9 +333,10 @@ The `entity-upsert` worker path validates the queued page hash, updates the
 wiki index, and, when a persisted semantic vector index exists, runs a
 best-effort ANN attach into `graphify-out/entity-overlays.jsonl`. That overlay
 lets the runtime resolver connect a new or updated entity to existing graph
-neighbors without recomputing global all-pairs similarity. The worker still
-queues the normal incremental `graph-export` job, and the entity markdown page
-remains the source of truth.
+neighbors without recomputing global all-pairs similarity. When modular wiki
+packs exist, the same write is mirrored into a wiki overlay pack. The worker
+also queues a graph-store refresh so dashboard and resolver reads see the merged
+view. The entity markdown page or wiki page overlay remains the source of truth.
 
 For manual review or debugging:
 
@@ -316,9 +412,9 @@ This page is intentionally current-state only. Older graph sizes made the public
 page look stale even when the headline table was correct, so historical refresh
 notes live in `CHANGELOG.md` instead of being repeated here.
 
-The shipped artifact currently records **102,928 nodes**, **2,913,960 edges**,
-**52 Louvain communities**, **1,683,193 semantic edges**, **897,784 tag edges**,
-and **433,245 slug-token edges**. The current build is fully reproducible from
+The shipped artifact currently records **79,958 nodes**, **1,778,069 edges**,
+**52 Louvain communities**, **1,088,763 semantic edges**, **474,837 tag edges**,
+and **280,275 slug-token edges**. The current build is fully reproducible from
 the wiki content and the checked-in graph build configuration.
 
 ## Pre-ship gates
@@ -338,3 +434,9 @@ review reports and never auto-modify the inventory.
   frontmatter and proposes a backfill drawn from slug tokens, body
   keywords, and the existing tag vocabulary. Report-only by default;
   pass `--apply` to write. Backfills are additive only.
+- **`ctx-skillspector-audit`** — runs a static `--no-llm` check over
+  shipped skill bodies with
+  [NVIDIA SkillSpector](https://github.com/NVIDIA/SkillSpector), writes
+  `graph/skillspector-audit.jsonl.gz`, and stamps skill entity pages in the
+  full wiki artifact. This is a ctx-run check, not NVIDIA endorsement or
+  certification.

docs/marketplace-registry.md

@@ -44,7 +44,7 @@ still require an explicit review if replacement content is proposed.
 ```yaml
 name: shipped-skills
 type: shipped-index
-shipped_entries: 89465
+shipped_entries: 67024
 local_index: graph/<skill-index>.json.gz
 hydrated_wiki: external-catalogs/<source>/catalog.json
 refresh: on-demand

docs/qa/dashboard-user-story-status.csv

@@ -0,0 +1,48 @@
+dashboard_id,surface,page_or_api,route_or_control,source_evidence,user_story,expected_behavior,setup_preconditions,test_command_or_steps,status,first_test_result,error_id,error_summary,fix_status,retest_result,last_verified_at,notes
+DASH-PAGE-001,Dashboard Page,Home,/,src/ctx/monitor/pages/home.py,As a dashboard user I can open the monitor home page,Home renders current graph stats loaded counts quick actions and health summaries without blocking on full graph parsing,ctx-monitor running,Open / and inspect cards links and number formatting,Tested Pass,"PASS: live Playwright page probe opened /, found expected page markers, and detected no traceback or server-error text; dashboard_smoke also returned HTTP 200.",,,,,2026-06-25,Deeper controls are tracked in dedicated function/API/mutation rows.
+DASH-PAGE-002,Dashboard Page,Loaded,/loaded,src/ctx/monitor/pages/loaded.py,As a dashboard user I can see currently loaded skills agents and MCPs,Loaded page renders active entity state and exposes safe load or unload actions where allowed,ctx-monitor running with manifest data,Open /loaded and verify cards pagination and actions,Tested Pass,"PASS: live Playwright page probe opened /loaded, found expected page markers, and detected no traceback or server-error text; dashboard_smoke also returned HTTP 200.",,,,,2026-06-25,Deeper controls are tracked in dedicated function/API/mutation rows.
+DASH-PAGE-003,Dashboard Page,Skills,/skills,src/ctx/monitor/pages/skills.py,As a dashboard user I can browse skill and sidecar cards,Skills page supports bounded cards filters pagination grades and wiki links without rendering thousands of cards at once,ctx-monitor running with sidecars,Open /skills and verify search filters pagination and cards,Tested Pass,"PASS: live Playwright page probe opened /skills, found expected page markers, and detected no traceback or server-error text; dashboard_smoke also returned HTTP 200.",,,,,2026-06-25,Deeper controls are tracked in dedicated function/API/mutation rows.
+DASH-PAGE-004,Dashboard Page,SkillSpector,/skillspector,src/ctx/monitor/pages/skillspector.py,As a dashboard user I can review SkillSpector findings,SkillSpector page renders audit records severity filters and remediation context from the audit service,ctx-monitor running with audit data,Open /skillspector and verify filters counts and empty state,Tested Pass,"PASS: live Playwright page probe opened /skillspector, found expected page markers, and detected no traceback or server-error text; dashboard_smoke also returned HTTP 200.",,,,,2026-06-25,Deeper controls are tracked in dedicated function/API/mutation rows.
+DASH-PAGE-005,Dashboard Page,Wiki,/wiki,src/ctx/monitor/pages/wiki.py,As a dashboard user I can browse wiki entities,Wiki page shows searchable skill agent MCP and harness tiles with type filters and entity links,ctx-monitor running with wiki data,Open /wiki and validate search filters tiles and links,Tested Pass,"PASS: live Playwright page probe opened /wiki, found expected page markers, and detected no traceback or server-error text; dashboard_smoke also returned HTTP 200.",,,,,2026-06-25,Deeper controls are tracked in dedicated function/API/mutation rows.
+DASH-PAGE-006,Dashboard Page,Graph,/graph,src/ctx/monitor/pages/graph.py,As a dashboard user I can explore the knowledge graph,Graph page shows correct top-line counts live slug search interactive neighborhood filters and readable relationship details,ctx-monitor running with graph artifact,Open /graph and test focus search graph render filters click hover double click and match range,Tested Pass,"PASS: live Playwright page probe opened /graph, found expected page markers, and detected no traceback or server-error text; dashboard_smoke also returned HTTP 200.",,,,,2026-06-25,Deeper controls are tracked in dedicated function/API/mutation rows.
+DASH-PAGE-007,Dashboard Page,Manage,/manage,src/ctx/monitor/pages/manage.py,As a dashboard user I can manage entities,Manage page supports search inspect edit delete and manual import flows guarded by mutation tokens,ctx-monitor running with mutation token,Open /manage and validate search edit delete and import UI without unsafe mutation,Tested Pass,"PASS: live Playwright page probe opened /manage, found expected page markers, and detected no traceback or server-error text; dashboard_smoke also returned HTTP 200.",,,,,2026-06-25,Deeper controls are tracked in dedicated function/API/mutation rows.
+DASH-PAGE-008,Dashboard Page,Harness Setup,/harness,src/ctx/monitor/pages/harness.py,As a custom model user I can run harness setup from the dashboard,Harness Setup interviews model provider goal runtime tools privacy and presents fit or no-fit guidance,ctx-monitor running with harness catalog,Open /harness and test wizard fields validation and dry-run recommendation,Tested Pass,"PASS: live Playwright page probe opened /harness, found expected page markers, and detected no traceback or server-error text; dashboard_smoke also returned HTTP 200.",,,,,2026-06-25,Deeper controls are tracked in dedicated function/API/mutation rows.
+DASH-PAGE-009,Dashboard Page,Docs,/docs,src/ctx/monitor/pages/docs.py,As a dashboard user I can read repo docs inside the monitor,Docs page renders markdown as readable docs with tabs sidebar table of contents and local dashboard search behavior,ctx-monitor running,Open /docs and verify tabs TOC hierarchy search and markdown rendering,Tested Pass,"PASS: live Playwright page probe opened /docs, found expected page markers, and detected no traceback or server-error text; dashboard_smoke also returned HTTP 200.",,,,,2026-06-25,Deeper controls are tracked in dedicated function/API/mutation rows.
+DASH-PAGE-010,Dashboard Page,Config,/config,src/ctx/monitor/pages/config.py,As a dashboard user I can inspect and edit ctx configuration,Config page shows required settings descriptions examples defaults and validates saves or clears through the config API,ctx-monitor running with mutation token,Open /config and validate required fields defaults save clear and error states,Tested Pass,"PASS: live Playwright page probe opened /config, found expected page markers, and detected no traceback or server-error text; dashboard_smoke also returned HTTP 200.",,,,,2026-06-25,Deeper controls are tracked in dedicated function/API/mutation rows.
+DASH-PAGE-011,Dashboard Page,Status,/status,src/ctx/monitor/pages/ops.py,As a dashboard user I can inspect system status,Status page shows graph wiki config backup and queue health with actionable error text,ctx-monitor running,Open /status and verify status sections and stale artifact messages,Tested Pass,"PASS: live Playwright page probe opened /status, found expected page markers, and detected no traceback or server-error text; dashboard_smoke also returned HTTP 200.",,,,,2026-06-25,Deeper controls are tracked in dedicated function/API/mutation rows.
+DASH-PAGE-012,Dashboard Page,KPI,/kpi,src/ctx/monitor/pages/ops.py,As a dashboard user I can inspect dashboard KPIs,KPI page shows usage quality load and recommendation metrics with readable number formatting,ctx-monitor running,Open /kpi and verify metric cards charts and empty states,Tested Pass,"PASS: live Playwright page probe opened /kpi, found expected page markers, and detected no traceback or server-error text; dashboard_smoke also returned HTTP 200.",,,,,2026-06-25,Deeper controls are tracked in dedicated function/API/mutation rows.
+DASH-PAGE-013,Dashboard Page,Runtime,/runtime,src/ctx/monitor/pages/ops.py,As a dashboard user I can inspect runtime state,Runtime page shows process paths caches graph status and current monitor environment without secrets,ctx-monitor running,Open /runtime and verify no secrets plus useful cache status,Tested Pass,"PASS: live Playwright page probe opened /runtime, found expected page markers, and detected no traceback or server-error text; dashboard_smoke also returned HTTP 200.",,,,,2026-06-25,Deeper controls are tracked in dedicated function/API/mutation rows.
+DASH-PAGE-014,Dashboard Page,Sessions,/sessions,src/ctx/monitor/pages/activity.py,As a dashboard user I can browse ctx sessions,Sessions page lists sessions links details and handles empty history cleanly,ctx-monitor running with or without sessions,Open /sessions and verify list empty state and detail links,Tested Pass,"PASS: live Playwright page probe opened /sessions, found expected page markers, and detected no traceback or server-error text; dashboard_smoke also returned HTTP 200.",,,,,2026-06-25,Deeper controls are tracked in dedicated function/API/mutation rows.
+DASH-PAGE-015,Dashboard Page,Logs,/logs,src/ctx/monitor/pages/activity.py,As a dashboard user I can inspect audit logs,Logs page tails audit JSONL entries and handles missing logs without a blank page,ctx-monitor running,Open /logs and verify log rows empty state and formatting,Tested Pass,"PASS: live Playwright page probe opened /logs, found expected page markers, and detected no traceback or server-error text; dashboard_smoke also returned HTTP 200.",,,,,2026-06-25,Deeper controls are tracked in dedicated function/API/mutation rows.
+DASH-PAGE-016,Dashboard Page,Live Events,/events,src/ctx/monitor/pages/activity.py,As a dashboard user I can watch live events,Live page connects to server-sent events and shows either audit events or a clear waiting state,ctx-monitor running,Open /events and verify SSE connection and empty state,Retested Pass,FAIL: /api/events.stream did not send initial bytes within 10 seconds so the Live page could remain blank.,,,,PASS: /events returned HTTP 200 and /api/events.stream returned : connected promptly after the SSE fix.,2026-06-25,
+DASH-PAGE-017,Dashboard Page,Live Alias,/live,src/ctx/monitor/routes.py,As a dashboard user I can use the legacy live route,The /live alias renders the same live events experience as /events,ctx-monitor running,Open /live and compare with /events,Retested Pass,PASS: /live alias returned the Live events page marker and shares the fixed SSE stream behavior.,,,,PASS: /live returned HTTP 200 and shares the fixed SSE stream behavior.,2026-06-25,
+DASH-PAGE-018,Dashboard Page,Catalog,/catalog,src/ctx/monitor/routes.py,As a dashboard user I can open a local catalog route,The local catalog route resolves to the wiki index and supports type and query filters instead of returning 404,ctx-monitor running,Open /catalog?type=agent&q=review and verify tiles/search,Tested Pass,PASS: /catalog?type=agent&q=review returned 200 and rendered the local catalog via the wiki index route.,,,,,2026-06-25,
+DASH-PAGE-019,Dashboard Page,Catalog Slash,/catalog/,src/ctx/monitor/routes.py,As a dashboard user I can open the slash catalog route,The /catalog/ route behaves like /catalog and does not break badge or copied links,ctx-monitor running,Open /catalog/?type=harness and verify result,Tested Pass,PASS: /catalog/?type=harness returned 200 and rendered the local catalog via the wiki index route.,,,,,2026-06-25,
+DASH-PAGE-020,Dashboard Page,Session Detail,/session/<session_id>,src/ctx/monitor/routes.py,As a dashboard user I can inspect a session detail page,Session detail opens valid session IDs and gives a safe not-found page for missing sessions,ctx-monitor running with session fixture,Open /session/<session_id> and invalid session path,Tested Pass,PASS: /session/<session_id> route returned 200 for an observed session detail URL and did not crash.,,,,,2026-06-25,
+DASH-PAGE-021,Dashboard Page,Legacy Skill Detail,/skill/<slug>,src/ctx/monitor/routes.py,As a dashboard user I can open legacy skill detail links,Legacy /skill/<slug> links resolve safely to entity detail information or a useful not-found page,ctx-monitor running,Open /skill/github and invalid slug path,Tested Pass,PASS: /skill/github returned 200 and rendered a legacy skill detail page.,,,,,2026-06-25,
+DASH-PAGE-022,Dashboard Page,Wiki Entity Detail,/wiki/<slug>,src/ctx/monitor/pages/wiki_entity.py,As a dashboard user I can inspect an entity detail page,Entity detail shows overview subgraph quality drilldown frontmatter and rendered wiki body in tabs,ctx-monitor running with wiki data,Open /wiki/github?type=mcp-server and verify tabs subgraph quality and body,Tested Pass,PASS: /wiki/github?type=mcp-server returned 200 and rendered the github entity detail page.,,,,,2026-06-25,
+DASH-NUM-001,Dashboard Number,Graph top-line counts,/graph header,src/ctx/monitor/pages/graph.py and graph/wiki-graph-stats.json,As a dashboard user I see graph counts that match shipped artifacts,/graph displays nodes and edges from the authoritative graph artifact stats or dashboard index,ctx-monitor running and graph artifacts present,Compare /graph header with graph/wiki-graph-stats.json and update_repo_stats.read_graph_stats,Tested Pass,"Observed /graph shows 79,958 nodes and 1,778,069 edges; graph/wiki-graph-stats.json and update_repo_stats.read_graph_stats report the same counts.",,,,,2026-06-25,This answers the current dashboard count question.
+DASH-NUM-002,Dashboard Number,Home graph stats,/ home graph card,src/ctx/monitor/pages/home.py,As a dashboard user I see consistent graph counts on Home,Home graph card uses the same graph stats source and formats numbers with thousands separators,ctx-monitor running,Compare / home graph card with DASH-NUM-001,Tested Pass,"PASS: live Playwright home probe found 79,958 and 1,778,069 on /, matching DASH-NUM-001 with thousands separators.",,,,,2026-06-25,
+DASH-NUM-003,Dashboard Number,API graph stats,/api/status.json and /api/runtime.json,src/ctx/monitor/api/readonly.py,As a dashboard client I can read graph status from APIs,Status and runtime APIs expose graph availability and counts consistently with page displays,ctx-monitor running,GET status and runtime APIs and compare graph count fields,Retested Pass,"FAIL: /api/status.json exposed local graph_store counts without also exposing the shipped graph artifact counts, which made 79,960 / 941,901 appear beside the canonical 79,958 / 1,778,069 graph count.",DASH-UX-002,Status API/page did not show authoritative shipped graph stats beside local graph-store stats.,Fixed by adding published wiki-graph-stats counts to /api/status.json artifacts.wiki_graph_tar and rendering them as published graph counts on /status.,"PASS: /api/status.json artifacts.wiki_graph_tar.counts reports 79,958 nodes and 1,778,069 edges; /status renders published graph: 79,958 nodes, 1,778,069 edges and labels graph-store as local store.",2026-06-25,
+DASH-GRAPH-001,Dashboard Function,Graph live search,#focus and #graph-live-results,src/ctx/monitor/pages/graph.py and graph_client.py,As a dashboard user I get live graph search suggestions while typing,Typing a partial slug updates suggestions without a page reload and supports loose matching,ctx-monitor running,Type brainstorm or github into /graph focus input and verify suggestions,Tested Pass,PASS: live Playwright graph probe typed brainstorm and graph-live-results returned matching entity suggestions without reload.,,,,,2026-06-25,
+DASH-GRAPH-002,Dashboard Function,Graph interaction,node click hover double click,src/ctx/monitor/pages/graph_client.py,As a dashboard user I can interact with the graph directly,Hover shows useful node or edge info click highlights and focuses a node and double click returns to prior graph,ctx-monitor running with graph data,Open /graph?slug=github&type=skill and test hover click double-click,Retested Pass,FAIL: live Playwright graph probe showed double-click could still allow a pending single-click drill to overwrite the intended return graph.,DASH-UX-003,Graph double-click back raced with pending node-drill load.,Fixed by handling second-click events as back actions and cancelling stale graph loads with a load sequence guard.,"PASS: live Playwright graph probe selected a node, double-clicked, and returned focus to github; focused browser regression uses real Playwright dblclick.",2026-06-25,
+DASH-GRAPH-003,Dashboard Function,Graph filters,type tag match range histogram,src/ctx/monitor/pages/graph.py and graph_client.py,As a dashboard user I can narrow a noisy neighborhood,Type filters tag filter match range slider and histogram update visible nodes and counts without server reload,ctx-monitor running with graph data,Open /graph and test type checkboxes tag filter range and histogram bars,Tested Pass,PASS: live Playwright graph probe found 10 histogram bars; clicking a bar changed the match window result from 20 visible to 1 visible.,,,,,2026-06-25,
+DASH-API-001,Dashboard API,Sessions API,/api/sessions.json,src/ctx/monitor/api/readonly.py,As a dashboard client I can fetch session summaries,API returns JSON session rows and safe empty state data,ctx-monitor running,GET /api/sessions.json and validate JSON shape,Tested Pass,PASS: /api/sessions.json returned HTTP 200 and a JSON list of session rows in 0.328s.,,,,,2026-06-25,
+DASH-API-002,Dashboard API,Manifest API,/api/manifest.json,src/ctx/monitor/api/readonly.py,As a dashboard client I can fetch loaded manifest data,API returns loaded skills agents and MCP metadata without leaking secrets,ctx-monitor running,GET /api/manifest.json and validate JSON shape,Tested Pass,PASS: /api/manifest.json returned HTTP 200 JSON with load unload and warnings keys.,,,,,2026-06-25,
+DASH-API-003,Dashboard API,Status API,/api/status.json,src/ctx/monitor/api/readonly.py,As a dashboard client I can fetch health status,API returns dashboard health graph config and artifact status as JSON,ctx-monitor running,GET /api/status.json and validate JSON shape,Tested Pass,PASS: /api/status.json returned HTTP 200 JSON with queue and artifacts keys.,,,,,2026-06-25,
+DASH-API-004,Dashboard API,KPI API,/api/kpi.json,src/ctx/monitor/api/readonly.py,As a dashboard client I can fetch KPI data,API returns metric payloads that match the KPI page,ctx-monitor running,GET /api/kpi.json and compare with page expectations,Tested Pass,PASS: /api/kpi.json returned HTTP 200 JSON with generated_at total and grade summary keys.,,,,,2026-06-25,
+DASH-API-005,Dashboard API,Grades API,/api/grades.json,src/ctx/monitor/api/readonly.py,As a dashboard client I can fetch grade summaries,API returns quality grade summaries for skills agents MCPs and harnesses,ctx-monitor running,GET /api/grades.json and validate JSON shape,Tested Pass,PASS: /api/grades.json returned HTTP 200 JSON with grades and total keys.,,,,,2026-06-25,
+DASH-API-006,Dashboard API,Sidecars API,/api/sidecars.json,src/ctx/monitor/api/readonly.py,As a dashboard client I can fetch searchable card data,API supports q type grade floor and limit filters with bounded output,ctx-monitor running,GET /api/sidecars.json?q=review&type=agent&limit=5,Tested Pass,PASS: /api/sidecars.json?q=review&type=agent&limit=5 returned HTTP 200 JSON with items total and pagination keys.,,,,,2026-06-25,
+DASH-API-007,Dashboard API,Runtime API,/api/runtime.json,src/ctx/monitor/api/readonly.py,As a dashboard client I can fetch runtime diagnostics,API returns useful runtime diagnostics without secrets,ctx-monitor running,GET /api/runtime.json and scan for secret-like fields,Tested Pass,PASS: /api/runtime.json returned HTTP 200 JSON with lifecycle diagnostic keys.,,,,,2026-06-25,
+DASH-API-008,Dashboard API,SkillSpector API,/api/skillspector.json,src/ctx/monitor/api/readonly.py,As a dashboard client I can fetch SkillSpector findings,API returns audit records filtered by severity and query,ctx-monitor running,GET /api/skillspector.json?severity=HIGH&q=prompt,Tested Pass,PASS: /api/skillspector.json?severity=HIGH&q=prompt returned HTTP 200 JSON with summary filters and records keys.,,,,,2026-06-25,
+DASH-API-009,Dashboard API,Config API,/api/config.json,src/ctx/monitor/api/readonly.py,As a dashboard client I can fetch effective config,API returns defaults overrides required metadata and no secrets,ctx-monitor running,GET /api/config.json and validate required fields,Tested Pass,PASS: /api/config.json returned HTTP 200 JSON with defaults user effective and path keys.,,,,,2026-06-25,
+DASH-API-010,Dashboard API,Entity Search API,/api/entities/search.json,src/ctx/monitor/api/readonly.py,As a dashboard client I can search entities for autocomplete,API returns typed entity suggestions for search terms and rejects unsafe queries cleanly,ctx-monitor running,GET /api/entities/search.json?q=github&type=skill,Tested Pass,PASS: /api/entities/search.json?q=github&type=skill&limit=5 returned HTTP 200 JSON with results and total keys.,,,,,2026-06-25,
+DASH-API-011,Dashboard API,Events Stream API,/api/events.stream,src/ctx/monitor/api/readonly.py,As a dashboard client I can stream live events,API opens a server-sent event stream and sends data or a clear heartbeat without hanging page load,ctx-monitor running,GET /api/events.stream with timeout and validate SSE framing,Retested Pass,FAIL: /api/events.stream timed out without returning bytes within 10 seconds.,DASH-UX-001,SSE stream did not send an initial heartbeat or ready comment.,Fixed by flushing an immediate : connected SSE comment.,PASS: /api/events.stream returned HTTP 200 and : connected within 1.1s after dashboard restart.,2026-06-25,
+DASH-API-012,Dashboard API,Entity Detail API,/api/entity/<slug>.json,src/ctx/monitor/routes.py,As a dashboard client I can fetch typed entity detail,API returns full entity detail for safe slugs and safe 404 for unknown or unsafe slugs,ctx-monitor running,GET /api/entity/github.json?type=mcp-server and invalid slug,Tested Pass,PASS: /api/entity/github.json?type=mcp-server returned HTTP 200 JSON with slug type path frontmatter and body keys.,,,,,2026-06-25,
+DASH-API-013,Dashboard API,Skill Detail API,/api/skill/<slug>.json,src/ctx/monitor/routes.py,As a dashboard client I can fetch legacy skill detail,API returns sidecar skill JSON or safe 404 without leaking paths,ctx-monitor running,GET /api/skill/github.json and invalid slug,Tested Pass,PASS: /api/skill/github.json?type=skill returned HTTP 200 JSON sidecar payload with grade score signals and slug keys.,,,,,2026-06-25,
+DASH-API-014,Dashboard API,Graph Neighborhood API,/api/graph/<slug>.json,src/ctx/monitor/services/graph.py,As a dashboard client I can fetch graph neighborhoods quickly,API resolves slug and type to bounded nodes edges suggestions and readable relationship data,ctx-monitor running with graph artifact,GET /api/graph/github.json?type=skill&limit=20 and validate JSON shape plus latency,Tested Pass,PASS: /api/graph/github.json?type=skill&limit=20 returned HTTP 200 JSON with nodes edges center resolved suggestions schema layout and insights keys.,,,,,2026-06-25,
+DASH-POST-001,Dashboard Mutation,Load API,/api/load,src/ctx/monitor/api/mutations.py,As a dashboard user I can load an entity safely,POST validates mutation token entity type and slug before mutating active load state,ctx-monitor running with mutation token and fixture,POST /api/load against temp fixture and verify response plus state,Tested Pass,PASS: focused pytest covered /api/load token and fixture-backed load mutation behavior.,,,,,2026-06-25,
+DASH-POST-002,Dashboard Mutation,Unload API,/api/unload,src/ctx/monitor/api/mutations.py,As a dashboard user I can unload an entity safely,POST validates mutation token entity type and slug before unloading without deleting source files,ctx-monitor running with mutation token and fixture,POST /api/unload against temp fixture and verify response plus state,Tested Pass,PASS: focused pytest covered /api/unload token and fixture-backed unload mutation behavior.,,,,,2026-06-25,
+DASH-POST-003,Dashboard Mutation,Config Save API,/api/config,src/ctx/monitor/api/mutations.py,As a dashboard user I can save config changes safely,POST validates mutation token required fields and writes only allowed config overrides,ctx-monitor running with mutation token and temp config,POST /api/config with temp profile and verify file contents,Tested Pass,PASS: focused pytest covered config page dirty-field posting and clear-overrides behavior.,,,,,2026-06-25,
+DASH-POST-004,Dashboard Mutation,Entity Upsert API,/api/entity/upsert,src/ctx/monitor/api/mutations.py,As a dashboard user I can add or update entities manually,POST validates type slug and body runs entity-specific safety gates and queues graph refresh,ctx-monitor running with mutation token and temp wiki,POST /api/entity/upsert against temp wiki and verify entity page plus queue,Tested Pass,"PASS: focused pytest covered /api/entity/upsert validation, entity write, and queue behavior.",,,,,2026-06-25,
+DASH-POST-005,Dashboard Mutation,Entity Delete API,/api/entity/delete,src/ctx/monitor/api/mutations.py,As a dashboard user I can delete dashboard-managed entities safely,POST validates mutation token safe slug and entity ownership before deleting or tombstoning,ctx-monitor running with mutation token and temp wiki,POST /api/entity/delete against temp wiki and verify no unrelated files removed,Tested Pass,PASS: focused pytest covered /api/entity/delete validation and safe deletion behavior.,,,,,2026-06-25,

docs/qa/feature-user-story-status.csv

@@ -0,0 +1,143 @@
+feature_id,surface,feature,entrypoint_or_route,source_evidence,user_story,expected_behavior,setup_preconditions,test_command_or_steps,status,first_test_result,error_id,error_summary,fix_status,retest_result,last_verified_at,notes
+CLI-001,CLI,Generic model run harness,ctx,pyproject.toml project.scripts,As a user I can run or resume a model-agnostic ctx session,ctx creates or resumes a session with configured provider tools budgets and transcript ordering intact,Provider credentials or dry-run/local test provider available,ctx --help then focused run/resume smoke,Tested Pass,test_harness_cli_run.py: 67 passed for ctx run/resume/sessions.,,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-002,CLI,Repository recommendation,ctx-recommend,pyproject.toml project.scripts,As a user I can ask ctx for current repo recommendations,ctx returns capped relevant skill agent MCP recommendations from the shared graph engine,Graph installed and target repo available,ctx-recommend --help then sample repo recommendation,Tested Pass,recommend CLI/golden subset: 24 passed for ctx-recommend and shared recommendation surfaces.,,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-003,CLI,Initial setup,ctx-init,pyproject.toml project.scripts,As a new user I can install hooks graph and model mode from one command,ctx-init installs requested pieces idempotently and reports failures with non-zero exit,Writable user config directory,ctx-init --model-mode skip --graph,Retested Pass,"PASS: temp USERPROFILE ctx-init --model-mode skip --knowledge-mode skip created .claude config/toolboxes and exited 0. PASS: temp USERPROFILE ctx-init --graph --graph-install-mode runtime --model-mode skip installed graph.json and harness page in 129.2s.",CTX-AZ-006,Full graph install exceeded the 10-minute Windows smoke budget before packed wiki artifacts: native-tar full install completed in 759.0s and cleanup took 171.7s.,Packed full artifact now ships wiki-packs and omits expanded non-root markdown fanout; ctx-init checksum updated.,PASS: temp USERPROFILE ctx-init --graph --graph-install-mode full --model-mode skip --knowledge-mode skip exited 0 in 409.7s with graph-store.sqlite3 wiki-packs harness pages and no expanded skills/agents/MCP/converted/concepts markdown.,2026-06-23,Runtime path remains usable; full path now installs packed markdown wiki under the smoke budget while keeping harness pages direct.
+CLI-004,CLI,Claude hook install,ctx-install-hooks,pyproject.toml project.scripts,As a Claude Code user I can install ctx hooks,Hooks are installed idempotently and point to existing modules,Claude config path writable,ctx-install-hooks --help then temp-home smoke,Tested Pass,inject hooks/ctx-init hook subset: 24 passed for hook install and failure handling.,,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-005,CLI,Repo stack scan,ctx-scan-repo,pyproject.toml project.scripts,As a developer I can scan a repo and get stack plus recommendations,Scan detects stack signatures and renders recommendations consistently with graph engine,Sample repos available,ctx-scan-repo --repo . --recommend,Retested Pass,FAIL: first run classified ctx as ml-project because optional embeddings extra contains torch,CTX-AZ-002,Optional pyproject extras were treated as primary project-type dependencies,Fixed by excluding optional/dev pyproject deps from primary project-type classification while keeping them as searchable signals,PASS: focused scan tests 5 passed; live scan now reports Type infrastructure and recommendations render,2026-06-23,
+CLI-006,CLI,Skill add,ctx-skill-add,pyproject.toml project.scripts,As a user I can add or update a skill,Skill is validated micro-skill gated written to wiki and attached to graph/index without duplicate stale edges,Temp skill directory and wiki path,ctx-skill-add --skill-path temp/SKILL.md --name demo --wiki temp/wiki,Retested Pass,Failed in isolated A-Z flow: Windows UTF-8 BOM input was rejected by markdown/JSON parsing; some rejected batch CLIs could still exit 0.,CTX-AZ-004,"Entity onboarding was not Windows-BOM-safe across skill/agent/MCP/harness inputs, and failed batches needed non-zero exits.",Fixed,Skill add accepted BOM-prefixed SKILL.md and wrote wiki entity in temp CLI flow. Focused pytest regressions passed.,2026-06-23,Regression coverage added for BOM inputs and MCP rejected-batch exit.
+CLI-007,CLI,Skill install,ctx-skill-install,pyproject.toml project.scripts,As a Claude Code user I can install a recommended skill,Skill installs into Claude skills directory with manifest and safe overwrite behavior,Temp Claude home,ctx-skill-install --help then dry/smoke path if available,Tested Pass,"install/unload batch: 187 passed, including skill install behavior.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-008,CLI,Skill unload,ctx-skill-unload,pyproject.toml project.scripts,As a user I can unload stale skills,Skill is disabled/removed from active load state without deleting unrelated user files,Temp installed skill,ctx-skill-unload --help then temp uninstall smoke,Tested Pass,"install/unload batch: 187 passed, including skill unload behavior.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-009,CLI,Skill mirror,ctx-skill-mirror,pyproject.toml project.scripts,As a user I can mirror installed skills into wiki,Mirror preserves source metadata and does not overwrite higher quality records silently,Temp skill source,ctx-skill-mirror --help,Tested Pass,"mirror/quality batch: 123 passed, including skill mirror behavior.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-010,CLI,Skill health,ctx-skill-health,pyproject.toml project.scripts,As a maintainer I can check skill health,Health check reports missing frontmatter orphan entries and line drift with actionable exits,Repo graph/wiki available,ctx-skill-health --help then focused check,Tested Pass,"SkillSpector/health batch: 56 passed, including skill health behavior.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-011,CLI,Skill quality,ctx-skill-quality,pyproject.toml project.scripts,As a maintainer I can compute skill quality,Quality scores explain telemetry intake graph and routing signals,Repo graph/wiki available,ctx-skill-quality --help then sample,Tested Pass,"mirror/quality batch: 123 passed, including skill quality behavior.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-012,CLI,Agent add,ctx-agent-add,pyproject.toml project.scripts,As a user I can add or update an agent,Agent page is validated written atomically and connected to graph,Temp agent markdown and wiki path,ctx-agent-add --agent-path temp/agent.md --name demo --wiki temp/wiki,Retested Pass,Failed in isolated A-Z flow: Windows UTF-8 BOM input was rejected by markdown/JSON parsing; some rejected batch CLIs could still exit 0.,CTX-AZ-004,"Entity onboarding was not Windows-BOM-safe across skill/agent/MCP/harness inputs, and failed batches needed non-zero exits.",Fixed,Agent add accepted BOM-prefixed agent markdown and wrote wiki entity in temp CLI flow. Focused pytest regressions passed.,2026-06-23,Regression coverage added for BOM inputs and MCP rejected-batch exit.
+CLI-013,CLI,Agent install,ctx-agent-install,pyproject.toml project.scripts,As a Claude Code user I can install an agent,Agent installs safely and appears in manifest/load surface,Temp Claude home,ctx-agent-install --help,Tested Pass,"install/unload batch: 187 passed, including agent install behavior.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-014,CLI,Agent unload,ctx-agent-unload,pyproject.toml project.scripts,As a user I can unload stale agents,Agent active state is removed safely and recommendation can suggest replacements,Temp installed agent,ctx-agent-unload --help,Tested Pass,install/unload batch plus monitor 3-type coverage: 187 passed for install/unload core behavior.,,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-015,CLI,Agent mirror,ctx-agent-mirror,pyproject.toml project.scripts,As a user I can mirror agents into wiki,Mirror emits normalized wiki pages with source metadata,Temp agent source,ctx-agent-mirror --help,Tested Pass,Temp CLI smoke passed: ctx-agent-mirror mirrored agent body into converted-agents and cleaned temp files.,,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-016,CLI,MCP add,ctx-mcp-add,pyproject.toml project.scripts,As a user I can add or update an MCP server,MCP record is validated enriched written atomically and linked in graph,Temp MCP JSON/URL and wiki path,ctx-mcp-add --dry-run with fixture,Retested Pass,Failed in isolated A-Z flow: Windows UTF-8 BOM input was rejected by markdown/JSON parsing; some rejected batch CLIs could still exit 0.,CTX-AZ-004,"Entity onboarding was not Windows-BOM-safe across skill/agent/MCP/harness inputs, and failed batches needed non-zero exits.",Fixed,MCP add accepted BOM-prefixed JSON and wrote sharded wiki entity in temp CLI flow; stdin BOM regression is covered by pytest. Focused pytest regressions passed.,2026-06-23,Regression coverage added for BOM inputs and MCP rejected-batch exit.
+CLI-017,CLI,MCP install,ctx-mcp-install,pyproject.toml project.scripts,As a Claude Code user I can install an MCP server,MCP config is updated safely and secrets are not echoed or persisted inline,Temp Claude config,ctx-mcp-install --help then dry/temp smoke,Tested Pass,"install/unload batch: 187 passed, including MCP install behavior.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-018,CLI,MCP uninstall,ctx-mcp-uninstall,pyproject.toml project.scripts,As a user I can uninstall an MCP server,MCP config entry is removed without damaging other servers,Temp Claude config,ctx-mcp-uninstall --help,Tested Pass,"install/unload batch: 187 passed, including MCP uninstall behavior.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-019,CLI,MCP fetch,ctx-mcp-fetch,pyproject.toml project.scripts,As a maintainer I can fetch MCP catalog data,Fetch produces normalized records with source provenance and retry-safe output,Network available or fixture mode,ctx-mcp-fetch --help,Tested Pass,"MCP fetch/ingest/server batch: 77 passed, 1 skipped.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-020,CLI,MCP ingest,ctx-mcp-ingest,pyproject.toml project.scripts,As a maintainer I can ingest MCP catalog data,Ingest deduplicates normalizes and updates wiki/graph inputs,Fixture catalog,ctx-mcp-ingest --help,Tested Pass,"MCP fetch/ingest/server batch: 77 passed, 1 skipped.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-021,CLI,MCP enrich,ctx-mcp-enrich,pyproject.toml project.scripts,As a maintainer I can enrich MCP records,Enrichment updates metadata without clobbering curated fields,Fixture record,ctx-mcp-enrich --help,Tested Pass,"MCP enrich/canonical/quality signals batch: 78 passed, 1 skipped.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-022,CLI,MCP quality,ctx-mcp-quality,pyproject.toml project.scripts,As a maintainer I can score MCP quality,MCP score explains source docs install and metadata signals,Repo wiki available,ctx-mcp-quality --help,Tested Pass,"MCP quality batches passed: 123 passed plus 78 passed, 1 skipped in signal/enrich coverage.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-023,CLI,MCP rebuild index,ctx-mcp-rebuild-index,pyproject.toml project.scripts,As a maintainer I can rebuild MCP lookup index,Index rebuild is deterministic and validates duplicate slugs,Repo wiki available,ctx-mcp-rebuild-index --help,Tested Pass,Temp CLI smoke passed: ctx-mcp-rebuild-index wrote .canonical-index.json; canonical index tests included in 78 passed batch.,,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-024,CLI,MCP server,ctx-mcp-server,pyproject.toml project.scripts,As an MCP client I can connect to ctx as an MCP server,Server speaks JSON-RPC over stdio exposes ctx-core tools and shapes invalid requests safely,Local MCP client or stdio smoke,JSON-RPC initialize then tools/list and tools/call against ctx-mcp-server,Tested Pass,test_mcp_server.py covers initialize tools/list tools/call error shaping subprocess round-trip and telemetry redaction.,,,,,2026-06-29,Corrected tracker behavior from nonexistent --help path to the actual stdio MCP server contract.
+CLI-025,CLI,Harness add,ctx-harness-add,pyproject.toml project.scripts,As a user I can add or update a harness,Harness page is atomic symlink-safe scored and linked to compatible model goals,Temp harness JSON/wiki,ctx-harness-add --dry-run --from-json fixture,Retested Pass,Failed in isolated A-Z flow: Windows UTF-8 BOM input was rejected by markdown/JSON parsing; some rejected batch CLIs could still exit 0.,CTX-AZ-004,"Entity onboarding was not Windows-BOM-safe across skill/agent/MCP/harness inputs, and failed batches needed non-zero exits.",Fixed,Harness add accepted BOM-prefixed JSON and wrote wiki entity in temp CLI flow. Focused pytest regressions passed.,2026-06-23,Regression coverage added for BOM inputs and MCP rejected-batch exit.
+CLI-026,CLI,Harness install/recommend,ctx-harness-install,pyproject.toml project.scripts,As a local/API model user I can get harness recommendations and install one,Wizard interviews model goal tools privacy runtime and recommends harness above threshold or no-fit PRD,Graph/wiki installed,ctx-harness-install --dry-run --goal sample --model openai/gpt-4.1,Retested Pass,FAIL: generic Python coding-agent goal recommended narrow text-to-cad harness,CTX-AZ-003,Narrow-domain harnesses could win generic goals via shared python/filesystem/verification terms,Fixed with domain-fit penalty unless the user goal names the harness domain,PASS: generic goal now returns no-fit PRD; explicit CAD/robotics goal still recommends text-to-cad; focused tests 4 passed,2026-06-23,
+CLI-027,CLI,Bundle suggest,ctx-bundle-suggest,pyproject.toml project.scripts,As a session-start hook I can get a capped bundle suggestion,Bundle suggestions are capped deduped and explain why each entity is useful,Graph installed and repo context,ctx-bundle-suggest --help,Tested Pass,"bundle/lifecycle/toolbox batch: 110 passed, including bundle suggestion/orchestration behavior.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-028,CLI,Lifecycle,ctx-lifecycle,pyproject.toml project.scripts,As a user I can track load/unload lifecycle,Usage and stale entities are tracked with confirmable unload behavior,Audit/log path available,ctx-lifecycle --help,Tested Pass,"bundle/lifecycle/toolbox batch: 110 passed, including lifecycle behavior.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-029,CLI,Toolbox,ctx-toolbox,pyproject.toml project.scripts,As a user I can manage toolbox councils,Toolbox init/list/run is idempotent and does not warn on expected existing state,Temp toolbox home,ctx-toolbox --help,Tested Pass,"bundle/lifecycle/toolbox batch: 110 passed, including toolbox config/hooks behavior.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-030,CLI,Dedup check,ctx-dedup-check,pyproject.toml project.scripts,As a maintainer I can block duplicate entities,Dedup gate catches near duplicates and reports merge/update advice,Repo wiki/graph available,ctx-dedup-check --help then sample,Tested Pass,"wiki queue/dedup/source/package/category batch: 106 passed, including dedup behavior.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-031,CLI,Tag backfill,ctx-tag-backfill,pyproject.toml project.scripts,As a maintainer I can backfill weak tags,Backfill adds useful tags without overwriting curated tags blindly,Fixture wiki,ctx-tag-backfill --help,Tested Pass,Temp-home CLI smoke passed: ctx-tag-backfill generated a report for an empty-tag skill; generated report artifact was removed.,,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-032,CLI,Source registry,ctx-source-registry,pyproject.toml project.scripts,As a maintainer I can track external sources,Registry records source status license and update provenance,Repo source registry available,ctx-source-registry --help,Tested Pass,Source registry test plus CLI JSON smoke passed; source registry emitted validated JSON and temp output was removed.,,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-033,CLI,Wiki graphify,ctx-wiki-graphify,pyproject.toml project.scripts,As a maintainer I can build the knowledge graph,Graphify exports crash-safe graph artifacts refreshes generated links and validates counts,Repo wiki path,ctx-wiki-graphify --dry-run or graph-only fixture,Tested Pass,wiki graphify/security/density/quality/harness entity tests: 43 passed.,,,,,2026-06-23,Validated in final A-Z pass.
+CLI-034,CLI,Incremental attach,ctx-incremental-attach,pyproject.toml project.scripts,As a maintainer I can attach new nodes fast,Attach uses pinned embedding/index geometry writes provenance-rich overlays and supports dry-run/queued fallback,Vector index and fixture node,ctx-incremental-attach attach --dry-run ...,Tested Pass,"graph packs/store/incremental batch: 59 passed, including incremental attach A-Z flow.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-035,CLI,Incremental shadow,ctx-incremental-shadow,pyproject.toml project.scripts,As a maintainer I can compare incremental attach with batch graph,Shadow mode reports precision recall top-k agreement and bad examples,Graph/index available,ctx-incremental-shadow --help,Tested Pass,incremental shadow tests: 6 passed.,,,,,2026-06-23,Validated in final A-Z pass.
+CLI-036,CLI,Graph store,ctx-graph-store,pyproject.toml project.scripts,As a dashboard user I can search graph quickly via SQLite store,Store builds validates searches and returns neighborhoods consistent with graph artifacts,Graph artifact available,ctx-graph-store --help,Tested Pass,"graph packs/store/incremental batch: 59 passed, including graph-store CLI build/validate/search/neighborhood behavior.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-037,CLI,Pack compaction,ctx-pack-compact,pyproject.toml project.scripts,As a maintainer I can compact overlay packs,Compaction validates overlays tombstones counts and writes new base artifacts atomically,Graph packs available,ctx-pack-compact --help,Tested Pass,graph packs/store/incremental batch: 59 passed plus pack_compaction coverage.,,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-038,CLI,Wiki worker,ctx-wiki-worker,pyproject.toml project.scripts,As a maintainer I can drain wiki maintenance queue,Worker leases retries jobs and recovers after failure without corrupting artifacts,Temp wiki queue,ctx-wiki-worker --once --limit 1 on fixture,Tested Pass,"wiki queue/dedup/source/package/category batch: 106 passed, including wiki worker upsert/delete/compaction jobs.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-039,CLI,SkillSpector audit,ctx-skillspector-audit,pyproject.toml project.scripts,As a maintainer I can audit skill quality and stale resources,Audit reports stale wrappers invalid references and remediation actions,Repo skills available,ctx-skillspector-audit --help,Tested Pass,"SkillSpector/health batch: 56 passed, including audit payload/report normalization.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-040,CLI,SkillSpector scan,ctx-skillspector-scan,pyproject.toml project.scripts,As a maintainer I can scan SkillSpector data for dashboard,Scan produces dashboard-readable results without blocking normal monitor load,Repo skills available,ctx-skillspector-scan --help,Tested Pass,"SkillSpector/health batch: 56 passed, including scan/service behavior.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-041,CLI,SkillSpector remediation,ctx-skillspector-remediation,pyproject.toml project.scripts,As a maintainer I can remediate SkillSpector findings,Remediation proposes or applies safe fixes with audit evidence,Audit fixture,ctx-skillspector-remediation --help,Tested Pass,"SkillSpector/health batch: 56 passed, including remediation behavior.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+CLI-042,Dashboard,Monitor server,ctx-monitor,pyproject.toml project.scripts,As a user I can launch the local dashboard,Dashboard starts on local host serves all nav pages and does not expose LAN mode unauthenticated,Graph runtime installed,ctx-monitor serve --host 127.0.0.1 --port 8765,Tested Pass,Started ctx-monitor on 127.0.0.1:8765; HTTP dashboard responded after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+CLI-043,CLI,Telemetry export,ctx-telemetry-export,pyproject.toml project.scripts and docs/telemetry.md,As an enterprise operator I can export local ctx telemetry to configured sinks,Export reads local event and metric spools applies checkpoints and supports local JSONL or OTLP sinks with host allow-listing,Telemetry spool and optional exporter config,ctx-telemetry-export --dry-run --json,Tested Pass,enterprise telemetry focused tests covered exporter configuration checkpointing local JSONL and OTLP payload paths.,,,,,2026-06-29,Validated in telemetry release gate without requiring external collector credentials.
+CLI-044,CLI,Telemetry retention,ctx-telemetry-retention,pyproject.toml project.scripts and docs/telemetry.md,As an enterprise operator I can preview and enforce telemetry retention,Retention plans and enforces TTL cleanup for local telemetry signals while recording status without leaking payloads,Telemetry config and local spool paths,ctx-telemetry-retention plan --signal all --json,Tested Pass,enterprise telemetry focused tests covered retention planning enforcement status output and privacy salt behavior.,,,,,2026-06-29,Validated as local-only enterprise privacy default with exporters separately configurable.
+PYAPI-001,Python API,Public Python API,ctx.api and ctx top-level re-exports,src/ctx/api.py and src/ctx/__init__.py,As a harness author I can import ctx from Python without depending on internal modules,recommend_bundle graph_query wiki_search wiki_get list_all_entities default_wiki_dir and CtxCoreToolbox keep stable signatures safe defaults and top-level re-exports,Runtime wiki or synthetic fixture available,pytest src/tests/test_public_api.py -q,Tested Pass,test_public_api.py covers __all__ exports top-level re-exports signatures happy paths empty paths and telemetry privacy payloads.,,,,,2026-06-29,Added during canonical feature inventory gap pass.
+MCP-001,MCP/Core Tools,Read/query tool catalog,"ctx__recommend_bundle, ctx__graph_query, ctx__wiki_search, ctx__wiki_get",src/ctx/adapters/generic/ctx_core_tools.py and src/ctx/mcp_server/server.py,As an MCP or generic harness client I can call ctx read tools consistently,Read tools return recommendations graph neighborhoods wiki search and wiki entity payloads through both generic toolbox and MCP stdio surfaces,Synthetic graph/wiki fixture available,pytest src/tests/test_harness_ctx_core.py src/tests/test_mcp_server.py -q,Tested Pass,test_harness_ctx_core.py and test_mcp_server.py pin the read tool names schemas dispatch success paths and JSON-RPC tools/list exposure.,,,,,2026-06-29,Canonical tracker row for the first-class ctx-core read tools.
+MCP-002,MCP/Core Tools,Lifecycle and session tool catalog,"ctx__observe_dev_event, ctx__load_entity, ctx__mark_entity_used, ctx__record_validation, ctx__record_escalation, ctx__unload_entity, ctx__session_end, ctx__session_state",src/ctx/adapters/generic/ctx_core_tools.py and runtime_lifecycle.py,As an MCP or generic harness client I can record runtime lifecycle evidence,Lifecycle tools append privacy-safe session events enforce bound session IDs and expose session state without leaking raw entity slugs,Temp runtime lifecycle directory available,pytest src/tests/test_harness_ctx_core.py src/tests/test_mcp_server.py -q,Tested Pass,test_harness_ctx_core.py covers lifecycle append order bound session enforcement telemetry hashing and test_mcp_server.py covers lifecycle tools/call round-trip.,,,,,2026-06-29,Canonical tracker row for lifecycle/session tools exposed in the MCP/core toolbox catalog.
+MCP-003,MCP Router,Trusted third-party MCP attachment,McpClient and McpRouter,src/ctx/adapters/generic/tools/mcp_router.py,As a generic harness user I can attach trusted third-party MCP servers safely,Router starts MCP subprocesses with isolated environment namespaces tools handles timeouts and redacts secrets from errors,Fake MCP server fixture available,pytest src/tests/test_mcp_router.py -q,Tested Pass,test_mcp_router.py covers client start stop tool listing calls namespace routing timeout crash handling environment isolation and stderr secret redaction.,,,,,2026-06-29,Added because third-party MCP attachment is user-facing host functionality not just internal plumbing.
+MCP-004,MCP/Core Tools,Response format negotiation,output_format and _response_format,src/ctx/adapters/generic/ctx_core_tools.py,As a tool caller I can request JSON or GCF output from read tools,Read tool schemas expose optional output_format and _response_format aliases and fall back to JSON errors when GCF codec is unavailable,Generic toolbox fixture available,pytest src/tests/test_harness_ctx_core.py -q,Tested Pass,test_harness_ctx_core.py covers optional schema fields JSON default GCF opt-in public alias and codec-missing fallback.,,,,,2026-06-29,Tracks a schema-visible behavior exposed to MCP/tool clients.
+DASH-001,Dashboard,Home page,/,src/ctx/monitor/routes.py,As a user I can land on a useful dashboard home,Home shows current counts and high-value entry points without stale numbers,Monitor running,GET /,Tested Pass,GET / returned 200 in 1506ms after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+DASH-002,Dashboard,Loaded page,/loaded,src/ctx/monitor/routes.py,As a user I can see loaded entities,Loaded page lists active skills agents MCPs and supports load state clarity,Monitor running,GET /loaded,Tested Pass,GET /loaded returned 200 in 79ms after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+DASH-003,Dashboard,Skills page,/skills,src/ctx/monitor/routes.py,As a user I can browse skills with pagination/search,Skills page is fast and does not dump all cards at once,Monitor running,GET /skills,Tested Pass,GET /skills returned 200 in 165ms after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+DASH-004,Dashboard,SkillSpector page,/skillspector,src/ctx/monitor/routes.py,As a maintainer I can inspect quality findings,SkillSpector page renders findings and remediation links,Monitor running,GET /skillspector,Tested Pass,GET /skillspector returned 200 in 3315ms after restart; functional but slower than core pages.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+DASH-005,Dashboard,Wiki index/catalog,"/wiki, /catalog, and /catalog/",src/ctx/monitor/routes.py,As a user I can search entity catalog,Wiki/catalog supports autocomplete-like search and tiles for skill agent MCP harness,Monitor running,GET /catalog?type=agent&q=review,Retested Pass,FAIL: live route timed out after 60018ms before fix,CTX-AZ-001,/catalog with query rebuilt too much server-side catalog state while /api/entities/search was fast,Fixed by using bounded search results for queried wiki/catalog render,PASS: live route 200 in 1422ms after monitor restart; focused tests 4 passed,2026-06-23,Regression covered by test_render_wiki_index_query_uses_bounded_search
+DASH-006,Dashboard,Wiki entity page,/wiki/<slug>,src/ctx/monitor/routes.py,As a user I can inspect a full entity page,Entity page has Overview Subgraph Quality tabs and rendered markdown/frontmatter,Monitor running,GET /wiki/github?type=mcp-server,Tested Pass,GET /wiki/github?type=mcp-server returned 200 in 2705ms after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+DASH-007,Dashboard,Graph page,/graph,src/ctx/monitor/routes.py,As a user I can explore graph interactively,Graph loads live search results click-to-focus double-click-back filters match histogram and useful inspector,Monitor running,GET /graph then interact,Retested Pass,PASS: /graph returned 200 in 31ms after monitor restart,,,,"PASS: Playwright test_ctx_monitor_browser.py::test_graph_page_uses_builtin_svg_renderer covered renderer click focus double-click back filters histogram live search type shapes and inspector.",2026-06-23,Browser interaction pass completed.
+DASH-020,Dashboard,Graph live search type preservation,/graph focus search,src/ctx/monitor/pages/graph_client.py,As a dashboard user searching duplicate graph slugs I can keep the selected entity type,Live search sends the selected focus type to /api/entities/search.json so duplicate slugs resolve to the intended skill agent MCP server or harness,Monitor running with graph search data,pytest src/tests/test_ctx_monitor.py::test_render_graph_focus_controls_preserve_type -q,Retested Pass,FAIL: graph live search fetched /api/entities/search.json without type even when focus-type was selected.,DASH-UX-004,Graph live search ignored the selected focus entity type and could suggest the wrong duplicate slug type,Fixed by appending selectedFocusType to the live entity search request,"PASS: focused graph render test pins selected type in live search URL generation.",2026-06-29,Added from dashboard/graph expert lane UX finding.
+DASH-008,Dashboard,Manage page,/manage,src/ctx/monitor/routes.py,As a user I can manage entities,Manage supports search upload/upsert delete/manual edit with safety prompts,Monitor running,GET /manage,Tested Pass,GET /manage returned 200 in 261ms after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+DASH-009,Dashboard,Harness setup,/harness,src/ctx/monitor/routes.py,As a local/API model user I can use a harness wizard,Harness Setup interviews model and goals recommends matching harness or no-fit PRD,Monitor running,GET /harness,Tested Pass,GET /harness returned 200 in 23ms after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+DASH-010,Dashboard,Docs page,/docs,src/ctx/monitor/routes.py,As a user I can read repo docs inside dashboard,Docs render markdown like mkdocs with tabs sidebar hierarchy and local search,Monitor running,GET /docs,Tested Pass,GET /docs returned 200 in 1219ms after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+DASH-011,Dashboard,Config page,/config,src/ctx/monitor/routes.py,As a user I can view/edit important config,Config shows explanations defaults required fields validation and safe save,Monitor running,GET /config and POST /api/config,Tested Pass,GET /config returned 200 in 12ms after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+DASH-012,Dashboard,Status page,/status,src/ctx/monitor/routes.py,As a user I can see system health,Status reports graph/wiki/cache/session health with actionable errors,Monitor running,GET /status,Tested Pass,GET /status returned 200 in 3750ms after restart; functional but slower than core pages.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+DASH-013,Dashboard,KPI page,/kpi,src/ctx/monitor/routes.py,As a user I can inspect recommendation effectiveness,KPIs show usage score quality and lifecycle trends without slow unbounded render,Monitor running,GET /kpi,Tested Pass,GET /kpi returned 200 in 107ms after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+DASH-014,Dashboard,Runtime page,/runtime,src/ctx/monitor/routes.py,As a user I can inspect runtime artifacts,Runtime shows graph store cache versions and artifact freshness,Monitor running,GET /runtime,Tested Pass,GET /runtime returned 200 in 25ms after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+DASH-015,Dashboard,Sessions page,/sessions,src/ctx/monitor/routes.py,As a user I can inspect sessions,Sessions page lists transcripts and details without leaking secrets,Monitor running,GET /sessions,Tested Pass,GET /sessions returned 200 in 269ms after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+DASH-016,Dashboard,Logs page,/logs,src/ctx/monitor/routes.py,As a user I can inspect logs,Logs render audit/log files or clear empty state,Monitor running,GET /logs,Tested Pass,GET /logs returned 200 in 132ms after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+DASH-017,Dashboard,Live events,/events and /live,src/ctx/monitor/routes.py,As a user I can tail live events,Live page connects SSE and shows clear empty/disconnected states,Monitor running,GET /events and /api/events.stream,Tested Pass,GET /live returned 200 in 87ms after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+DASH-018,Dashboard,Session detail page,/session/<session_id>,src/ctx/monitor/routes.py,As a user I can inspect one session timeline,Session detail filters audit and load events to the requested session and escapes untrusted values,Monitor running with audit fixtures,GET /session/<session_id>,Tested Pass,Focused monitor tests cover session_detail filtering and render_session_detail escaping.,,,,,2026-06-23,Added during route inventory coverage audit.
+DASH-019,Dashboard,Sidecar detail page,/skill/<slug>,src/ctx/monitor/routes.py,As a user I can inspect one entity sidecar,Sidecar detail renders quality breakdown and timeline for typed skill agent MCP or harness sidecars,Monitor running with sidecar fixtures,GET /skill/<slug>?type=agent,Tested Pass,Focused monitor tests cover sidecar links plus render_skill_detail route wiring and typed sidecar loading.,,,,,2026-06-23,Added during route inventory coverage audit.
+API-001,Dashboard API,Sessions API,/api/sessions.json,src/ctx/monitor/routes.py,As a dashboard client I can fetch sessions JSON,Endpoint returns valid JSON quickly with no secrets,Monitor running,GET /api/sessions.json,Tested Pass,GET /api/sessions.json returned 200 in 241ms after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+API-002,Dashboard API,Manifest API,/api/manifest.json,src/ctx/monitor/routes.py,As a dashboard client I can fetch manifest JSON,Endpoint returns loaded entities and counts consistently,Monitor running,GET /api/manifest.json,Tested Pass,GET /api/manifest.json returned 200 in 5ms after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+API-003,Dashboard API,Status API,/api/status.json,src/ctx/monitor/routes.py,As a dashboard client I can fetch health JSON,Endpoint returns graph/wiki/cache health with correct status code,Monitor running,GET /api/status.json,Tested Pass,GET /api/status.json returned 200 in 4303ms after restart; functional but slower than core APIs.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+API-004,Dashboard API,KPI API,/api/kpi.json,src/ctx/monitor/routes.py,As a dashboard client I can fetch KPI JSON,Endpoint returns bounded KPI payload quickly,Monitor running,GET /api/kpi.json,Tested Pass,GET /api/kpi.json returned 200 in 105ms after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+API-005,Dashboard API,Grades API,/api/grades.json,src/ctx/monitor/routes.py,As a dashboard client I can fetch grades JSON,Endpoint returns score and grade payload with explanations,Monitor running,GET /api/grades.json,Retested Pass,Initial dashboard sweep: GET /api/grades.json returned 200 but took 16833ms for a tiny payload.,CTX-AZ-005,Grades API ignored cached KPI grade_counts and rescanned all quality sidecars on demand.,Fixed,"After routing through cached KPI summary, GET /api/grades.json returned 200 in 92ms after restart.",2026-06-23,Fallback full sidecar scan remains for missing KPI summary.
+API-006,Dashboard API,Runtime API,/api/runtime.json,src/ctx/monitor/routes.py,As a dashboard client I can fetch runtime JSON,Endpoint returns artifact/cache versions and paths safely,Monitor running,GET /api/runtime.json,Tested Pass,GET /api/runtime.json returned 200 in 21ms after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+API-007,Dashboard API,Entity search API,/api/entities/search.json,src/ctx/monitor/routes.py,As a dashboard client I can search entities,Endpoint supports live query type filters and useful fuzzy results,Monitor running,GET /api/entities/search.json?q=review&type=agent,Tested Pass,PASS: endpoint returned 200 in 28ms with agent review results,,,,,2026-06-23,
+API-008,Dashboard API,Entity detail API,/api/entity/<slug>.json,src/ctx/monitor/routes.py,As a dashboard client I can fetch entity details,Endpoint returns canonical entity docs frontmatter and graph sidecar,Monitor running,GET /api/entity/github.json?type=mcp-server,Tested Pass,GET /api/entity/github.json?type=mcp-server returned 200 in 27ms after restart.,,,,,2026-06-23,Dashboard route sweep; no mutation performed.
+API-009,Dashboard API,Graph neighborhood API,/api/graph/<slug>.json,src/ctx/monitor/routes.py,As a dashboard client I can fetch a graph neighborhood,Endpoint returns bounded nodes edges scores and reasons fast after runtime install,Monitor running,GET /api/graph/github.json?type=skill&limit=20,Tested Pass,PASS: endpoint returned 200 in 2295ms with nodes/edges JSON,,,,,2026-06-23,
+API-010,Dashboard API,Load/unload APIs,/api/load and /api/unload,src/ctx/monitor/routes.py,As a dashboard user I can load/unload entities,POST validates input changes active state and rejects unsafe requests,Monitor running and temp state,POST /api/load then /api/unload,Tested Pass,"Focused pytest passed: perform_load rejects invalid slugs, load security scan surfaces output, perform_unload rejects invalid slugs.",,,,,2026-06-23,"Validated through isolated monitor mutation tests, not live local catalog mutation."
+API-011,Dashboard API,Entity upsert/delete APIs,/api/entity/upsert and /api/entity/delete,src/ctx/monitor/routes.py,As a dashboard user I can manually add edit or delete entities,POST validates type slug content and queues graph/wiki updates safely,Monitor running and temp wiki,POST fixture upsert/delete,Tested Pass,Focused pytest passed: entity upsert writes wiki page and queues graph refresh; existing-page confirmation and delete behavior covered.,,,,,2026-06-23,"Validated through isolated monitor mutation tests, not live local catalog mutation."
+API-012,Dashboard API,Config read API,/api/config.json,src/ctx/monitor/routes.py,As a dashboard client I can fetch effective config JSON,Endpoint returns defaults plus user overrides with required config metadata and no secrets,Monitor running,GET /api/config.json,Tested Pass,Focused monitor config tests cover effective payload rendering and config save/clear behavior.,,,,,2026-06-23,Added during route inventory coverage audit.
+API-013,Dashboard API,Sidecars API,/api/sidecars.json,src/ctx/monitor/routes.py,As a dashboard client I can fetch paginated sidecar cards,Endpoint supports query type grade floor and limit filters without full unbounded scans,Monitor running with sidecar fixtures,GET /api/sidecars.json?q=review&type=agent&grade=A&hide_floor=1&limit=1,Tested Pass,Focused monitor API test returned filtered sidecar JSON with total limit filters and caps.,,,,,2026-06-23,Added during route inventory coverage audit.
+API-014,Dashboard API,SkillSpector API,/api/skillspector.json,src/ctx/monitor/routes.py,As a dashboard client I can fetch SkillSpector findings,Endpoint returns filtered audit summary and records for dashboard remediation views,Monitor running with skillspector audit fixture,GET /api/skillspector.json?severity=HIGH&q=prompt,Tested Pass,Focused monitor API test returned HIGH prompt-injection SkillSpector record JSON.,,,,,2026-06-23,Added during route inventory coverage audit.
+API-015,Dashboard API,Sidecar detail API,/api/skill/<slug>.json,src/ctx/monitor/routes.py,As a dashboard client I can fetch one sidecar JSON,Endpoint returns typed sidecar details or a safe 404 for missing/unsafe slugs,Monitor running with typed sidecar fixture,GET /api/skill/filesystem.json?type=mcp-server,Tested Pass,Focused monitor API test returned typed MCP sidecar JSON and unsafe slug rejection is covered.,,,,,2026-06-23,Added during route inventory coverage audit.
+GRAPH-001,Graph/Wiki,Full graph artifact validation,src/validate_graph_artifacts.py,pyproject and scripts/ci_preflight.py,As a maintainer I can validate shipped graph artifacts,Validation deep-checks tar members counts no originals no locks exact release counts and line thresholds,Repo graph artifacts present,python src/validate_graph_artifacts.py --deep ...,Tested Pass,PASS: exact counts validated nodes 79958 edges 1778069 semantic 1088763 pages skills 68494 agents 467 MCPs 10790 harnesses 207,,,,,2026-06-23,
+GRAPH-002,Graph/Wiki,Published stats sync,src/update_repo_stats.py,pyproject and src/update_repo_stats.py,As a maintainer I can keep README docs and About counts in sync,Stats come from shipped graph artifacts and checks fail when docs drift,Repo graph artifacts present,python src/update_repo_stats.py --check,Tested Pass,PASS: README/docs stats are up to date; test_release_graph_count_sync 3 passed,,,,,2026-06-23,
+GRAPH-003,Graph/Wiki,Graph pack manifest,ctx core graph_packs/pack_validation,src/ctx/core/graph and wiki modules,As a maintainer I can use base and overlay graph packs,Packs have manifest export IDs parent IDs checksums tombstones and merged reads,Graph pack fixtures,pytest graph pack tests,Tested Pass,graph packs/store/incremental batch: 59 passed and graph pack manifest tests passed.,,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+GRAPH-004,Graph/Wiki,SQLite operational graph store,ctx-graph-store,src/ctx/core/graph/graph_store.py,As a dashboard user I get fast search/neighborhoods,Store builds from graphify-out validates freshness and accelerates reads,Runtime graph installed,ctx-graph-store build/search/neighborhood fixture,Tested Pass,"graph packs/store/incremental batch: 59 passed, including SQLite graph store tests.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+GRAPH-005,Graph/Wiki,Vector index and ANN attach,ctx-incremental-attach,src/ctx/core/graph/vector_index.py,As a maintainer I can update graph without global rebuild,New node embedding queries base+delta index and writes overlay edges with provenance,Index fixture,incremental attach dry-run and validate-indexes,Tested Pass,"graph packs/store/incremental batch: 59 passed, including vector/incremental attach A-Z tests.",,,,,2026-06-23,Validated in focused pytest or isolated temp CLI smoke during A-Z pass.
+HARNESS-001,Harness,Own-model harness recommendation,ctx-init and ctx-harness-install,ctx_init.py and harness_install.py,As a user with non-Claude model I can choose model/goals and get best harness,Flow interviews provider model goal runtime tools privacy and returns top harnesses above configured score,Runtime graph installed,ctx-init --model-mode custom or harness dry-run,Retested Pass,FAIL: generic own-model coding-agent goal returned text-to-cad false positive,CTX-AZ-003,Narrow-domain harnesses were not penalized for generic goals,Fixed with domain-fit penalty preserving explicit domain matches,PASS: generic coding-agent goal returns no recommendations plus custom harness PRD,2026-06-23,
+HARNESS-002,Harness,No-fit harness PRD,ctx-harness-install,harness_install.py,As a user with no fitting harness I get instructions to build one,No-fit path produces provider-aware PRD attachable to ctx recommendation system,Graph with threshold forcing no match,ctx-harness-install --dry-run with restrictive constraints,Tested Pass,PASS: --plan-on-no-fit printed provider-aware Custom Harness PRD for openai/gpt-4.1 with runtime/tools/privacy/verification fields,,,,,2026-06-23,
+DOC-001,Docs,Public docs install path,docs/index.md and docs/*.md,docs file inventory,As a first-time user I can follow docs exactly,Docs commands are current numbers accurate no dead module paths no future-roadmap fluff,Docs built locally,mkdocs build or docs route smoke,Tested Pass,python -m mkdocs build --strict passed; python src/update_repo_stats.py --check passed.,,,,,2026-06-23,Validated in final A-Z pass.
+DOC-002,Docs,README badges/catalog links,README.md and docs/catalog.md,README plus public docs,As a GitHub visitor I can click badges and browse catalog,Skill agent MCP harness badges open public catalog pages with working search guidance,Public docs available,Inspect README links and catalog route,Tested Pass,"README top badges checked for Tests, Graph, Skills, Agents, MCPs, Harnesses; update_repo_stats --check passed.",,,,,2026-06-23,Validated in final A-Z pass.
+DOC-NAV-001,Docs,Public home page,docs/index.md,mkdocs.yml nav,As a docs visitor I can start from the ctx home page,The page explains ctx positioning install entry points and links onward through public docs,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-002,Docs,Public catalog page,docs/catalog.md,mkdocs.yml nav,As a docs visitor I can browse the public catalog,The page exposes searchable skill agent MCP and harness catalog guidance without needing the local dashboard,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-003,Docs,Knowledge graph page,docs/knowledge-graph.md,mkdocs.yml nav,As a docs visitor I can understand shipped graph artifacts,The page documents graph contents counts validation and usage expectations for enterprise review,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-004,Docs,Hugging Face publish page,docs/huggingface-publish.md,mkdocs.yml nav,As a release operator I can follow the Hugging Face publishing docs,The page explains dataset sync artifacts and release expectations with credential requirements separated from code,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-005,Docs,Entity onboarding page,docs/entity-onboarding.md,mkdocs.yml nav,As a curator I can onboard skills agents MCPs and harnesses from docs,The page describes entity inputs validation and graph attachment behavior for contributor workflows,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-006,Docs,Dashboard page,docs/dashboard.md,mkdocs.yml nav,As a dashboard user I can understand the local monitor,The page documents dashboard routes data sources and expected monitor workflows,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-007,Docs,Telemetry page,docs/telemetry.md,mkdocs.yml nav,As an enterprise operator I can configure telemetry safely,The page documents OpenTelemetry configuration exporters privacy defaults and operational checks,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-008,Docs,Harness host attachment page,docs/harness/attaching-to-hosts.md,mkdocs.yml nav,As a harness integrator I can attach ctx to supported hosts,The page describes host attachment expectations and verification steps for harness adoption,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-009,Docs,Clean-host contract page,docs/harness/clean-host-contract.md,mkdocs.yml nav,As a release reviewer I can understand the clean host contract,The page documents clean environment install checks and what must pass for release confidence,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-010,Docs,Toolbox overview page,docs/toolbox/index.md,mkdocs.yml nav,As a toolbox user I can understand toolbox capabilities,The page introduces toolbox configuration council execution hooks and related workflows,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-011,Docs,Toolbox configuration page,docs/toolbox/configuration.md,mkdocs.yml nav,As a toolbox user I can configure ctx toolboxes,The page documents configuration files fields and expected toolbox behavior,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-012,Docs,Starter toolboxes page,docs/toolbox/starters.md,mkdocs.yml nav,As a new toolbox user I can start from prepared toolbox examples,The page presents starter toolbox choices and the workflow each starter supports,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-013,Docs,Council runner page,docs/toolbox/council-runner.md,mkdocs.yml nav,As a toolbox operator I can run council workflows,The page documents council runner behavior inputs outputs and review expectations,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-014,Docs,Toolbox hooks page,docs/toolbox/hooks.md,mkdocs.yml nav,As a toolbox user I can configure hooks and triggers,The page documents hook trigger behavior and safe integration expectations,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-015,Docs,Behavior miner page,docs/toolbox/behavior-miner.md,mkdocs.yml nav,As a maintainer I can understand behavior mining workflows,The page documents behavior miner purpose inputs outputs and review use cases,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-016,Docs,Intent interview page,docs/toolbox/intent-interview.md,mkdocs.yml nav,As a toolbox user I can run intent interview flows,The page documents interview prompts outputs and how intent feeds recommendation decisions,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-017,Docs,Verdicts and guardrails page,docs/toolbox/verdicts.md,mkdocs.yml nav,As a reviewer I can understand toolbox verdicts and guardrails,The page documents verdict meanings guardrail checks and decision support behavior,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-018,Docs,Backup hook install page,docs/backup-hook-install.md,mkdocs.yml nav,As a Claude Code user I can install backup hooks from docs,The page documents backup hook install behavior and safety expectations,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-019,Docs,Skill router overview page,docs/skill-router/index.md,mkdocs.yml nav,As a skill-router user I can understand routing behavior,The page explains routing inputs outputs and how ctx chooses useful skills,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-020,Docs,Stack signatures page,docs/stack-signatures.md,mkdocs.yml nav,As a maintainer I can understand stack signature matching,The page documents stack signatures and how repo signals inform recommendations,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-021,Docs,Skill-stack matrix page,docs/skill-stack-matrix.md,mkdocs.yml nav,As a docs visitor I can inspect skill to stack coverage,The page documents how skills map to stack signals and where recommendations come from,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-022,Docs,Marketplace registry page,docs/marketplace-registry.md,mkdocs.yml nav,As a docs visitor I can understand marketplace registry data,The page documents registry source expectations and public catalog meaning,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-023,Docs,Skill health page,docs/skills-health.md,mkdocs.yml nav,As a maintainer I can understand skill health checks,The page documents health signals expected remediation and release review meaning,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-024,Docs,Memory anchoring page,docs/memory-anchor.md,mkdocs.yml nav,As a user I can understand memory anchoring behavior,The page documents memory anchor concepts configuration and expected product behavior,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-025,Docs,Skill lifecycle and dashboard page,docs/skill-lifecycle-and-dashboard.md,mkdocs.yml nav,As a dashboard user I can understand skill lifecycle views,The page documents lifecycle states dashboard linkage and expected user workflows,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DOC-NAV-026,Docs,Skill-quality install page,docs/skill-quality-install.md,mkdocs.yml nav,As an installer I can understand skill quality install guidance,The page documents quality signals install decisions and user-visible expectations,Docs build environment available,python -m mkdocs build --strict --quiet plus tracker nav coverage test,Tested Pass,python -m mkdocs build --strict --quiet passed; tracker nav coverage test passed.,,,,,2026-06-29,Added for public MkDocs nav coverage enforcement.
+DIST-001,Distribution,GitHub About metadata,GitHub repository About,src/update_repo_stats.py,As a GitHub visitor I can understand ctx positioning and current counts from the repo About,About says ctx is a recommendation layer not a marketplace and uses shipped graph counts,GitHub CLI authenticated,python src/update_repo_stats.py --check-github-about,Retested Pass,PASS: GitHub About description is up to date on main 16c96b1.,,,,,2026-06-29,Revalidated after inventory wording merge with python src/update_repo_stats.py --check-github-about.
+DIST-002,Distribution,Main CI test workflow,.github/workflows/test.yml,.github/workflows/test.yml,As a contributor I can trust the required main test workflow,Main push runs static gates unit-linux canaries package smoke browser security and required CI aggregate,GitHub Actions available,gh run view 28340695216,Retested Pass,PASS: main Tests workflow run 28340695216 for 16c96b1 completed successfully and CI required job 83954824744 passed.,,,,,2026-06-29,"Matrix pytest static gates unit-linux browser monitor security telemetry enterprise gate package smoke clean-host similarity and A-Z canary all passed."
+DIST-003,Distribution,Docs deploy workflow,.github/workflows/docs.yml,.github/workflows/docs.yml,As a docs visitor I get the current public docs after main updates,Docs workflow builds strict MkDocs and deploys GitHub Pages without stale generated content,GitHub Pages enabled,gh run view 28340695222 and curl public docs URLs,Retested Pass,PASS: Deploy docs to GitHub Pages run 28340695222 for 16c96b1 succeeded and public docs home telemetry dashboard and knowledge-graph URLs returned HTTP 200.,,,,,2026-06-29,"Public docs reflect the post-merge main that labels the test count as 4,400 test inventory."
+DIST-004,Distribution,Hugging Face sync workflow,.github/workflows/huggingface-sync.yml,.github/workflows/huggingface-sync.yml and scripts/sync_huggingface.py,As a Hugging Face visitor I get the same tracked repo and graph artifacts as GitHub,Workflow hydrates graph artifacts by matching LFS sha/size release assets before publishing and refuses stale README/docs stats,Valid write-scoped HF_TOKEN configured in GitHub secrets,GitHub Actions Sync Hugging Face workflow on main,Needs Fix,"FAIL: main Sync Hugging Face workflow run 28340695227 for 16c96b1 failed after README/docs stats and graph artifact hydration passed; upload to https://huggingface.co/api/datasets/Stevesolun/ctx/preupload/main returned 401 Unauthorized / Invalid username or password.",CTX-CICD-001,GitHub HF_TOKEN secret is invalid revoked or lacks write access for the Stevesolun/ctx dataset repo,Rotate and revoke the exposed token update the GitHub HF_TOKEN secret outside chat then rerun failed job 28340695227,,2026-06-29,"Public HF dataset remains stale: sha 9422c922b706b385d429983aa4c76e281a62ab38 lastModified 2026-06-14T16:16:55Z pyproject version 1.0.11 README still says Tests-4043_collected and Graph-102,928 nodes / 2.9M edges and docs/qa/feature-user-story-status.csv returns 404."
+DIST-005,Distribution,Clean host contract workflow,.github/workflows/clean-host-contract.yml,.github/workflows/clean-host-contract.yml,As a new installer I can verify ctx works on a clean host,Workflow installs the package in a clean environment and runs the clean-host smoke contract,GitHub Actions available,gh run view 28340695216,Retested Pass,PASS: Clean host contract job 83954561453 passed inside main Tests run 28340695216 for 16c96b1.,,,,,2026-06-29,Revalidated through the current required main workflow after the inventory wording merge.
+DIST-006,Distribution,PyPI publish workflow,.github/workflows/publish.yml,.github/workflows/publish.yml,As a PyPI user I can install the tagged release with matching graph artifacts,Tag publish builds the wheel validates graph artifacts uploads release assets and publishes the package,Published release tag and clean temporary PyPI install environment,Inspect publish workflow run plus release/PyPI metadata; install claude-ctx from PyPI and run graph init/recommend smoke,Retested Pass,"PASS: latest published tag v1.0.19 Publish to PyPI workflow run 27986904249 succeeded; release assets include full/runtime graph artifacts with SHA-256 digests; PyPI exposes claude-ctx 1.0.19 wheel and sdist; clean temp venv installed claude-ctx==1.0.19, ctx-init --graph --graph-install-mode runtime exited 0, and ctx-scan-repo --recommend exited 0.",,,,,2026-06-29,"Current main is version 1.0.20 but no v1.0.20 tag GitHub release or PyPI artifact exists yet; next release must tag and rerun the publish smoke before announcing 1.0.20 as published."
+DIST-007,Distribution,Parallel pytest experiment workflow,.github/workflows/xdist-experiment.yml,.github/workflows/xdist-experiment.yml,As a maintainer I can benchmark pytest-xdist safely before adopting it,Workflow runs only when explicitly dispatched and does not affect required checks until proven stable,GitHub Actions available,Manual workflow_dispatch run for xdist experiment,Tested Pass,GitHub Actions run 28133264595 passed on ubuntu-latest windows-latest and macos-latest with Python 3.12.,,,,,2026-06-24,Dispatched manually on main; optional experiment remains out of required checks.
+MAINT-001,Maintainer,Backup snapshot audit,scripts/audit_backup.py,scripts/audit_backup.py,As a maintainer I can inspect backup snapshots for missing expected files,Script summarizes backup contents and flags missing graph/wiki/report artifacts without mutating the repo,Backup fixture available,Run script against representative backup fixture,Retested Pass,FAIL: BOM-prefixed manifest.json from PowerShell Set-Content -Encoding UTF8 raised JSONDecodeError.,CTX-AZ-008,Backup audit read manifest JSON with utf-8 and rejected common Windows BOM input,Fixed by reading manifest.json with utf-8-sig,PASS: temp backup fixture with BOM manifest printed entries and OK coverage; regression pytest passed.,2026-06-23,
+MAINT-002,Maintainer,Dashboard graph index builder,scripts/build_dashboard_graph_index.py,scripts/build_dashboard_graph_index.py,As a dashboard user I get fast graph search and neighborhoods,Script builds the dashboard SQLite/index artifacts from graph exports for fast monitor reads,Graph fixture available,Run script against small graph fixture and query resulting index,Retested Pass,FAIL: BOM-prefixed graph.json from PowerShell Set-Content -Encoding UTF8 raised JSONDecodeError.,CTX-AZ-008,Dashboard graph index builder read graph JSON with utf-8 and rejected common Windows BOM input,Fixed by reading graph JSON with utf-8-sig,PASS: temp graph fixture built SQLite index with 2 nodes and neighbor mcp-server:github; regression pytest passed.,2026-06-23,
+MAINT-003,Maintainer,CI change classifier,scripts/ci_classifier.py,scripts/ci_classifier.py and .github/workflows/test.yml,As a contributor I get the right CI gates for the files I changed,Classifier marks docs graph source package browser and similarity changes conservatively,CI classifier tests available,python -m pytest src/tests/test_ci_classifier.py -q,Tested Pass,CI classifier suite covers path classes and workflow contract behavior.,,,,,2026-06-23,Validated by focused pytest in this tracker slice.
+MAINT-004,Maintainer,No-test policy gate,scripts/ci_no_test_policy.py,scripts/ci_no_test_policy.py and .github/workflows/test.yml,As a reviewer I can reject risky code or workflow changes without test updates,Policy fails contract changes that omit matching tests while allowing metadata-only releases,CI policy tests available,python -m pytest src/tests/test_ci_classifier.py -q,Tested Pass,CI classifier suite covers no-test policy contract files and release metadata exceptions.,,,,,2026-06-23,Validated by focused pytest in this tracker slice.
+MAINT-005,Maintainer,Required CI aggregate,scripts/ci_required.py,scripts/ci_required.py and .github/workflows/test.yml,As a branch maintainer I can trust the required CI summary,Aggregate rejects failed missing or wrongly skipped required jobs and allows documented conditional skips,CI required tests available,python -m pytest src/tests/test_ci_classifier.py -q,Tested Pass,CI classifier suite covers required job dependency success failure and conditional skip cases.,,,,,2026-06-23,Validated by focused pytest in this tracker slice.
+MAINT-006,Maintainer,CI preflight gate,scripts/ci_preflight.py,scripts/ci_preflight.py and scripts/ci_classifier.py,As a contributor I can run the same preflight logic locally that CI uses,Preflight classifies changes then emits the exact docs graph browser package and similarity gates required,Repo checkout with git available,Run scripts/ci_preflight.py against representative changed files,Tested Pass,"select_checks(base_ref='origin/main', files=['README.md','docs/index.md'], profile='quick') returned whitespace repo stats and docs strict build.",,,,,2026-06-23,Validated through the script's public selection seam without launching expensive full preflight.
+MAINT-007,Maintainer,Clean host contract script,scripts/clean_host_contract.py,scripts/clean_host_contract.py and .github/workflows/clean-host-contract.yml,As a new installer I can smoke ctx on a clean host,Script builds a clean venv installs ctx and runs init scan harness and monitor checks,Network and clean temp venv available,GitHub clean-host contract or local script smoke,Tested Pass,Clean host contract job passed inside PR #195 required checks.,,,,,2026-06-23,Workflow evidence covers the script path.
+MAINT-008,Maintainer,Dashboard smoke script,scripts/dashboard_smoke.py,scripts/dashboard_smoke.py,As a maintainer I can smoke a running monitor before release,Script probes an already running ctx-monitor base URL and checks key pages/APIs with optional warmup,Monitor running or fake HTTP fixture available,python -m pytest src/tests/test_dashboard_smoke.py -q,Tested Pass,Dashboard smoke test suite covers route probing warmup and failure reporting for a supplied base URL.,,,,,2026-06-29,Corrected wording from starts-or-probes to probes-running-monitor; ctx-monitor startup is tracked separately by CLI-042.
+MAINT-009,Maintainer,Graph artifact guard,scripts/graph_artifact_guard.py,scripts/graph_artifact_guard.py,As a maintainer I can prevent huge graph artifacts from bloating local Git state,Guard parks unparks and prunes graph artifacts safely without deleting unrelated files,Graph artifact fixture available,python -m pytest src/tests/test_graph_artifact_guard.py -q,Tested Pass,Graph artifact guard suite covers park unpark prune and explicit git prune safety.,,,,,2026-06-23,Validated by focused pytest in this tracker slice.
+MAINT-010,Maintainer,Overlay wiki entities,scripts/overlay_wiki_entities.py,scripts/overlay_wiki_entities.py,As a graph maintainer I can apply curated entity overlays to the wiki artifact,Script overlays entity pages and rebuilds dashboard index without corrupting packed wiki structure,Overlay fixture available,python -m pytest src/tests/test_overlay_wiki_entities.py -q,Tested Pass,Overlay wiki entities tests cover page generation replacements and CLI help.,,,,,2026-06-23,Validated by focused pytest in this tracker slice.
+MAINT-011,Maintainer,Full wiki tar repacker,scripts/pack_full_wiki_tar.py,scripts/pack_full_wiki_tar.py,As a maintainer I can ship a packed full LLM-wiki artifact without huge expanded fanout,Repacker moves high-fanout pages into wiki packs omits raw originals and is idempotent,Wiki tar fixture available,python -m pytest src/tests/test_pack_full_wiki_tar.py -q,Tested Pass,Pack full wiki tar tests cover packed wiki output original omission and idempotent repack.,,,,,2026-06-23,Validated by focused pytest in this tracker slice.
+MAINT-012,Maintainer,SkillSpector wiki pruner,scripts/prune_skillspector_wiki.py,scripts/prune_skillspector_wiki.py,As a maintainer I can prune low-value SkillSpector wiki noise before shipping,Script builds pruned artifacts in dry-run/apply modes while preserving required catalog metadata,Prune fixture available,python -m pytest src/tests/test_prune_skillspector_wiki.py -q,Tested Pass,Prune SkillSpector wiki tests cover dry-run apply and artifact rewrite behavior.,,,,,2026-06-23,Validated by focused pytest in this tracker slice.
+MAINT-013,Maintainer,Hugging Face sync script,scripts/sync_huggingface.py,scripts/sync_huggingface.py and .github/workflows/huggingface-sync.yml,As a Hugging Face visitor I get a clean repo-card snapshot without ignored local artifacts,Script exports tracked files adds repo-card metadata validates graph artifacts and removes stale remote files,HF token or fake API available,python -m pytest src/tests/test_huggingface_sync.py -q,Tested Pass,Hugging Face sync tests cover metadata wrapping stale remote cleanup and hardened workflow contract.,,,,,2026-06-23,Validated by focused pytest in this tracker slice.
+MAINT-014,Maintainer,Similarity threshold tuner,scripts/tune_similarity_thresholds.py,scripts/tune_similarity_thresholds.py,As a graph maintainer I can calibrate similarity thresholds against fixtures,Tuner sweeps threshold settings and reports quality metrics without mutating graph artifacts,Similarity fixture corpus available,Run tuner against fixture corpus,Tested Pass,python scripts/tune_similarity_thresholds.py completed and printed near/distinct/adversarial score distributions plus threshold sweep.,,,,,2026-06-23,Validated with current fixture corpus; unauthenticated HF warning did not block local cached model load.
+PUBLIC-001,Docs,Public catalog search JavaScript,docs/assets/javascripts/catalog.js,docs/assets/javascripts/catalog.js and docs/catalog.md,As a GitHub Pages visitor I can filter catalog tiles without a local dashboard,JavaScript wires input and checkbox filters and updates visible catalog cards/counts client-side,Docs assets available,python -m pytest src/tests/test_docs_catalog_page.py -q,Tested Pass,Docs catalog page tests verify script inclusion input listener and public non-local links.,,,,,2026-06-23,Validated by focused pytest in this tracker slice.
+PUBLIC-002,Docs,Public repo stats refresh JavaScript,docs/assets/javascripts/repo-stats-refresh.js,docs/assets/javascripts/repo-stats-refresh.js and mkdocs.yml,As a docs visitor I see current repo stats when GitHub allows client refresh,JavaScript is included by MkDocs and degrades safely when live repo stats cannot be fetched,Docs assets available,python -m pytest src/tests/test_docs_repo_stats.py -q,Tested Pass,Docs repo stats tests verify MkDocs includes the script and the script has the expected refresh behavior.,,,,,2026-06-23,Validated by focused pytest in this tracker slice.

docs/skill-router/index.md

@@ -8,8 +8,7 @@ skills/agents/MCP recommendation layer can be used by that host.
 ## Problem
 
 Every loaded skill, agent, and MCP server costs tokens, attention, and tool
-surface area. Most sessions need a small top-scored bundle from the 91K+ skills,
-460+ agents, and 10K+ MCP servers in the shipped graph, not the whole inventory.
+surface area. Most sessions need a small top-scored bundle from the 68,494 skills, 467 agents, and 10,790 MCP servers in the shipped graph, not the whole inventory.
 Loading too much:
 
 - wastes context on irrelevant instructions,

docs/telemetry.md

@@ -0,0 +1,454 @@
+# Enterprise Telemetry
+
+ctx records privacy-first operational telemetry for API, MCP, CLI, core-tool, and
+runtime lifecycle boundaries. The default mode is local and redacted: events are
+written to `~/.ctx/telemetry/events.jsonl`, metric points are written separately
+to `~/.ctx/telemetry/metrics.jsonl`, raw prompts and queries are hashed or
+removed, and network export is disabled unless an operator explicitly enables it
+or runs an export.
+
+## Event Shape
+
+Events use the `ctx.telemetry.v1` envelope and OpenTelemetry-style naming:
+
+- `ctx.api.recommend_bundle`
+- `ctx.mcp.request`
+- `ctx.core.recommend_bundle`
+- `ctx.runtime_lifecycle.record`
+- `ctx.cli.run`
+- `ctx.cli.resume`
+
+Outcome and dimensions live in attributes such as `otel.status_code`,
+`ctx.operation`, `ctx.tool.name`, `ctx.result.count`, and hashed identifiers like
+`ctx.query.hash`, `ctx.slug.hash`, or `ctx.session.hash`.
+
+Every recorded event gets a generated OpenTelemetry-compatible `trace_id` and
+`span_id` when the caller does not provide one. OTLP export maps those to the
+log record `traceId` and `spanId` fields and also includes ctx release
+provenance as `ctx.version`.
+
+## Metric Shape
+
+Metrics use the `ctx.telemetry.metrics.v1` envelope and the same local redaction
+rules as events. `record_counter()` writes monotonic counter points and
+`record_histogram()` writes histogram observations. OTLP export maps counters to
+delta `sum` metrics and observations to delta `histogram` metrics under
+`resourceMetrics`.
+
+Metrics use a separate spool, checkpoint, and status file:
+
+- `~/.ctx/telemetry/metrics.jsonl`
+- `~/.ctx/telemetry/metrics.jsonl.export-checkpoint.json`
+- `~/.ctx/telemetry/metrics.jsonl.export-status.json`
+
+Metric checkpointing is independent from event/log checkpointing, so replaying
+or repairing one signal does not advance the other.
+
+## Privacy Defaults
+
+The shipped config keeps telemetry local:
+
+```json
+{
+  "telemetry": {
+    "enabled": true,
+    "mode": "local_redacted",
+    "path": "~/.ctx/telemetry/events.jsonl",
+    "export": {
+      "enabled": false,
+      "sink": "otlp_http",
+      "otlp": {
+        "endpoint": "http://localhost:4318/v1/logs",
+        "allowed_hosts": []
+      }
+    },
+    "metrics": {
+      "enabled": true,
+      "path": "~/.ctx/telemetry/metrics.jsonl",
+      "export": {
+        "enabled": false,
+        "sink": "otlp_http",
+        "path": "~/.ctx/telemetry/exported-metrics.jsonl",
+        "otlp": {
+          "endpoint": "http://localhost:4318/v1/metrics",
+          "allowed_hosts": []
+        }
+      }
+    },
+    "privacy": {
+      "store_raw_inputs": false,
+      "hash_identifiers": true,
+      "hash_salt_env": "CTX_TELEMETRY_HASH_SALT",
+      "hash_salt_path": "~/.ctx/telemetry/hash-salt"
+    },
+    "retention": {
+      "enabled": true,
+      "status_path": "~/.ctx/telemetry/retention-status.json",
+      "min_keep_records": 1000,
+      "drop_malformed": false,
+      "events": {
+        "max_age_days": 90,
+        "max_records": 100000
+      },
+      "metrics": {
+        "max_age_days": 30,
+        "max_records": 200000
+      }
+    }
+  }
+}
+```
+
+`local_redacted` removes or hashes raw input fields such as `query`, `prompt`,
+`tool_input`, `stdout`, `stderr`, paths, repo names, and secrets. The only
+accepted modes are `local_redacted`, `disabled`, `off`, and `none`; unknown modes
+fail closed instead of emitting raw fields.
+
+Local JSONL records retain the top-level `session_id` field for compatibility
+with existing local-only workflows, but they also include a salted
+`session_hash`. Remote OTLP export sends `ctx.session.hash` and never sends the
+raw session id, including when exporting legacy local records that predate
+`session_hash`. Manual `local_jsonl` export preserves the same local envelope,
+so treat exported JSONL as local-sensitive if session ids are present.
+
+Identifier hashes are salted by default. ctx first checks the
+`CTX_TELEMETRY_HASH_SALT` environment variable, then any configured
+`privacy.hash_salt`, then an owner-only local salt file at
+`~/.ctx/telemetry/hash-salt`. Set `CTX_TELEMETRY_HASH_SALT` per tenant or
+deployment when multiple hosts need to correlate the same redacted identifiers.
+Do not commit a literal `privacy.hash_salt` into shared source control.
+
+## Manual Export
+
+Use `ctx-telemetry-export` to export an existing local spool without changing
+the default privacy posture.
+
+Export to another JSONL file:
+
+```bash
+ctx-telemetry-export \
+  --sink local_jsonl \
+  --output /var/log/ctx/exported-events.jsonl
+```
+
+Export to an OpenTelemetry Collector logs endpoint:
+
+```bash
+ctx-telemetry-export \
+  --sink otlp_http \
+  --otlp-endpoint https://collector.example:4318/v1/logs \
+  --otlp-allowed-host collector.example
+```
+
+Remote OTLP endpoints must use `https://` and their host must be listed in
+`telemetry.export.otlp.allowed_hosts`, or provided for a one-off command with
+`--otlp-allowed-host`. Plain `http://` is accepted only for loopback collectors
+(`localhost`, `127.0.0.1`, or `[::1]`). Literal metadata/link-local, multicast,
+unspecified, and reserved IP endpoints are rejected even when a command-line or
+`OTEL_EXPORTER_OTLP_*` endpoint override is used. Redirects are refused instead
+of revalidating a second network target.
+
+Preview the event count without exporting:
+
+```bash
+ctx-telemetry-export --dry-run --json
+```
+
+Export metrics with the same CLI:
+
+```bash
+ctx-telemetry-export \
+  --signal metrics \
+  --sink otlp_http \
+  --otlp-endpoint https://collector.example:4318/v1/metrics \
+  --otlp-allowed-host collector.example
+```
+
+Export metrics from Python:
+
+```python
+from pathlib import Path
+
+from ctx.telemetry import export_metrics, record_counter, record_histogram
+
+record_counter("ctx.api.requests", attributes={"ctx.source": "api"})
+record_histogram("ctx.api.duration", value=42.0, unit="ms")
+
+result = export_metrics(
+    Path("~/.ctx/telemetry/metrics.jsonl"),
+    config={
+        "metrics": {
+            "enabled": True,
+            "export": {
+                "enabled": True,
+                "sink": "otlp_http",
+                "otlp": {
+                    "endpoint": "https://collector.example:4318/v1/metrics",
+                    "allowed_hosts": ["collector.example"],
+                },
+            },
+        }
+    },
+)
+```
+
+Metrics export uses its own checkpoint and status files next to
+`metrics.jsonl`, and the `OTEL_EXPORTER_OTLP_METRICS_ENDPOINT` environment
+variable overrides the configured metrics endpoint. `OTEL_EXPORTER_OTLP_ENDPOINT`
+is also supported and automatically appends `/v1/metrics` for metric exports.
+
+Successful exports advance an owner-only checkpoint file. By default it lives
+next to the spool as `events.jsonl.export-checkpoint.json`, so later runs export
+only new events. Use `--checkpoint /path/to/checkpoint.json` to choose another
+checkpoint file, or `--all` when you intentionally want to replay the full spool.
+
+The command exits non-zero if the selected exporter fails. Use
+`--fail-on-degraded` when running from cron or CI and you also want malformed
+pending records or checkpoint anomalies to fail the command. Real export
+attempts also write an owner-only status file next to the spool as
+`events.jsonl.export-status.json`. It records an explicit `status` of `ok`,
+`noop`, `failed`, or `degraded`, plus the sink, destination hash,
+attempted/exported/failed counts, checkpoint-before/checkpoint-after ids,
+whether the checkpoint advanced, malformed pending record counts, and the last
+exporter error kind.
+
+`degraded` means the exporter delivered the well-formed events it could, but ctx
+detected a condition an operator should inspect, such as malformed pending local
+records or a checkpoint id that no longer appears in the spool. ctx does not
+advance the checkpoint past malformed pending records; retrying after repair may
+re-export already delivered events, so downstream collectors should deduplicate
+by `event_id`.
+
+## Retention
+
+Retention is explicit operator action, never a background deletion. Plan first:
+
+```bash
+ctx-telemetry-retention plan --signal all --json
+```
+
+Then enforce:
+
+```bash
+ctx-telemetry-retention enforce --signal all --json
+```
+
+Malformed JSONL records are preserved by default so an operator can inspect and
+repair them. Use `--drop-malformed` only when the malformed lines have already
+been preserved elsewhere. Every enforcement run writes an owner-only status file
+at `~/.ctx/telemetry/retention-status.json`.
+
+## Continuous Export
+
+To export every new event as it is recorded, enable the exporter in config. User
+overrides live at `~/.claude/skill-system-config.json`.
+
+```json
+{
+  "telemetry": {
+    "export": {
+      "enabled": true,
+      "sink": "otlp_http",
+      "otlp": {
+        "endpoint": "https://collector.example:4318/v1/logs",
+        "allowed_hosts": ["collector.example"],
+        "service_name": "ctx",
+        "service_namespace": "ctx",
+        "deployment_environment": "prod"
+      }
+    }
+  }
+}
+```
+
+`OTEL_EXPORTER_OTLP_LOGS_ENDPOINT` overrides the configured logs endpoint.
+`OTEL_EXPORTER_OTLP_ENDPOINT` is also supported and automatically appends
+`/v1/logs`.
+
+## Collector Examples
+
+Use an OpenTelemetry Collector between ctx and the observability backend. That
+keeps ctx vendor-neutral and gives enterprise operators one place to add
+batching, retry, TLS, auth, routing, and backend-specific exporters.
+
+Local loopback smoke config:
+
+```yaml
+receivers:
+  otlp:
+    protocols:
+      http:
+        endpoint: 127.0.0.1:4318
+
+processors:
+  batch:
+
+exporters:
+  debug:
+    verbosity: detailed
+
+service:
+  pipelines:
+    logs:
+      receivers: [otlp]
+      processors: [batch]
+      exporters: [debug]
+    metrics:
+      receivers: [otlp]
+      processors: [batch]
+      exporters: [debug]
+```
+
+Run it, then point ctx at the local Collector:
+
+```bash
+otelcol --config=file:ctx-otel-local.yaml
+
+ctx-telemetry-export \
+  --sink otlp_http \
+  --otlp-endpoint http://127.0.0.1:4318/v1/logs \
+  --otlp-allowed-host 127.0.0.1
+```
+
+For production, keep ctx pointed at a tenant-approved HTTPS Collector and
+allow-list only that host:
+
+```json
+{
+  "telemetry": {
+    "export": {
+      "enabled": true,
+      "sink": "otlp_http",
+      "otlp": {
+        "endpoint": "https://otel-gateway.example.com:4318/v1/logs",
+        "allowed_hosts": ["otel-gateway.example.com"],
+        "service_name": "ctx",
+        "service_namespace": "ctx",
+        "deployment_environment": "prod"
+      }
+    },
+    "metrics": {
+      "export": {
+        "enabled": true,
+        "sink": "otlp_http",
+        "otlp": {
+          "endpoint": "https://otel-gateway.example.com:4318/v1/metrics",
+          "allowed_hosts": ["otel-gateway.example.com"]
+        }
+      }
+    }
+  }
+}
+```
+
+Production Collector sketch:
+
+```yaml
+receivers:
+  otlp:
+    protocols:
+      http:
+        endpoint: 0.0.0.0:4318
+
+processors:
+  memory_limiter:
+    check_interval: 5s
+    limit_mib: 512
+  batch:
+
+exporters:
+  otlphttp/vendor:
+    endpoint: https://observability-vendor.example.com/otlp
+    headers:
+      Authorization: ${env:OTEL_VENDOR_AUTH_HEADER}
+
+service:
+  pipelines:
+    logs:
+      receivers: [otlp]
+      processors: [memory_limiter, batch]
+      exporters: [otlphttp/vendor]
+    metrics:
+      receivers: [otlp]
+      processors: [memory_limiter, batch]
+      exporters: [otlphttp/vendor]
+```
+
+Keep the Collector's public listener and upstream exporter TLS/auth policy under
+the enterprise network owner. ctx still rejects non-loopback plaintext OTLP
+endpoints before it sends data.
+
+## Dashboards And Alerts
+
+Build the first production dashboard from the stable ctx attributes instead of
+raw message text:
+
+| Panel | Query dimensions |
+|---|---|
+| Request volume | count logs grouped by `event.name`, `ctx.source`, `ctx.operation` |
+| Error rate | count logs where `otel.status_code = ERROR`, grouped by `ctx.source` |
+| Exception fingerprints | count logs grouped by `ctx.exception.fingerprint`, `ctx.exception.type` |
+| API latency | histogram metric `ctx.api.duration` by `ctx.operation` |
+| CLI/runtime usage | count logs for `ctx.cli.run`, `ctx.cli.resume`, `ctx.runtime_lifecycle.record` |
+| Exporter health | status JSON fields `status`, `malformed_pending_count`, `last_error_kind` |
+| Spool growth | `event_count`, `malformed_count`, and checkpoint age from `/api/status.json` |
+
+Recommended enterprise alerts:
+
+| Alert | Condition |
+|---|---|
+| `CtxTelemetryExporterFailed` | latest export status is `failed` for 2 consecutive runs |
+| `CtxTelemetryExporterDegraded` | latest export status is `degraded` or `malformed_pending_count > 0` |
+| `CtxTelemetrySilent` | telemetry is enabled but no new event appears during an expected active window |
+| `CtxTelemetrySpoolGrowing` | local spool count grows while checkpoint id stays unchanged |
+| `CtxTelemetryUnhandledExceptions` | new `ctx.exception.fingerprint` appears in prod |
+
+For local dashboard checks, use:
+
+```bash
+ctx-monitor serve
+curl -fsS http://127.0.0.1:8765/api/status.json
+```
+
+The monitor surfaces telemetry health, spool counts, malformed counts,
+checkpoint presence, and exporter status without rendering event payloads.
+
+## Operator Runbook
+
+1. Confirm config posture:
+   `ctx-telemetry-export --dry-run --json`.
+2. Inspect dashboard health:
+   `curl -fsS http://127.0.0.1:8765/api/status.json`.
+3. Inspect exporter status:
+   `cat ~/.ctx/telemetry/events.jsonl.export-status.json` and
+   `cat ~/.ctx/telemetry/metrics.jsonl.export-status.json`.
+4. Repair malformed local records by preserving the original file, removing only
+   invalid JSON lines, and rerunning export with `--fail-on-degraded`.
+5. Replay intentionally with `--all` only after confirming the downstream
+   backend deduplicates by `event_id`.
+6. Rotate tenant salts only during a planned privacy reset; rotation breaks
+   cross-run correlation for hashed identifiers and exception fingerprints.
+
+## Verification
+
+For a local smoke test, run:
+
+```bash
+ctx-telemetry-export --dry-run --json
+ctx-telemetry-export --sink local_jsonl --output /tmp/ctx-telemetry-export.jsonl --json
+ctx-telemetry-export --all --sink local_jsonl --output /tmp/ctx-telemetry-replay.jsonl --json
+```
+
+The exported JSONL should contain the same event ids as the local spool and no
+raw prompt, query, path, repo, stdout, stderr, token, or secret values.
+
+Inspect the durable exporter status after a real run:
+
+```bash
+cat ~/.ctx/telemetry/events.jsonl.export-status.json
+```
+
+The ctx monitor also surfaces the same local health summary on `/status` and
+`/api/status.json`: capture enabled/mode, spool event and malformed counts, the
+latest event name/outcome, checkpoint presence, and the last exporter status.
+The monitor does not render telemetry payloads.

graph/README.md

@@ -4,15 +4,16 @@ This directory ships the pre-built ctx LLM-wiki and knowledge graph.
 
 Current snapshot:
 
-- **102,928 graph nodes**
-- **2,913,960 graph edges**
+- **79,958 graph nodes**
+- **1,778,069 graph edges**
 - **52 Louvain communities**
-- **91,464 skill entity pages**; **89,465** have hydrated catalog bodies
+- **68,494 skill entity pages**; **67,024** have hydrated catalog bodies
 - **467 agent pages**
 - **10,790 MCP server pages**
 - **207 harness pages**
-- **89,465 hydrated `SKILL.md` bodies**
-- **28,612 long skill bodies converted through the micro-skill gate**
+- **67,024 hydrated imported `SKILL.md` bodies**
+- Long skill bodies are kept behind the configured micro-skill line gate; the
+  shipped tarball excludes raw `SKILL.md.original` backups.
 
 The runtime recommendation paths use this graph in two ways:
 
@@ -24,8 +25,9 @@ The runtime recommendation paths use this graph in two ways:
 | File | Contents |
 |---|---|
 | `wiki-graph-runtime.tar.gz` | Fast install artifact used by default `ctx-init --graph`: `graphify-out/*`, the skill index, 207 harness pages, wiki index files, and Obsidian metadata needed for recommendations and harness dry-runs without expanding every entity page |
-| `wiki-graph.tar.gz` | Full LLM-wiki: entity pages, converted skill bodies, mirrored agent bodies, concept pages, `graphify-out/graph.json`, `graph-delta.json`, export manifest, communities, skill indexes, and Obsidian metadata |
-| Skill catalog gzip | Compressed skill index for the 89,465 body-backed skill entries shipped in the wiki |
+| `wiki-graph.tar.gz` | Full LLM-wiki: entity pages, converted skill bodies, mirrored agent bodies, concept pages, `graphify-out/graph.json`, `graph-delta.json`, export manifest, communities, skill indexes, SkillSpector stamps, and Obsidian metadata |
+| `skillspector-audit.jsonl.gz` | Compact per-skill audit records produced by a ctx-run static `--no-llm` pass with [NVIDIA SkillSpector](https://github.com/NVIDIA/SkillSpector). This is not NVIDIA endorsement or certification. The same gzip is embedded in `wiki-graph.tar.gz` as `security/skillspector-audit.jsonl.gz`. |
+| Skill catalog gzip | Compressed skill index for the 67,024 body-backed skill entries shipped in the wiki |
 | `communities.json` | Current Louvain community export |
 | `entity-overlays.jsonl` | Release overlay for first-class entities added after the base graph export; installed beside `graphify-out/graph.json` by `ctx-init --graph` |
 | `graphify-out/dashboard-neighborhoods.sqlite3` inside both tarballs | Compact top-neighbor index used by `ctx-monitor` so `/api/graph/<slug>.json` does not cold-parse the 818 MiB graph JSON |
@@ -49,6 +51,30 @@ harness pages needed by `ctx-harness-install --dry-run`. Use
 `ctx-init --graph --graph-install-mode full` or manual full extraction when you
 want local wiki browsing, Obsidian, or the converted skill body tree.
 
+## Modular Pack Model
+
+The installed graph/wiki can be maintained as immutable base packs plus small
+overlay packs. The merged view is intended to behave like the old single graph:
+dashboard, search, recommendations, and harness setup still see one catalog,
+but local adds, updates, and deletes no longer need to rewrite the full graph
+and full wiki tarball.
+
+Active pack layout:
+
+```text
+~/.claude/skill-wiki/
+  graphify-out/packs/base-<export-id>/
+  graphify-out/packs/overlay-<id>/
+  wiki-packs/base-<export-id>/
+  wiki-packs/overlay-<id>/
+```
+
+Overlay packs carry changed nodes, edges, wiki page upserts, and tombstones.
+Periodic compaction merges the active base plus overlays into a new staged base
+pack set. The full release artifact is still rebuilt explicitly for published
+snapshots, but normal local updates should use overlays and the SQLite graph
+store refresh path.
+
 ## What Is Inside `wiki-graph.tar.gz`
 
 - `entities/skills/` - all skill entity pages
@@ -59,6 +85,7 @@ want local wiki browsing, Obsidian, or the converted skill body tree.
 - `converted-agents/` - mirrored agent bodies
 - `concepts/` - community concept pages
 - `external-catalogs/` - machine-readable skill index, summary, and coverage metadata
+- `security/skillspector-audit.jsonl.gz` - per-skill SkillSpector audit records
 - `graphify-out/graph.json` - NetworkX node-link graph
 - `graphify-out/graph-delta.json` - delta export for the latest graph generation
 - `graphify-out/graph-export-manifest.json` - export manifest tying graph, delta, communities, and report to one generation
@@ -111,14 +138,14 @@ For release-count validation, pin the exact snapshot numbers:
 
 ```bash
 python src/validate_graph_artifacts.py --deep \
-  --expected-nodes 102928 \
-  --expected-edges 2913960 \
-  --expected-semantic-edges 1683193 \
+  --expected-nodes 79958 \
+  --expected-edges 1778069 \
+  --expected-semantic-edges 1088763 \
   --expected-harness-nodes 207 \
-  --expected-skills-sh-nodes 89471 \
-  --expected-skills-sh-catalog-entries 89465 \
-  --expected-skills-sh-converted 89465 \
-  --expected-skill-pages 91464 \
+  --expected-skills-sh-nodes 67028 \
+  --expected-skills-sh-catalog-entries 67024 \
+  --expected-skills-sh-converted 67024 \
+  --expected-skill-pages 68494 \
   --expected-agent-pages 467 \
   --expected-mcp-pages 10790 \
   --expected-harness-pages 207
@@ -190,6 +217,42 @@ It reports precision/recall, top-k agreement, score deltas, and bad examples;
 the release gate fails when recall at the largest requested top-k is below the
 overlap floor.
 
+To compact local graph/wiki overlays into a new coordinated base pack set:
+
+```bash
+ctx-pack-compact compact \
+  --wiki-path ~/.claude/skill-wiki \
+  --base-export-id <new-export-id> \
+  --staging-dir /tmp/ctx-pack-stage \
+  --json
+```
+
+Then validate and promote the staged graph and wiki packs together:
+
+```bash
+ctx-pack-compact promote \
+  --wiki-path ~/.claude/skill-wiki \
+  --staged-graph-packs-dir /tmp/ctx-pack-stage/graph-packs \
+  --staged-wiki-packs-dir /tmp/ctx-pack-stage/wiki-packs \
+  --json
+```
+
+Promotion requires the top-level `pack-compaction-manifest.json`, matching graph
+and wiki export IDs, valid checksums, non-empty merged graph/wiki contents, and
+entity consistency between known graph nodes and wiki pages. It refreshes
+`graphify-out/graph-store.sqlite3` by default so dashboard graph APIs do not
+fall back to cold-parsing `graph.json`. If you disable that refresh, rebuild and
+validate the store explicitly:
+
+```bash
+ctx-graph-store build \
+  --graph-dir ~/.claude/skill-wiki/graphify-out \
+  --db ~/.claude/skill-wiki/graphify-out/graph-store.sqlite3
+
+ctx-graph-store validate \
+  --db ~/.claude/skill-wiki/graphify-out/graph-store.sqlite3
+```
+
 For release artifact rebuilds:
 
 ```bash
@@ -231,8 +294,21 @@ python src/import_skills_sh_catalog.py \
   --update-wiki-tar
 ```
 
-For a full local wiki repack, write the tarball to the sibling staged path,
-then promote that staged candidate after validation:
+For a full local wiki repack from an existing artifact, use the packed-page
+repacker. It writes `wiki-packs/base-<export-id>/`, removes expanded
+skill/agent/MCP entity pages from the tar member list, and leaves harness pages
+directly available for fast runtime setup:
+
+```bash
+python scripts/pack_full_wiki_tar.py \
+  --source graph/wiki-graph.tar.gz \
+  --target graph/wiki-graph.tar.gz.staged
+python -c "from pathlib import Path; from ctx.core.wiki.artifact_promotion import promote_staged_artifact; from import_skills_sh_catalog import _validate_wiki_tarball_candidate; promote_staged_artifact(Path('graph/wiki-graph.tar.gz.staged'), Path('graph/wiki-graph.tar.gz'), validate=_validate_wiki_tarball_candidate)"
+```
+
+For a full local wiki repack from an expanded `~/.claude/skill-wiki` tree, write
+the tarball to the sibling staged path, then promote that staged candidate after
+validation:
 
 ```bash
 cd ~/.claude/skill-wiki

graph/skills-sh-catalog.json.gz

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:2a7307de2b6ec46ea6ee7b585a4f5bf138b5a4901172109de07eefb55faf4843
-size 11660713
+oid sha256:d1bb927e93d65ef86cdbc6d68c7f57511d64c8f13026e8193287a9c4ca6f5815
+size 10763626

graph/skillspector-audit.jsonl.gz

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7b1b7627317c516ca1b2a9eb383750777d34e3bb58b3d99316ee401b66a6588a
+size 4932061

graph/wiki-graph-runtime.tar.gz

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:334fb19bace3fd6e4b92087850f17297fb248032957d123f3f1432dfde2e36c0
-size 175773376
+oid sha256:993fc08377fdb09edcff4414c59b10fc121189b4a161bf796e3f8f6600907bb1
+size 122141091

graph/wiki-graph-stats.json

@@ -0,0 +1,29 @@
+{
+  "schema_version": 1,
+  "artifact": {
+    "path": "graph/wiki-graph.tar.gz",
+    "size": 296113770,
+    "sha256": "d051d4f21208abe3e73975a9c30650150138d88919c27979d725be936a6ea10a"
+  },
+  "source": "validated graph artifact release contract",
+  "counts": {
+    "nodes": 79958,
+    "edges": 1778069,
+    "semantic_edges": 1088763,
+    "skills": 68494,
+    "agents": 467,
+    "mcps": 10790,
+    "harnesses": 207,
+    "communities": 52,
+    "skills_sh_entries": 67024,
+    "skills_sh_bodies": 67024,
+    "tag_edges": 474837,
+    "token_edges": 280275,
+    "hydrated_incident_edges": 1516298,
+    "hydrated_semantic_incident_edges": 911922,
+    "cross_skill_agent_edges": 52382,
+    "cross_skill_mcp_edges": 30295,
+    "cross_agent_mcp_edges": 229,
+    "harness_edges": 5063
+  }
+}

graph/wiki-graph.tar.gz

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:91b30795e7d200cf31a62a8749969d12658f5f74636d2de06d6b2b24b393c12f
-size 457545675
+oid sha256:d051d4f21208abe3e73975a9c30650150138d88919c27979d725be936a6ea10a
+size 296113770