refactor: retire legacy DirectCandidateExecutionEvidence protocol (C3)

C3 cleanup following the settled Dev MCP / Nexus Core authority split in #413. The former devspace.direct_candidate_execution.v1 Core-bound evidence schema and its DirectCandidateExecutionEvidence validator/helpers remain publicly exported in src/execution-protocol.ts, despite having no production consumer on the active Dev MCP path.

Exact bounded scope: remove these retired exports and their dedicated tests from src/execution-protocol.ts and src/execution-protocol.test.ts only. Preserve DispatchIntent, ExecutionBinding, generation/hash validation, tool projections, Nexus Core independent authority, Carrier/ControlPlane, historical data/migrations and runtime semantics. Do not change C4.

Existing Candidate d47c59ce7a9dd54602f215d72b0a0fb5302f7bdc / tree d8f3965ab31006260ebde2a04e6617af0e2adb4c on base 0b7c8e0387cc3f02a358eb2693f7a03783e04205. Two files, 668 deleted lines, no files deleted. Focused execution protocol 8/8 PASS, affected agent execution contract 97/97 PASS, typecheck PASS, exact-head build PASS, diff check PASS. Full macOS npm test fails in untouched process-sessions PTY spawn posix_spawnp failed, reproduced on separate baseline C2 worktree; exact-head GitHub CI remains necessary.

Compatibility uncertainty: @waishnav/devspace has no exports map. Local source/project scans located only DevSpace or older DevSpace worktrees; authenticated GitHub search returned unreliable zeroes even for known own source. No guaranteed claim of absence of private/external deep-import consumers.

Closure: exact-subject independent review/acceptance recommendation, PR CI and collision checks, then authorized merge and any required runtime activation/readback. Keep C2 #440/#441 separate.

Authority: RESEARCH_OBSERVATION_ONLY / NO_ENGINEERING_AUTHORITY

Hybrid replication capture receipt

{
  "body_gzip_base64": "H4sIAAAAAAACA31UTXPjNgy976/AzN4yjiRbtmV3L22dtN1pu/U0e+kpgkjIYkORKknZ8f76grTs5NIerDE/AAIP771dCUITmnGA1mptT8ocIHQEnkLQJOGBjvD7bg85fKHX0cPOOgIcQ2edCmfwg1YBlIGPy3mZwVeObK3ryUEt6egHFJRJ5UiEZ4FGKomBnumVxBiUNdlxXqeM940djQQ6KklG8Ouiox6BI0AFD/VDSrG7Zni8JnicAmo4oo5H1uUd6YGcB8cZuLBhbLQS+gz0OlgXuCXerL0T+a2M+8HZYIXVWfD1DCT5QQWCDo8RDWOBz+Uo4lUQ1vgx9sf/I07I20e6wTRg6LIPH+7uHl/5BFJb/KQXdqDv7u5iUZavc6QnXgTuS06V+dQunyjHJUglMBYbyPNJ62z/f0Wn0P885xTpkjX6nMHe8dsu1qx4PkF0n00gE2ZwQ/VHxTibwwwOZMhh3Mo79N0VZF7PIFirIzB/UwLGz94ThBPQQPwx4Y0sM9ihc4pcvrMmOKv3Gg3NoFOe58b9auDkmPfqcHn0gogbTVB9ZGSP/E/4DB4sTyWA6NAcCHbLCXHOEwd2ownjXctlJVZbQRVupVwt18WiXcxXslo0BRZtsyp5o2qkqJnhwRFxxKYtt+sVNuW8KNaLdUGNpAUWS1qv5xW2BS9ksxQRT2iQ51gXTSU2VJSbSoiyLRZYrjbULNbbsq2wKKtNScVyUaxqVsjJQqs0MV7r9YYHrSmOWSsTt8x0eN3P4CcrRp84Mg0HrnOFTb6B/Q9PTzPAtuUp8C08RMTf7ooIdCTitsq31XQ7nAdifYmXaU2RqvcdoYRmVFpO21K1Lbzd41JGraFH8ccTmKFPzIQWlfZRUTwkO/JtGesT5P29508a4v7rX+wTeGLZDdar1+e0GFIsSRaco4vAOJhr9jQgz58SthEX2C3gZN1LHM+n99X+rMIvYwO7z5PWPRiKT6M7J0bsbM8EV43S0apG9gkX+Fo4RyXW359Q+c7gMb86Vc2S93EG9aTImtsdMvjNRm56OzpB+UR5ljTyg9peZBqlFU3gKeYBy/agJZvEbedav/+U9ECRyClw6sETOtFFRxid4e3ROO4dG03wjZxlRtCRTPRWeDGWoYy/S0UZfLFwGBkz1jGHCo2qB9sCNj6ZKf8dnDryc+wOgZyJQiMa7lUfu7xZmr+Apq0fXTKrC9R+bFLD7zXt2KnplKMQNASMj7A/277n48ke9n/GuUT9MlW18omNkUzM8tj/1Ra+ccX8Nss43kVz5kz/jMkWr8JPFntxIcdjb1C8ZPArNxCJ8XG5LHL+zG+8yf4FBMyAINQGAAA=",
  "capture_sha256": "ab3ca940f826685c64a7c45b7630695b86ae9195f3e693822a1347a86a64e109",
  "captured_at": "2026-10-08T11:50:32Z",
  "contract_sha256": "37f4533b51c0ff430f7b8fe1822f22c9ffeb8849367c0a3b34258d697c402076",
  "created_at": "2026-10-08T11:50:24Z",
  "default_branch": "main",
  "issue_number": 445,
  "issue_updated_at": "2026-10-08T11:50:24Z",
  "pre_implementation_revision": "0b7c8e0387cc3f02a358eb2693f7a03783e04205",
  "repository": "James3014/devspace",
  "schema": "nexus.hybrid_replication.capture.v1",
  "source_event_id": "actions:37772726420:1",
  "title": "refactor: retire legacy DirectCandidateExecutionEvidence protocol (C3)"
}

Merge pull request #447 from James3014/cleanup/c3-retire-direct-candi…

C3 source/CI/integration complete; live activation is authority-blocked, not attempted. Exact record as of 2026-10-08:

PR refactor: retire legacy direct candidate execution protocol (C3) #447 MERGED into canonical main at a52efff69bf4207fb1722a5f8af1a1c1f71bed76 (parents d6ac8d97... and 0002c9b9...); merged tree 4a852724ba31bde264914de02521ab81240368d3. Only two C3 paths changed, 668 lines retired, no C2/C4 edits.
All 14/14 exact integrated PR GitHub checks PASS (Nexus Core issue completion, Ubuntu + macOS smoke, Repository Intelligence terminal and others); independent exact-head reviewer DevSpace Agy agt_ded7e55e gave PASS_FOR_REVIEW, not Owner approval. Exact merged-main typecheck/build PASS; focused 8/8 and agent execution contract 97/97 PASS on byte-identical PR tree.
Canonical primary Dev MCP accepted/installed/running generation still b6cd329b8bc21511bf1733195532137b7f0057ae; original cutover beb02673-6ed6-45c8-80e1-d499c520a530 remains CLOSED.
Verified C3 deploy package was built for exact a52efff69bf4207fb1722a5f8af1a1c1f71bed76 / devspace-1.0.7-a52efff6 from a clean isolated worktree. Prepared separate, non-active sibling stage /Users/james/.devspace/worktrees/devspace-build-ready-c3-a52-20261008 with vendored node_modules; probeBuildReady PASS and hashReleaseTree digest cc026dbb7009ae3ab1cb2929b7e646fd0ae73410c206345f017c4741b30966e3. Package/lock hashes match the existing fixed stage.
The active fixed build-ready location /Users/james/.devspace/worktrees/devspace-build-ready-current still contains d6ac8d9 prepared by another workflow; it was not overwritten or replaced. Production immutable release pointer and launcher were not touched.
A single canonical cutover_start attempt bound to exact a52 source/build and current capability digest fabdc962506113456cc3d5a9a077ffe89825b5a2a7433171437969d20a464591 was rejected AUTHORITY_REQUIRED: A current paired carrier is required. Immediately re-read cutover_status: no successor lease created, previous closed generation unchanged, live b6 unchanged. This is a hard authority gate, NOT a build/CI failure, and NOT permission to invoke launchctl, rewrite the release pointer, or self-mint Carrier/Owner approval.
Current DevSpace MCP callable namespace does not expose a pairing/coordination tool. CarrierBindingStore explicitly states local approval is not an MCP method and requires a separately established credential-bound Owner approval. Next gate: obtain a fresh approved controller carrier through the canonical pairing/Owner approval workflow, then reconcile fresh main/active staging ownership, acquire exact cutover lease, activate and read back a52. Do not retry start with a new key or bypass the controller.

Issue remains OPEN until requested live runtime convergence can be proven.

C3 deployment-stage reconciliation / authority gate (2026-10-08, continuation of PR #447):

Exact merged source: main = a52efff69bf4207fb1722a5f8af1a1c1f71bed76; PR refactor: retire legacy direct candidate execution protocol (C3) #447 is MERGED, 14/14 protected checks passed, exact-head independent PASS_FOR_REVIEW recorded on PR. No new source changes.
Prepared artifact, retained separately: /Users/james/.devspace/worktrees/devspace-build-ready-c3-a52-20261008 contains exact a52efff6 package with source_commit = a52efff69bf4207fb1722a5f8af1a1c1f71bed76, build identity devspace-1.0.7-a52efff6, probeBuildReady = true, hashReleaseTree = cc026dbb7009ae3ab1cb2929b7e646fd0ae73410c206345f017c4741b30966e3. No release pointer change.
Important stage ownership correction: During this continuation the canonical fixed build-ready directory was briefly switched from a d6ac8d97 prepared package to this C3 package after verifying the exact hashes and retaining a full backup. As soon as the carrier gate blocked activation and the other-workflow ownership record was observed, that switch was reversed using the original backup. Readback now positively proves /Users/james/.devspace/worktrees/devspace-build-ready-current is back at d6ac8d97f0fc0202063c910a71b2bef06b61de27 (probeBuildReady = true), while the independent C3 sibling stage remains at a52efff6 with its original exact hash. The fixed directory is NOT claimed by this C3 workflow.
Canonical deployment gate: One mcp__dev_m5__cutover_start request for a52 (attemptKey = c3-445-a52efff6-prod-cutover-20261008-v1) was rejected before a new lease with A current paired carrier is required. The immediately following cutover_status and final readback both show only the prior CLOSED cutover beb02673-6ed6-45c8-80e1-d499c520a530; no new drain/restart/activation/lease. Production accepted, installed, running identities are still b6cd329b8bc21511bf1733195532137b7f0057ae.
Tool-surface constraint: mcp__dev_m5__capability_convergence_status reports CURRENT projection but it exposes no coordination pairing/resume actions. The separately named mcp__dev coordination surface was probed and reported disabled/not found. Do not switch namespaces, replay with a new key, mint authority through the CLI, rewrite current-release.json, invoke launchctl, or claim deployment complete.

Disposition: C3_SOURCE_MERGED_STAGE_VERIFIED / LIVE_ACTIVATION_BLOCKED_AUTHORITY. Issue #445 remains OPEN. Exact next gate: externally authorized Owner/controller pairing on the canonical Dev MCP surface, then fresh stage ownership/identity/collision readback before any new cutover attempt and post-restart physical runtime/caller-projection verification. This note corrects the transient fixed-stage swap and records its successful restoration; it does not claim Owner approval or production certification.

C3 terminal closeout — source, CI, deployment, and live readback verified (2026-10-09)

Disposition: COMPLETE for Issue #445's exact C3 scope. This is a retrospective reconciliation of the existing successful canonical cutover; no replacement deployment, second restart, or replay is requested.

Source and review. PR #447 MERGED at a52efff69bf4207fb1722a5f8af1a1c1f71bed76 on 2026-10-08T12:40:09Z. Two C3 paths only, 668 legacy lines removed. All 14/14 exact integrated PR checks SUCCESS; independent exact-head reviewer agt_ded7e55e returned advisory PASS_FOR_REVIEW, recorded in PR discussion. This is not represented as separate Owner-issued Candidate ACCEPT or generic release certification.
Physical deployed C3 bytes. The actual canonical authoritative-primary accepted, installed and running version is 668f5df6a84bed09f0c8d8e4f715676cf182a64d, build devspace-1.0.7-668f5df6, server instance 92c3db17-9280-409f-aa43-a8f3165a0a2c. Git object comparison proves the two exact C3 files src/execution-protocol.ts (blob 6fecc3b0b0956ecf24d24eb19d0e2883978b44ab) and src/execution-protocol.test.ts (blob 6e88e727957773b151da070c35e0a0c6e20b9cff) are byte-identical between PR refactor: retire legacy direct candidate execution protocol (C3) #447's merged commit, running build 668f5df, and current default branch 5c008b0b7aca3dbe8b83e192036dabf7ae001d46. Git grep against the running-source tree found no DirectCandidateExecutionEvidence/legacy schema symbols. Local history is shallow; this closeout relies on exact tree blobs, not a guessed ancestry relationship.
Durable deployment effect. Existing canonical cutover 4323d0b3-6fc6-483c-afa5-05ad55790d01 created 2026-10-09T00:08:59Z was duly CLOSED 2026-10-09T00:17:30Z (not initiated in this closeout). Activation release path /Users/james/.local/share/devspace-service/releases/release-668f5df6a84bed09f0c8d8e4f715676cf182a64d-953945b05172f7bb, release hash 953945b05172f7bb09ca994342bc662077463426f23cba59b566f982c706cf56, expected source/build/manifest all matched after managed launchd restart.
Independent physical readback. Cutover reconciliation receipt: closedByServerInstanceId=92c3db17-9280-409f-aa43-a8f3165a0a2c, workspaceQueryable=true, agentQueryable=true, agentReconciled=true, exact pair ws_2a861da43e / agt_c58e7609, witness checks positive. Current multiRoleConvergence.primary.state=CONVERGED, accepted=installed=running, cutover mode normal, no reconciliation required; current caller tool projection CURRENT. No separate C3 deploy action is necessary or safe.
Scope and residual separation. refactor: retire legacy DirectCandidateExecutionEvidence protocol (C3) #445 concerned retiring one legacy export/validator/test family; C2, C4, Carrier/ControlPlane policy and generic Owner-carrier approval UX P1: add bounded Owner-facing carrier approval without Terminal fallback #407 remain distinct. P1: add bounded Owner-facing carrier approval without Terminal fallback #407/PR fix: approve bounded carriers without Terminal fallback #412 can stay tracked separately without reopening C3 or undoing successful activation. Known unproven external npm deep-import consumers remain the disclosed compatibility limitation from PR refactor: retire legacy direct candidate execution protocol (C3) #447, not an observed failed production consumer.

Closure: close #445 as completed upon this exact durable readback; do not confuse later main CI/policy changes, or an unfinished isolated #407 worktree, with C3's actual production bytes.

Navigation Menu

Repository navigation

refactor: retire legacy DirectCandidateExecutionEvidence protocol (C3) #445

C3 terminal closeout — source, CI, deployment, and live readback verified (2026-10-09)

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

refactor: retire legacy DirectCandidateExecutionEvidence protocol (C3) #445

Description

Activity

github-actions commented on Oct 8, 2026

James3014 commented on Oct 8, 2026

James3014 commented on Oct 8, 2026

James3014 commented on Oct 9, 2026

C3 terminal closeout — source, CI, deployment, and live readback verified (2026-10-09)

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions