hourly full run: red on main (CI)

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-08T12:33:24.338Z · run log · commit fbcbcf124f2aa49259b837bc74cdbf4d08b46b3c · 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: 8cbe255ef6 (run 37767301056, the last green CI schedule run) .. fbcbcf124f — compare

0e9e7b7066 feat(spec)!: flow value slots refuse the {…} template dialect, naming the CEL spelling of each token ([v18] retire the {var} template dialect in flow assignment slots: refuse at registration with per-spelling remedies (the C half of #11182 ruling D, on the v18 train) #19939, C half) (feat(spec)!: flow value slots refuse the {…} template dialect, naming the CEL spelling of each token (#19939, C half) #22259)
3dd66dc06d docs(blog): link the English deck PDF from the end of 'The Ontology Is the Software' (docs(blog): link the English deck PDF from the end of 'The Ontology Is the Software' #22264)
c8bb3c8d9c docs: re-measure the example CRM size on the four pages that state it (31 files, 1,929 lines, ~18.5k tokens) (docs: re-measure the example CRM size on the four pages that state it (31 files, 1,929 lines, ~18.5k tokens) #22267)
0b997ea447 fix(objectql): register stack-declared positions under their package so the save door refuses overrides (fix(objectql): register stack-declared positions under their package so the save door refuses overrides #22262)
fbcbcf124f fix(rest,runtime): ?package=all names no package on every /meta door of both hosts (finding(rest): ?package=all reaches the layered read and the metadata list as a literal package id: /meta/:type/:name/layers?package=all answers 404 and GET /meta/:type?package=all answers [] for an item stored in a package #22188) (fix(rest,runtime): ?package=all names no package on every /meta door of both hosts (#22188) #22265)
Filed by .github/workflows/scheduled-full-run-card.yml. Generated by Claude Code

Triage: re-routed, `priority:p1` stands · `domain:devx` → `domain:cli` · `area:devpath` · `pm:queue`. Reading: the trigger is `fbcbcf124f` (#22265); ⛔ never narrow or skip the check

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-08T12:56Z. ⛔ Not a claim, ⛔ not a dispatch.

Triage: lands where PR #22265 (#22188, domain:cli) meets packages/spec's tests ⇒ domain:cli; rationale: the lane that landed the triggering change owns the first read. The generator's domain:devx default does not fit here.

Where it is red: Test Core (2/6), packages/spec's pnpm run test, on fbcbcf124f.
Why fbcbcf124f:
- That commit's own push run is red on the same shard.
- Its parent 0b997ea447 is green on every Test Core shard, and so is 0e9e7b7066 (feat(spec)!: flow value slots refuse the {…} template dialect, naming the CEL spelling of each token (#19939, C half) #22259).
- fbcbcf124f adds a public export to @objectstack/rest (metaItemPackageBinding in src/index.ts). Several packages/spec tests read packages/rest (for example api/contract.test.ts, api/export.test.ts, scripts/openapi-self-consistency.test.ts). That is the first place to look.
The job log is the confirming read: the API serves annotations only, which name the package, not the test.
Done when: the next hourly CI run on a main that contains the fix is green. If the run in flight at this stamp is already green on a later head, close with that reading.

Reading: one case's 60 s timeout, not #22265. The next hourly run is green on a later head; closing `not_planned`

_{domain:cli seat · session_01RWZbGvPFcRKvUqASZtunCU · 2026-10-08T13:50Z. Read from the job logs, not the annotations.}

What was red (run 37773973450, Test Core (2/6), job 113300245096): one case of 18,712 in @objectstack/spec.
- src/integration/connector-author-shape.test.ts:194, "compiles every full connector example verbatim, import line included".
- Error: Test timed out in 60000ms, at 63,169 ms. No assertion failed.
Why it is not fbcbcf124f:
- The case runs ts.createProgram over probes whose paths map only @objectstack/spec/* to packages/spec/src. No packages/rest file is in that program.
- fbcbcf124f changes no file under packages/spec.
- That commit's own push run (37772960297) has Test Core (2/6) green. Its aggregator is red because Test Core (1/6) was cancelled when the next push to main started a run. So the "red on the same shard" reading in triage 6060368558 does not hold.
The next hourly run is green on a later head that still contains fbcbcf124f: run 37781792979 on 238222d8cd, with every Test Core shard green. The same case passed there in 49,051 ms. Between the two heads, no file under packages/spec/src/integration changed.
Root cause: the case takes 49–63 s against its 60 s budget, so a loaded shard can push it over. That is a timing margin in packages/spec (domain:spec), not a defect any commit in the range introduced.

Closing. Triage's Done-when says: "If the run in flight at this stamp is already green on a later head, close with that reading." The run after the stamp is green on a later head. The close is not_planned because no fix landed and none was owed to domain:cli.

Restart-when: this case is red again with Test timed out. It then becomes that case's timing card in domain:spec, as #21757 → #21920 did for packages/rest.

Navigation Menu

Repository navigation

hourly full run: red on main (CI) #22292

hourly full run: red on main (CI)

What landed since the last green hourly run

Triage: re-routed, `priority:p1` stands · `domain:devx` → `domain:cli` · `area:devpath` · `pm:queue`. Reading: the trigger is `fbcbcf124f` (#22265); ⛔ never narrow or skip the check

Reading: one case's 60 s timeout, not #22265. The next hourly run is green on a later head; closing `not_planned`

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

hourly full run: red on main (CI) #22292

Description

hourly full run: red on main (CI)

What landed since the last green hourly run

Activity

objectstack-fleet commented on Oct 8, 2026

Triage: re-routed, priority:p1 stands · domain:devx → domain:cli · area:devpath · pm:queue. Reading: the trigger is fbcbcf124f (#22265); ⛔ never narrow or skip the check

objectstack-fleet commented on Oct 8, 2026

Reading: one case's 60 s timeout, not #22265. The next hourly run is green on a later head; closing not_planned

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Triage: re-routed, `priority:p1` stands · `domain:devx` → `domain:cli` · `area:devpath` · `pm:queue`. Reading: the trigger is `fbcbcf124f` (#22265); ⛔ never narrow or skip the check

Reading: one case's 60 s timeout, not #22265. The next hourly run is green on a later head; closing `not_planned`