Skip to content

RAL-206: the Marshal e2e's shim never borrows the runner's identity - #295

Merged
Castor-o7 merged 1 commit into
mainfrom
ral-199-e2e-identity
Nov 17, 2026
Merged

Castor-o7 merged 1 commit into
mainfrom
ral-199-e2e-identity

Conversation

@Castor-o7

Copy link
Copy Markdown
Owner

RAL-206: the Marshal e2e's throwaway shim never borrows the identity of the session that runs it.

Why: fervent-dace noticed this while reading RAL-199 part 3. The throwaway marshal-shim in tests/marshal.rs inherited CLAUDE_CODE_SESSION_ID, which is the first thing the shim reads to find its session. So it registered under whichever Claude Code session ran the test, with that session's id and nickname. It only ever reached the throwaway daemon, but the test depended on who ran it.

Change: the shim gets no inherited CLAUDE*, MARSHAL_* or MYKO_* variable. It is given a fixed test session id (e2e00199-…), and both e2e tests now assert that id.

Tests: fmt and clippy -D warnings are clean. cargo test --test marshal -- --ignored --nocapture passes 3 of 3, and the shim's row reads session_id: e2e00199-0000-4000-8000-000000000199 (nickname quick-gecko) rather than the runner's. Only tests/marshal.rs and the roadmap change.

🤖 Generated with Claude Code

tests/marshal.rs's throwaway marshal-shim inherited CLAUDE_CODE_SESSION_ID,
the first thing the shim reads to find its session. So it registered
under whichever Claude Code session ran the test, with that session's id
and nickname. It only ever reached the throwaway daemon, but the test
depended on who ran it (fervent-dace's note on RAL-199 part 3).

The shim now gets no inherited CLAUDE*, MARSHAL_* or MYKO_* variable. It
is given a fixed test session id, and both e2e tests assert that id.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Castor-o7
Castor-o7 merged commit 614a89a into main Nov 17, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant