Repository navigation
test(agents): keep the image PATH in the setup-gate profile fixtures - #72
Conversation
The Codex setup gate requires the image's exact PATH, so manual-gate failed once the fixture prepended a fake op for the vault's Depot read. Keep PATH in the gate modes, and drop the depot service from the manual-gate profile so its bootstrap never calls op.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
What
test-profile.pyhas failed itsmanual-gatemode since buzz #71, with "profile did not reach the account gate". The image itself is fine. The failure comes from the fixture:optoPATHin every mode. The Codex setup gate (setup.js) requiresPATHto equal the image's exactPATH, so it refused the gate session.PATHis unchanged andopis the image's own, so the published images aren't affected.Fix
manual-gate,gate-api-key) keep the image'sPATH.manual-gatealso rotates the fixture profile to a via profile without adepotservice, so its bootstrap never calls the image'sopagainst the emulated network. The other modes still read Depot through the fakeop.Tested
I ran the full
test-profile.pylocally against the publishedmainimage (voltage-buzz-agent-staging@sha256:c7bc5ad9…2547, fromf87d8c981). Every mode passes, includingmanual-gate: "rotated shared profile with a Claude subscription token reaches manual account-login gate".Summary by CodeRabbit
PATHin selected modes and cover profile rotation with a subscription token and without a Depot service. The API-key mode is also covered without profile rotation. These changes affect test coverage only; no end-user behavior changes are noted.