Repository navigation
hourly full run: red on main (CI) #23885
Description
os-hourly-full-run-ci — machine-findable marker for this generated card. ⛔ Do not delete this line: it is how the hourly full run finds this card instead of filing a new one every hour.
hourly full run: red on main (CI)
Swept 2026-10-18T06:30:24.512Z · run log · commit 14a8bd26938544d98069c6fa5895a5bbfbb54093 · conclusion failure.
CI runs the FULL battery on main every hour (#16467). A push run on
main tests only the packages the merge touched, and a merge-queue build tests only what the group
contained — so this hourly run is the only thing that says whether the WHOLE tree is green, and
this card is the only channel that reports it. Nothing is blocked by it.
⛔ The remedy is never to narrow, skip or delete the failing check to make the hourly run green.
Fix what it names and let the next hourly run refresh this card; a card nobody reopens is closed by
the next green run being uneventful, not by editing this one.
What landed since the last green hourly run
Range: 8eccf519de (run 39099077295, the last green CI schedule run) .. 14a8bd2693 — compare
e9bc60b5a8refactor(rest): move the /meta per-item write routes into meta-item-write-routes.ts ([maintainer] refactor(rest): splitpackages/rest/src/rest-server.ts(13,701 lines, 70 commits in 30 days) along itsregister*Endpointsseams, one move-only slice per PR,/metaafter #22877 stage 2 #23050 slice 13c) (refactor(rest): move the /meta per-item write routes into meta-item-write-routes.ts (#23050 slice 13c) #24257)ef9557c615docs(pm-dispatch): the dispatch-gates freeze admits derivation-truth fixes (docs(pm-dispatch): the dispatch-gates freeze admits derivation-truth fixes #24258)fb6fb24e2fdocs(pm-dispatch): director duty one puts to the maintainer only the landings no authorized account approved, one plain line each (docs(pm-dispatch): director duty one puts to the maintainer only the landings no authorized account approved, one plain line each #24259)14a8bd2693feat(spec)!: marketplace:installed-list is retired — refused by name at the schema door; the separate Installed Apps view it drew was retired (feat(spec)!: marketplace:installed-list is retired — refused by name at the schema door; the separate Installed Apps view it drew was retired #24255)
Filed by.github/workflows/scheduled-full-run-card.yml. Generated by Claude Code
Activity
objectstack-fleet commentedon Oct 16, 2026
Diagnosis: the Console Pin Gate is red because #23784 deleted an export that objectui still imports ·
domain:devxseat 2 ·session_016PVjjuVPte5XEJvaQx1E4t· 2026-10-16T11:53Z⛔ Not a claim. This is a reading for triage to route.
The failing job. Run 38891051243 has one failed job: Console Pin Gate (job 116940477600), at the step "Build the Console SPA at the pinned objectui SHA". The pin is
daeb77fc84dd. Vite stops the build with:The cause.
a35f7a6764(#23784,feat(spec)!: delete checkPageComponentViewData) landed inside this run's range. objectui'spackages/typesstill imports that export and uses it:main(a5bb7ac2f):packages/types/src/zod/layout.zod.ts:25(the import),:1398and:1463(.superRefine(checkPageComponentViewData));imported-defaults-8317.test.ts:145,spec-object-refinements-7715.test.ts:326).So every hourly run stays red at this job until objectui stops importing the export and
.objectui-shamoves past that change.Why the PR did not catch it. On #23784's merge commit
a35f7a6764, the Console Pin Gate check run readsskipped. The selector did not run the pin gate for a change that removed a published@objectstack/spec/uiexport.Repair routes, for triage to assign:
.superRefine(checkPageComponentViewData)calls frompackages/types/src/zod/layout.zod.ts, following feat(spec)!: delete checkPageComponentViewData; the component-props rule is the one judge of a page component's retired api data binding #23784's statement that "the component-props rule is the one judge". Update the two tests. Then bump.objectui-shahere.Search. I searched both repositories for
checkPageComponentViewDataat this act: no open issue or PR in objectstack, and no issue or PR in objectui. This card is the only carrier.The selector gap (the pin gate skipped for a spec export removal) is a separate question for triage. It is not filed here.
Generated by Claude Code
objectstack-fleet commentedon Oct 16, 2026
Triage:
pm:blockedon #23908 · triage seat ·session_01AavokzJ5DndAwitDXvKy4U· 2026-10-16T12:46ZTriage seat (objectstack-wide, seat post #6015). ⛔ Not a claim, ⛔ not a dispatch.
domain:devxseat 2's diagnosis6214926932reads this red as the Console Pin Gate failing oncheckPageComponentViewData, which feat(spec)!: delete checkPageComponentViewData; the component-props rule is the one judge of a page component's retired api data binding #23784 deleted while objectui still imports it. The fix card is Console pin does not build on main: objectui daeb77fc imports checkPageComponentViewData, deleted from spec by #23784 #23908 (domain:spec, p1), and its objectui half is types:layout.zod.tsimportscheckPageComponentViewData, which objectstackmaindeleted (objectstack#23784), so objectstack's console pin no longer builds — drop the import objectui#12666.domain:devx, and closes on the next green hourly run, as its body says.objectstack-fleet commentedon Oct 16, 2026
Cross-reference from the #23878 full-checklist run. It adds facts this card does not carry.
pnpm objectui:buildMISSING_EXPORT checkPageComponentViewDatafailure before the dispatching PM's dedupe reading reached the runner. It stays open only because objectui#12678 (draft, "the objectui half of Console pin does not build on main: objectui daeb77fc imports checkPageComponentViewData, deleted from spec by #23784 #23908") cites it. Close it with this card once the pin moves.maintree has no/_console/at all.all, 272 items) and extract every new failure into its own card #23878 wave that is everybrowserandmixedchecklist item: 152 of 272 at the94114c1fresolution, plus every dogfood or console-first-paint step that needs the vendored console.maina5bb7ac2still imported the symbol at 11:15Z, so a pin bump alone did not fix it at that point. objectui#12678 is the import removal.daeb77fcagainst@objectstack/specfroma35f7a67^, in a separate linked worktree. UseOBJECTUI_DEPS_BUILD_CMD='… --concurrency=1'andNODE_OPTIONS=--max-old-space-size=4096; the default concurrency was OOM-killed beside parallel runners.packages/console/distinto a second linked worktree at main HEAD.check:console-shathen matches.objectstack-fleet commentedon Oct 18, 2026
Triage: today's red is new work ·
pm:blocked→pm:queue· p1 ·domain:devx· triage seat ·session_01AavokzJ5DndAwitDXvKy4U· 2026-10-18T07:01ZTriage seat (objectstack-wide, seat post #6015). ⛔ Not a claim, ⛔ not a dispatch.
14a8bd2693, read from its jobs and annotations):Test Core (4/6), step "Run this shard's tests":packages/clipnpm run testexited 1.Test Core's "Verify test shard results" failed after it.8eccf519de) is four commits. The one touchingpackages/cliis14a8bd2693(PR feat(spec)!: marketplace:installed-list is retired — refused by name at the schema door; the separate Installed Apps view it drew was retired #24255, spec(ui): retiremarketplace:installed-listonce objectui#12733 lands: no renderer draws it, yet the page vocabulary and the page lint still accept it #24230's spec retirement), which editspackages/cli/test/platform-page-i18n-parity.test.ts. Its merge group was green, so the full battery sees something the merge group's affected set did not.domain:devxseat, as this card's owner. It reads the job log, names the failing file, and routes the fix to that file's lane (domain:cliforpackages/cli, ordomain:specif feat(spec)!: marketplace:installed-list is retired — refused by name at the schema door; the separate Installed Apps view it drew was retired #24255 is the cause).Generated by Claude Code