Repository navigation
hourly full run: red on main (CI) #23516
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-14T16:25:59.124Z · run log · commit 1418de4c7e07bf15469ee8a91ebab19fc843d0b1 · 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: cb9841aa25 (run 38560750566, the last green CI schedule run) .. 1418de4c7e — compare
1baf976cf9fix(metadata-protocol)!: a delete with dropStorage drops an object's table only with its last stored row, refused 409 while another row remains (fix(metadata-protocol)!: a delete with dropStorage drops an object's table only with its last stored row, refused 409 while another row remains #23464)73c7dc4a3dfix(spec): PermissionSet.description liveness cites its live reader, Studio's permission-set list column (fix(spec): PermissionSet.description liveness cites its live reader, Studio's permission-set list column #23467)0f059078ecfeat(spec,core,plugin-auth)!: an API key answers as its owner's session does when the ADR-0069 policy holds the account (auth-gate parity: a request carrying an API key beside a session cookie held by ADR-0069 is refused at REST but admitted by the five raw-host route families — one cross-seam answer is owed (session versus user) #23287) (feat(spec,core,plugin-auth)!: an API key answers as its owner's session does when the ADR-0069 policy holds the account (#23287) #23440)d54e2393bfdocs(adr-0069): D3 states what the gate holds — the account's standing, so an API key answers as the session does (ruling C′ item 5) (docs(adr-0069): D3 states what the gate holds — the account's standing, so an API key answers as the session does (ruling C′ item 5) #23472)87d061922ffeat(spec): the app item read answers by package id — 403 / 404 by the package key, per ADR-0048 §3.1 (feat(spec): the app item read answers by package id — 403 / 404 by the package key, per ADR-0048 §3.1 #23468)0ecac9613bfix(plugin-sharing, runtime): an email-audience share link answers every caller it does not open for with one refusal (fix(plugin-sharing, runtime): an email-audience share link answers every caller it does not open for with one refusal #23471)22fb225dcepm(skills): rest-channel.md names the relay's release.yml refresh stroke (pm(skills): rest-channel.md names the relay's release.yml refresh stroke #23476)a1285f26dbfeat(cli): os meta delete and os meta register take --package, forwarded as the SDK's packageId (cli:os meta deletedeclares no--package, so the reset door's409 RESOURCE_CONFLICTremedy (name one package) cannot be sent from the CLI, andos meta registercannot name the package a save writes into #23350) (feat(cli): os meta delete and os meta register take --package, forwarded as the SDK's packageId (#23350) #23475)0d3ea295d1refactor(plugin-security): remove the retired catalog objects' write gates and the walled data door; report positions naming an unresolved set (C3 stage 8-post) (refactor(plugin-security): remove the retired catalog objects' write gates and the walled data door; report positions naming an unresolved set (C3 stage 8-post) #23428)873151021ffix(tooling): check:type-check-debt's closure build takes the shared verify lock, and a call from inside a hold runs NESTED (fix(tooling): check:type-check-debt's closure build takes the shared verify lock, and a call from inside a hold runs NESTED #23486)05e3b8e934feat(service-mailbox): store an ingested message's attachments, and each forwarded message as an .eml, through file-attachments (feat(service-mailbox): store an ingested message's attachments, and each forwarded message as an .eml, through file-attachments #23484)8693110c4cfeat(spec)!: retire page-header-subtitle-alias and inline-action-api-params-to-body-extra from the load path at 18 (feat(spec)!: retire page-header-subtitle-alias and inline-action-api-params-to-body-extra from the load path at 18 #23485)650933ec76fix(runtime)!: the dispatcher's PATCH /data/:object/:id honours a body expectedVersion and If-Match, as RestServer's twin does (fix(runtime)!: the dispatcher's PATCH /data/:object/:id honours a body expectedVersion and If-Match, as RestServer's twin does #23490)394f65e891docs(pm-dispatch): triage-duties — a measured fleet-velocity cost is a third tooling entry door; the p2/p3 not_planned rule takes only a card with none of the three (docs(pm-dispatch): triage-duties — a measured fleet-velocity cost is a third tooling entry door; the p2/p3 not_planned rule takes only a card with none of the three #23482)ad5a7d7c39fix(spec)!: page action rows carry ActionSchema's declarative-update rules, read from one judge (fix(spec)!: page action rows carry ActionSchema's declarative-update rules, read from one judge #23494)111b5821cetest(runtime): pin which sys_metadata row the /automation flow doors write; no caller holds a package to name (test(runtime): pin which sys_metadata row the /automation flow doors write; no caller holds a package to name #23499)5547ad451afeat(spec): export the controlled_by_parent exactly-one-master predicate; lint reads it (feat(spec): export the controlled_by_parent exactly-one-master predicate; lint reads it #23496)3a2adc8835fix(cli): os migrate meta --stored says what holds for each failed row, and names a flow the engine refuses at boot (fix(cli): os migrate meta --stored says what holds for each failed row, and names a flow the engine refuses at boot #23500)f9b421716dfeat(cli): os migrate organization-ownership --apply executes only the reviewed plan file (ADR-0131 D10, C7b S4) (feat(cli): os migrate organization-ownership --apply executes only the reviewed plan file (ADR-0131 D10, C7b S4) #23437)1418de4c7echore(spec): retire check:objectui-pin-citations; objectui read points become dated readings and move into the liveness ledger ([Decision] Every objectui pin hop rewrites spec docblocks: move the objectui read-point citations out of packages/spec/src? #23434, part 1) (chore(spec): retire check:objectui-pin-citations; objectui read points become dated readings and move into the liveness ledger (#23434, part 1) #23502)
Filed by.github/workflows/scheduled-full-run-card.yml. Generated by Claude Code
Activity
objectstack-fleet commentedon Oct 14, 2026
Triage:
domain:devx·pm:on-hold· this red is #23493's, and its fix has landed · triage seat ·session_01AavokzJ5DndAwitDXvKy4U· 2026-10-14T17:01ZRead fresh. Run
38594515010(schedule, 16:01Z, on1418de4c7e) has one red lane,Dogfood Regression Gate (3/3)(job115957830288), plus its aggregate. Its 4 failures are the 4 that #23493 named:bearer-lane-password-change.dogfood.test.ts:246, three lanes: expectedPASSWORD_EXPIRED, receivedPASSWORD_RESET_REQUIRED;admin-ledger-decision-metadata.dogfood.test.ts:392:revokeSessionsAndKeysis undeclared in the test's closed set.The 13:01Z, 14:01Z and 15:02Z hourly runs are red on the same shard.
The fix has landed. PR #23512 (#23493) merged at 16:12Z as
3f7cb1b0a3, after this run started on1418de4c7e. The dogfood shards skip on PRs and in the merge queue, so the next hourlyCIrun on a descendant of3f7cb1b0a3is the authority.Restart-when: the first hourly
CIrun on a descendant of3f7cb1b0a3is red; the card then returns to triage with that run's reading. If it is green, the card closes under the main-red convention.objectstack-fleet commentedon Oct 14, 2026
Closed: the next hourly
CIrun is green on a descendant of the fix · triage seat ·session_01AavokzJ5DndAwitDXvKy4U· 2026-10-14T17:55ZThis card's
Restart-when(6173795627) is settled on its green side:3f7cb1b0a3at 16:12Z.CIrun38603056630(schedule, 17:01Z) on222293f60a, a descendant of3f7cb1b0a3, concludedsuccess. The dogfood shards that were red at 13:01Z, 14:01Z, 15:02Z and 16:01Z pass.Closed
completedunder the main-red convention. Per the workflow's rule, a later red is a regression, filed fresh.