The run-linkage test covers only the opencode spawnHarness path for CODEDECK_RUN_ID forwarding. The claude launcher path (launchClaude in src/cli/commands/open.ts, around the call that passes {CODEDECK_RUN_ID} positionally) is not pinned by any test, so a signature reorder could silently drop run-id forwarding for claude sessions without failing CI.
Source: PR #30 independent review, non-blocking finding #5. Note: tests/run-linkage.test.ts was refactored in that PR to share tests/helpers/open-harness.ts, so add the claude case alongside the existing opencode case using that helper.
Suggested fix: mirror the opencode run-linkage assertion for the claude launcher, asserting CODEDECK_RUN_ID reaches the spawned claude process environment.
The run-linkage test covers only the opencode spawnHarness path for CODEDECK_RUN_ID forwarding. The claude launcher path (launchClaude in src/cli/commands/open.ts, around the call that passes {CODEDECK_RUN_ID} positionally) is not pinned by any test, so a signature reorder could silently drop run-id forwarding for claude sessions without failing CI.
Source: PR #30 independent review, non-blocking finding #5. Note: tests/run-linkage.test.ts was refactored in that PR to share tests/helpers/open-harness.ts, so add the claude case alongside the existing opencode case using that helper.
Suggested fix: mirror the opencode run-linkage assertion for the claude launcher, asserting CODEDECK_RUN_ID reaches the spawned claude process environment.