feat(ci): accept a wizard-app gateway token under --ci - #1225
feat(ci): accept a wizard-app gateway token under --ci#1225brandonleung wants to merge 1 commit into
Conversation
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Test against a Context Mill branch:
Add Results will be posted here when complete. |
4f68870 to
c67f713
Compare
c67f713 to
02fd94d
Compare
02fd94d to
77aadc3
Compare
77aadc3 to
d3adb30
Compare
gewenyu99
left a comment
There was a problem hiding this comment.
Yah this is fine. I will approve top of stack once I run it e2e
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
d3adb30 to
6723957
Compare
|
Full Express flow completed; snapshot assertions FAIL due to a baseline harness bug.
Tested checkout SHAs: Wizard A full real Wizard Express integration run on the locally restacked model, effort, budget and backend chains, with no model-turn cutoff. Gateway system-prompt PRs #455/#464/#461 and companion Wizard #1227 were excluded. Skills: Current full-run logs confirm http://localhost:8765 for skill menu and skill ZIP, http://localhost:8787/mcp for MCP, and http://localhost:8010 for PostHog. Credential distinction: This run used a locally minted wizard-app OAuth fixture with the application’s full scope ceiling. The user’s two supplied PostHog keys were not exercised. A separate locally generated narrow control token returned a project-read 403; that result does not establish any scope defect in the user’s keys or explain an issue with them. Every observed gateway model completion has a PNG below, including child-agent requests. These show the rendered TUI at capture time; concurrent requests can share the same visible state. Integration completed through MCP setup, Slack skip and Keep Skills (frames 154–164); all 73 model completions succeeded. Snapshot assertions failed because the pre-existing resultWritten guard preserved the earlier outro state. The same guard exists on main. No cutoff was active. The final screen reports one conflict to review: npm installation succeeded but reported two moderate dependency audit vulnerabilities (frame 149). Outcome and capture manifest · Source-stack provenance. Source PR tips and local run adjustmentsThe tested SHAs above include local stack assemblies; source PR tips are recorded separately below.
Full Express run — all 164 PNG snapshots |




































































































































































Problem
The CI smoke test runs
--ci --api-key phx_, and the gateway-token mint refuses a personal API key. CI works today only because that refusal falls through to the legacy gateway, so it breaks when the legacy product is switched off.Changes
pha_under--ci, matched at the start of the string, so the smoke test can carry the credential the mint actually accepts.The token itself comes from the management command in the paired posthog PR, and still needs rotating into the CI secret.
Test plan
pnpm test. The guard's warning is asserted present for every other prefix and absent for this one.