[objectstack-fleet]

Requested by Bill · project thread

Fixes #25203
Part of #15212

Clause-②: no
Metadata-protocol: none

What this changes

Items 9 and 10 of the card: two comments in @objectstack/organizations that still named the retired orphan claim (claimOrphanOrgRows) among the legitimate SYSTEM_CTX writers that name another organization. That writer no longer exists, so both lists now name only the writers that do.

• packages/plugins/organizations/src/organizations-plugin.ts (Middleware A, the isSystem short-circuit note): "the per-org seed replay, the orphan claim, imports, migrations" becomes "the per-org seed replay, imports, migrations".
• packages/plugins/organizations/src/organizations-plugin.test.ts (the comment above the system-context cross-org test): "per-org seed replay / orphan-claim, migrations" becomes "per-org seed replay, migrations".

Comments only: no code, no assertion and no test name moves.

Why this closes the card

This is the card's last slice. Items 1, 2, 3, 6, 7 and 8 landed through #25266, and item 4 landed with #25210. Item 5 is a governed .claude/** line and has its own carrier, #25276, which remains open and is not addressed here.

What stays

git grep -n -i orphan -- packages/plugins/organizations/src after the edit, every remaining hit and why it stays:

• organizations-plugin.ts:151 and :434-435: they describe the retirement itself ("NO ORPHAN CLAIM", "There used to be a Fallback A"), which is true. Left alone on purpose.
• first-organization-orphan-rows.pin.test.ts:7: the suite docblock says claimOrphanOrgRows "used to run here" and that the claim is retired. True.
• first-organization-orphan-rows.pin.test.ts:152-207: fixture row ids and names (acc_orphan, task_orphan_1, "Orphan account") for organization-less rows. They name the data shape, not the retired writer.
• org-scoping-engine.ts:16: names OrphanCleanupEngine in plugin-sharing, an unrelated live engine.

Verification

• pnpm --filter @objectstack/organizations test: Test Files 16 passed (16), Tests 239 passed (239), lock VERDICT command-exit 0, at 641031d3d.
• pnpm --filter @objectstack/organizations typecheck: lock VERDICT command-exit 0, at 641031d3d.
• The derived local gate list (node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack, 56 commands) was run at 641031d3d; exit codes are in the dispatch report on the card.

Changeset

None. The diff moves only source comments, which publish nothing, so this PR carries skip-changeset.

---

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 1 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• 1 name(s) were too generic to anchor anything (single lowercase words)
• 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 — 9 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 bda53bb0ba3e81edbd3b244eaa656bf06ce49637 → packageMentionDocs.

[objectstack-fleet]

Contract review

Served-tier: TIER_DEFAULT
Head-sha: 641031d3dbf2d812deaf807d641344429829ebba
Local-runs: none
Scope: packages/plugins/organizations/src/organizations-plugin.ts, packages/plugins/organizations/src/organizations-plugin.test.ts

The seat's review of record. Inputs: card #25203 (items 9 and 10, epic seat note 6345275520), claim 6349496270, dev report 6350511634, the net diff against main, the head's check-runs.

① Derived judgments

1. Comments only. Two hunks, both inside // comments: Middleware A's isSystem note (organizations-plugin.ts:378) and the comment above the [#2937] system-context test (organizations-plugin.test.ts:179-180). No code, assertion or test name moves.
2. The new text is true. claimOrphanOrgRows was retired by fix(organizations)!: retire claimOrphanOrgRows — the first organization no longer adopts organization-less rows #25246 (e3190b949); the remaining writers named (per-org seed replay, imports, migrations) still run under SYSTEM_CTX. The two history comments at :151 and :434-435 that describe the retirement are left as they are, rightly.
3. The remaining orphan hits the dev listed (fixture ids for organization-less rows, OrphanCleanupEngine) are not the retired writer.

② Semver level

None: comment-only in a non-published spot; skip-changeset, Check Changeset green. Clause-②: no, Metadata-protocol: none.

③ Boundary flags

• Fixes #25203 is right: items 1–4 and 6–8 landed (refactor(objectql)!: retire the PLATFORM_OBJECT_TENANCY ledger — the tenant-audit mute is decided by the schema, and the [tenant-audit] warning names both readings #25210, fix(plugin-sharing): the declared-rule organization walk ends on the rows read; ADR-0131 small carriers retire the NULL-means-global texts #25266), 9 and 10 land here, and item 5 has its own carrier, skills: platform-readings.md still says D9 system-write stamping reads PLATFORM_OBJECT_TENANCY tenant-scoped (the ledger is gone; the rule is a tenant column, not federated) #25276.
• Check-runs on this head: 34 success, 12 skipped, 0 failed, 0 pending.

Implemented-by: claude/project-thread-2jqksb
Reviewed-by: session_01FaVyM6YvQLg9CsjPVCYc5K

VERDICT: PASS

[objectstack-fleet]

席位核对

ACCEPT · domain:engine seat 2 (seat post #20966) · os-bill · session_01FaVyM6YvQLg9CsjPVCYc5K · 2026-10-22T20:26Z · head 641031d3dbf2d812deaf807d641344429829ebba · card #25203 (p3, items 9 and 10, Part of #15212).

1. Form: draft, Fixes #25203, Part of #15212, assignee os-bill, 2 files (comments), skip-changeset. check-governed-merges --pr 25283: not governed ⇒ ordinary queue landing.
2. Premise measured: both texts were still on main at 8dfd1265f after their blocker fix(organizations)!: retire claimOrphanOrgRows — the first organization no longer adopts organization-less rows #25246 merged; the dev's grep lists every remaining orphan hit and why it stays.
3. Gates: the seat's review of record PASS (the comment above, on this head). 55 of 56 derived gates exit 0 locally, check:dual-build-cjs-loads NOT MEASURED locally (prerequisite) and green in CI; every check on this head reads completed green (34 success, 12 skipped).
4. Accepted deviations: the branch is the seat's designated branch (claude/project-thread-2jqksb, in-seat subagent); the attribution line is the order's; the [#2937] prefix on the test comment is pre-existing and kept.
5. Out of scope, disposed: item 5 is carried by skills: platform-readings.md still says D9 system-write stamping reads PLATFORM_OBJECT_TENANCY tenant-scoped (the ledger is gone; the rule is a tenant column, not federated) #25276 (domain:skills).
6. Landing: the seat flips ready and arms auto-merge through the relay now; the card closes on merge by Fixes #25203.