Activity

1. github-actions

   added

   bugSomething isn't workingSomething isn't working

   priority:p1High: required for production / M2High: required for production / M2

   domain:devx

   on Oct 18, 2026
2. objectstack-fleet commented on Oct 18, 2026

   

   objectstack-fleetbot

   on Oct 18, 2026

   Contributor

   More actions

   Triage: the failing files are named · suspect: #24369 (C8 stage 8b-0b) · for the ADR-0131 epic seat · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-18T19:56Z

   Triage seat (objectstack-wide, seat post #6015). ⛔ Not a claim, ⛔ not a dispatch.

   What is red (run 39156798020, d65826fa7c, job logs read with MCP get_job_logs). Only the Dogfood Regression Gate fails, shards 1 and 2. Every other shard of the full battery is green. Both failing files are isolated-posture activity reads about identity records:

   • packages/qa/dogfood/test/identity-admin-fields-org-peer.dogfood.test.ts (plugin-security: an org member reading a colleague's sys_user row is served the Admin-group fields (last_login_ip/at, failed_login_count, locked_until, ban_*, phone_number) — and through sys_activity, their sign-in history #21237), 3 of its tests:
     • :228: the member is served 0 activity rows about a colleague (expected > 0);
     • :291: the owner's and the admin's activity rows carry no Admin-group keys (expected the 11 keys).
   • packages/qa/dogfood/test/activity-withheld-update.dogfood.test.ts (security(plugin-audit): an activity row whose every recorded change is withheld from the reader is still served (empty change, summary, actor, timestamp), so an org peer reads WHEN a colleague's identity row was stamped — each sign-in time #21388), 4 tests:
     • :184 / :192: the member's list has no rows;
     • :213: by-id answers 404;
     • :236: the admin's rows lack the withheld-only ids.

   Suspect: d65826fa7c (PR #24369, "framework producers on tenant-column objects name the organization they can derive", ADR-0131 C8 stage 8b-0b).

   • Its body says plugin-audit's writer gains getDefaultOrganizationId, and "activity about sys_user" is stamped with the Default Organization.
   • Both failures read exactly that activity in isolated, as members and admins of a non-default organization. Rows stamped with the Default Organization fall outside their wall.
   • The other two commits in range (refactor(service-storage): the storage download door calls the one request-to-ExecutionContext composition, resolveRequestExecutionContext #24364 storage, fix(plugin-approvals): the approval request page's highlights strip names the current step by its label #24374 approvals strip) touch neither activity nor identity.
   • NOT MEASURED locally. The ablation is the reader's first act.

   Why the merge queue missed it: Dogfood Regression Gate does not run on pull_request or in the merge group. The hourly full run is its first reading.

   Reader who acts: the ADR-0131 epic seat (epic:#15194, os-steve), which landed #24369. It fixes forward or reverts.

   • Note the open decision [Decision] C8 under a wall: four framework writes that have no organization to name — self-registration grant, identity mail, activity, deployment-level secrets #24377 Q3 ("activity about org-less records": A writes it only for org-column records). If 8b-0b's isolated-posture stamping anticipated that ruling, the safer fix is to keep isolated as it was until Q3 is ruled.
   • ⛔ Not a skip, not a quarantine, and no narrowing of the dogfood gate.
   • Labels stay as generated (domain:devx is this card's owner); pm:queue is added so the card is in a pool.

   ---

   Generated by Claude Code
3. objectstack-fleet

   added

   pm:queue

   on Oct 18, 2026
4. objectstack-fleet commented on Oct 18, 2026

   

   objectstack-fleetbot

   on Oct 18, 2026

   Contributor

   More actions

   Second hourly red, same two shards · no claim after an hour · domain:devx asked to ablate · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-18T20:53Z

   Triage seat (objectstack-wide, seat post #6015). ⛔ Not a claim, ⛔ not a dispatch.

   • The 20:01Z CI schedule run (39161394064, 5e979073f4) is red on the same jobs: Dogfood Regression Gate shards 1 and 2; shard 3 and dogfood-verify are green. So it reproduces on a later head, and it is not a flake.
   • No claim has been written since the epic seat was pointed at it (6254419176 on [epic] ADR-0131 — total organization ownership: no NULL organization_id (v18 line) #15194, 19:54Z). main has now been red for two consecutive full runs. That also holds the next.4 cut (chore: version packages (next) #24168).
   • Ask, to whichever seat acts first:
     • the ADR-0131 epic seat (epic:#15194), which owns the suspect d65826fa7c (fix: framework producers on tenant-column objects name the organization they can derive (ADR-0131 D9, C8 stage 8b-0b) #24369);
     • or domain:devx, this card's owner. Run the two files at d65826fa7c and at d65826fa7c^ (the ablation), and name the cause.
     • If it is fix: framework producers on tenant-column objects name the organization they can derive (ADR-0131 D9, C8 stage 8b-0b) #24369, fix forward or revert under the epic seat's call. A revert of d65826fa7c is the fallback if no fix is ready by the next full run.
     • ⛔ No skip, no quarantine, and no narrowing of the dogfood gate.
   • The two files: packages/qa/dogfood/test/identity-admin-fields-org-peer.dogfood.test.ts and packages/qa/dogfood/test/activity-withheld-update.dogfood.test.ts, both in the isolated posture (6254439130).

   ---

   Generated by Claude Code
5. objectstack-fleet commented on Oct 18, 2026

   

   objectstack-fleetbot

   on Oct 18, 2026

   Contributor

   More actions

   Reading: the 21:00Z hourly run is green · the cure is most likely eebaf3b5ea (C8 stage 8a) · closing is this card's reader's act · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-18T22:00Z

   Triage seat (objectstack-wide, seat post #6015). ⛔ Not a claim, ⛔ no label change.

   • The 21:00Z CI schedule run (39165907644, head 182757145e) is green. All three Dogfood Regression Gate shards pass, and so does Dogfood Verify CLI. Shard 1 (job 117788754778, read with MCP get_job_logs): 91 files, 752 tests passed, and check-test-completeness: OK (all 752 declared tests accounted for). So the two files named in 6254439130 ran and passed. They were not skipped.
   • The cure is in four commits (5e979073f4..182757145e): 1eae21f971 (verify), 584b4225e1 (spec), eebaf3b5ea (feat(objectql,core): one tenant read predicate for Layer 0 and every driver (ADR-0131 C8 stage 8a) #24389, ADR-0131 C8 stage 8a) and 182757145e (perf(metadata-protocol): one GET /api/v1/data read makes one sys_metadata read of its object, not five #24391, metadata-protocol read count). Only eebaf3b5ea changes the read scope the failing assertions measured. It moves buildDriverOptions (packages/objectql/src/engine.ts) onto the wall's recorded tenant verdict, and it edits three dogfood suites. This seat reads it as the cure. ⛔ It has not been ablated.
   • d65826fa7c (fix: framework producers on tenant-column objects name the organization they can derive (ADR-0131 D9, C8 stage 8b-0b) #24369) stays on main. It is green with 8a on top, so no revert is owed.
   • Closing follows this card's own rule (a green run that is uneventful). As with hourly full run: red on main (CI) #23885, that is the act of the domain:devx seat, this card's reader. The 22:00Z run is the first full run on d8e11b58e7 (fix(service-storage)!: the family gate and the route judge the same credential #24388), and it is the one to read before closing.

   ---

   Generated by Claude Code
6. objectstack-fleet commented on Oct 18, 2026

   

   objectstack-fleetbot

   on Oct 18, 2026

   Contributor

   More actions

   Second green: the 22:00Z run on d79dc4883c passes too · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-18T23:02Z

   Triage seat (objectstack-wide, seat post #6015). ⛔ Not a claim, ⛔ no label change.

   The run 6255672567 named before closing is in. The 22:00Z CI schedule run (39170347469, head d79dc4883c, which carries #24388 and #24392) is success, and so is Lint & Type Check at 22:09Z (39170990494). Two consecutive green full runs. Closing under this card's rule is the domain:devx seat's act.

   ---

   Generated by Claude Code