deadbyte-mcp 0.15.42 → 0.15.44

package/docs/R67-ALPHA-STATIC-COMPARISON.json

@@ -0,0 +1,205 @@
+{
+  "schema": "deadbyte.r67-competitor-static-compare.v1",
+  "scope": "static npm archives only; do not execute or install competitor",
+  "stable_version": "0.2.52",
+  "alpha_version": "0.3.1-alpha.2",
+  "alpha_tarball_sha256": "faaf3f34f114589c0630ce4eaa7114ecc628ce2030822dfe67feac0e17fedc4b",
+  "stable_compared_files": 121,
+  "alpha_selected_compared_files": 135,
+  "added": 14,
+  "changed": 59,
+  "unchanged": 62,
+  "removed_from_selected_scope": 0,
+  "relevant_changes": [
+    {
+      "path": "handlers/process-handlers.js",
+      "status": "UNCHANGED",
+      "stable_sha256": "9f9f53d3bf322c4dc813cb9fdf0357993fd209620a344a5025507460c99356c1",
+      "alpha_sha256": "9f9f53d3bf322c4dc813cb9fdf0357993fd209620a344a5025507460c99356c1",
+      "delta_bytes": 0
+    },
+    {
+      "path": "handlers/terminal-handlers.js",
+      "status": "UNCHANGED",
+      "stable_sha256": "e0e67f4ed78e421bd42dc438fb48f5994347f14437a5c2516fb9ed197405236d",
+      "alpha_sha256": "e0e67f4ed78e421bd42dc438fb48f5994347f14437a5c2516fb9ed197405236d",
+      "delta_bytes": 0
+    },
+    {
+      "path": "remote-device/desktop-commander-integration.js",
+      "status": "CHANGED",
+      "stable_sha256": "0b198eb1ff897e1bf9156f546f32bfd3987e72157348ff492fee03d1b887436a",
+      "alpha_sha256": "fe0a5965fe077866deae661e38c3dd4a5aa11c0e0892fb57228a948a0cd1f650",
+      "delta_bytes": -293
+    },
+    {
+      "path": "remote-device/device-authenticator.js",
+      "status": "UNCHANGED",
+      "stable_sha256": "b7884d9398135264babe96d3fbaa22bf1300b16e03259cd739ec1d44da84f170",
+      "alpha_sha256": "b7884d9398135264babe96d3fbaa22bf1300b16e03259cd739ec1d44da84f170",
+      "delta_bytes": 0
+    },
+    {
+      "path": "remote-device/device.js",
+      "status": "CHANGED",
+      "stable_sha256": "629b99b96d14baaa237f743cab6861562c722d2aa1bf925f952ece42cb6389ae",
+      "alpha_sha256": "edc2991e00fc604c118982b4b837ec9df8f99f8e58e87393690665a5bdce1372",
+      "delta_bytes": 5198
+    },
+    {
+      "path": "remote-device/diagnostics/device-log.js",
+      "status": "ADDED",
+      "stable_sha256": null,
+      "alpha_sha256": "891e994c5dd3c70ba331d5c1819b39d1c0e91162f9315c3526aaf6a5bc373f51",
+      "delta_bytes": null
+    },
+    {
+      "path": "remote-device/diagnostics/redact.js",
+      "status": "ADDED",
+      "stable_sha256": null,
+      "alpha_sha256": "a84f9654aac58d885fa6cfd60fa063abeaeb96e406cff4fdc4fec206d0baa7c5",
+      "delta_bytes": null
+    },
+    {
+      "path": "remote-device/diagnostics/report.js",
+      "status": "ADDED",
+      "stable_sha256": null,
+      "alpha_sha256": "6a777e6422742e56d09e242eab23a6120370367430a38aadd26f23fc1302cecf",
+      "delta_bytes": null
+    },
+    {
+      "path": "remote-device/diagnostics/upload.js",
+      "status": "ADDED",
+      "stable_sha256": null,
+      "alpha_sha256": "0054d7f6f28e67b2927f22781ab9717770a9112e51cdd24f6549215881b11771",
+      "delta_bytes": null
+    },
+    {
+      "path": "remote-device/remote-channel.js",
+      "status": "CHANGED",
+      "stable_sha256": "4c48a276b53183bb0753baa681d856016a367a1def295af605123036ce827ce0",
+      "alpha_sha256": "29d17eee3a76bdd8d1a95ecd2d8f7e522449289d2c8393486d032acaba64b6fe",
+      "delta_bytes": 2793
+    },
+    {
+      "path": "remote-device/scripts/blocking-offline-update.js",
+      "status": "CHANGED",
+      "stable_sha256": "fcec23e7bcfc15cf22e104d968f4f206d0959b09c31df05e9ef039f7115fed0c",
+      "alpha_sha256": "95055078e2979f7b031c92638f06ab4524eaf73097870730b620e419f6731817",
+      "delta_bytes": 2482
+    },
+    {
+      "path": "remote-device/transport-telemetry.js",
+      "status": "ADDED",
+      "stable_sha256": null,
+      "alpha_sha256": "2c96cbaae3b6671bb2c26f0bf45f6684aa548d3553daafabcfdbc9a93d3b61c5",
+      "delta_bytes": null
+    },
+    {
+      "path": "terminal-manager.js",
+      "status": "CHANGED",
+      "stable_sha256": "d4d0773b79501858be4fd45fcd03066fd98acf8cb969e65f168c89c52ee564c3",
+      "alpha_sha256": "92a97f083a5b650a86dc3ecfd029dd3a371ca7a0636d9d1f93233a2b70a68e41",
+      "delta_bytes": 6564
+    },
+    {
+      "path": "tools/improved-process-tools.js",
+      "status": "CHANGED",
+      "stable_sha256": "702d972ec92424298315a2bc551bbc9b12c337949f62a84410879576d50235fb",
+      "alpha_sha256": "044d378895df493df09f73c87fed42360a71a004cf252f050202d55e157ef803",
+      "delta_bytes": 6408
+    },
+    {
+      "path": "tools/pdf/extract-images.js",
+      "status": "CHANGED",
+      "stable_sha256": "b7830fa8758211bf89ecb9df501293e1856e1672b28dbfec01bc1a84e5adf793",
+      "alpha_sha256": "1030fd05f2542ef263b19b89eac6ee3f212896b05bf63c07a1c73d230f19c2da",
+      "delta_bytes": 275
+    },
+    {
+      "path": "tools/pdf/index.js",
+      "status": "CHANGED",
+      "stable_sha256": "d58afad5e9bb31c86859bc017e7c6c998d2ea83cfefefad8288044e2eb0985dc",
+      "alpha_sha256": "9d7de10bb791a158fae0c61ee48d3d27bd3a623b6d7150335d6b97f71ee287ef",
+      "delta_bytes": 130
+    },
+    {
+      "path": "tools/pdf/lib/pdf2md.js",
+      "status": "CHANGED",
+      "stable_sha256": "fbcff6b076b04240916b37d3969893ee3784c1ee673b32b052f96a3a9ca63ccf",
+      "alpha_sha256": "33aaa8ec3ddf44cdfc95634339fa91ebeb6685042a294421659c3b91dc797892",
+      "delta_bytes": 429
+    },
+    {
+      "path": "tools/pdf/manipulations.js",
+      "status": "CHANGED",
+      "stable_sha256": "79f60eeb790ad4f60d6774aa65ddf99d99cd2e1099f1ed6b5a1ba763838eec38",
+      "alpha_sha256": "28d473e1752fbd67dcb6299df59902d7dc24b74d383b1564fb63d74764ffaa9c",
+      "delta_bytes": 786
+    },
+    {
+      "path": "tools/pdf/markdown.js",
+      "status": "CHANGED",
+      "stable_sha256": "223a7cf36d662c04a29b9472e8b523f04fe80fdba23e3d836bf0b879c6d686a9",
+      "alpha_sha256": "61685462f9abb2517e4691fbc7baebea23260e776d3e216d941480551450e982",
+      "delta_bytes": 23985
+    },
+    {
+      "path": "tools/pdf/utils.js",
+      "status": "CHANGED",
+      "stable_sha256": "e22a4c088d4526b948187a3d49c0fd6a4048715c8e97a33e11330cbb5637ddb0",
+      "alpha_sha256": "68c382642ce8fcae86e7b24994058ee5ea86fe2bcf91ccfac7d4409c88dcadc2",
+      "delta_bytes": 165
+    },
+    {
+      "path": "tools/process.js",
+      "status": "CHANGED",
+      "stable_sha256": "e3965e913e1a0c0840a666861529e85c0b80d5e97147cada4737ddec5a6fb384",
+      "alpha_sha256": "d9c85fb1d15751f356c616c886cb2004717669227c4186b85e7442a025d4e9eb",
+      "delta_bytes": 271
+    },
+    {
+      "path": "tools/schemas.js",
+      "status": "CHANGED",
+      "stable_sha256": "f342345e34e48769dabaefe1b932f09d41e2e207b422f7794a15ee50ffa8f140",
+      "alpha_sha256": "6a290497b29f9dc5f43d66008ea54fcf0c302edea5612af519ef52ab3816d29e",
+      "delta_bytes": 776
+    },
+    {
+      "path": "utils/exit-process.js",
+      "status": "ADDED",
+      "stable_sha256": null,
+      "alpha_sha256": "b75d45fe351edc385e6f6ccceb84d79aef92c18b0db3e0ae657faca76f84776f",
+      "delta_bytes": null
+    },
+    {
+      "path": "utils/files/pdf.js",
+      "status": "CHANGED",
+      "stable_sha256": "8678f41e7513267d2d7ee659db7f4aae9624c41cc9e500d710d451ba0f920e71",
+      "alpha_sha256": "97b8250e35e5e7c5a89170cabd0d73686620c43fe12e4eb35cfc0b3acdc67b83",
+      "delta_bytes": -487
+    },
+    {
+      "path": "utils/mcp-ui-ab-test.js",
+      "status": "UNCHANGED",
+      "stable_sha256": "978c72e71812e555f6e90cf107d936be5777f60f2e2658109af92513a2a06a42",
+      "alpha_sha256": "978c72e71812e555f6e90cf107d936be5777f60f2e2658109af92513a2a06a42",
+      "delta_bytes": 0
+    },
+    {
+      "path": "utils/process-detection.js",
+      "status": "CHANGED",
+      "stable_sha256": "50b11aa5d3258692c2844befc197aa1845770fe6857e4fc51471108a9934201f",
+      "alpha_sha256": "b4273acd6c4b601602915bc1b3f2b817891c14eb51a3bbfa990cb8da1b3e5073",
+      "delta_bytes": 7354
+    },
+    {
+      "path": "utils/process-tree.js",
+      "status": "ADDED",
+      "stable_sha256": null,
+      "alpha_sha256": "ede6be5982d553ed986367942c8faa74496947f03a03ea739245dbc2d9f46f77",
+      "delta_bytes": null
+    }
+  ],
+  "caveat": "Alpha was selectively extracted; do not treat missing alpha inventory as deleted without checking full archive."
+}

package/docs/R67-CANDIDATE-PARENT.json

@@ -0,0 +1,10 @@
+{
+  "schema": "deadbyte.r67-candidate-parent.v1",
+  "parent_release_id": "v0.15.43-4c4a64a4c8e9f5a6",
+  "parent_manifest_sha256": "4c4a64a4c8e9f5a6e9eecce85fd0007ebcac99121b29c07f1a1fc81d1643cd33",
+  "source_directory": "D:\\Projects\\deadbyte-mcp\\development\\deadbyte-mcp-0.15.43-r66",
+  "candidate_directory": "D:\\Projects\\deadbyte-mcp\\development\\deadbyte-mcp-0.15.44-r67",
+  "copied_files": 2279,
+  "copied_bytes": 59002921,
+  "mutation": false
+}

package/docs/R67-EVIDENCE-RECONCILE-CLOSEOUT-20261011.md

@@ -0,0 +1,64 @@
+# R67 Verification Hardening — 2026-10-11
+
+**STATUS: CANDIDATE ONLY / NOT SEALED / NO ACTIVATION / NO PUBLISH.**
+
+## Authority and source boundary
+
+- Candidate: `D:\Projects\deadbyte-mcp\development\deadbyte-mcp-0.15.44-r67`.
+- Production observed after edits: `v0.15.43-4c4a64a4c8e9f5a6`.
+- Immutable production release manifest SHA-256: `4c4a64a4c8e9f5a6e9eecce85fd0007ebcac99121b29c07f1a1fc81d1643cd33`.
+- Generation manifest SHA-256: `ef3b041e2a87c2e143d4733a98a52d9db80cd16ad7007e112fcb5202e70c77c3`.
+- No release activation, npm publication, manual arm, host/desktop operation, or competitor execution occurred this round.
+- Original frozen full regression `r67isolate-20261011b` remains **a historical, v1-schema 32-shard evidence set** on source tree `95b408f5...16379ce`. Its recorded 1,354 pass and 42 non-pass/unclassified cases MUST NOT be recycled into the modified source tree or treated as the R67 release gate.
+
+## Problem reproduced and fixed
+
+### E2E regression verifier vs local-only source assertions
+
+The existing `r67-regression-shards.test.mjs` had source-text checks and direct unit assertions, but there was no independent test running the durable 32-shard reader against a real file hierarchy containing actual `intent.json` and `result.json` records. The CLI and its source logic were duplicated, increasing the chance of future v2 schema drift.
+
+**Change:** `src/r67-evidence-reconcile.mjs` now supplies the shared independent evaluator used by `scripts/r67-regression-reconcile.mjs`, and `test/r67-evidence-reconcile.test.mjs` creates 32 disposable shard directories and drives the same evaluator as the real CLI. Each v2 record must satisfy exact operation and shard identity, original intent-to-result consistency, receipt-body SHA-256, source tree and test list hash, file membership, configured deadline and TAP count invariants.
+
+### Correct STALE_SOURCE rather than fabricated FAILED_INTEGRITY
+
+Freshly observed RED: Running the new evaluator against historical `r67isolate-20261011b` initially classified 31 of 32 v1 receipts `FAILED_INTEGRITY` because it compared historical intent files directly to the **current** plan before checking their self-consistency. This was a false integrity accusation, not observed tampering.
+
+Fix: check historical intent's own `files_sha256` against its original `files` bytes and compare original result/intent identity before deciding whether the historical plan is now stale.
+
+Fresh independent CLI command with a **new argument identity** afterward:
+`r67-regression-reconcile.mjs r67isolate-20261011b fresh-v2-verify-001`
+returned `STALE_SOURCE`, **32 stale / zero integrity faults / zero current receipts**, exit code 2 as expected. Signed coding command receipt SHA-256:
+`6a92ec6b19210e793f312c5b19b3ef4d4e0e63cc055117fb16b2ae2fc0025bfb`.
+
+The former v1 records remain unaltered.
+
+### Fail-closed contradictory outcomes
+
+Freshly observed RED: a synthetic v2 receipt bearing `PASS` and `timed_out=true` could pass verification if an attacker recomputed the file's ordinary SHA-256. The evaluator now rejects `PASS` when the receipt indicates timeout, nonzero exit or non-null failure reason, with the required terminal summaries and counts enforced by the shard verifier.
+
+The verifier also rejects incomplete plans, changed source trees, tampered digests and unknown exits, and returns `BLOCKED_NONPASS_CLASSIFICATION` when v2 results contain skipped/todo/cancelled cases with no case-level proof.
+
+**NOTE:** Recomputed plain SHA-256 values alone cannot establish authenticity against an attacker able to rewrite a whole receipt. A trusted runtime signer and exact signed receipt chain are still **REQUIRED BEFORE RELEASE**.
+
+## Tests and verification
+
+- Original test of new module was RED with missing implementation.
+- New v1-historical-plan race regression was RED; fixed GREEN.
+- New contradictory PASS+timeout regression was RED; fixed GREEN.
+- `test/r67-evidence-reconcile.test.mjs`: 7 PASS, 0 FAIL.
+- `test/r67-regression-shards.test.mjs`: 10 PASS, 0 FAIL.
+- Updated `scripts/r67-focused-gate.mjs` includes the independent 32-shard fixture and parses complete Node TAP totals, refusing skipped, todo, cancelled and malformed summary instead of merely scraping numeric counts.
+- Full fresh **focused** gate: **62 PASS / 0 FAIL / 0 skipped / 0 cancelled / 0 todo**. Signed coding command receipt ID: `2472ca3c620580c551dd64eb`; SHA-256: `c7e9c30218ae061ab0213f85e037e33c2456a8ff4d65f682dc06cef17c3c53d6`.
+- Independent `coding_receipt_verify`: `ok:true`, `signature_valid:true` for the focused command.
+- Native inspector binary pin in focused gate: `c814771dddac8bfb184250b868ddb6ab9f5e0e43613c04c3ed8abe09324ec4db`.
+
+## Engineering decision / acceptance
+
+1. Maintain separate R67 candidate and sealed production; do not activate or publish `0.15.44` until explicitly authorized later.
+2. A full-suite PASS must have 32 current **v2** evidence receipts, no stale/missing/unknown shards, terminal TAP totals and classifiable non-pass cases, plus a trusted signed command/observation evidence graph. Historical v1 receipts can be validated for local integrity but never upgraded into current release proof.
+3. The 42 previously unclassified cases need a new per-case outcome/reason ledger on the next frozen run; hashes of old stdout alone cannot reconstruct them. Do not relabel them as PASS.
+4. The previously measured shard 17 (55.34s/58s) contained `r58-controller-live-local.test.mjs`; the candidate's current planner already isolates that measured controller suite into a dedicated 120s shard and the remote lifecycle into a 165s shard. **Do not expand deadlines again without fresh observed variance.**
+5. The Native Inspector currently signs observations only when a trusted signer is **explicitly injected by the caller**. It does not yet prove runtime-owned key custody, machine-generation binding, authority policy, or revocation during execution. These are P0 release blockers.
+6. Remaining release gates: native Win32 process-exit/access-denied fault injection, signer/runtime binding and adversarial verifier, full current-source regression and test-case skip classification, stdio/HTTP compatibility, package manifest/doctor, isolated rollback/restore plus authority continuity and independent closure.
+
+**Verdict:** R67 candidate improved. Focused test gate PASS. Production readiness NOT PROVEN. Nothing deployed/published.

package/docs/R67-FULL-REGRESSION-UNKNOWN.json

@@ -0,0 +1,27 @@
+{
+  "schema": "deadbyte.r67-full-regression-outcome-unknown.v1",
+  "candidate": "D:\\Projects\\deadbyte-mcp\\development\\deadbyte-mcp-0.15.44-r67",
+  "attempt": {
+    "script": "scripts/r67-full-regression.mjs",
+    "script_sha256": "8ebff7294927241902002f851550a92d0af04a172dfed3300174ccabeca76034",
+    "request_args": [
+      "r67-full-source-20261011-01"
+    ],
+    "remote_claim_id": "0626a82fcc72cf57169ac53e19a4512ae8de549d704b65597536fd33db65177b",
+    "tool_error": "remote claim outcome unknown after dispatch; no replay",
+    "observed_exit_code": null,
+    "observed_test_counts": null
+  },
+  "reconciliation": {
+    "machine_release_id": "v0.15.43-4c4a64a4c8e9f5a6",
+    "coding_armed": true,
+    "owned_process_sessions": 0,
+    "machine_observation_process_rows_scanned": 272,
+    "remaining_process_match_for_full_regression": false,
+    "completed_receipt_available": false,
+    "verdict": "OUTCOME_UNKNOWN",
+    "must_not_promote_release_from_this_attempt": true
+  },
+  "remediation": "Run a fresh, uniquely identified bounded regression with durable append-only result written atomically before delivery; reconcile existing operation before any retry.",
+  "production_unchanged": true
+}

package/docs/R67-NATIVE-INSPECT-BINARY.json

@@ -0,0 +1,11 @@
+{
+  "schema": "deadbyte.r67-native-inspector-binary.v1",
+  "status": "candidate",
+  "exe": "bin/deadbyte-native-inspect-r67.exe",
+  "sha256": "c814771dddac8bfb184250b868ddb6ab9f5e0e43613c04c3ed8abe09324ec4db",
+  "source": "native/deadbyte-native-inspect-r67.cpp",
+  "source_sha256": "b10d0d1886b091849402501bfde5bd5a7f6ba547902c6594b502891e5e1ec38a",
+  "allow_network_egress": false,
+  "max_output_bytes": 2097152,
+  "exit_fail_closed": true
+}

package/docs/R67-NPM-EXDEV-PRESERVATION-20261011.md

@@ -0,0 +1,39 @@
+# R67 npm cross-volume artifact preservation — 11 October 2026
+
+## Incident
+
+Operator invoked `node scripts/npm-release-r48.mjs --publish-only` on Windows. It reached step 5/7 after a successful npm pack (2333 files), manifest surface validation (2332 manifest entries) and isolated doctor. The next operation attempted `rename` from the D: candidate directory to the C: publication evidence directory, producing `EXDEV`. The log does not show npm publish being dispatched in that invocation.
+
+Post-failure read-only audit of the machine found:
+- D: source tarball **EXISTS**, 13,309,422 bytes, SHA-256 `b589be8cddfa725c120728b422ba5ee813d9cfcea6eca606e5d0bbc5fa964910`
+- C: preserved artifact **ABSENT**
+- C: publication `claim.json` **ABSENT**
+- Production observed `v0.15.43-4c4a64a4c8e9f5a6`
+- Registry status is **NOT inferred** from absence of a local claim. No npm registry query or publish was executed in the remediation.
+
+## Surgical correction
+
+`scripts/npm-preserve-artifact-r67.mjs` implements staging on the **destination volume** followed by fsync, SHA-512 integrity validation, no-clobber hard-link publication, final byte verification and only then source unlink. Existing destination bytes must match exactly for recovery, and a conflict never overwrites. This makes D: to C: preservation possible without unsafe cross-volume rename. Publication dispatch still belongs solely to `npm-publication-r65.mjs` and its immutable `claim.json` fence.
+
+`scripts/npm-release-r48.mjs` now invokes that helper with npm pack's integrity and shasum instead of `rename(tarball,preservedTarball)`.
+
+`scripts/npm-release-readiness-r67.mjs` blocks public R67 publication when `RELEASE.json` is still unsealed or any mandated gate is pending, prior to npm pack or publish dispatch. This is an **additional metadata fence**, not a substitute for independent test evidence, trusted attestation or final release verification. Operator consent and full gate verification remain required for public release.
+
+## Test contract
+
+- Cross-volume preservation fixture on Windows D: and C:; original source removed only after destination digest verification
+- Wrong npm-integrity leaves original source untouched and destination absent
+- Pre-existing different destination cannot be overwritten
+- Post-commit/pre-cleanup recovery accepts only exact same bytes
+- Symlink source is rejected
+- Unsealed R67 metadata is rejected before publishing
+- Every mandatory gate must be PASS
+- Source wiring asserts the publishing code checks readiness before the network/pack step
+
+## Cautions / blockers
+
+The old 13,309,422-byte tarball is historical evidence. Its SHA-256 alone does not prove it matches the current source tree after edits. Do not delete, overwrite, repack into, or publish it until separately reconciled. The new `assertVacantPackDestination` guard aborts both `--verify-only` and publication before `npm pack` when that historical tarball still exists. This guard protects against a known pre-existing file, but is not a multi-process locking mechanism. Move/archive the old tarball through an approved file operation, preserving its hash and chain of custody, before attempting a fresh non-publishing package verification.
+
+Changing source invalidates earlier candidate `MANIFEST.SHA256` and regression snapshot receipts until regenerated and independently re-verified. Do not claim `0.15.44` is released or deployed: R67 full Windows regression, trusted native signer, fault injection, isolated activation/rollback/restore and final closure remain gates.
+
+**STATUS: CANDIDATE HARDENING / NO DEPLOY / NO npm publish.**

package/docs/R67-OBSERVATION-TRUTH.md

@@ -0,0 +1,82 @@
+# R67 Native Observation & Runtime Truth — observed candidate state
+
+Status: **DRAFT / UNSEALED / NOT DEPLOYED**. Candidate path: `D:\Projects\deadbyte-mcp\development\deadbyte-mcp-0.15.44-r67`. Metadata still says `0.15.43`; do not publish as `0.15.44` without a new immutable release cycle.
+
+## Exact predecessor
+
+- Production: `v0.15.43-4c4a64a4c8e9f5a6`, release manifest `4c4a64a4c8e9f5a6e9eecce85fd0007ebcac99121b29c07f1a1fc81d1643cd33`.
+- Parent copy: 2,279 manifest-verified files; immutable production slot was not modified.
+- Independent live Ed25519 signature verification: PASS, signed message SHA `12a4c9b2114d0719e0ec7dd504ba6ea0de4445473e704263310d0c9f784945b0`; verifier command receipt `a18a800aa73b269bcdc9e61a43b95be85c51b545d3ebfa2bf5d29c44085f665e`.
+- Baseline record: `D:\Projects\deadbyte-mcp\testing\0.15.44-r67\R67-PRODUCTION-BASELINE.json`.
+
+## Actual implementation and API boundaries
+
+Native executable `bin/deadbyte-native-inspect-r67.exe` is compiled using MSVC x64 /W4 /WX /Brepro. Source SHA-256 `b10d0d1886b091849402501bfde5bd5a7f6ba547902c6594b502891e5e1ec38a`; EXE SHA-256 `c814771dddac8bfb184250b868ddb6ab9f5e0e43613c04c3ed8abe09324ec4db`. Canonical binary pin is `docs/R67-NATIVE-INSPECT-BINARY.json`.
+
+CLI commands implemented:
+
+- `node src/deadbyte-cli.mjs inspect process [limit]` — bounded Toolhelp snapshot, actual handle observations, explicit access errors. Records `snapshot_binding=UNVERIFIED` when a snapshot PID and later handle share a name: it does **not** claim that name equality proves identity. Name mismatch is `stale_or_reused`.
+- `node src/deadbyte-cli.mjs inspect identity PID` — opens handle and returns exact process creation FILETIME (decimal string), image path and exited state.
+- `node src/deadbyte-cli.mjs inspect memory self [limit]` — `VirtualQueryEx` metadata only, no private-memory reads.
+- `node src/deadbyte-cli.mjs inspect memory PID creation_filetime [limit]` — identity token required for external PID; verifies the token against the handle **before** observing regions. Mismatch fails `PROCESS_IDENTITY_MISMATCH`; process exit is reported, never silently treated as a different PID.
+- `node src/deadbyte-cli.mjs inspect pe FILE` — PE32/PE32+ MZ/COFF sections, RVA vs file-offset separation, raw file SHA-256 bounded to 64 MiB.
+
+No additional public MCP tools and no new arbitrary command/PID authority were created. CLI remains local, owner-operated and Windows permission constrained.
+
+## Receipts and trust status
+
+`src/r67-observation-receipt.mjs` accepts only an **explicit injected private+public Ed25519 signing pair**. `src/native-inspector-r67.mjs` signs real observations only when a trusted signer is injected; default CLI invocations are unsigned. `scripts/r67-independent-observation-verify.mjs` independently verifies signature, receipt SHA-256, result digest, exact argv request SHA and a pinned executable SHA. Forged keys, changed outputs, changed receipts or mismatched argv/executable fail. Tests use ephemeral test keys only, never a production private key.
+
+**Open blocker:** production observation runtime has not yet wired this signer, admission policy or append-only receipt persistence. This is a verified cryptographic *contract*, not proof of deployed runtime signed receipts.
+
+## Test evidence
+
+- Latest focused R67 and inherited subsystem tests: **44 PASS / 0 FAIL / 0 SKIP**, signed coding command receipt SHA-256 `33dac5e47fdf3181c50c554d548637653733373a53de64adc9ce645ad1252339`. This is a focused gate, not the Windows full release gate.
+- Deterministic process-exit test spawns a Windows child, obtains its true creation FILETIME, terminates it, and verifies that a later memory map cannot return success using stale identity.
+- Full regression attempt `r67-full-source-20261011-01`: **OUTCOME_UNKNOWN** after dispatch, remote claim `0626a82fcc72cf57169ac53e19a4512ae8de549d704b65597536fd33db65177b`. Read-only reconciliation found 0 owned process sessions and no remaining matching full-test process across 272 observed processes, but no durable completion receipt/exit status was recovered. **This is neither PASS nor FAIL.** See `docs/R67-FULL-REGRESSION-UNKNOWN.json`.
+
+## Reference provenance and forward roadmap
+
+Source references inspected under `D:\Projects\deadbyte-mcp\references`, recorded with exact SHA-256 in `docs/R67-REFERENCE-GAP-MATRIX.json`. Local Desktop Commander reference has `0.2.52` metadata; not evidence of production readiness of the `0.3.1-alpha` series. Third-party source is comparison material, never authority or executable donor.
+
+Subsequent scoped work: local-only redacted diagnostics package, explicit upload consent (network egress DENY by default), MCP `ToolAnnotations` hints and stdio/HTTP compatibility checks. Hints never enlarge native policy authority.
+
+## Release blockers
+
+1. Trusted production signer integration and independent persisted receipt verification, including runtime revocation.
+2. Memory inspection fault injection during `VirtualQueryEx`, PID reuse stress, cross-bitness and executable identity drift.
+3. Durable full-regression receipt and a definite exit status, then the actual Windows gate.
+4. Prepare correct `0.15.44` metadata, seal the immutable manifest, doctor/package checks, activation, exact predecessor rollback, exact successor restoration and signed final closure.
+
+Until those are proven: `R67_CANDIDATE=PARTIAL`; `PRODUCTION=v0.15.43`; `PUBLIC_0.15.44=NOT_PUBLISHED`.
+
+
+## Candidate continuation: 2026-10-11, NO DEPLOYMENT
+
+### Offline diagnostics
+
+Implemented owner-triggered local CLI command: node src/deadbyte-cli.mjs diagnostics export --output LOCAL.zip.
+There is no upload mode, implicit controller activation, or outbound-network code path. The source logs are fixed controller start/restart stdout/stderr files; 8-file limit, 64 KiB/file, regular non-symlink, and a 256-event report cap. Each log line is reduced to approved timestamp, level, event and Win32 error fields. Free-form lines are discarded rather than transported, so the report deliberately loses detail. An offline ZIP is created with exclusive-create semantics, and an independent Windows .NET ZipArchive reader proved the archive can be opened and decoded. ZIP file hashes alone are NOT signatures, and application-level no-upload does not prove OS-wide egress containment.
+
+New tests: r67-diagnostics.test.mjs, r67-diagnostics-cli.test.mjs, r67-diagnostics-zip-oracle.test.mjs.
+
+### MCP compatibility
+
+Four existing machine tools have annotations: machine_list and machine_status are read-only and idempotent; machine_ping is read-only and non-idempotent; machine_revoke is destructive and non-idempotent. These are declarative risk hints only. The underlying assertRevokeAuthority runtime enforcement remains intact and a denial-path regression passed. Registration coverage is NOT yet full stdio/HTTP conformance or ChatGPT end-to-end client coverage.
+
+### Deterministic, durable full-suite shards
+
+There are now 32 deterministic regression shards, with operation ID, SHA-256 bound test-tree and membership, durable intent before effects, atomic result recording, and a no-replay directory lock. A reconciliation utility reads results independently and blocks changed source trees, incomplete coverage, and corrupted receipts. The prior 220-second synchronous full-suite request is not treated as successful.
+
+Historical operation r67shard-20261011a:
+- Shards 0-4, 6-11, and 31 generated durable PASS receipts.
+- Shard 5 generated OUTCOME_UNKNOWN after a 58-second child timeout. No automatic replay was performed. It includes long remote-session-cli and controller-epoch tests; exact cause remains unproven.
+- After subsequent test additions, all 13 recorded shards are STALE_SOURCE against the new test-tree fingerprint. Independent reconciliation must never combine them with the changed candidate.
+- A real NULL-count timeout case exposed a verifier bug (incorrectly classifying UNKNOWN as FAILED). RED was observed; repaired code now reports OUTCOME_UNKNOWN, regression GREEN.
+
+Current focused candidate gate: 44 PASS, 0 FAIL, 0 SKIP. Signed coding command receipt SHA-256:
+33dac5e47fdf3181c50c554d548637653733373a53de64adc9ce645ad1252339.
+
+Remaining blockers: full-suite immutable-source coverage and exact worker reconciliation, signed runtime observation receipts and trusted signer integration, Windows native fault injections, protocol conformance, Windows release gate, recovery proof, final seal, independent closure.
+
+Conclusion: R67 remains DRAFT / UNSEALED / NOT DEPLOYED. Production v0.15.43 is untouched.

package/docs/R67-REFERENCE-GAP-MATRIX.json

@@ -0,0 +1,57 @@
+{
+  "schema": "deadbyte.r67-reference-gap-matrix.v1",
+  "status": "source_inspected_no_donor_code_executed",
+  "predecessor_version": "0.15.43",
+  "candidate_version": "0.15.44-draft",
+  "source_directory": "D:\\Projects\\deadbyte-mcp\\references",
+  "sources": [
+    {
+      "path": "desktop-commander/package.json",
+      "sha256": "5dbe02548ec8665f790b98854b26e9f61a8f74d8074273dc6011aa395d82ee71",
+      "version": "0.2.52",
+      "observed": "local reference package metadata only; does not prove alpha"
+    },
+    {
+      "path": "desktop-commander/README.md",
+      "sha256": "f812befad126c0ab9011b6bfc3efd8ba2e620e07f3162e4c50866441faaf54f4",
+      "observed": "local tool-call log retention and warnings; native privacy requirements differ"
+    },
+    {
+      "path": "remcp/chatgpt-app-submission.json",
+      "sha256": "e5a72adcff6b3574077f323c62f7816ef90029f629eae25ffeaad4b9247c0400",
+      "observed": "client-facing readOnlyHint, destructiveHint, idempotentHint, openWorldHint examples; annotations are not execution grants"
+    },
+    {
+      "path": "secure-host-mcp/README.md",
+      "sha256": "973d6b7368f35b09b4a5dad6ea0a4f226e32e2b8000351933a27377394090d9b",
+      "observed": "principal-scoped sessions and interrupted-redacted process summaries; evaluated as reference, not imported runtime"
+    }
+  ],
+  "decisions": [
+    {
+      "capability": "Native process memory truth",
+      "implementation": "R67 candidate native identity/PID creation pin, VirtualQueryEx metadata, no private reads",
+      "gate": "identity match and negative mismatched token green; adversarial process-exit fault injection still pending"
+    },
+    {
+      "capability": "Signed observation receipt",
+      "implementation": "R67 candidate trusted signer injection with independent Ed25519 verifier; direct CLI default remains unsigned",
+      "gate": "crypto/tamper focused tests green; authoritative runtime signer and on-disk append-only receipts pending"
+    },
+    {
+      "capability": "Remote diagnostics",
+      "implementation": "defer to scoped CLI with bounded redaction and signed local-first export; network upload prohibited by default",
+      "gate": "secret canary redaction; ZIP traversal; external egress observation; explicit upload approval"
+    },
+    {
+      "capability": "ChatGPT/MCP tool annotations",
+      "implementation": "thin bridge-only hints; never authority; keep 43 compact public tools where feasible",
+      "gate": "actual MCP tools/list stdio+HTTP parity, negative destructive classification and schema conformance"
+    }
+  ],
+  "no_donor_authority": true,
+  "no_new_external_service": true,
+  "no_new_kernel_driver": true,
+  "production_mutated": false,
+  "release_gates_complete": false
+}

package/docs/R67-REGRESSION-CLOSURE-20261011.md

@@ -0,0 +1,24 @@
+# R67 Regression Reconciliation — 2026-10-11
+
+Status: CANDIDATE ONLY; not deploy/publish/release.
+
+## Observed defect and correction
+
+Current R67 shard runner `scripts/r67-regression-shard-run.mjs` emits `deadbyte.r67-shard-result.v2`; historical independent reader `scripts/r67-regression-reconcile.mjs` incorrectly required `v1`. That turned legitimate new results into `FAILED_INTEGRITY`. A RED test reproduced the contract mismatch.
+
+The reconciler now validates hashes and operation identity first, accepts authenticated legacy `v1` only as `STALE_SOURCE`, and admits `v2` receipts to the current-source hash/plan verification. Tampered IDs or receipt digests remain `FAILED_INTEGRITY` and are not downgraded.
+
+After fix, old historical operation `r67shard-20261011a` changed from `FAILED_INTEGRITY` to **`STALE_SOURCE`**, with 13 stale indices (0–11,31), zero integrity faults and zero receipts usable for current suite. The old shard 5 `OUTCOME_UNKNOWN` after 58s is not recast as successful. No replay under the historical operation ID.
+
+## Verification
+
+- `test/r67-regression-shards.test.mjs`: 10 PASS / 0 FAIL; includes two RED-to-GREEN schema contract tests.
+- `scripts/r67-focused-gate.mjs`: 55 PASS / 0 FAIL / 0 SKIP, candidate-only.
+- Signed command receipt: `cf4f4872c226af007f70550c65383ca2d61b188f9ff153899c5e8f592890c17f`; independent DEADBYTE receipt verification returned `signature_valid=true`.
+- Production verified unchanged: `v0.15.43-4c4a64a4c8e9f5a6`, release manifest `4c4a64a4c8e9f5a6e9eecce85fd0007ebcac99121b29c07f1a1fc81d1643cd33`.
+
+## Next remaining gates
+
+Do not count old records as full regression. Must freeze a new candidate snapshot, run all 32 shards with unique operation IDs and durable receipts, reconcile exact source identity, isolate live Windows fault-injection for the native observer and prove signed per-observation evidence, then run full Windows gate, rollback/recovery gate and independent final closure. The previous measurement already isolated slow `remote-session-cli.test.mjs` (~110s) and controller lifecycle (~53s) onto standalone shards with increased timeouts; the earlier mixed 58s timeout cannot justify claiming an inherent hang.
+
+No production mutation, npm publication or deployment in this round.