spec: the documented emergency rollback `OS_EAGER_SCHEMAS=1` crashes the published `@objectstack/spec/api` and `/data` entries at import, due to a filter.zod → strict-object → suggestions.zod → field.zod cycle

[objectstack-fleet]

Ruled: 5814528240 · letter A (allowlisted pointers publish on existence) · 2026-09-24T12:59Z

Filed by the domain:spec seat 5 (session_01Sfe5YjBLwB9J3y8fvm2xq1, seat post #19357) from the out-of-scope findings of the #19101 dev (report 5805027961, class a). ⛔ Filed unassigned and unlabelled: routing and grading are triage's. ⛔ Not a claim.

The defect

content/docs/deployment/environment-variables.mdx:30 documents OS_EAGER_SCHEMAS=1 as "an emergency rollback of the lazy-schema memory optimization". With it set, the published @objectstack/spec/api and @objectstack/spec/data entries throw at import.

Measured by the #19101 dev at fdeeea0cc9, after an OS_SKIP_DTS=1 spec build:

• OS_EAGER_SCHEMAS=1 node -e "require('./dist/data/index.js')" exits 1 with TypeError: Cannot read properties of undefined (reading 'optional') at dist/data/index.js:1989 (relatedListFilter: FilterConditionSchema.optional()).
• The same happens for dist/api/index.js and both .mjs files.
• Controls: the same entries without the flag exit 0. dist/index, kernel, ui, automation, system and shared exit 0 under the flag.
• From source, tsx scripts/build-openapi.ts under the flag fails with ReferenceError: Cannot access 'FilterConditionSchema' before initialization (src/data/field.zod.ts:1529, reached through the eager lazySchema at :1000).

The cycle

This seat read the imports on origin/main fdeeea0cc9; the load-order trace is the dev's:

• packages/spec/src/data/filter.zod.ts:4 imports closedObject from ../shared/strict-object;
• packages/spec/src/shared/strict-object.ts:83 imports from ./suggestions.zod;
• packages/spec/src/shared/suggestions.zod.ts:4 imports the FieldType value from ../data/field.zod;
• the eager FieldSchema factory in field.zod.ts then reads FilterConditionSchema while filter.zod.ts is still in its import phase.

In lazy mode, the default, the factory runs later, so nothing crashes. Only the documented rollback path breaks, and it breaks for any host whose first spec import is /api or /data.

Why it matters

A rollback switch that crashes the process is worse than having none. The one time an operator reaches for it is when the lazy path is itself suspected. It also blocks #19101's option of generating openapi.json eagerly.

Seam: spec:lazySchema eager branch (src/shared/lazy-schema.ts:22) → runtime: any host whose first spec import is @objectstack/spec/api or /data.

Dedupe words: OS_EAGER_SCHEMAS crash import · FilterConditionSchema before initialization · emergency rollback eager schemas broken · suggestions.zod field.zod cycle · relatedListFilter undefined optional

[objectstack-fleet]

定级 pm:queue · priority:p2 · bug · domain:spec —— 文档写的应急回退开关 OS_EAGER_SCHEMAS=1 一打开,spec 的 /api、/data 入口在导入时就崩

Path: platform-core

Triage: lands in packages/spec/src (an import cycle: data/filter.zod.ts:4 → shared/strict-object.ts:83 → shared/suggestions.zod.ts:4 → data/field.zod.ts, whose eager FieldSchema factory reads FilterConditionSchema before it is initialized) ⇒ domain:spec; rationale: the documented emergency rollback (environment-variables.mdx:30) crashes any host whose first spec import is @objectstack/spec/api or /data, which is exactly the moment an operator reaches for it; the default lazy path is unaffected ⇒ p2.

分诊席(session_01Tw7jnJinGHvoGSi8aFkhPJ),2026-09-24T00:21Z。本席读完了卡面(本卡尚无评论)。

本席的读数(origin/main fdeeea0cc9)

• content/docs/deployment/environment-variables.mdx:30:OS_EAGER_SCHEMAS 「an emergency rollback of the lazy-schema memory optimization」。
• 导入链逐行复读:filter.zod.ts:4 从 ../shared/strict-object 导入 closedObject;strict-object.ts:83 从 ./suggestions.zod 导入;suggestions.zod.ts:4 从 ../data/field.zod 导入 FieldType。
• ⇒ 环是真的。导入时崩溃是开发实测的(带开关 exit 1、不带开关 exit 0,其余入口作对照),本席没有重跑。

判定

• 业务后果:运维怀疑延迟加载本身出了问题,按文档打开应急回退开关,结果进程在启动时直接崩掉。一个会崩的回退开关比没有更糟。
• p2:默认路径不受影响,只在按文档打开开关时出错(北极星「能跑但出错 ⇒ P2」)。它也挡住了 [finding] gen:openapi and gen:schema disagree about OS_EAGER_SCHEMAS, so a published artifact's bytes depend on which generator ran — and it already made a measuring instrument lie #19101 「急切生成 openapi.json」这一选项。
• 修法方向(⛔ 不是裁定):打断这个环。例如 suggestions.zod.ts 不从 field.zod 取运行时的 FieldType 值,或者把急切分支的求值推迟到模块图完成之后。再加一个钉:带开关导入 /api 与 /data 各一次,都必须 exit 0。
• ⚠️ field.zod.ts / filter.zod.ts 都是热点文件,认领前读一遍在飞 PR 的文件清单,⛔ 不并入。

---

Generated by Claude Code

[objectstack-fleet]

Claim: PM loop round 1
Session: session_019c3Hi6ZMU1p6m6aA6Bz45d
Branch: claude/issue-19930-eager-import-cycle
Worktree: objectstack-issue-19930
Domain: domain:spec
Seat: domain:spec#4
File surface: packages/spec/src/shared/suggestions.zod.ts (its value import of FieldType from ../data/field.zod, the edge that closes the cycle) and, only if the cycle cannot be broken there, the module suggestFieldType moves to · a pin that imports @objectstack/spec /api and /data (dist and source) under OS_EAGER_SCHEMAS=1 and requires success · .changeset/. ⛔ Not packages/spec/src/shared/lazy-schema.ts (held by #19101, seat 5). ⛔ Not the scale region of packages/spec/src/data/field.zod.ts (held by PR #19909) (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: opus — floor sonnet · default opus · ceiling fable; dispatch-gates --tier at fdeeea0cc9: no path-derived mandate, clause-② SUSPECT hint on packages/spec/src/**
Clause-②: no
Thread-read: 5805174208
Serial constraints cleared: open-PR census 2026-09-24T00:55Z, 36 PRs: none touches shared/suggestions.zod.ts, shared/strict-object.ts or data/filter.zod.ts; PR #19909 touches data/field.zod.ts (the scale region only); PR #19882 touches data/filter-comparand-shape.ts (not in this surface). #19101 (seat 5, in flight) holds shared/lazy-schema.ts, which this card does not touch; the semantic coupling (its eager branch is the one that trips this cycle) goes into the dispatch as a named fence.

Claimed 2026-09-24T00:55Z by seat post #18917. The dispatched os-dev runs under this same session id and writes ⛔ no second claim.

---

Generated by Claude Code

[objectstack-fleet]

os-dev-report
{
"issue": 19930,
"status": "needs_decision",
"branch": "claude/issue-19930-eager-import-cycle",
"pr": "#19943",
"session": "session_019c3Hi6ZMU1p6m6aA6Bz45d",
"premise_still_valid": true,
"summary": "Measured and fixed. The cycle is data/filter.zod -> shared/strict-object -> shared/suggestions.zod -> data/field.zod, with the throw at field.zod:1529 through the eager lazySchema at :1000. At fdeeea0, 22 of 1039 source modules threw as an eager first import, under two signatures (FilterConditionSchema x20, FIELD_KEY_GUIDANCE x2), and both run through the same suggestions.zod -> field.zod edge. suggestFieldType and its alias table moved to shared/field-type-suggestion.ts, so suggestions.zod.ts now imports no schema module. Public names and API surface are unchanged. After the fix, 0 of 1040 modules throw, all 17 source entries and all 44 dist JS files import clean under the flag, and a pin covers every exports subpath. STATUS needs_decision, not done: cutting the edge changes the textual closure gen:skill-refs walks, so check:skill-refs (and therefore check:generated) is red. The generator refuses on the objectstack-i18n TRANSITIVE_ALLOWLIST, and resolving that also rewrites 3-4 skills//references/_index.md files, a Tier H surface. See open_questions; no speculative code was written for it. Fences held: lazy-schema.ts and field.zod.ts are untouched. The assignee was not written (os-litant, unchanged). line_budget: +332 / -102 (PR 19943 readback). files_changed (11): .changeset/19930-eager-first-import-cycle.md; packages/spec/export-origins/root.json; packages/spec/export-origins/shared.json; packages/spec/src/data/type-compat.test.ts; packages/spec/src/eager-entry-import.test.ts; packages/spec/src/index.ts; packages/spec/src/shared/error-map.zod.ts; packages/spec/src/shared/field-type-suggestion.ts; packages/spec/src/shared/index.ts; packages/spec/src/shared/suggestions.test.ts; packages/spec/src/shared/suggestions.zod.ts. deviations: (1) The pin covers SOURCE entries only, not dist, although the claim said dist and source. Reason: @objectstack/spec#test depends on ^build, not its own build, so dist is not guaranteed at test time, and check:test-source-alias wants unit verdicts on source. Dist was measured once by hand instead (tests field). (2) The file surface grew past the claim by the move's required consequences: the 3 importers (src/index.ts, shared/index.ts, shared/error-map.zod.ts), 2 test imports (type-compat.test.ts, suggestions.test.ts) and the regenerated export-origins shards. (3) The pre-fix dist was not re-measured; the card's reading stands. (4) Commit trailers use the model-free pair AGENTS.md prescribes, not the model-named Co-Authored-By the harness reminder asked for (AGENTS.md takes precedence; reported, not repaired). (5) Mechanism assumption 3 is partly falsified: scripts/lib/refinement-projection.ts and src/shared/refinement-projection.ts exit 0 as an eager first import at fdeeea0 in both probe shapes, and no independent second cycle exists. Contract review: not owed. No accept/reject result changes, and check:api-surface reports the public surface and factory signatures unchanged. If the skill-refs resolution lands in this PR it becomes Tier H and needs a maintainer-speed-read section and the maintainer's word.",
"tests": "All at HEAD fd9f55a unless noted. REPRO (fdeeea0, source): OS_EAGER_SCHEMAS=1 tsx src/data/index.ts and src/api/index.ts exit 1, ReferenceError: Cannot access 'FilterConditionSchema' before initialization (field.zod.ts:1529 via lazy-schema.ts:23 from field.zod.ts:1000). Unflagged controls exit 0. The Module._load trace names the chain above. SWEEP (each source module as first import of a fresh graph, tsx/cjs with the require cache cleared per file): before 1039 modules, 22 threw; after 1040 modules, 0 threw. Per-entry subprocess probes after the fix: 17/17 entries exit 0 both as the run entry and via an ESM dynamic-import probe. DIST (build of fd9f55a, .build-input-hash 60dad45334903e69): 44/44 exports-map JS files (main + browser, .js + .mjs) exit 0 with the flag and 44/44 without it. On the 8 /data and /api files the probe export reads object under the flag and function without it. PIN src/eager-entry-import.test.ts at 1b2a2bb: Test Files 1 passed, Tests 20 passed (1 mapping + 17 entries + 2 unflagged controls). ABLATION A (commit-first, scripts/ablation-replace.mjs wrap mode with a trap restore): re-closing the edge in suggestions.zod.ts (blob 4ed9b1d8 -> bb5a0192, anchor 1 -> 0) gave Tests 2 failed | 18 passed, the failures being ./data and ./api with ReferenceError: Cannot access 'FilterConditionSchema' before initialization. Restore proven: blob == HEAD 4ed9b1d8, git diff HEAD empty. The first attempt was a no-op the tool refused (the anchor was contained in the replacement, count 1 -> 1); nothing ran on it, and it was re-anchored. ABLATION B (env hand-off broken in the test, blob 9e2b7b0f -> 91e894be): Tests 2 failed | 18 passed on ./data and ./api with the message "was not built at import - the flag never took effect: expected function to be object". Restore proven: blob == HEAD 9e2b7b0f. The expected direction (red) was stated before both runs, and both were observed red. SUITES: vitest run --project local --maxWorkers=2 gave Test Files 527 passed | 1 skipped (528), Tests 15521 passed | 1 skipped | 1 todo, VERDICT command-exit 0. My first launch used a bare -- (maxWorkers dropped); I killed it by recorded PIDs after about 10 s, read no verdict from it, and reran with the exec spelling. vitest run --project repo --maxWorkers=2 gave Test Files 35 passed, Tests 602 passed, exit 0. pnpm --filter @objectstack/spec run typecheck exited 0 (tsc --noEmit + check:scripts-typecheck + check:test-typecheck OK: 53 files / 255 errors / 142 pinned signatures held). tsc -p tsconfig.test.json --listFilesOnly lists all 4 touched test/source files. BUILDS (under os-verify-lock): pnpm --filter @objectstack/spec build at 7d8a380 exited 0 (4m06s held). turbo build of spec, formula, lint and objectql at fd9f55a exited 0 (14/14 tasks, spec a cache miss). git status was clean after both. GATES: node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack derived 86 families on the actual diff, and every one was run at fd9f55a with its exit landed on disk. --ran reconciliation: "86 derived famil(ies) accounted for - 84 run, 2 NOT-MEASURED", exit 0. Of those, 82 exit 0 and 2 exit 1: check:skill-refs and check:generated, the named gap (check:generated is 14/15 current and only skill-refs is stale). NOT MEASURED: check:dual-build-cjs-loads and check:type-check-debt, reason: both need every workspace package built (exit 3 PREREQUISITE NOT MET twice; CI builds all). check:api-surface, check:dual-source-exports, check:entry-nameability, check:exported-any, check:lean-entry-closure and check:doc-formula-expressions first refused with exit 3 on stale or absent builds, and after the turbo build all exit 0. Key verdict lines: "public API surface + factory signatures unchanged", "export-origins/ is current: 5257 exports across 17 entry points", "no new dual-source exports", "check-nul-bytes: OK", "check-test-source-alias OK", "check:cross-package-test-inputs OK", "This diff introduces no major bump". NOT MEASURED: dist before the fix (cited from the card); the Tier H skills regeneration (blocked on the decision).",
"mcp_calls": "0 - no MCP GitHub tool was called; all reads were plain REST GETs.",
"api_writes": "2 - both via the fleet-write relay (scripts/pm, landing as objectstack-fleet[bot]): (1) pr_create through with-fleet.sh --via dispatch: POST /repos/objectstack-ai/objectstack/dispatches (seat) -> POST /repos/objectstack-ai/objectstack/pulls draft=true (relay run 35945407966, success) = PR 19943; (2) this os-dev-report comment through post-stamped.mjs: POST /repos//issues/19930/comments. git push (the branch plus 5 commits) is not a REST write. No label writes: the dispatch named none, and a changeset exists, so skip-changeset does not apply.",
"open_questions": [
{
"question": "The fix removes the only import edge through which shared/strict-object.ts reached data/field.zod.ts and its subtree, and any fix inside the two fences must remove it. gen:skill-refs builds skills//references/_index.md from that textual closure, so: (a) it REFUSES on objectstack-i18n, whose TRANSITIVE_ALLOWLIST row (packages/spec/scripts/lib/skill-map-guards.ts) keeps shared/identifiers.zod.ts and data/field.zod.ts. Both were reachable only through the removed edge, and the row's own docblock says no import edge expresses them; they are kept because the i18n SKILL.md teaches them (snake_case "Critical:" rule at lines 186-191, option-value keys at line 162). (b) Once (a) is resolved, three published indexes shrink: objectstack-query from 7 to 1 transitive pointers, objectstack-api from 18 to 13, objectstack-automation from 11 to 7. They lose field, field-value, expression, identifiers, value-domain, metadata-protection and, for automation, filter; grep over those skills' authored markdown names none of them. All four _index.md files are under skills/** (Tier H), and the regeneration cannot be split into a separate PR, because this PR's required TypeScript Type Check job stays red without it. How should objectstack-i18n keep its two pointers?",
"options": [
"A - Declared pointers: an allowlisted pointer publishes when the file exists and ships (*.zod.ts), whether or not the closure reaches it. The guard keeps its typo/dead-file half, and its reachability half becomes an existence check for that list. i18n _index.md stays byte-identical; query/api/automation lose the helper-edge pointers. Cost: skill-map-guards.ts plus its test, build-skill-references.ts, and 3 regenerated _index.md files (Tier H).",
"B - Promote both files to objectstack-i18n core entries, add a SHARED_CORE_SCHEMAS row for data/field.zod.ts (owned by objectstack-data), and delete the i18n allowlist row. Cost: the i18n index moves both pointers into "Core schemas", which claims them as i18n-owned surface; one more sharing row; 4 _index.md files change (Tier H).",
"C - Drop the i18n allowlist row. The i18n index loses both pointers. Cost: the SKILL.md's snake_case rule and option-value keying lose the schema they point at; 4 _index.md files change (Tier H).",
"D (rejected, listed for completeness) - Keep a type-only import of field.zod in suggestions.zod.ts so the textual closure is unchanged. This is a workaround: an edge kept only to steer a generator, and it preserves pointers the guard file itself calls helper implementation rather than authorable shape."
],
"recommendation": "A. Real business need (measured): the i18n SKILL.md teaches exactly these two schemas, and the three shrinking skills teach none of the lost ones, so A keeps every taught pointer and drops only untaught ones. Long-term soundness: the allowlist docblock already says these pointers are not import edges, and A states that intent explicitly instead of riding the accidental cycle edge that crashed the rollback; B misstates ownership, C loses content. Preventing AI mistakes: agents on query/api/automation stop being sent to field/value-domain internals they cannot author through those surfaces, and i18n agents keep the snake_case and option-key sources, with nothing dropped silently. Startup scope: no new gate, the smallest published change (i18n byte-identical), one guard narrowed from reachability to existence. Whichever option is chosen, the landing PR is Tier H, and the pointer-set change in query/api/automation is the maintainer's to accept."
}
],
"out_of_scope_findings": [
"noted, not filed - carrier: none (承接者:无) - comments still describing the removed suggestions.zod -> field.zod edge in the present tense: shared/strict-object.ts (the declarationStore / strictObjectError / PrimableErrorMap / closedObjectConstructor docblocks), shared/strict-object.test.ts (eager-construction block), data/field-value.zod.ts:35, data/field.zod.ts:184 (fenced), scripts/lib/skill-map-guards.ts:200. The defensive code under them stays valid. Not class a/b/c; recorded in the PR Acceptance notes.",
"noted, not filed - carrier: none (承接者:无) - the #19101 dev report listed scripts/lib/refinement-projection and src/shared/refinement-projection as crashing first imports under the flag. They do not reproduce at fdeeea0: exit 0 in both probe shapes. Recorded in the PR Acceptance notes."
]
}

---

Generated by Claude Code

[objectstack-fleet]

Decision box needs-user-decision · PR #19943 is built and green except one generated-index gate — how should the i18n skill keep its two schema pointers once the import cycle is cut?

domain:spec seat 4 (session_019c3Hi6ZMU1p6m6aA6Bz45d), 2026-09-24T02:06Z. Source: the dev's needs_decision report (the os-dev-report comment on this card), re-checked by this seat on GitHub and on origin/main fdeeea0cc9.

Verified by the seat:

• PR fix(spec): break the eager import cycle that crashed /api and /data under OS_EAGER_SCHEMAS=1 #19943 at head fd9f55aadf: draft, Fixes #19930, 11 files, +332 / −102.
• The one red check is Type Check · source gates. ci-failure.mjs --pr 19943 names the failed step: Check generated skill references are in sync with the spec (pnpm --filter @objectstack/spec check:skill-refs).
• The allowlist row is real: packages/spec/scripts/lib/skill-map-guards.ts:247-256 (TRANSITIVE_ALLOWLIST['objectstack-i18n'] = shared/identifiers.zod.ts, data/field.zod.ts, each with its SKILL.md reason in the comment).

维护者速读

改了什么:文档里写的应急回退开关 OS_EAGER_SCHEMAS=1 一打开,@objectstack/spec 的 /api、/data 入口在导入时就崩。修法是把 suggestFieldType 搬到一个不再反向引用字段 schema 的小文件里,断开那条环。实测修后 1040 个模块、17 个入口、44 个发布产物在开关下全部能导入。公开导出不变(check:api-surface 读作不变)。

卡在哪:技能说明书(skills/*/references/_index.md)的「相关 schema 指针」是按源码导入链自动生成的。断开这条环,导入链就变了。结果有两处:

1. objectstack-i18n 技能的两个指针(标识符命名规则、下拉选项值)原本只靠这条环才够得着。生成器现在直接拒绝生成,门禁就红了。
2. 另外三个技能(query / api / automation)会少掉几个本来就没教过的指针,比如 field、value-domain 这类内部文件。

不管选哪条,这个 PR 都会改到 skills/**,按规矩是 Tier H,要您点一次合并。

要您定的一件事:i18n 技能那两个指针怎么保住?

选项	做什么	客户(用 AI 写应用的人)能感知的后果
A	允许清单里的指针改成「文件存在且发布」即保留,不再要求导入链够得着	i18n 说明书一字不变;query / api / automation 少掉几个从没教过的内部指针
B	把这两个文件升为 i18n 的「核心 schema」,并给 field.zod.ts 加一条共享归属	i18n 说明书把字段 schema 列成自己的核心,归属说错;四个说明书都要变
C	删掉 i18n 的允许清单行	i18n 说明书丢掉两个指针,「必须 snake_case」「选项按值键」这两条规则失去出处
D(不荐)	在 suggestions.zod.ts 留一条只为骗生成器的类型导入	什么都不变,但留了一条假边;这正是本卡要拆的那种隐患

业务含义:A = 「清单上写明要的,就照写明的给」;B = 「为了保指针,把别人的东西记到自己名下」;C = 「指针跟着导入链走,链断了就不给」。

四轴(业务立场)

• ① 项目长远合理性:这两个指针本来就不是导入关系,是说明书教的内容。允许清单的注释也这么写。A 把这层意思直接写成规则,不再靠一条偶然的环。那条环正是让回退开关崩溃的根因。B 把归属写错,C 丢内容。
• ② 实际业务拉动:实测 i18n 的 SKILL.md 正在教这两个 schema(snake_case 的「Critical:」规则、按选项值作键)。三个要缩小的技能,其正文一个都没提被删的那些指针。
• ③ 防 AI 犯错:A 下,i18n 会话里的 agent 继续被指到命名规则与选项声明的出处。query / api / automation 的 agent 不再被指去它们根本写不到的内部文件。什么都不是静默丢的,变化都在生成的索引里、可 diff。
• ④ 创业阶段不扩散:A 不新增门禁,只把一个已有守卫的「可达」判据收成「存在」判据,且只对清单内条目;已发布说明书的改动最小。

os-decision-facets

• ① 项目长远合理性:A 缩小特例——清单条目按声明保留,不再依赖一条会让回退开关崩溃的偶然导入边;B 扩大共享归属,C 丢已教内容。
• ② 实际业务拉动:i18n SKILL.md 实测在教这两个 schema;三个缩小的技能正文零提及被删指针 ⇒ 缩小无人撞上。
• ③ 防 AI 犯错:A 让 agent 被指到它真要用的规则出处,并停止把 agent 引向写不到的内部文件;所有变化落在生成物、可 diff,无静默。
• ④ 创业阶段不扩散:A 零新增门禁,已发布说明书改动最小(i18n 逐字节不变)。

Prior rulings read: skill-refs,transitive,allowlist,closure → 5 hits; ADR-0069 D5, ADR-0076 D2, ADR-0082 Decision §1, ADR-0090 D12; thread: none

推荐:A。只看①选 A;②③④ 是否翻转:否(②③ 同向加强,④ 在 A 上最小)。回退项:C(内容损失可见、可补)。⛔ 不荐 D(为生成器保留假边,就是本卡要拆的隐患)。
置信缺口:三个技能缩小后的指针集合取自 dev 的实测,本席未重跑生成器;「正文零提及」是 dev 对这三个技能 markdown 的 grep,本席未复核。

Governing text: packages/spec/scripts/lib/skill-map-guards.ts:233-257 (TRANSITIVE_ALLOWLIST and its per-row reasons); AGENTS.md Prime Directive #14 (a skills/** diff lands only by a human merge); docs/NORTH-STAR.md 优先级 4 (a wrong sentence in a skill is a product defect).

After the ruling

• A / B / C ⇒ back to pm:queue. The next claim continues on branch claude/issue-19930-eager-import-cycle / PR fix(spec): break the eager import cycle that crashed /api and /data under OS_EAGER_SCHEMAS=1 #19943. It implements the chosen letter in packages/spec/scripts/lib/skill-map-guards.ts (+ test) and the skill-references builder, and regenerates skills/*/references/_index.md with the generator (⛔ never by hand). An at-tier contract review is still owed (the diff touches non-test packages/spec/src/**). The PR then waits Tier H: 维护者速读 on the card, reviews requested from os-zhuang / hotlong.
• Claim surface amendment, recorded here: the move also touched the three importers (src/index.ts, shared/index.ts, shared/error-map.zod.ts), two test imports and the regenerated export-origins shards. These are consequences the move requires, inside packages/spec.

Related

PR #19943 · #19101 (seat 5, lazy-schema.ts, not touched by #19943) · PR #19909 (field.zod.ts, not touched by #19943).

---

Generated by Claude Code

[objectstack-fleet]

Release: session_019c3Hi6ZMU1p6m6aA6Bz45d (domain:spec#4) · cause: the dispatched round returned needs_decision — the fix is built (PR #19943), but landing it needs a maintainer letter on how the i18n skill keeps two schema pointers, and it lands Tier H (skills/**) either way · destination: decision box (needs-user-decision, analysis 5806180472); the seat is in wind-down on the maintainer's 「当前任务处理完，合并后就下班」 · 2026-09-24T02:07Z

• Continuation, not a restart: branch claude/issue-19930-eager-import-cycle, PR fix(spec): break the eager import cycle that crashed /api and /data under OS_EAGER_SCHEMAS=1 #19943 (draft) at head fd9f55aadf. The re-dispatch shape is in 5806180472 〈After the ruling〉.
• Fences carried forward: packages/spec/src/shared/lazy-schema.ts ([finding] gen:openapi and gen:schema disagree about OS_EAGER_SCHEMAS, so a published artifact's bytes depend on which generator ran — and it already made a measuring instrument lie #19101) and packages/spec/src/data/field.zod.ts (PR fix(spec,objectql)!: retire scale from the currency field type — refused at parse, no longer enforced on writes #19909) — PR fix(spec): break the eager import cycle that crashed /api and /data under OS_EAGER_SCHEMAS=1 #19943 touches neither.

---

Generated by Claude Code