test(dogfood): fixtures read permission sets from the security catalog (#15204 stage 6b-2, T2)

[objectstack-fleet]

Part of #15204
Clause-②: no

T2 of stage 6b-2: tests only. Fixtures that looked up a permission set's seeded sys_permission_set row now read the set from the security catalog (ADR-0131 D3, the catalog is its one home). Fixtures that model an existing database write the legacy row themselves. It is split off the 6b-2 code PR (#22900) so that PR falls under 3,000 changed lines.

Landing, as sequenced by the seat: T1, T2 and the 6b-2 code PR (#22900) stay drafts until #22900's own gates clear (the #22865 pickers and objectui PR-4), then land back to back, T1 → T2 → #22900. That way the publish materializer and the seeders are never live on main with their pins gone. 6b-2a (#22899) is independent and goes to the maintainer separately. This branch is green on main as it is today, while the seeder still runs. No production file changes.

What changes

• New packages/qa/dogfood/test/catalog-permission-set.ts:
  • catalogPermissionSet(ql, name) returns the set the catalog serves (via securityCatalogReaderOf; it throws if no reader is bound, so a missing catalog cannot pass as an absent set);
  • ensureLegacyPermissionSetRow(ql, name, { managedBy }) writes the organization-less legacy row with its full body from the catalog definition, for the suites whose data-door cases need a row.
• About 30 dogfood suites move from findOne('sys_permission_set') preconditions to catalogPermissionSet.
• showcase-permission-zoo, two-doors-permission, showcase-permission-projection, permission-set-write-through-package-binding and permission-set-lock-row-provenance write the legacy row where their cases edit one. two-doors-permission 块1 (a publish materializes a row) goes; the materializer is deleted in 6b-2.
• armed.dogfood.test.ts: the seeded controls use signed-up members, not usr_system.
• permission-set-clone-boot-unowned-warning.dogfood.test.ts is deleted (it pins the seeder's boot warning).
• plugin-security: new src/__tests__/legacy-catalog-rows.testkit.ts (seedLegacyPlatformBucket). Eight suites that model an existing database call it before their bootstrap.

Size

51 files, +312 / −308 (620 changed lines).

Verification

On this branch, with the seeder still running: full build; dogfood typecheck green; the 8 plugin-security fixture suites, 8 files, 72 passed; the 40 migrated dogfood suites, 40 files, 447 passed, 1 skipped. The three double-contract gates, check:changeset-no-major, check:nul-bytes green. The same fixtures also pass with the seeder deleted: they are inside the 6b-2 branch's full dogfood run (248 files green).

Test-only: skip-changeset.

---

🤖 Generated with Claude Code

https://claude.ai/code/session_013XKtmoR5QCUSTMjiQ3os49

[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 63739521d854d49dbb08dbc5370c99fde8a7555c → packageMentionDocs.