You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
main is red: #231 Agent Document stage broke runtime-inspector and public-api declaration tests #240
Deterministic failures (all three Node legs on a0c2add8b):
packages/workbench/tests/runtime-inspector.test.ts — "renders the six accessible panels, decoded tree, shared protocol, and provider-only render trace in the production bundle" — likely the Agent Document stage changed the inspector's panel census.
packages/agent-bundle/tests/public-api.test.ts — "keeps bundled config extension types in emitted root declarations" — promise rejected with "Command failed" (declaration build).
Not the pre-existing examples-real.e2e stale-diagnostic flake — that one is intermittent; these two reproduce on every leg.
Impact: every open PR is red too, because pull_request runs build the merge ref against current main (e.g. #232, a workflows-only change, fails on exactly these tests). The local-ci merge gate evidently passed for #231 in isolation, so this may be a semantic conflict with a commit that landed between its local run and merge.
cc PR #231 / #234 owners — main needs a fix or revert of 8a5b425.
Verified this against current origin/main at 82c44352b6233ec240eb6b02031172e645484603.
The two exact regressions both fail at PR #235's first parent (cbbaf0e90c1303d037df9cdcbe1b2adff1076a5b):
runtime-inspector.test.ts: 0/1 passed; Playwright strict-mode violation because getByLabel('Agent Document') matched the stage and timeline.
public-api.test.ts: 0/1 passed; the clean consumer declaration compile rejected.
PR #235, merged as 64aaab0b2c1b01a43143489a01739d8a39c62514, fixes exactly those causes: it makes the Agent Document runtime loader structural so the optional @agent-bundle/runtime peer types do not leak into emitted root declarations, and makes the Workbench locator exact.
After a clean pnpm build on current main, the same scoped integration runs pass:
Activity
ScriptedAlchemy commentedon Sep 1, 2026
Verified this against current
origin/mainat82c44352b6233ec240eb6b02031172e645484603.The two exact regressions both fail at PR #235's first parent (
cbbaf0e90c1303d037df9cdcbe1b2adff1076a5b):runtime-inspector.test.ts: 0/1 passed; Playwright strict-mode violation becausegetByLabel('Agent Document')matched the stage and timeline.public-api.test.ts: 0/1 passed; the clean consumer declaration compile rejected.PR #235, merged as
64aaab0b2c1b01a43143489a01739d8a39c62514, fixes exactly those causes: it makes the Agent Document runtime loader structural so the optional@agent-bundle/runtimepeer types do not leak into emitted root declarations, and makes the Workbench locator exact.After a clean
pnpm buildon current main, the same scoped integration runs pass:Closing as already fixed by #235.