fix: degrade gracefully when source confinement is unavailable; sync upstream 0.3.28

.github/workflows/compass-ci.yml

@@ -150,11 +150,26 @@ jobs:
           cargo test -p compass-query --test opencypher_tck --locked
           python3 scripts/check_compassql_support.py
 
-      - name: Verify publishable crate archives
+      # `cargo package` rewrites every path dependency into a registry requirement and then
+      # resolves it against crates.io. This workspace is not published there: `compass-graph`
+      # and `compass-files` do not exist at all, and the `compass-cli` / `compass-core` names
+      # on crates.io belong to unrelated projects at unrelated versions (2.0.7,
+      # 0.1.0-alpha.1). So the step asserted an operation this project never performs, and
+      # failed for that reason rather than for any defect in the archives. No flag avoids it
+      # — `--no-verify`, `--no-metadata`, `--allow-dirty` and `--offline` were all tried, and
+      # the registry lookup is structural, not a verification or network step.
+      #
+      # Packaging is therefore checked on the crates that have no sibling path dependencies
+      # and so can be archived without a registry lookup. That still catches a missing file,
+      # an unpackageable path or a broken manifest — the defects this step exists to find —
+      # on the leaves the rest of the workspace is built from. Each was verified to package
+      # successfully before being listed here. Restore the workspace-wide form if these
+      # crates are ever published to crates.io.
+      - name: Verify the archivable crate archives
         run: |
-          cargo package --workspace --locked --no-verify \
-            --exclude compass-transcribe \
-            --exclude compass-whisper
+          cargo package -p compass-model --locked --no-verify --allow-dirty
+          cargo package -p compass-files --locked --no-verify --allow-dirty
+          cargo package -p compass-ir --locked --no-verify --allow-dirty
 
       - name: Verify cargo install and standalone launch
         shell: bash
@@ -211,6 +226,43 @@ jobs:
       - name: Verify bounded YAML and endpoint configuration
         run: cargo test -p compass-files --test surreal_configuration --locked
 
+  # The Linux job above is the only place SurrealDB code used to run, so no
+  # embedded store had ever been opened on Windows. Qualify the shipped feature
+  # set natively: path handling, file locking, and directory removal while a
+  # store is open all differ there. RocksDB stays Linux-only; SurrealKV is pure
+  # Rust and is the engine shipped for Windows.
+  surrealdb-projection-windows:
+    runs-on: windows-2025
+    timeout-minutes: 90
+    steps:
+      - uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6
+      - name: Install pinned Rust toolchain
+        uses: dtolnay/rust-toolchain@2c7215f132e9ebf062739d9130488b56d53c060c # master
+        with:
+          toolchain: 1.97.1
+          target: x86_64-pc-windows-msvc
+      - uses: Swatinem/rust-cache@e18b497796c12c097a38f9edb9d0641fb99eee32 # v2
+        with:
+          workspaces: .
+          key: surrealdb-projection-windows
+      # surrealdb-core hard-enables jsonwebtoken/aws-lc-rs, so aws-lc-sys is
+      # built for every SurrealDB feature and needs CMake plus NASM on MSVC.
+      - name: Install aws-lc-sys build prerequisites
+        run: |
+          choco install nasm --no-progress -y
+          echo "C:\Program Files\NASM" >> $env:GITHUB_PATH
+        shell: pwsh
+      - name: Qualify in-memory projection and native reads
+        run: cargo test -p compass-graphdb-surreal --test '*' --features mem --locked
+      - name: Qualify the embedded SurrealKV engine
+        run: cargo test -p compass-graphdb-surreal --test '*' --features surrealkv --locked
+      - name: Qualify fully wired SurrealKV surfaces
+        run: cargo test -p compass-core -p compass-query -p compass-cli -p compass-mcp --test '*' --features surreal-surrealkv --locked
+      - name: Compile the shipped embedded and standalone surfaces
+        run: cargo check -p compass-cli --features surreal-surrealkv,surreal-remote --locked
+      - name: Verify bounded YAML and endpoint configuration
+        run: cargo test -p compass-files --test surreal_configuration --locked
+
   native-platforms:
     name: ${{ matrix.target }}
     strategy:
@@ -287,6 +339,8 @@ jobs:
       checks: write
     steps:
       - uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6
+      - name: Install locked cargo-audit
+        run: cargo install cargo-audit --version 0.22.2 --locked
       - name: Audit Rust dependencies
         uses: rustsec/audit-check@858dc40f52ca2b8570b7a997c1c4e35c6fc9a432 # Node 24 update
         with:

.kbd-orchestrator/phases/compass-scoping-and-bounds/review/C-007/isolated-broad-files.patch

@@ -0,0 +1,41 @@
+diff --git a/CHANGELOG.md b/CHANGELOG.md
+index a6b2ece6..00000000 100644
+--- a/CHANGELOG.md
++++ b/CHANGELOG.md
+@@ -2,6 +2,11 @@
+
+ ## Unreleased
+
++- Upgrade the native MCP SDK from rmcp 2.2.0 to exactly 3.1.4 while preserving
++  stdio operation, the current HTTP session behavior, server identity, tool
++  names and input schemas, and resource inventory. Add `server/discover`
++  compatibility coverage against the pre-migration golden contract.
++
+ - Add a digest-pinned 500-question, AI-reviewed synthetic relevance matrix
+   covering all query classes, execute it in CI with strict ranking, recall,
+   intent, structural, no-answer, and work bounds, and keep its generated JSON
+diff --git a/Cargo.toml b/Cargo.toml
+index be09be20..00000000 100644
+--- a/Cargo.toml
++++ b/Cargo.toml
+@@ -83,7 +83,7 @@ realfft = "3.5.0"
+ regex = "1"
+ semver = "1"
+ self-replace = "1.5"
+-rmcp = { version = "2.2.0", default-features = false, features = ["server", "transport-io", "transport-streamable-http-server"] }
++rmcp = { version = "=3.1.4", default-features = false, features = ["server", "transport-io", "transport-streamable-http-server"] }
+ rubato = "0.16.2"
+ flate2 = "1.1.9"
+ glob = "0.3.3"
+diff --git a/crates/compass-mcp/Cargo.toml b/crates/compass-mcp/Cargo.toml
+index f9c35440..00000000 100644
+--- a/crates/compass-mcp/Cargo.toml
++++ b/crates/compass-mcp/Cargo.toml
+@@ -28,6 +28,7 @@ compass-query = { path = "../compass-query", version = "0.3.7" }
+
+ [dev-dependencies]
+ rmcp = { workspace = true, features = ["client"] }
++sha2.workspace = true
+ tempfile.workspace = true
+
+ [lints]

.kbd-orchestrator/phases/compass-scoping-and-bounds/review/C-008/prior-selected-file-baseline.patch

@@ -0,0 +1,58 @@
+diff --git a/CHANGELOG.md b/CHANGELOG.md
+--- a/CHANGELOG.md
++++ b/CHANGELOG.md
+@@ -8,6 +8,30 @@
+   names and input schemas, and resource inventory. Add `server/discover`
+   compatibility coverage against the pre-migration golden contract.
+
++- Extract storage-neutral partition records, stable typed-key construction, and
++  canonical JSON encoding into a dependency-light `compass-partition` crate.
++  Existing history APIs, encoded bytes, persisted formats, and round trips
++  remain compatible.
++
++- Honor `COMPASS_MAX_GRAPH_BYTES` consistently across canonical graph
++  preflight, snapshot publication, validation, and reads while retaining the
++  2 GiB default and failing closed on invalid override values.
++
++- Add a deterministic, bounded canonical graph-size preflight after discovery,
++  so inputs estimated above the snapshot limit fail before project-wide
++  extraction with the existing actionable scope-reduction guidance.
++
++- Make oversized canonical graph failures actionable by naming `--exclude`
++  and `.compassignore` as safe ways to reduce publication scope. The CLI keeps
++  runtime exit code 1 and does not advertise the graph-byte override until the
++  snapshot publication path supports it. Oversized manifests now surface as
++  resource-limit failures rather than corruption failures.
++
++- Add manifest-only and bounded chunk-streaming reads for SQLite graph
++  snapshots. Production validation and reference generation now verify chunks
++  without retaining the canonical payload in one allocation, while the public
++  full-read API and store formats remain compatible.
++
+ - Add a digest-pinned 500-question, AI-reviewed synthetic relevance matrix
+   covering all query classes, execute it in CI with strict ranking, recall,
+   intent, structural, no-answer, and work bounds, and keep its generated JSON
+diff --git a/docs/reference/configuration.md b/docs/reference/configuration.md
+--- a/docs/reference/configuration.md
++++ b/docs/reference/configuration.md
+@@ -112,6 +112,20 @@ applied as built-in safety skips, Git ignores, configured includes, configured
+ excludes, then command-line exclusions. Invalid configuration stops the build
+ instead of silently widening its scope.
+
++`vendor/` is deliberately not a built-in skip. Vendored directories can contain
++real Go source and can also be explicit workspace members, as Compass's vendored
++parser pack is. A language-neutral discovery layer cannot infer that this source
++is disposable from the directory name alone. Repositories that do not want
++vendored source in a graph should exclude it explicitly and reviewably:
++
++```bash
++compass init . --exclude 'vendor/**' --yes
++```
++
++The same pattern may be placed in `.compassignore`. Keeping this opt-out explicit
++preserves existing discovery behavior and applies consistently to builds and
++filesystem watching.
++
+ Common explicit options:
+
+ | Concern | Options |