[objectstack-fleet]

Requested by Elon · project thread

Refs #32910 (D2-N2 wording; the pins land in #33439)

Area-lease pilot #33059 · area E2b · seat domain:server#5 · os-elon-musk · session_016WV4cz4f7zEQZ2C9GTG382

What changes

The released 18.4.0 entries for PR #32877 (a re-bind takes the old owner's bare-name claim off with the function) in packages/objectql/CHANGELOG.md and packages/runtime/CHANGELOG.md say:

So a name the package still holds under another owner spelling (its bare id) keeps its claim …

Both now read:

So a name the package still holds in the engine's holder set under another owner spelling (its bare id) keeps its claim …

Docs-only. No code, no test, no changeset.

Why

#32910 D2-N2 (epic red-line delta read 6840550973): whether the package "still holds" the name is read from the engine's holder set, and with the two owner spellings registered in the other order the shared holder entry is replaced first and the claim is (correctly) freed. #32910 asked to qualify the changeset-level wording; that changeset has been consumed by the 18.4.0 release, so per AGENTS.md (RELEASE-OWNED, packages/*/CHANGELOG.md) the released entries are amended in a dedicated docs-only PR.

Verification

• git diff origin/main — two lines, the same five-word insertion in each entry.
• git grep "another owner spelling" origin/main finds only these two entries.

Clause-②: no
Metadata-protocol: none

Human Minimum

• 1. Schemas start as Zod; packages/spec holds no runtime logic. (n/a)
• 2. Every name I added uses the casing for its kind. (n/a)
• 3. No formatter ran; pnpm lint passes.
• 4. One issue, one branch off an up-to-date main, one pull request.
• 5. A change that publishes carries a changeset — n/a, docs-only amendment of released entries (skip-changeset).
• 6. packages/spec touched: n/a.
• 7. No hand edits to packages/*/CHANGELOG.md — deliberate exception: AGENTS.md's dedicated docs-only amendment of a released entry.
• 8. Title, body and comments are in English.
• The Before Submitting list in CONTRIBUTING.md is done.

🤖 Generated with Claude Code

https://claude.ai/code/session_016WV4cz4f7zEQZ2C9GTG382

[github-actions]

📓 Docs Drift Check

⚠️ 2 changed file(s) yielded no anchor (packages/objectql/CHANGELOG.md, packages/runtime/CHANGELOG.md), so the pages documenting them are NOT COVERED by this run — this is not a clean bill of health for those files. Nothing else in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 2 changed package(s)).

What this run could not see

• 2 changed file(s) yielded no anchor (packages/objectql/CHANGELOG.md, packages/runtime/CHANGELOG.md) — pages documenting those are invisible to this run
• 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 — 40 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 ba35dfd78283d5f839eaaaab24764322ae3e263a → packageMentionDocs.

[objectstack-fleet]

Contract-review-claim: session_016WV4d1PGptBW3QRQNmy5e6 · head 46c8664 · 2026-11-14T21:55:28Z

review#3.

[objectstack-fleet]

Review — PASS

Head-sha: 46c8664450afdbd8d245400580992d9561e67000

The PR touches two files: in each of packages/objectql/CHANGELOG.md and packages/runtime/CHANGELOG.md, it inserts the phrase "in the engine's holder set" into the released 18.4.0 entry for #32877. The sentence now reads "a name the package still holds in the engine's holder set under another owner spelling (its bare id) keeps its claim". There is no other change.

• Allowed edit of a released-owned file. AGENTS.md (Documentation Guardrails, packages/*/CHANGELOG.md row) allows a factual correction to a released entry only "in a dedicated docs-only PR", and never as an erratum in a later entry or a rider on code. This PR is exactly that: docs-only, no code, two lines.
• Accurate. The same entry says the binder asks the engine's holder set (stillHolds), and the runtime re-bind now reads the package's own holder entry (fix(objectql, runtime)!: a function's bare-name read is refused naming both when the platform and a package hold the name, and answers nothing for a name only a disabled package holds (ADR-0150 D4) #33439). "Still holds" therefore means the holder set, not the bare read. Naming that removes the reading where a bare-read miss (for example a disabled package, objectql: the engine's function holder set follows ruling A's served-holders default #32933) would count as "no longer holds".
• skip-changeset fits: the edit publishes nothing new on its own, and the next release's tarball carries the amended file.

The ACCEPT re-reads every check at the landing head.

Reviewed-by: session_016WV4d1PGptBW3QRQNmy5e6 (review#3)

[objectstack-fleet]

domain:server#5 · os-elon-musk · session_016WV4cz4f7zEQZ2C9GTG382
ACCEPT · area E2b (area-lease pilot #33059) · 2026-11-14T22:12Z

• Refs: objectql: runtime pins for a function's bare-name claim release — pre-seal re-bind, move-path ordering, owner-spelling order (#32877 follow-up) #32910 (D2-N2 wording; the pins land in fix(objectql, runtime)!: a function's bare-name read is refused naming both when the platform and a package hold the name, and answers nothing for a name only a disabled package holds (ADR-0150 D4) #33439).
• Review: review#3 PASS on head 46c86644 (comment 6884797343): a dedicated docs-only amendment of released entries; "in the engine's holder set" is accurate.
• Changeset: skip-changeset (publishes nothing).
• Governed: check-governed-merges --pr 33446 ⇒ NOT governed; +2 / −2.
• Checks on 46c86644: 35 success, 21 skipped, 0 failing.
• Landing: ready + auto-merge by the area thread (Elon 15:21Z in the E2b thread).