test: repair main verification fixtures

[ScriptedAlchemy]

Summary

• reserve a real loopback host listener in the relay-shell sandbox test so ephemeral proxy allocation cannot reuse its origin
• align the Claude path-token integration fixture with feat(claude): validate substitution tokens and record lifecycle contract #347's documented field matrix by moving plugin-data coverage from unsupported cwd to supported env
• keep local-ci: current-node doctor sockets exceed AF_UNIX path cap #335's short Rstest worker-root regressions unchanged and green

Root cause and provenance

Node 22.19 sandbox origin

• CI assigned the proxy's port: 0 listener the test's hard-coded 43123, correctly triggering the production different-origin guard
• deterministic red proof reproduced the exact assertion by binding the proxy to the hard-coded host port
• candidate merges feat(test): assert warm runtime identity in contract matrix #337, fix(test): cap Rstest worker socket paths #341, docs: add agent-bundle walkthrough canvas #342, and feat(dev): re-sync installed dev hosts on epoch swap behind the stable proxy (#179 stage 2) #343 do not change the sandbox source or test; fix(test): cap Rstest worker socket paths #341's /tmp/ab-rstest-* worker roots are unrelated
• the hard-coded fixture originates in 099744222 from feat: add agent-bundle compiler and developer workbench #2; 3a1c235c6 later reserved the host origin for the first test but left this second occurrence latent

Node 24 path token

• feat(claude): validate substitution tokens and record lifecycle contract #347 correctly rejected path tokens in Claude MCP cwd, but path-token-resolver.test.ts still built a fixture with cwd: pluginData
• the updated fixture exercises the same plugin-data substitution through documented MCP env support

Test plan

• Red: Node 22.19 targeted collision fails with MCP App sandbox proxy must use a different origin from its host
• Green: Node 22.19 targeted relay-shell test passes
• Node 22.19 full mcp-app-sandbox.test.ts — 11/11
• Node 22.19 rstest-worker-isolation.test.ts — 2/2 (local-ci: current-node doctor sockets exceed AF_UNIX path cap #335 regression coverage)
• Red: Node 24 targeted path-token test fails with claude.substitution.token.unsupported
• Green: Node 24 full path-token-resolver.test.ts — 9/9
• pnpm build
• pnpm typecheck
• pnpm lint — 0 errors, 0 warnings

[changeset-bot]

⚠️ No Changeset found

Latest commit: 43309ab

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-03T01:08:44.068287Z	4e73c2b	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[pkg-pr-new]

npm i https://pkg.pr.new/ScriptedAlchemy/agent-bundle@349

npm i https://pkg.pr.new/ScriptedAlchemy/agent-bundle/create-agent-bundle@349

npm i https://pkg.pr.new/ScriptedAlchemy/agent-bundle/@agent-bundle/runtime@349

commit: 43309ab