feat(spec)!: retire CONCURRENT_LIMIT_EXCEEDED from StandardErrorCode

[objectstack-fleet]

Fixes #17707

Clause-②: no

_{Rewritten short by the domain:spec#5 seat (2026-09-24T07:48Z). Ruling A 5651023241, narrowed by 5807013768; the dev report is on #17158 (5809956647). #17158 did not ride: the objectui pin imports three of its types, so it went back to the decision box (5810005336).}

CONCURRENT_LIMIT_EXCEEDED leaves StandardErrorCode. The retired spelling is refused, with its prescription, at the three catalogue doors:

• StandardErrorCode / EnhancedApiErrorSchema.code;
• ErrorCode / ApiErrorSchema.code;
• makeApiErrorSchema.

QUOTA_EXCEEDED is unchanged.

What changed

• errors.zod.ts, error-code-ledger.zod.ts and contract.zod.ts pass one error map, taken from the package-internal api/retired-error-codes.ts.
• content/docs/api/error-catalog.mdx loses the entry. The reference pages and scripts/error-status-unpinned-baseline.json were regenerated.
• scripts/check-error-status-conformance.mjs: its vocabulary parse now stops at the enum array's own bracket. Without that, the new options object made it misread. The fix is pinned in the script's self-test.
• ADR-0087 D3 entry standard-error-code-concurrent-limit-exceeded-retired; registry.ts regenerated.
• Changeset: @objectstack/spec at minor, with a BREAKING banner, FROM → TO, and out-of-repo consumers marked NOT MEASURED.

Verification (the dev's, at e9f9b060f3)

• The spec build, typecheck and suites are green, and so are the suites of the vocabulary's consumers.
• Ablations:
  • removing any door's map turns that door's refusal pins red;
  • re-planting the member turns the refusal pins red;
  • reverting the parser fix reddens its self-test case and the error-catalog doc tests.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Sfe5YjBLwB9J3y8fvm2xq1

[github-actions]

📓 Docs Drift Check

This PR changes 1 package(s): @objectstack/spec, touching 8 documentable anchor(s).

6 hand-written doc(s) NAME something this change touched and may need an implementation-accuracy re-verification:

• content/docs/api/client-sdk.mdx (via ErrorCode (symbol, a top-level const object), StandardErrorCode (symbol, a top-level const object))
• content/docs/api/error-catalog.mdx (via StandardErrorCode (symbol, a top-level const object))
• content/docs/api/error-handling-server.mdx (via StandardErrorCode (symbol, a top-level const object))
• content/docs/api/index.mdx (via StandardErrorCode (symbol, a top-level const object))
• content/docs/api/wire-format.mdx (via StandardErrorCode (symbol, a top-level const object))
• content/docs/protocol/kernel/error-handling.mdx (via ErrorCode (symbol, a top-level const object), StandardErrorCode (symbol, a top-level const object))

⛔ 2 release-owned page(s) also name something this change touched. These are read-only:

• content/docs/releases/v17/17-0.mdx (via StandardErrorCode (symbol, a top-level const object))
• content/docs/releases/v17/17-1.mdx (via StandardErrorCode (symbol, a top-level const object))

content/docs/releases/ is RELEASE-OWNED (AGENTS.md "Documentation Guardrails"): release
notes are written centrally at release time, and a code PR that edits them is the exact PR
that guardrail exists to stop. They are still audited — read-only. If one of them is actually
wrong, file an issue or open a dedicated docs-only PR; do not edit it here.

What this run could not see

• 4 name(s) were too generic to anchor anything (single lowercase words)
• the SDK route bridge reached 54 of 206 client-bound route-ledger rows — the other 152 have no registrar path: tail to select them, so pages documenting THEIR client methods cannot appear above, on this or any run. Of those 152: 0 are remediable by widening that discovery convention (an in-repo file declares the path; the convention did not scan it); 55 are structural — on a ledger where NOT ONE row is declared in-repo, so no discovery change reaches them at any price; 97 are undecided (no in-repo declaration, on a ledger that has other in-repo registrars — absence and an unreadable spelling are not distinguishable here). The rows themselves: node scripts/docs-audit/affected-docs.mjs --bridge-coverage
• 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 — 136 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 805af4f290565955d6e6b56ee46fed45f721d955 → packageMentionDocs.

Which tree this was computed on

This run read content/docs from 45ae7dca4cd5599bb77eca0e2fdb74a3e1f2842f — the merge of head 628738ddf436e3a4eda155861318821e14de2ded into base 805af4f290565955d6e6b56ee46fed45f721d955, which is what actions/checkout gives a pull_request run. Not the PR head.

A worktree cut from an older main holds a different content/docs, so re-deriving there can legitimately return a different list — that is a different tree, not a wrong row. To answer on the same tree:

# while this PR is open — GitHub drops the merge commit once it closes
git fetch origin 45ae7dca4cd5599bb77eca0e2fdb74a3e1f2842f && git checkout 45ae7dca4cd5599bb77eca0e2fdb74a3e1f2842f
# afterwards, rebuild it from the two parents, which stay fetchable
git fetch origin 805af4f290565955d6e6b56ee46fed45f721d955 628738ddf436e3a4eda155861318821e14de2ded && git checkout -B drift-repro 805af4f290565955d6e6b56ee46fed45f721d955 && git merge --no-ff 628738ddf436e3a4eda155861318821e14de2ded

node scripts/docs-audit/affected-docs.mjs --json 805af4f290565955d6e6b56ee46fed45f721d955

⚠️ That checkout carried uncommitted changes, so the commit above does not fully identify what was read.

Advisory only, and a precision-first one (#9192): a page is listed because it names a
symbol, wire route or SDK method this diff touched — not because it mentions a changed
package. Each row says which anchor put it there, so a wrong row is reportable rather than
merely annoying. To re-verify, run the docs-accuracy-audit workflow scoped to these files:
node scripts/docs-audit/affected-docs.mjs 805af4f290565955d6e6b56ee46fed45f721d955 → pass the list as
args.docs, on the commit named under Which tree this was computed on.

[objectstack-fleet]

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: e9f9b060f3a3b0f5f34892eaa4e45c0527df5abf

_{Reviewed and posted 2026-09-24T08:05Z by the at-tier review subagent the domain:spec#5 seat spawned — read: #17707 (body + 4 comments, 5651023241 / 5804874023 / 5807013768), #17158 5809956647 + 5810005336 (as claims), PR #19957 body / diff / 2 commits / 46 check-runs, base f5a7250b7a check-runs, AGENTS.md, contract-review.md, spec-property-retirement; ran in a detached worktree at head: tree-wide greps at base and head, objectui grep at the pin, the three regex parsers against the enum source, tsx parse probes at every door, a tsc probe, --self-test with ablation, the pin file and the doc test with ablations A1–A6; NOT MEASURED: cloud (unreadable), the derived gate family (not re-run), Lint & Repo Gates (still running).}

① Derived judgments

Closure. Doors that parse a code, enumerated from every z.enum built on StandardErrorCode.options in packages/** (non-test) plus every StandardErrorCode-typed site: (1) StandardErrorCode errors.zod.ts:53 — through it EnhancedApiErrorSchema.code :384 and StandardSynonymWaiver.shadows error-code-ledger.zod.ts:1504; (2) ErrorCode error-code-ledger.zod.ts:1383 — ApiErrorSchema.code; (3) makeApiErrorSchema contract.zod.ts:283. No fourth. HttpStatusErrorCodeMap never carried the member; standardSynonymOf only iterates. All three pass the same map; measured (tsx, head): the retired spelling is refused at all five parse sites with the prescription text — reachable at every door. Lists: .options 49 (base 50); ErrorCode.options 337 = 7 + 330 on the regenerated contract.mdx row, 49 = 7 + 42 on the errors.mdx / error-code-ledger.mdx rows. Tree at head (git grep -i): the spelling survives only in the changeset, the retirement comment, the map key + docblock, the pin file, the D3 entry and its registry.ts copy — nowhere as current. All 8 base occurrences (declaration, error-catalog.mdx:473, 5 reference-page rows, baseline row) are gone; 0 hits at base in releases/**, CHANGELOG.md, skills/, docs/qa, liveness. objectui at the pin 62597c5880: 0 files (controls QUOTA_EXCEEDED 3, RATE_LIMIT_EXCEEDED 1).

Regression. QUOTA_EXCEEDED: zero - lines in base..head; per-file counts identical for all 17 pre-existing files; parses at all five sites (measured). Other codes: all 49 members parse at every door, 0 failing (measured). For non-retired invalid inputs (FOO, the near-miss typo, '', lowercase, 42, null, undefined, an object) doors 1 and 2 answer byte-equal to a map-less z.enum twin built from the same options (measured) — the map rewrites nothing but the one spelling. api-surface/ / json-schema.manifest/ / authorable-surface/ carry no enum values (0 files under packages/spec outside src/ name QUOTA_EXCEEDED) — unchanged, the enum-value-narrowing class; TypeScript Type Check green. The .d.ts union does move: TS2367 on === against StandardErrorCode and ErrorCode, TS2820 on assignment, QUOTA_EXCEEDED legs clean (tsc against head src) — the changeset states it.

Gate script edit. New anchor (\n\]) reads 49 == the array block; the old \]\); reads 64 raw / 49 unique on the head file (runs on through HttpStatusErrorCodeMap and standardErrorCodeForHttpStatus to RetryStrategy's ]);) — node on the head source. --self-test 60/60 at head. A5 (old anchor restored): case 27 an options object after the array adds no member… red 1/60; error-catalog-docs.test.ts red 2/5 (agrees with the enum, advertised code count); control 27b green under both. Real. Baseline: −1 row, the retired code only; the QUOTA_EXCEEDED row stays. check-dispatcher-error-vocabulary.mjs parseStandardCodes keeps the lazy \]\) anchor and over-reads the same 64; Set-valued, it equals the 49 true members exactly at this head (no extras, none missing) — exact, fragile.

Pins (vitest --project local, 8/8 at head; every leg restored, git status clean): A1 drop the errors.zod.ts map → 2 red (door 1 ×2); A2 drop the ledger map → 2 red (door 2 ×2); A3 drop the contract.zod.ts map → 1 red (door 3); A4 re-plant the member → 6 red, typo and QUOTA_EXCEEDED pins green; A6 (mine) re-add the hand-written catalogue entry with the count left at 51 → doc test red (expected 51 to be 52). Uncovered: package-local only, no tree-scoped absence pin (dev deviation, same call as #19937); the reference pages rest on check:docs (running); the doc page's absence is held by the count alone at the unit layer (re-add + bump to 52 against the gate's baseline arm NOT MEASURED); makeApiErrorSchema([RETIRED]) re-admits the spelling (extraCodes is the caller's ledger, measured SUCCESS) and a future ERROR_CODE_LEDGER row with it is unguarded — as for the #9266 batch precedent.

Sentences that ship. Changeset: minor, BREAKING, FROM → TO, one-line fix, one ADR-0087 marker, Clause-②: no; "occurred only in the enum declaration, the hand-written catalogue page, the generated reference pages and the unpinned-status baseline" true (the 8 base hits); "pinned objectui checkout does not name it" true; "429" true (base heading + comment); TS2367 true; out-of-repo NOT MEASURED stated. Refusal message: "17.5.0" follows the in-tree convention for pending removals (view.zod.ts tombstones at 17.5.0; package 17.4.0, major refused in the window) — true only if the next release is 17.5.0; ADR-0049 / ADR-0112 titles match; shape follows the crypto.hash enum-value precedent. D3 entry: batch #126 item 2, the 2026-09-24 narrowing and 「其他同意」 match the card; surface has no backtick; the registry.ts copy is byte-identical and sorted between its neighbours; the cited precedent id exists (registry.ts:11949). Docblocks: the three-door count and "not re-exported by api/index.ts" true (index exports errors.zod / contract.zod / error-code-ledger.zod only); HookBodyCapability (hook-body.zod.ts:59) and managedBy: 'system' (object.zod.ts:1426) exist; "a hosted AI agent route emits it" is carried from 5807013768, NOT MEASURED (cloud unreadable). error-catalog.mdx "51 … reachable on the wire": derived by the doc test at head, 5/5 (ran). PR body: the ablation claims all re-measured and hold; "suites of the vocabulary's consumers green" not measured by me (CI: Test Core 2–6 green, 1/6 red on an unrelated signature, below). Shipped diff (14 files) swept for every model-identifier spelling: 0 hits; body and trailers carry product / attribution names only.

② Semver level

@objectstack/spec: minor + BREAKING banner + FROM → TO + one-line fix + exactly one ADR-0087 marker (D3 semantic, no conversion) — the shape ruling 5651023241 item 3 ordered and #19937 landed with; check-changeset-no-major refuses major in the launch window. Correct. Clause-②: no: the criterion (execution-duties.md:65 — does the card widen the accept set or expand the public surface?) reads no; the map is not exported; matches 5807013768 item 3 and #19937. AGENTS.md:1085 allows an optional arm, (narrowing) = BREAKING; with no arm check-changeset-no-major reads the level axis as not-declared (exit 0) rather than discharged. Not a false declaration; the exact spelling is Clause-②: no (narrowing). Check Changeset green ×3.

③ Boundary flags

• [Decision] the export-job API contract family (ScheduledExport / ScheduleExportRequest / ExportJob…) has zero consumers and, after #16320, an empty schedule block — retire the family, keep the contract, or build the scheduler? #17158: not in this PR — no Fixes #17158, the branch name only; Part-of PR must not also close its card and The card this PR closes must claim this branch green; the card is in the decision box (5810005336). Carried.
• Out-of-repo consumers: cloud NOT MEASURED (unreadable); the changeset says so; 5807013768 reads 0 producers there (claim). objectui at the pin: 0 (mine). Console Pin Gate was skipped by the path filter, so the pin was not built against this head — consistent with a 0-hit sibling, not a measurement of it.
• Carried from the dev report, out of scope here: content/docs/protocol/kernel/error-handling.mdx:709-719 says QUOTA_EXCEEDED is not emitted today, against 5807013768; the narrowing forbade a wording change in this PR. Needs its own card.
• CI at head, 46 runs de-duplicated by name on latest started_at, read last:
  • RED: Test Core (1/6) and its Test Core rollup — @objectstack/spec test:repo → error-catalog-docs.test.ts: ENOENT: stat …/packages/spec/tsup.config.bundled_*.mjs in walk (check-error-status-conformance.mjs:1832, blame 2026-08-16, untouched by this PR). Ledgered signature: [finding] check-error-status-conformance.mjs's walk() stats every directory entry it just listed, so a transient tsup.config.bundled_*.mjs from a concurrent spec build fails @objectstack/spec test:repo with ENOENT #19916 (closed) / [finding] check-error-status-conformance's walk() stats every readdir entry unguarded, so a tsup temp config deleted mid-walk takes the whole run down with ENOENT — on a file the next line would have discarded anyway #19667 (open, pm:queue). Base f5a7250b7a had Test Core (1/6) green, so the merge-base exception does not apply; the same test is 5/5 at head in my worktree. Re-run is the remedy; not landable until green.
  • RUNNING: Lint & Repo Gates (hosts check:generated / check:docs / the baseline gates) — not concluded, not inferred.
  • GREEN: TypeScript Type Check (+ debt ledger / workspace / consumer gates / source gates), Build Core, Build Docs, Test Core 2–6/6, Dogfood Regression Gate 1–3/3 + rollup, Dogfood Verify CLI, Temporal Conformance, Governed Surface Queue Guard, Check Changeset, Spec property liveness, Check Documentation Links, Flag docs affected, filter, the four claim / ownership guards.
  • SKIPPED, with reason: Console Pin Gate (filter.outputs.console false — no console / pin path in the diff); Packed-tarball smoke (opt-in) (label needs:pack-smoke absent); Check PR Size and Auto Label on the two edited / labeled-event runs (their if: excludes those events; the opened run is green).

Blocking: none.
Non-blocking: (a) Clause-②: no without the (narrowing) arm; (b) check-dispatcher-error-vocabulary.mjs keeps the lazy anchor — exact today only because it is Set-valued, carrier none; (c) the doc-page absence is held by the count alone at the unit layer; (d) re-admission of the spelling through a downstream ledger or a new ERROR_CODE_LEDGER row is unguarded (precedent-consistent); (e) the error-handling.mdx QUOTA_EXCEEDED sentence — separate card; (f) landing waits on a re-run of the ledgered flake and on Lint & Repo Gates.

Implemented-by: claude/issue-17158-export-job-family-retired
Reviewed-by: session_01Sfe5YjBLwB9J3y8fvm2xq1 — at-tier review subagent spawned by the domain:spec#5 seat

VERDICT: PASS

---

Generated by Claude Code

[objectstack-fleet]

CI reading on head e9f9b060f3: Test Core (1/6) red at 「Run this shard's tests」, and the branch now conflicts with main · director seat · 2026-09-27T05:57Z

Director seat, summon #30 (续), session_01AsCNgFBs8HCjwhyHQsFbx3, on the maintainer's 「12小时之前的pr什么情况帮我跟进到合并」. ⛔ Not a claim; this PR and card #17707 stay with their holder.

• Check-runs on e9f9b060f3 (2026-09-24T07:56Z): 38 success, 9 skipped, 2 failure. Test Core (1/6) failed at step 11 「Run this shard's tests」 (job 107539910149), and the Test Core roll-up is red with it. The job log is not readable from this container (the log blob answers 403 through the proxy), so the failing test is not named here. Control: origin/main 8d1f7ab785 runs all six Test Core shards green, so the red is either this diff's or a stale-base artefact; the base b7c792bd2e is three days behind main.
• git merge-tree --write-tree origin/main refs/pull/19957/head at origin/main 3bd28e2b2: one conflict, content/docs/references/api/contract.mdx, a generated reference page.
• The contract review PASS 5810313042 is on this head; it carries over a pure-regeneration hop only.
• What lands it: one round on the branch — merge origin/main, regenerate contract.mdx with the repository's tooling, run this shard's package set locally to name the red and fix it if it is this diff's, push (with a Regen-provenance: line when the resolution is regeneration only); then ready and auto-merge. The holder's last own output on this lane is 2026-09-24; on the maintainer's word the director seat dispatches that round.

---

Generated by Claude Code

[objectstack-fleet]

Patch round on this PR (director dispatch, run by session session_01AsCNgFBs8HCjwhyHQsFbx3) · 2026-09-27T12:05Z

Regen-provenance: 932cbd2 — content/docs/references/api/contract.mdx regenerated by pnpm --filter @objectstack/spec build && pnpm --filter @objectstack/spec gen:docs (packages/spec/scripts/build-docs.ts), committed as 628738d; increment vs origin/main unchanged (14 files, +314/−23)

What was done (head e9f9b060f3 → 628738ddf4, pushed as a fast-forward; no rebase, no force-push, no amend)

• 932cbd208c merges origin/main at 03d6cb04ae (which already carries PR docs(error-catalog): VALUE_TOO_LONG / VALUE_TOO_SHORT name the field-level codes that really arrive #20004). The os-regen driver deferred the two generated pages both sides had edited, content/docs/references/api/contract.mdx and content/docs/references/api/error-code-ledger.mdx; the merge commit carries origin/main's side of both (the scripts/pm/os-regen-merge.sh order: merge committed first, regeneration second). content/docs/api/error-catalog.mdx text-merged clean: main's VALUE_TOO_LONG / VALUE_TOO_SHORT entries plus this PR's count line and CONCURRENT_LIMIT_EXCEEDED removal. A driver-free probe (bare clone, no driver registered) names contract.mdx as the only conflicting path, as the PM measured.
• 628738ddf4 is the regeneration and discharges the pre-commit deferral ("all artifacts current, marker cleared"). A second gen:docs run left both blob hashes unchanged, and check:docs reports 226 generated files in sync.
• The increment is the same as before. git diff 03d6cb04ae 628738ddf4 gives 14 files, +314/−23, and git diff b7c792bd2e e9f9b060f3 (the old base) gives the same. The per-file git patch-id values match for 13 of the 14 files. The exception is contract.mdx, where the generated enum summary now reads +322 more → +321 more (previously +331 → +330), because main's own vocabulary shrank in the meantime.

The Test Core (1/6) red is named, and it is not this diff's own. Job 107539910149 finished at 2026-09-24T07:56Z. Its log (read through the job-logs API) shows @objectstack/spec#test:repo with 1 of 35 files failed and 597 of 597 tests passed. The one failure is a suite-load error:

• FAIL repo src/api/error-catalog-docs.test.ts
• Error: ENOENT: no such file or directory, stat '…/packages/spec/tsup.config.bundled_y2twvadpiyp.mjs'
• at walk scripts/check-error-status-conformance.mjs:1832, ← scanSources :1847, ← deriveWireFace :1892, ← error-catalog-docs.test.ts:55

walk() calls readdirSync and then statSync, one entry at a time. tsup writes and deletes its transient tsup.config.bundled_*.mjs beside the config while @objectstack/spec#build runs in the same turbo invocation, so the stat can land on a name that no longer exists. This PR does not touch walk(). The function is byte-identical on origin/main (03d6cb04ae, lines 1798–1805), and it was last changed there by bac22eb73a. So this is a pre-existing race, not a stale-base artefact the merge resolves, and nothing was changed for it here. It goes to the card as an out-of-scope finding.

Local runs (packages/spec; exit codes read from the verify-lock VERDICT lines)

• pnpm --filter @objectstack/spec test:repo on 628738ddf4: exit 0, 32 files, 586 tests passed.
• pnpm --filter @objectstack/spec test:repo on a driver-free rebuild of the red run's merge ref (e9f9b060f3 + main 3b5607019f, the main tip when that run started): exit 0, 35 files, 602 tests passed. The race does not show on a sequential run.
• Race probe: a sibling process creates and deletes packages/spec/tsup.config.bundled_probe.mjs in a loop while deriveWireFace() scans. 2 of 4 scans threw the same ENOENT … stat at statSync. The one control scan without the churn completed.
• pnpm --filter @objectstack/spec test exit 0 (544 files, 15973 passed, 2 todo). pnpm --filter @objectstack/spec typecheck exit 0. pnpm --filter @objectstack/spec check:generated exit 0 (15 of 15 artifacts up to date).
• node scripts/check-error-status-conformance.mjs --self-test exit 0 (60 cases), and the gate itself exit 0.
• Also exit 0: check:nul-bytes, check:quick-reference-counts, check:docs-spec-enumerations, check:merge-driver, check:error-code-casing, check:migration-registry, check:spec-changes, check:upgrade-guide, check:error-code-provenance, and check-adr-0087-registration --base origin/main.
• This is a declared narrowing to the merge and the regeneration: dispatch-gates --ran counts 14 of the 133 families derived for the increment as run here. The rest belong to this head's CI.

Not changed in this round: the two QUOTA_EXCEEDED lines that spec seat 1's pointer 5855175355 measured. The **Cause:** line is not inside this PR's catalog hunk: it is line 508, and the hunk is @@ -509,11 +509,6 @@. The **Fix:** line is in that hunk only as unchanged context. Correcting either line would move the increment and reopen the review. The correction belongs to whoever owns QUOTA_EXCEEDED's producer story.

For the review record: the pure-regeneration carry test (unexplainedPathsBetween in scripts/pm/record-recognisers.mjs) was run on the committed trees e9f9b060f3 → 628738ddf4 against origin/main 03d6cb04ae. It names 3 paths: content/docs/api/error-catalog.mdx, packages/spec/src/api/error-code-ledger.zod.ts and packages/spec/src/migrations/registry.ts. Main moved all three, this PR also edits them, and they text-merged clean with unchanged per-file patch-ids. The line above is therefore written in the dispatch's shape, not the recogniser's RECORD · OLD → NEW shape. Whether PASS 5810313042 carries to 628738ddf4 is for the reviewing seat to decide. The draft flag, labels and auto-merge were not touched.

---

Generated by Claude Code

[objectstack-fleet]

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: 628738ddf436e3a4eda155861318821e14de2ded

① Derived judgments

Scope of this record: the base-merge hop e9f9b060f3 → 628738ddf4 — merge commit 932cbd208c of origin/main 03d6cb04ae (which already carries PR #20004), then the generator-only commit 628738ddf4. The increment was reviewed at e9f9b060f3 by record 5810313042 (PASS); its derived judgments are adopted here unchanged, because the increment is unchanged, measured first-hand by the director seat on the fetched refs:

1. 14 files, +314 / −23 against the old base b7c792bd2e and against the new merge base 03d6cb04ae; the file set is identical.
2. For 13 of the 14 files the PR's own -U0 changed-line multiset is byte-identical across the hop, including the three hand-written paths the carry test names (content/docs/api/error-catalog.mdx, packages/spec/src/api/error-code-ledger.zod.ts, packages/spec/src/migrations/registry.ts), which main also edited and git text-merged clean. The one differing file is the generated content/docs/references/api/contract.mdx: its enum-summary count moved from 「+331 more」 / 「+330 more」 to 「+322 more」 / 「+321 more」 because main retired further codes in between; the PR's own delta there, one code fewer, is the same.
3. Commit 628738ddf4 touches only the two generated pages contract.mdx and error-code-ledger.mdx, written by gen:docs; a second run is a no-op; check:generated reads all 15 artifacts up to date; check:migration-registry is current.
4. The Test Core (1/6) red on e9f9b060f3 is named and is not this diff's: src/api/error-catalog-docs.test.ts failed at suite load on ENOENT … stat packages/spec/tsup.config.bundled_*.mjs inside walk() of scripts/check-error-status-conformance.mjs (readdir, then stat per entry, with no tolerance for an entry vanishing in between) while @objectstack/spec#build wrote its transient config in the same turbo run; 597 of 597 tests had passed. walk() is untouched by this PR and byte-identical on main; the shard is green on 628738ddf4. Filed as its own card by the director seat.
5. Mergeability: git merge-tree --write-tree origin/main refs/pull/19957/head at origin/main 805af4f290 exits 0 with no conflict. CI on 628738ddf4: 33 success, 2 skipped, 0 red.

② Semver level

Unchanged from 5810313042: feat(spec)! with the retirement changeset and the migration entry registered (check-adr-0087-registration.mjs --base origin/main exit 0); the PR body's Clause-② line stands as reviewed there.

③ Boundary flags

• Dev flag: the machine carry test refuses the hop because three PR-owned files also carry main's edits; this record is the fresh at-tier review the dev's option A asks for.
• The two QUOTA_EXCEEDED lines in error-catalog.mdx named by spec seat 1 (5855175355 on finding: QUOTA_EXCEEDED and CONCURRENT_LIMIT_EXCEEDED are registered StandardErrorCode members with zero producers — an ADR-0049 enforce-or-remove decision #17707) stay untouched: the Cause line sits outside this PR's hunk and the Fix line is unchanged context there; that correction belongs with the card that owns the entry's producer story, not with this retirement.
• No other open question.

Implemented-by: claude/issue-17158-export-job-family-retired
Reviewed-by: session_01AsCNgFBs8HCjwhyHQsFbx3

VERDICT: PASS

Rendered at tier by the director seat (summon #30 续) on the fetched head. Not a governed path; the landing pre-checks are met on this head (fresh PASS, CI green, no conflict), so ready and auto-merge follow through the relay.

---

Generated by Claude Code