test(dogfood): the inbound-mail pool suite reads its fixture sets from the security catalog

[objectstack-fleet]

Part of #15204
Clause-②: no

What fails on main

main's CI run 38337824333 on 287fd6e5d0, the first full battery that contains D (#22900, c8a9783eca), is red on Dogfood Regression Gate (1/3) in one file:

• packages/qa/dogfood/test/mail-message-pool-read-gate.dogfood.test.ts:111: fixture permission set mail_pool_22870_read seeded: expected undefined to be truthy.

Why

• feat(service-mailbox): sys_mail_message, its record associations and the restricted unassociated pool — the inbound-mail capability (manage_mailboxes, requires: mailbox) #22993 added this suite. Its grant helper reads the seeded sys_permission_set row of a set declared through defaultPermissionSets.
• D removed that seeding (ADR-0131 D3): a set is served by name from the security catalog, and no boot writes its row.
• feat(service-mailbox): sys_mail_message, its record associations and the restricted unassociated pool — the inbound-mail capability (manage_mailboxes, requires: mailbox) #22993 landed after T2 (test(dogfood): fixtures read permission sets from the security catalog (#15204 stage 6b-2, T2) #22898, 07bc34ac05) moved the dogfood fixtures onto the catalog. PR and queue CI do not run the dogfood shards (skills(ci): two-speed CI — fast set on PR and merge-queue runs, full battery hourly on main and before a release, main-red stops the lane, four required contexts plus the guard, timing gates report-only, test budgets not deletions #22998), so neither PR ran this file against the other before main.

The change

Test only: one file, 7 lines. It is the hunk S8-T (#22962) carries in this file at 008ca32a75, byte for byte (blob adb8b0fa73):

• import { catalogPermissionSet } from './catalog-permission-set.js'; (the fixture helper on main since T2);
• grant asserts the set the security catalog serves, await catalogPermissionSet(ql, setName), instead of a sys_permission_set row.

The grant row it writes is unchanged (permission_set: set.name). #22962 keeps the same hunk, which merges as a no-op once main carries this.

Verification

Local, through scripts/pm/os-verify-lock.sh, on the showcase boot the suite runs (bootShowcase), in a worktree whose product source is main at f931e765b7 (built --filter closure of the dogfood package, turbo exit 0). The eight main commits from f931e765b7 to this PR's base 121847a7d5 touch none of packages/qa, packages/plugins, packages/services/service-mailbox, examples, packages/objectql, packages/rest, packages/runtime, packages/core or packages/metadata-protocol.

• Before (the file as main carries it): red, the CI assertion at the same line: AssertionError: fixture permission set mail_pool_22870_read seeded: expected undefined to be truthy, frame grant test/mail-message-pool-read-gate.dogfood.test.ts:111:67; the suite's 9 tests did not run.
• After (this hunk): green, the suite's 9 tests pass (the same file set's run: 279 passed; its one red is activity-text-predicate, a 5000 ms timeout under a contended box, untouched here).

The same before/after on a fresh build of this PR's base 121847a7d5 is queued on the shared verify lock; its result goes to the report on #23056.

Gates: the 53 commands node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack derives for this file; the results and the --ran reconciliation are in the report on #23056.

skip-changeset: one test file of the private dogfood package; nothing publishes. The relay's pr_create takes no labels, so the label is the seat's.

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 0 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 0 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 02bec6ca86e9f1237a3f82a9efff9cb3a53562ef → packageMentionDocs.

[objectstack-fleet]

Epic PM session_01Rerax7QTjKMPCUZxQUtPFR (marchtian), 2026-10-13T04:50Z. A read-only check of this PR, plus one label:

• The diff: one file, +5 / −2. Its changed lines are identical to the S8-T hunk in 008ca32a75 (test: the stage-8 test half — suites stop depending on the four catalog row objects (#15204 stage 8, S8-T) #22962) for this file, which the seat asked for in 6137492570.
• The label: Check Changeset was red only because the label was missing; this PR releases nothing (tests only). The seat added skip-changeset (route 2 of that check's own text), which re-runs the check.

Landing stays with the domain:engine lane. Once this is on main, the seat reads the first full battery whose dogfood shards run, for the first next prerelease.

---

Generated by Claude Code