os init and os generate still emit the annotated-literal .object.ts shape — item ① of ruling 5644350230, the sibling half of #17418 (and the ruling under-names it: generate.ts too)

Filed by domain:spec execution seat 2, session session_01UDXER3sdqfeVYpEWZs5mZx, 2026-09-22T11:1xZ. ⛔ Unlabelled and unrouted — an execution seat files, triage grades and routes. Suggested lane: domain:cli, because that is the lane the ruling itself names.

This is half of a ruled change, and the ruling drew the line

Ruling 5644350230 (director seat, decision batch #122 item 1, maintainer 「同意」 2026-09-12) makes ObjectSchema.create({ … }) the one authorised shape for a *.object.ts. Its item 4:

The taker declares the file surface; if it crosses packages/cli and packages/spec / scripts, the cli half is a sibling PR by the domain:cli seat, ⛔ not a rider across lanes.

The spec/scripts half — item ② (the gate refuses the non-factory shape by name) and item ③ (census and convert in-repo literal-shaped object files) — is card #17418 / PR #19720, which opens 「Part of #17418」 rather than Fixes precisely so the card stays open for this half. This card is item ①.

⚠️ The ruling UNDER-NAMES its own item ①

Item ① names only init.ts TEMPLATES. Measured: there is a second emitter, and it carries a declared coupling to the first.

site	what it emits
`packages/cli/src/commands/init.ts:649` and `:744`	the two TEMPLATES entries for `src/objects/__name___item.object.ts`, both emitting a `Data.ServiceObject`-annotated object literal
`packages/cli/src/commands/generate.ts:99`	`os generate object` emits the SAME annotated literal — ⛔ named nowhere in the ruling

generate.ts's own docblock declares the coupling, quoted:

「#9666 took it once for the os init templates, and this emits the SAME value with the same explanation, so the two doors an author can arrive through agree. If that template value ever moves, this one moves with it.」

⇒ converting init.ts alone breaks the parity that docblock asserts. Both move together or neither does.

Pins that move with them

packages/cli/test/generate-refuses-unparseable-name.test.ts:255 — asserts the emitted source contains a Data.ServiceObject binding line.
packages/cli/test/generate-emission-parses.test.ts:148 — same assertion, plus its docblock worked example at :14.
packages/cli/test/scaffold-emission-typechecks.test.ts:26 — its docblock states the repair is Data.ServiceObject.
packages/cli/test/init.test.ts:493 — reads the scaffolded my_app_item.object.ts; re-check its assertions against the new bytes.
packages/cli/test/init-template-comments-self-contained.test.ts — ⚠️ the templates carry a long authored org-wide-default comment block that must survive the rewrite.

Docblock only, ⛔ no behaviour change: packages/cli/src/utils/emitted-source-parses.ts:14 — the utility is shape-agnostic (it asks the TypeScript parser whether the emitted bytes parse); only its worked example names the literal shape.

Coupled, probably no edit: scripts/sync-scaffold-emission-policy.mjs (its POLICY_SOURCE is packages/cli/src/commands/init.ts) syncs pnpm/typescript version ranges, ⛔ not declaration shape — but re-run it, because create-objectstack's bundled note.object.ts is already the factory shape, so the two scaffolders would finally agree.

Docs: content/docs/deployment/cli.mdx:1323.

⭐ The changeset obligation is THIS card's, not the spec half's

The ruling asks the changeset to state the one mechanical user rewrite (wrap the literal). That rewrite is something a user experiences, and the user-facing change is item ① — os init and os generate emitting the factory shape from a published package. The spec half publishes nothing (scripts/ sits in no package directory; measured, 77 manifests censused for files[] escape hatches, zero found), so it carries skip-changeset. ⇒ the ruling's changeset obligation attaches here.

Ordering, measured rather than assumed

⛔ There is no blocking dependency in either direction, and this was measured rather than guessed. check:keyed-text-bounds selects its population by filename suffix (walkObjectFiles over *.object.ts, repo-wide minus SKIP_DIRS): 112 files on origin/main, ZERO under packages/cli. The TEMPLATES are string literals inside a .ts file, so the gate never reads them in any shape; and every cli scaffold test writes into os.tmpdir() via mkdtempSync, never the repo tree. os init emits into a user's project, which carries no scripts/ directory of this repo.

⇒ item ② can land first without turning anything red that only ① can fix, and it is landing first. But until this card lands, os init and os generate keep writing the shape the ruling refuses — which is the whole reason it is filed rather than left implied.

Duplicate-search words

ObjectSchema.create, Data.ServiceObject, os init templates, generate.ts scaffolder parity, ruling 5644350230 item 1

Generated by Claude Code

Triage: domain:cli (packages/cli/src/commands/init.ts + generate.ts) · p3 · Bug · area:devpath; rationale: the scaffolder still emits the annotated-literal object shape the published docs deny — ruling batch #122 item ①

Path: 一条命令起一个项目 | cli.scaffold-first-run | P① | p3
Graded by the triage seat (session_01Tw7jnJinGHvoGSi8aFkhPJ) at 2026-09-22T19:35Z.

Gate class ③ — this is maintainer-directed work. Ruling batch #122 item 1 (5644350230, maintainer verbatim 「同意」) names this exact deliverable, and kept the family at p3, which is why this is p3 and not higher.

Class (b) on a published surface: content/docs/data-modeling/schema-design.mdx states 「Every object definition follows this pattern:」 followed by ObjectSchema.create({…}). The producers that contradict it are the published os init and os generate commands.

⭐ Two files, one round — and this is measured, not assumed: generate.ts's own docblock says of the template value 「If that template's value ever moves, this one moves with it」. Splitting them would leave the pair inconsistent.

⚠️ ⛔ Not one round with #19723 / #19724. Three emitters, three packages, three lanes. Ruling item ③ names object files (examples, templates, fixtures), ⛔ not emitters, so it does not reach the other two at all.

Generated by Claude Code

Pointer from the `domain:services` half — three pins assert the REFUSED spelling and will redden this card's PR

domain:services PM seat · session_01AhQASwqJr2Z7XfGWUdvnbF · 2026-09-23T03:06Z

⛔ Not a request to act, ⛔ not a claim on this card, and ⛔ no new card filed — this is the pointer, and this comment is its whole record.

The sibling half of ruling 5644350230 item ① landed as PR #19776 for #19723 (service-datasource's renderObjectSource). While reviewing it I read packages/cli to confirm no cli change was owed there. It was not — datasource/introspect.ts:80 writes draft.source verbatim and knows nothing of the shape. But the same read turned up three places that pin the spelling this ruling refuses, all measured on origin/main:

file:line	what it pins
`packages/cli/src/utils/emitted-source-parses.ts:14`	documents `src/objects/foo.bar.object.ts -> const foo.bar: Data.ServiceObject = {` as the contract
`packages/cli/test/generate-emission-parses.test.ts:148`	`expect(scaffold.source).toContain('const foo.bar: Data.ServiceObject = {')`
`packages/cli/test/generate-refuses-unparseable-name.test.ts:255`	`expect(scaffold).toContain('const orderLine: Data.ServiceObject = {')`

⇒ whoever implements this card has to repoint all three in the same PR, or the emitter change goes green locally and red in CI on pins that assert the old shape. They are easy to miss because two of them live in test/ and the third is prose in a src/utils docblock.

For whatever it is worth to the implementer, the services half kept its export NAMED with no export default beside it (the scaffolded barrel re-exports by name), and used a value import of ObjectSchema — import type is elided at compile time and the emitted module would throw on its own first line. Both choices are argued in renderObjectSource's docblock on that branch.

⛔ The domain:cli routing, grading and scheduling of this card are not this seat's to touch.

Generated by Claude Code

Claim: PM loop round 3, second slot (batch 3; beside #20156 on a disjoint file surface)
Session: session_01UYBdGBzWSrAMzpW8ah3GbP
Account: os-litant
Branch: claude/issue-19722-scaffold-object-factory
Worktree: objectstack-issue-19722
Domain: domain:cli
Seat: domain:cli#1
File surface: packages/cli/src/commands/init.ts (the two TEMPLATES entries for the *.object.ts file) and packages/cli/src/commands/generate.ts (the os generate object emitter and its parity docblock), the docblock of packages/cli/src/utils/emitted-source-parses.ts, the pins that assert the emitted shape under packages/cli/test/ (generate-refuses-unparseable-name, generate-emission-parses, scaffold-emission-typechecks, init, init-template-comments-self-contained, and any other the dev finds asserting the literal), content/docs/deployment/cli.mdx (the line describing the scaffolded object file), and one .changeset/19722-*.md. Read-only here: packages/spec/** and scripts/** (the spec lane's half, landed as PR #19720), and packages/cli/src/utils/scaffold-validate.ts plus packages/cli/src/commands/{validate,compile,lint}.ts, which R2's PR #20164 holds until it merges. CHANGELOG.md and package.json files belong to the Version Packages PR. Stop on breach and explain in the report
Container & model: M, mode:subagent, model: default judgment tier (this act's node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --tier over the two command files answered: no path-derived mandate). It rewrites two emitters in lockstep and a user-facing migration note, so it gets the default judgment tier.
Clause-②: no
Thread-read: 5788276757
Serial constraints cleared: init.ts and generate.ts are touched by no open PR: the file lists of all 10 open non-release PRs were read in this act. R2's PR #20164 (in the merge queue) holds packages/cli/src/utils/scaffold-validate.ts and the validate/compile/lint commands, which are read-only for this claim. R3's first slot #20156 is packages/rest and packages/runtime, which are disjoint. The lane sibling #19098 also edits generate.ts; fold-or-serial answered SERIAL (fold gate ① fails: a JSON-Schema projection override is a different defect from the emitted object shape), so it waits for this card's merge. The spec-lane half (#17418) landed as PR #19720 (42339e2f), and #17418 carries Blocked-by: #19722, so this card unlocks it. The NORTH-STAR 优先级 3 pre-pick: the domain:cli pm:queue holds no open P0/P1 at this act, and every p2 there is fenced (#20139 on rest-server.ts behind #20156, #20150 on validate.ts behind #20164, #19328 behind PR #19637)

Taken 2026-09-27T05:42Z, origin/main 9347c1f2. Clause-②: no is the ruling's own item 4 (ruling 5644350230: 「no accept-set change on a published payload; an authoring-shape rule tightens on the CLI surface」). The dev posts no second claim; this comment is its identity on this card.

Generated by Claude Code

os-dev-report
{
"issue": 19722,
"status": "done",
"branch": "claude/issue-19722-scaffold-object-factory",
"pr": "#20195",
"session": "session_01UYBdGBzWSrAMzpW8ah3GbP — mode:subagent; the id the dispatch and the claim name, carried in every commit Claude-Session trailer",
"premise_still_valid": true,
"summary": "os init (TEMPLATES app + plugin object files) and os generate object now emit import { ObjectSchema } from '@objectstack/spec/data' + const X = ObjectSchema.create({ … }) + the unchanged export default X, replacing the Data.ServiceObject-annotated literal; the OWD comment block survives byte for byte, cli.mdx describes the factory (os init paragraph + os generate "What it does" line), and .changeset/19722-scaffold-object-factory.md (@objectstack/cli patch) carries the one mechanical user rewrite. Zone 2 measured: (1) all three emission sites confirmed by symbol; (2) tree-wide grep found the pointer comment's three pins plus two more asserting/naming the old binding (const class: discriminator in generate-emission-parses.test.ts, docblock in generate-refuses-name-outside-charset.test.ts) — all repointed; (3) BEFORE: os validate / os compile / tsc all exit 0 on os init + os g object scaffolds (the CLI never judged the shape), while check-keyed-text-bounds sweep() over the 4 scaffolded files gave 0 parsed / 4 shape violations; AFTER: CLI gates still 0, sweep() 4 parsed / 0 violations, and the compiled dist/objectstack.json is byte-identical (cmp) for both templates — the measured basis for Clause-②: no; (4) create-objectstack note.object.ts is already the factory shape; sync-scaffold-emission-policy reads only version ranges, its --check (gate 84) is green, no write. New pin packages/cli/test/scaffold-object-declaration-shape.test.ts parses every emitter with the TS parser and asserts value import, a single un-annotated ObjectSchema.create({…}) declaration, default export = that binding, and ONE signature across os init and os generate object (the docblock parity), with two refusing controls. files_changed: [.changeset/19722-scaffold-object-factory.md, content/docs/deployment/cli.mdx, packages/cli/src/commands/generate.ts, packages/cli/src/commands/init.ts, packages/cli/src/utils/emitted-source-parses.ts, packages/cli/test/generate-emission-parses.test.ts, packages/cli/test/generate-refuses-name-outside-charset.test.ts, packages/cli/test/generate-refuses-unparseable-name.test.ts, packages/cli/test/scaffold-emission-typechecks.test.ts, packages/cli/test/scaffold-object-declaration-shape.test.ts]. deviations: [(1) base — worktree cut from origin/main 3bd28e2, not the dispatch's 9347c1f, because origin/main had advanced 2 commits (incl. cli.mdx) at creation; later merged origin/main 836aad2 (PR #20164 landed on packages/cli, releasing the held validate/compile/lint/scaffold-validate files — none of which this diff touches) as merge commit 3082b02, no rebase, no force-push, suite re-run after; (2) route — Zone 3 suggested export const; kept const X = ObjectSchema.create(...) + export default X because both barrels (os init index.ts and the barrel line os generate appends for all 7 generators) re-export default, and this makes the emitted file exactly the changeset's mechanical rewrite of the old one; (3) file surface — beyond the named pins: a one-token docblock edit in generate-refuses-name-outside-charset.test.ts and the new parity pin file, both under the claim's "any other the dev finds"; (4) local gate run — my 300s per-gate timeout killed check:type-check-debt's internal whole-workspace turbo run build mid-flight, leaving packages/mcp and service-cluster-redis dist without .d.ts, which check:dual-build-cjs-loads then flagged (exit 1); rebuilt both, re-ran both gates to exit 0 (type-check-debt 232s under the lock); three gates first answered exit 3 PREREQUISITE NOT MET (spec check:skill-examples, check:dual-build-cjs-loads, check:i18n-coverage) — built the 11 packages lacking dist and re-ran, final exits below; (5) commit trailers are the model-free pair (dispatch + AGENTS.md) although this session's harness reminder asked for a model-named Co-Authored-By; PR footer uses the AGENTS.md session-URL form]. line_budget: n/a — no skills/** diff. Cleanup: worktree node_modules removed and ../objectstack-issue-19722 removed (clean, 0 porcelain lines). No dev server or monitor was started.",
"tests": "All readings on head 3082b02 (git rev-parse --short HEAD after the final commit; no push since). cli unit tier: pnpm --filter @objectstack/cli exec vitest run --project unit --maxWorkers=2 --shard=N/4 ×4 under os-verify-lock → VERDICT command-exit 0 each; 57+57+56+56 = 226 files, 949+780+723+747 = 3199 tests passed. (Unsharded run hit my own 560s timeout on the shared box and was replaced by the 4 shards; NOT a failure.) cli integration tier, run locally because the diff touches two integration-tier files (tierOfFile: childProcess, entryBasename, tsxBin): --project integration test/generate-refuses-unparseable-name.test.ts test/generate-refuses-name-outside-charset.test.ts → 2 files / 25 tests passed; the rest of the integration tier is declared to CI. pnpm --filter @objectstack/cli typecheck (tsc --noEmit + check:test-typecheck) → exit 0, "check:test-typecheck: OK … 3 file(s) / 28 error(s) / 6 pinned signature(s) held"; the new test file is in the test program (tsc -p tsconfig.test.json --listFilesOnly count = 1). Pre-merge head 20526f3: unit tier 225 files / 3163 tests passed, same 2 integration files 25/25, typecheck exit 0; targeted 7-file run 153/153. Ablation (subject resolves to src via relative import, no dist involved): fix committed first; node scripts/ablation-replace.mjs --file …/packages/cli/src/commands/generate.ts --anchor \"generate: (name: string) => import { ObjectSchema } from '@objectstack/spec/data';" --replacement "…import type { ObjectSchema }…" -- vitest run test/scaffold-object-declaration-shape.test.ts → tool: \"anchor 1 -> 0, blob 03b8006959dc -> c26fc17f63cc\"; run: 2 failed / 5 passed (\"ObjectSchemais not value-imported from '@objectstack/spec/data' (type-only)\" on the generate door, and the one-signature parity row); restore: \"blob == HEAD (03b8006959dc) andgit diff HEADis empty\", confirmed again by an outer hash-object compare. Direction observed: red, as expected. Scaffold probe (built CLI, os init app/plugin --no-install + os g object my_T_order_line, then os validate / os compile / tsc / check-keyed-text-bounds sweep()): base 3bd28e2b → CLI gates 0/0/0, sweep 0 parsed / 4 shapeViolations; branch → 0/0/0, sweep 4 parsed / 0 shapeViolations / 0 refusals; re-run on merged 3082b024 identical; dist/objectstack.json byte-identical before/after (sha256 3981f1ab… app, e6d2c61d… plugin).pnpm lint(full eslint . --no-inline-config, not a narrowing) → exit 0 in 107s on 3082b024. Gate reconciliation:node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --ran ran.list→ \"Run reconciliation — 94 derived, 94 run, 0 NOT-MEASURED, 0 UNRUN.\" / \"✓ dispatch-gates --ran: 94 derived famil(ies) accounted for — 94 run, 0 NOT-MEASURED\". The derivation's own out-of-list blocks (CI job steps, type-check lanes, artifact rosters) are NOT MEASURED locally, reason: CI-only shells / whole-workspace filters, per the tool's own stderr. gates (command → exit): node scripts/check-adr-0087-registration.mjs --base origin/main → 0 ; node scripts/check-adr-0087-registration.mjs --self-test → 0 ; node scripts/check-changeset-no-major.mjs --base origin/main → 0 ; node scripts/check-changeset-no-major.mjs --self-test → 0 ; node scripts/check-ci-filter-parity.mjs → 0 ; node scripts/check-closing-keyword-parity.mjs → 0 ; node scripts/check-closing-keyword-parity.mjs --self-test → 0 ; node scripts/check-comment-mask-adoption.mjs → 0 ; node scripts/check-comment-mask-adoption.mjs --self-test → 0 ; node scripts/check-comment-mask-corpus.mjs → 0 ; node scripts/check-doc-frontmatter.mjs → 0 ; node scripts/check-doc-frontmatter.mjs --self-test → 0 ; node scripts/check-doc-route-spelling.mjs --advisory → 0 ; node scripts/check-doc-route-spelling.mjs --self-test → 0 ; node scripts/check-docs-section-name.mjs → 0 ; node scripts/check-docs-section-name.mjs --self-test → 0 ; node scripts/check-empty-changeset.mjs --base origin/main → 0 ; node scripts/check-empty-changeset.mjs --self-test → 0 ; node scripts/check-keyed-text-bounds.mjs → 0 ; node scripts/check-keyed-text-bounds.mjs --self-test → 0 ; node scripts/check-platform-object-tenancy-census.mjs → 0 ; node scripts/check-platform-object-tenancy-census.mjs --self-test → 0 ; node scripts/check-plugin-teardown-shape.mjs → 0 ; node scripts/check-plugin-teardown-shape.mjs --self-test → 0 ; node scripts/check-registry-log-declared.mjs → 0 ; node scripts/check-registry-log-declared.mjs --self-test → 0 ; node scripts/check-rest-log-spy-declared.mjs → 0 ; node scripts/check-rest-log-spy-declared.mjs --self-test → 0 ; node scripts/check-section-landing-index.mjs → 0 ; node scripts/check-section-landing-index.mjs --self-test → 0 ; node scripts/check-system-context-census.mjs → 0 ; node scripts/check-system-context-census.mjs --self-test → 0 ; node scripts/check-undeclared-dep-imports.mjs → 0 ; node scripts/check-undeclared-dep-imports.mjs --self-test → 0 ; node scripts/docs-audit/check-affected-docs.mjs → 0 ; node scripts/docs-audit/check-drift-comment.mjs → 0 ; node scripts/pm/release-rehearsal-clone.mjs --self-test → 0 ; pnpm --filter @objectstack/lint run check:doc-formula-expressions → 0 ; pnpm --filter @objectstack/lint run check:doc-security-posture → 0 ; pnpm --filter @objectstack/spec run check:docs → 0 ; pnpm --filter @objectstack/spec run check:duration-unit-keys → 0 ; pnpm --filter @objectstack/spec run check:empty-state → 0 ; pnpm --filter @objectstack/spec run check:liveness → 0 ; pnpm --filter @objectstack/spec run check:strictness-ledger → 0 ; pnpm --filter @objectstack/spec run check:variant-docs → 0 ; pnpm --filter @objectstack/spec run check:yaml-examples → 0 ; pnpm check:changeset-gate-self-tests → 0 ; pnpm check:cli-examples-parity → 0 ; pnpm check:cli-test-child-env → 0 ; pnpm check:corpus-claim-drift → 0 ; pnpm check:cross-package-test-inputs → 0 ; pnpm check:dispatcher-error-vocabulary → 0 ; pnpm check:doc-anchors → 0 ; pnpm check:doc-authoring → 0 ; pnpm check:docs-audit-scope → 0 ; pnpm check:docs-redirects → 0 ; pnpm check:docs-single-h1 → 0 ; pnpm check:docs-spec-enumerations → 0 ; pnpm check:docs-transcript-drift → 0 ; pnpm check:driver-memory-census → 0 ; pnpm check:dts-closure → 0 ; pnpm check:engine-double-contract → 0 ; pnpm check:gitlink-declared → 0 ; pnpm check:i18n → 0 ; pnpm check:i18n-walk-parity → 0 ; pnpm check:issue-citations → 0 ; pnpm check:lean-entry-closure → 0 ; pnpm check:logger-receiver-detach → 0 ; pnpm check:nul-bytes → 0 ; pnpm check:objectql-double-limit → 0 ; pnpm check:objectui-changeset → 0 ; pnpm check:org-identifier → 0 ; pnpm check:page-declaration-shape → 0 ; pnpm check:pm-changeset-deadline-census → 0 ; pnpm check:published-files → 0 ; pnpm check:published-readme-links → 0 ; pnpm check:query-options-erasure → 0 ; pnpm check:react-page-adapter-contract → 0 ; pnpm check:refd-timer-probe → 0 ; pnpm check:role-word → 0 ; pnpm check:scaffold-emission-policy → 0 ; pnpm check:skill-identifier-liveness → 0 ; pnpm check:slot-lookup → 0 ; pnpm check:sourcemap-no-sources-content → 0 ; pnpm check:test-source-alias → 0 ; pnpm check:tier-file-adoption → 0 ; pnpm check:type-check-coverage → 0 ; pnpm check:vendor-version-stamps → 0 ; pnpm check:watch-hint-literal → 0 ; pnpm check:where-matcher → 0 ; pnpm --filter @objectstack/spec run check:skill-examples → 0 ; pnpm check:i18n-coverage → 0 ; pnpm check:dual-build-cjs-loads → 0 ; pnpm check:type-check-debt → 0 ; pnpm lint → 0 ; pnpm --filter @objectstack/cli typecheck → 0", "mcp_calls": "0 — no MCP GitHub tool was called (card, comments, ruling and PR read-back via unauthenticated REST GETs with curl)", "api_writes": "3 — each a fleet-write relay stroke (POST /repos/objectstack-ai/objectstack/dispatches, executed by fleet-write.yml as objectstack-fleet[bot]): (1) pr_create → POST /repos/objectstack-ai/objectstack/pulls (draft, #20195; body read back byte-identical, 8811 chars); (2) scripts/pm/label-write.mjs --issue 20195 --assign os-litant → POST /repos/objectstack-ai/objectstack/issues/20195/assignees (read-back matches; labels documentation/size-m/tests/tooling came from the path labeler, not this write; no label was written — the dispatch named none and the diff publishes, so no skip-changeset); (3) this os-dev-report → POST /repos/objectstack-ai/objectstack/issues/19722/comments via scripts/pm/post-stamped.mjs. Not REST: git push ×3 of the branch (empty-branch probe, 20526f3d, merge 3082b024).", "open_questions": [], "out_of_scope_findings": [ "class: a · reach: public dooros validate— in a project fromos init my-app -t app, os g object order_linewritesname: 'order_line'andos validate/os compilethen exit 1/2 with \"Object 'order_line' is missing the package namespace prefix. Rename it to 'my_app_order_line' (namespace = 'my_app')\"; measured on a CLI built at base 3bd28e2b (unchanged by this PR); the documented exampleos g object customer(cli.mdx os generate section) lands the same way · evidence: scaffold probe log validate-app at base · dedupe words: os generate object namespace prefix, missing the package namespace prefix, os g object customer validate, generate.ts toSnakeCase manifest namespace", "carrier: spec lane (the #17418 follow-up, which this card unblocks) ·scripts/check-keyed-text-bounds.mjsliteralShapeMessage says \"theos initshape imports only* as Data\", which after this PR describes the pre-change os init shape; scripts/** read-only here · noted in PR Acceptance notes, not filed", "carrier: 承接者:无 · check:type-check-debt --re-measure runs a whole-workspace turbo run build` although check:* gates run outside the verify lock; killed mid-build it leaves partial dist that later gates misread · noted in PR Acceptance notes only"
]
}

Generated by Claude Code

REWORK (patch round 1): PR #20195 at `3082b024`, one documentation sentence

_{domain:cli execution PM seat #6024 · session session_01UYBdGBzWSrAMzpW8ah3GbP · review verdict, written 2026-09-27T07:38Z}

CI on 3082b024: 34 success, and 2 skips that are rostered expected skips. The diff is not governed (check-governed-merges --pr 20195: 298 lines).
The at-tier independent contract review answered FAIL on one item (record 5853875973); the seat verified it at source. content/docs/deployment/cli.mdx:1450 now says the other generator types emit typed literals, but os g skill emits defineSkill({ … }) (generate.ts:379). The fix is one sentence. Everything else the review judged correct:
- both emitters emit the factory shape the ruling authorises;
- the OWD comment block survives;
- the pins fail on the old shape;
- the changeset states ruling item 3's rewrite;
- patch and Clause-②: no (ruling item 4);
- no held file was touched.
Out-of-scope findings:
- os g object in an os init app omits the namespace prefix, so os validate refuses it → filed [finding] os generate object NAME in an os init -t app project writes name: 'NAME' with no namespace prefix, so the next os validate refuses the object the CLI just generated #20197;
- the gate's refusal text in scripts/check-keyed-text-bounds.mjs still describes the old os init shape → spec lane, noted in the PR's Acceptance notes (carrier: Two official scaffolders and two published docs disagree on how a .object.ts may be written — ObjectSchema.create() factory vs plain annotated literal #17418's follow-up);
- check:type-check-debt's whole-workspace build leaves a partial dist when killed → Acceptance notes only.

Patch round to the same dev, on the same claim and branch.

Generated by Claude Code

os-dev-report
{
"issue": 19722,
"status": "done",
"branch": "claude/issue-19722-scaffold-object-factory",
"pr": "#20195",
"session": "session_01UYBdGBzWSrAMzpW8ah3GbP — mode:subagent; the id the dispatch and the claim name, carried in every commit Claude-Session trailer",
"premise_still_valid": true,
"summary": "ROUND 1 (patch, same claim/branch; review of record PR comment 5853875973, VERDICT FAIL on one item): corrected content/docs/deployment/cli.mdx "What it does" item 1 — the clause "the other types as typed literals (UI.View, Automation.Flow, etc.)" was false for skill (generate.ts GENERATORS.skill emits defineSkill({ … })). It now reads, as one sentence: "an object declared with ObjectSchema.create({ … }), the same shape the os init templates write; a skill declared with defineSkill({ … }); the other types as typed literals (UI.View, UI.Action, Automation.Flow, UI.Dashboard, UI.App)" — each of the five literal annotations read off its GENERATORS entry (view/action/flow/dashboard/app); nothing else changed. Round-1 commits: worktree recreated from the pushed head 3082b02; origin/main had moved, so merged d7c0241 as e5499d5 (clean; delta vs main still exactly the 10 PR files; the incoming work touched one cli test file, not this diff), then docs commit 468000c; one git push 3082b02..468000c. origin/main moved again afterwards to 560b724 (one formula commit, touching neither packages/cli nor cli.mdx) and was not merged. PR body — NOT patched by me; seat to apply these exact find/replace pairs (current body is byte-identical to what I sent): (A) find: "that line now describes the factory, and the os init section gains" → replace: "that line now describes the factory (and names defineSkill({ … }) for skill, the one non-object type that is not a typed literal), and the os init section gains"; (B) find: "## Verification (head 3082b024, after merging origin/main 836aad2a)" → replace: "## Verification (head 3082b024, after merging origin/main 836aad2a; round 1 at 468000c4 below)"; (C) find: "- Before the merge (head 20526f3d): unit tier 225 files / 3163 tests passed, the same two integration files 25/25, typecheck exit 0." → replace: that same line, then a new line "- Round 1 (head 468000c4: origin/main d7c02413 merged as e5499d52, then the one-sentence cli.mdx correction naming defineSkill for skill): the 41 docs-scoped gates (dispatch-gates --commands content/docs/deployment/cli.mdx) all exit 0, --ran 41 of 41 accounted for, 0 NOT-MEASURED; pnpm lint exit 0; node scripts/check-issue-citations.mjs answered no issue citations added against d7c024133 (3 file(s) read). The cli test tiers were not re-run locally on this head; CI runs them." — ROUND 0 (unchanged record follows): os init (TEMPLATES app + plugin object files) and os generate object now emit import { ObjectSchema } from '@objectstack/spec/data' + const X = ObjectSchema.create({ … }) + the unchanged export default X, replacing the Data.ServiceObject-annotated literal; the OWD comment block survives byte for byte, cli.mdx describes the factory (os init paragraph + os generate "What it does" line), and .changeset/19722-scaffold-object-factory.md (@objectstack/cli patch) carries the one mechanical user rewrite. Zone 2 measured: (1) all three emission sites confirmed by symbol; (2) tree-wide grep found the pointer comment's three pins plus two more asserting/naming the old binding (const class: discriminator in generate-emission-parses.test.ts, docblock in generate-refuses-name-outside-charset.test.ts) — all repointed; (3) BEFORE: os validate / os compile / tsc all exit 0 on os init + os g object scaffolds (the CLI never judged the shape), while check-keyed-text-bounds sweep() over the 4 scaffolded files gave 0 parsed / 4 shape violations; AFTER: CLI gates still 0, sweep() 4 parsed / 0 violations, and the compiled dist/objectstack.json is byte-identical (cmp) for both templates — the measured basis for Clause-②: no; (4) create-objectstack note.object.ts is already the factory shape; sync-scaffold-emission-policy reads only version ranges, its --check (gate 84) is green, no write. New pin packages/cli/test/scaffold-object-declaration-shape.test.ts parses every emitter with the TS parser and asserts value import, a single un-annotated ObjectSchema.create({…}) declaration, default export = that binding, and ONE signature across os init and os generate object (the docblock parity), with two refusing controls. files_changed (whole PR; round 1 touched only content/docs/deployment/cli.mdx): [.changeset/19722-scaffold-object-factory.md, content/docs/deployment/cli.mdx, packages/cli/src/commands/generate.ts, packages/cli/src/commands/init.ts, packages/cli/src/utils/emitted-source-parses.ts, packages/cli/test/generate-emission-parses.test.ts, packages/cli/test/generate-refuses-name-outside-charset.test.ts, packages/cli/test/generate-refuses-unparseable-name.test.ts, packages/cli/test/scaffold-emission-typechecks.test.ts, packages/cli/test/scaffold-object-declaration-shape.test.ts]. deviations: [(1) base — worktree cut from origin/main 3bd28e2, not the dispatch's 9347c1f, because origin/main had advanced 2 commits (incl. cli.mdx) at creation; later merged origin/main 836aad2 (PR #20164 landed on packages/cli, releasing the held validate/compile/lint/scaffold-validate files — none of which this diff touches) as merge commit 3082b02, no rebase, no force-push, suite re-run after; (2) route — Zone 3 suggested export const; kept const X = ObjectSchema.create(...) + export default X because both barrels (os init index.ts and the barrel line os generate appends for all 7 generators) re-export default, and this makes the emitted file exactly the changeset's mechanical rewrite of the old one; (3) file surface — beyond the named pins: a one-token docblock edit in generate-refuses-name-outside-charset.test.ts and the new parity pin file, both under the claim's "any other the dev finds"; (4) local gate run — my 300s per-gate timeout killed check:type-check-debt's internal whole-workspace turbo run build mid-flight, leaving packages/mcp and service-cluster-redis dist without .d.ts, which check:dual-build-cjs-loads then flagged (exit 1); rebuilt both, re-ran both gates to exit 0 (type-check-debt 232s under the lock); three gates first answered exit 3 PREREQUISITE NOT MET (spec check:skill-examples, check:dual-build-cjs-loads, check:i18n-coverage) — built the 11 packages lacking dist and re-ran, final exits below; (5) commit trailers are the model-free pair (dispatch + AGENTS.md) although this session's harness reminder asked for a model-named Co-Authored-By; PR footer uses the AGENTS.md session-URL form]. line_budget: n/a — no skills/** diff. Cleanup (both rounds): worktree node_modules removed and ../objectstack-issue-19722 removed (clean, 0 porcelain lines); round 1 recreated it from 3082b02 and removed it again after the push. No dev server or monitor was started.",
"tests": "ROUND 1 readings, all on head 468000c (the pushed head; git rev-parse --short HEAD → 468000c): docs-scoped gates: node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands content/docs/deployment/cli.mdx derived 41 commands (29 pnpm, 12 node); every one exit 0 (spec/lint/client-react closure built first under the lock so the dist-reading gates measured: check:docs "✅ 226 generated files in sync", check:skill-examples "✅ 259 prose examples type-check", check:doc-anchors "378 internal #fragment link(s) … all resolve"). --ran over the same path: "Run reconciliation — 41 derived, 41 run, 0 NOT-MEASURED, 0 UNRUN." The unscoped derivation at 468000c is the same 94-command list as round 0 (diff empty). pnpm lint (full, not a narrowing) → exit 0, 121s. Board citation check, diff-scoped: node scripts/check-issue-citations.mjs → exit 0, verbatim "✅ check-issue-citations: no issue citations added against d7c0241 (3 file(s) read)." — the 3 files are the non-test package sources in its declared surface (generate.ts, init.ts, emitted-source-parses.ts); the one added #N-shaped token there, "decision batch #122", is a NON_CITATION_HEADS ordinal by the gate's own grammar; .changeset/** and test docblocks are its declared DEFERRED surfaces, so the changeset's "(#19722)" is not judged by it. NOT MEASURED on 468000c: cli unit/integration tiers and cli typecheck — reason: round scope set by the coordinator (docs gates + lint + citations); the round-1 diff is one docs sentence plus a clean merge whose only packages/cli file is a test this diff does not touch; CI runs the farm on the new head. round-1 gates (command → exit): node scripts/check-ci-filter-parity.mjs → 0 ; node scripts/check-closing-keyword-parity.mjs → 0 ; node scripts/check-closing-keyword-parity.mjs --self-test → 0 ; node scripts/check-comment-mask-corpus.mjs → 0 ; node scripts/check-doc-frontmatter.mjs → 0 ; node scripts/check-doc-frontmatter.mjs --self-test → 0 ; node scripts/check-doc-route-spelling.mjs --advisory → 0 ; node scripts/check-doc-route-spelling.mjs --self-test → 0 ; node scripts/check-docs-section-name.mjs → 0 ; node scripts/check-docs-section-name.mjs --self-test → 0 ; node scripts/check-section-landing-index.mjs → 0 ; node scripts/check-section-landing-index.mjs --self-test → 0 ; pnpm --filter @objectstack/lint run check:doc-formula-expressions → 0 ; pnpm --filter @objectstack/lint run check:doc-security-posture → 0 ; pnpm --filter @objectstack/spec run check:docs → 0 ; pnpm --filter @objectstack/spec run check:empty-state → 0 ; pnpm --filter @objectstack/spec run check:liveness → 0 ; pnpm --filter @objectstack/spec run check:skill-examples → 0 ; pnpm --filter @objectstack/spec run check:strictness-ledger → 0 ; pnpm --filter @objectstack/spec run check:variant-docs → 0 ; pnpm --filter @objectstack/spec run check:yaml-examples → 0 ; pnpm check:cli-examples-parity → 0 ; pnpm check:corpus-claim-drift → 0 ; pnpm check:cross-package-test-inputs → 0 ; pnpm check:doc-anchors → 0 ; pnpm check:doc-authoring → 0 ; pnpm check:docs-audit-scope → 0 ; pnpm check:docs-redirects → 0 ; pnpm check:docs-single-h1 → 0 ; pnpm check:docs-spec-enumerations → 0 ; pnpm check:docs-transcript-drift → 0 ; pnpm check:driver-memory-census → 0 ; pnpm check:gitlink-declared → 0 ; pnpm check:nul-bytes → 0 ; pnpm check:published-readme-links → 0 ; pnpm check:react-page-adapter-contract → 0 ; pnpm check:refd-timer-probe → 0 ; pnpm check:role-word → 0 ; pnpm check:skill-identifier-liveness → 0 ; pnpm check:vendor-version-stamps → 0 ; pnpm check:watch-hint-literal → 0 ; pnpm lint → 0 ; node scripts/check-issue-citations.mjs → 0. — ROUND 0 readings (head 3082b02) follow unchanged: All readings on head 3082b02 (git rev-parse --short HEAD after the final commit; no push since). cli unit tier: pnpm --filter @objectstack/cli exec vitest run --project unit --maxWorkers=2 --shard=N/4 ×4 under os-verify-lock → VERDICT command-exit 0 each; 57+57+56+56 = 226 files, 949+780+723+747 = 3199 tests passed. (Unsharded run hit my own 560s timeout on the shared box and was replaced by the 4 shards; NOT a failure.) cli integration tier, run locally because the diff touches two integration-tier files (tierOfFile: childProcess, entryBasename, tsxBin): --project integration test/generate-refuses-unparseable-name.test.ts test/generate-refuses-name-outside-charset.test.ts → 2 files / 25 tests passed; the rest of the integration tier is declared to CI. pnpm --filter @objectstack/cli typecheck (tsc --noEmit + check:test-typecheck) → exit 0, "check:test-typecheck: OK … 3 file(s) / 28 error(s) / 6 pinned signature(s) held"; the new test file is in the test program (tsc -p tsconfig.test.json --listFilesOnly count = 1). Pre-merge head 20526f3: unit tier 225 files / 3163 tests passed, same 2 integration files 25/25, typecheck exit 0; targeted 7-file run 153/153. Ablation (subject resolves to src via relative import, no dist involved): fix committed first; node scripts/ablation-replace.mjs --file …/packages/cli/src/commands/generate.ts --anchor \"generate: (name: string) => import { ObjectSchema } from '@objectstack/spec/data';" --replacement "…import type { ObjectSchema }…" -- vitest run test/scaffold-object-declaration-shape.test.ts → tool: \"anchor 1 -> 0, blob 03b8006959dc -> c26fc17f63cc\"; run: 2 failed / 5 passed (\"ObjectSchemais not value-imported from '@objectstack/spec/data' (type-only)\" on the generate door, and the one-signature parity row); restore: \"blob == HEAD (03b8006959dc) andgit diff HEADis empty\", confirmed again by an outer hash-object compare. Direction observed: red, as expected. Scaffold probe (built CLI, os init app/plugin --no-install + os g object my_T_order_line, then os validate / os compile / tsc / check-keyed-text-bounds sweep()): base 3bd28e2b → CLI gates 0/0/0, sweep 0 parsed / 4 shapeViolations; branch → 0/0/0, sweep 4 parsed / 0 shapeViolations / 0 refusals; re-run on merged 3082b024 identical; dist/objectstack.json byte-identical before/after (sha256 3981f1ab… app, e6d2c61d… plugin).pnpm lint(full eslint . --no-inline-config, not a narrowing) → exit 0 in 107s on 3082b024. Gate reconciliation:node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --ran ran.list→ \"Run reconciliation — 94 derived, 94 run, 0 NOT-MEASURED, 0 UNRUN.\" / \"✓ dispatch-gates --ran: 94 derived famil(ies) accounted for — 94 run, 0 NOT-MEASURED\". The derivation's own out-of-list blocks (CI job steps, type-check lanes, artifact rosters) are NOT MEASURED locally, reason: CI-only shells / whole-workspace filters, per the tool's own stderr. gates (command → exit): node scripts/check-adr-0087-registration.mjs --base origin/main → 0 ; node scripts/check-adr-0087-registration.mjs --self-test → 0 ; node scripts/check-changeset-no-major.mjs --base origin/main → 0 ; node scripts/check-changeset-no-major.mjs --self-test → 0 ; node scripts/check-ci-filter-parity.mjs → 0 ; node scripts/check-closing-keyword-parity.mjs → 0 ; node scripts/check-closing-keyword-parity.mjs --self-test → 0 ; node scripts/check-comment-mask-adoption.mjs → 0 ; node scripts/check-comment-mask-adoption.mjs --self-test → 0 ; node scripts/check-comment-mask-corpus.mjs → 0 ; node scripts/check-doc-frontmatter.mjs → 0 ; node scripts/check-doc-frontmatter.mjs --self-test → 0 ; node scripts/check-doc-route-spelling.mjs --advisory → 0 ; node scripts/check-doc-route-spelling.mjs --self-test → 0 ; node scripts/check-docs-section-name.mjs → 0 ; node scripts/check-docs-section-name.mjs --self-test → 0 ; node scripts/check-empty-changeset.mjs --base origin/main → 0 ; node scripts/check-empty-changeset.mjs --self-test → 0 ; node scripts/check-keyed-text-bounds.mjs → 0 ; node scripts/check-keyed-text-bounds.mjs --self-test → 0 ; node scripts/check-platform-object-tenancy-census.mjs → 0 ; node scripts/check-platform-object-tenancy-census.mjs --self-test → 0 ; node scripts/check-plugin-teardown-shape.mjs → 0 ; node scripts/check-plugin-teardown-shape.mjs --self-test → 0 ; node scripts/check-registry-log-declared.mjs → 0 ; node scripts/check-registry-log-declared.mjs --self-test → 0 ; node scripts/check-rest-log-spy-declared.mjs → 0 ; node scripts/check-rest-log-spy-declared.mjs --self-test → 0 ; node scripts/check-section-landing-index.mjs → 0 ; node scripts/check-section-landing-index.mjs --self-test → 0 ; node scripts/check-system-context-census.mjs → 0 ; node scripts/check-system-context-census.mjs --self-test → 0 ; node scripts/check-undeclared-dep-imports.mjs → 0 ; node scripts/check-undeclared-dep-imports.mjs --self-test → 0 ; node scripts/docs-audit/check-affected-docs.mjs → 0 ; node scripts/docs-audit/check-drift-comment.mjs → 0 ; node scripts/pm/release-rehearsal-clone.mjs --self-test → 0 ; pnpm --filter @objectstack/lint run check:doc-formula-expressions → 0 ; pnpm --filter @objectstack/lint run check:doc-security-posture → 0 ; pnpm --filter @objectstack/spec run check:docs → 0 ; pnpm --filter @objectstack/spec run check:duration-unit-keys → 0 ; pnpm --filter @objectstack/spec run check:empty-state → 0 ; pnpm --filter @objectstack/spec run check:liveness → 0 ; pnpm --filter @objectstack/spec run check:strictness-ledger → 0 ; pnpm --filter @objectstack/spec run check:variant-docs → 0 ; pnpm --filter @objectstack/spec run check:yaml-examples → 0 ; pnpm check:changeset-gate-self-tests → 0 ; pnpm check:cli-examples-parity → 0 ; pnpm check:cli-test-child-env → 0 ; pnpm check:corpus-claim-drift → 0 ; pnpm check:cross-package-test-inputs → 0 ; pnpm check:dispatcher-error-vocabulary → 0 ; pnpm check:doc-anchors → 0 ; pnpm check:doc-authoring → 0 ; pnpm check:docs-audit-scope → 0 ; pnpm check:docs-redirects → 0 ; pnpm check:docs-single-h1 → 0 ; pnpm check:docs-spec-enumerations → 0 ; pnpm check:docs-transcript-drift → 0 ; pnpm check:driver-memory-census → 0 ; pnpm check:dts-closure → 0 ; pnpm check:engine-double-contract → 0 ; pnpm check:gitlink-declared → 0 ; pnpm check:i18n → 0 ; pnpm check:i18n-walk-parity → 0 ; pnpm check:issue-citations → 0 ; pnpm check:lean-entry-closure → 0 ; pnpm check:logger-receiver-detach → 0 ; pnpm check:nul-bytes → 0 ; pnpm check:objectql-double-limit → 0 ; pnpm check:objectui-changeset → 0 ; pnpm check:org-identifier → 0 ; pnpm check:page-declaration-shape → 0 ; pnpm check:pm-changeset-deadline-census → 0 ; pnpm check:published-files → 0 ; pnpm check:published-readme-links → 0 ; pnpm check:query-options-erasure → 0 ; pnpm check:react-page-adapter-contract → 0 ; pnpm check:refd-timer-probe → 0 ; pnpm check:role-word → 0 ; pnpm check:scaffold-emission-policy → 0 ; pnpm check:skill-identifier-liveness → 0 ; pnpm check:slot-lookup → 0 ; pnpm check:sourcemap-no-sources-content → 0 ; pnpm check:test-source-alias → 0 ; pnpm check:tier-file-adoption → 0 ; pnpm check:type-check-coverage → 0 ; pnpm check:vendor-version-stamps → 0 ; pnpm check:watch-hint-literal → 0 ; pnpm check:where-matcher → 0 ; pnpm --filter @objectstack/spec run check:skill-examples → 0 ; pnpm check:i18n-coverage → 0 ; pnpm check:dual-build-cjs-loads → 0 ; pnpm check:type-check-debt → 0 ; pnpm lint → 0 ; pnpm --filter @objectstack/cli typecheck → 0", "mcp_calls": "0 — no MCP GitHub tool was called in either round (card, comments, ruling, review 5853875973 and PR read-backs via unauthenticated REST GETs with curl)", "api_writes": "Round 1: 1 — this os-dev-report → POST /repos/objectstack-ai/objectstack/issues/19722/comments via scripts/pm/post-stamped.mjs over the fleet-write relay (POST /repos/objectstack-ai/objectstack/dispatches, executed as objectstack-fleet[bot]); plus onegit push(3082b024..468000c4, not REST); the PR body was NOT patched (find/replace pairs are in summary). Round 0 (unchanged): 3 — each a fleet-write relay stroke (POST /repos/objectstack-ai/objectstack/dispatches, executed by fleet-write.yml as objectstack-fleet[bot]): (1) pr_create → POST /repos/objectstack-ai/objectstack/pulls (draft, #20195; body read back byte-identical, 8811 chars); (2) scripts/pm/label-write.mjs --issue 20195 --assign os-litant → POST /repos/objectstack-ai/objectstack/issues/20195/assignees (read-back matches; labels documentation/size-m/tests/tooling came from the path labeler, not this write; no label was written — the dispatch named none and the diff publishes, so no skip-changeset); (3) the round-0 os-dev-report (comment 5853702489) → POST /repos/objectstack-ai/objectstack/issues/19722/comments via scripts/pm/post-stamped.mjs. Not REST: git push ×3 of the branch (empty-branch probe, 20526f3d, merge 3082b024).", "open_questions": [], "out_of_scope_findings": [ "class: a · reach: public dooros validate— in a project fromos init my-app -t app, os g object order_linewritesname: 'order_line'andos validate/os compilethen exit 1/2 with \"Object 'order_line' is missing the package namespace prefix. Rename it to 'my_app_order_line' (namespace = 'my_app')\"; measured on a CLI built at base 3bd28e2b (unchanged by this PR); the documented exampleos g object customer(cli.mdx os generate section) lands the same way · evidence: scaffold probe log validate-app at base · dedupe words: os generate object namespace prefix, missing the package namespace prefix, os g object customer validate, generate.ts toSnakeCase manifest namespace", "carrier: spec lane (the #17418 follow-up, which this card unblocks) ·scripts/check-keyed-text-bounds.mjsliteralShapeMessage says \"theos initshape imports only* as Data\", which after this PR describes the pre-change os init shape; scripts/** read-only here · noted in PR Acceptance notes, not filed", "carrier: 承接者:无 · check:type-check-debt --re-measure runs a whole-workspace turbo run build` although check:* gates run outside the verify lock; killed mid-build it leaves partial dist that later gates misread · noted in PR Acceptance notes only"
]
}

Generated by Claude Code

ACCEPT: PR #20195 at `468000c4`, R3 of the `domain:cli` seat (after patch round 1)

_{domain:cli execution PM seat #6024 · session session_01UYBdGBzWSrAMzpW8ah3GbP · review of record, written 2026-09-27T08:09Z}

Reviewed against GitHub and origin/main, not against the report.

Checklist:

PR shape: draft, base main. The first line is Fixes #19722, and it is the body's only closing keyword. A line-initial Clause-②: no is present. The seat wrote the round-1 body edits from the dev's 3 find/replace pairs; the body reads back byte-identical.
Scope: 10 files, none governed (check-governed-merges --pr 20195: NOT governed; 298 changed lines, under 5000). Everything is inside the claimed surface: the two os init object templates, the os generate object emitter, the emission-parse helper, their pins, one new declaration-shape pin, content/docs/deployment/cli.mdx, and the @objectstack/cli patch changeset. @objectstack/cli is published. Nothing under content/docs/releases/. No file held by another in-flight card is touched.
Fix: read in the diff. All three emitters write import { ObjectSchema } from '@objectstack/spec/data' plus const X = ObjectSchema.create({ … }) and the unchanged export default X, in place of the Data.ServiceObject-annotated literal. The OWD comment block survives. The compiled dist/objectstack.json of both templates is byte-identical before and after (the dev's measured basis for Clause-②: no).
Tests: the new pin parses every emitter and asserts one declaration signature across os init and os generate object, with two refusing controls. The recorded ablation (value import swapped to import type) turns it red; restore proven.
CI on head 468000c4: 32 checks success by latest name, including TypeScript Type Check, Test Core, Lint & Repo Gates and Build Docs. 4 are skipped: Auto Label, Check PR Size, Console Pin Gate and Packed-tarball smoke (opt-in), each a rostered expected skip in scripts/pm/check-expected-skips.mjs.
Contract review (changeset prose and content/docs): round 0 answered FAIL (5853875973, the cli.mdx sentence called every non-object type a typed literal, but skill emits defineSkill). The seat verified the round-1 sentence against every GENERATORS entry at the head. The delta review on this head answered PASS (5854084066). Both were at-tier independent agents given only the card, the rulings and the PR.

Decisions of record:

Clause-②: no + patch: upheld by both reviews. No published accept set moves: ObjectSchema is .strict() for both shapes, and the compiled artifact is unchanged.
The route kept const X = ObjectSchema.create(…) + export default X rather than export const, because both barrels re-export default. Upheld: it makes the emitted file exactly the changeset's one mechanical rewrite.

Out-of-scope findings:

os g object in an os init app omits the namespace prefix, so os validate refuses it → filed [finding] os generate object NAME in an os init -t app project writes name: 'NAME' with no namespace prefix, so the next os validate refuses the object the CLI just generated #20197 (round 0).
scripts/check-keyed-text-bounds.mjs refusal text still describes the old os init shape → Acceptance notes in the PR, carrier: Two official scaffolders and two published docs disagree on how a .object.ts may be written — ObjectSchema.create() factory vs plain annotated literal #17418's follow-up in the spec lane.
generate.ts Args.type help lists six types and omits skill (pre-existing help string) → carrier: this seat's next generate.ts dispatch ([finding] os generate projects ObjectStackDefinitionSchema through THREE override-less z.toJSONSchema calls — the schema an author's editor validates against is wider than the runtime, at 7 measured sites #19098), as a declared rider in its order.
check:type-check-debt's whole-workspace build leaves a partial dist when killed → Acceptance notes only.

Next: landing through the relay ops pr_ready + automerge_enable. This unlocks #17418 (Blocked-by: #19722) at merge.

Generated by Claude Code

Landed: PR #20195 → `0bd11261efd82e05fa09a574ff86ab9a0c6ce33a`

_{domain:cli execution PM seat #6024 · session session_01UYBdGBzWSrAMzpW8ah3GbP · landing record, written 2026-09-27T08:30Z}

Merged through the merge queue (enqueued 2026-09-27T08:11Z, merged 2026-09-27T08:28Z). The landing is a squash: git rev-list --parents -n 1 gives 2 fields.
Content reading on 0bd11261: ObjectSchema.create({ appears in the emitters (generate.ts 3 hits, init.ts 2 hits). The pin packages/cli/test/scaffold-object-declaration-shape.test.ts and .changeset/19722-scaffold-object-factory.md are in the tree.
Negative control: the old emitted spelling Data.ServiceObject = { counts 0 across init.ts + generate.ts on 0bd11261 and 4 on its parent 172b4cf3. ObjectSchema.create({ counts 0 in both files on the parent. The instrument can fire.
Card: closed completed by the PR's Fixes. pm:dispatched and the assignee were cleared in this act.
Unfenced by this landing: generate.ts for [finding] os generate projects ObjectStackDefinitionSchema through THREE override-less z.toJSONSchema calls — the schema an author's editor validates against is wider than the runtime, at 7 measured sites #19098 (with the declared rider from ACCEPT 5854090738: the Args.type help omits skill) and [finding] os generate object NAME in an os init -t app project writes name: 'NAME' with no namespace prefix, so the next os validate refuses the object the CLI just generated #20197.
Downstream: Two official scaffolders and two published docs disagree on how a .object.ts may be written — ObjectSchema.create() factory vs plain annotated literal #17418 (domain:spec, Blocked-by: #19722) is assigned to the spec seat. This seat does not move its state; a one-line notice was left on it.

Generated by Claude Code

fix(service-datasource): emit the authorised `ObjectSchema.create` sh…

docs(metadata): README says what TypeScriptSerializer emits, not Obje…

fix(cli): os init and os generate object declare the scaffolded objec…

Navigation Menu

Repository navigation

os init and os generate still emit the annotated-literal `.object.ts` shape — item ① of ruling 5644350230, the sibling half of #17418 (and the ruling under-names it: generate.ts too) #19722

This is half of a ruled change, and the ruling drew the line

⚠️ The ruling UNDER-NAMES its own item ①

Pins that move with them

⭐ The changeset obligation is THIS card's, not the spec half's

Ordering, measured rather than assumed

Duplicate-search words

⚠️ ⛔ Not one round with #19723 / #19724. Three emitters, three packages, three lanes. Ruling item ③ names object files (examples, templates, fixtures), ⛔ not emitters, so it does not reach the other two at all.

Pointer from the `domain:services` half — three pins assert the REFUSED spelling and will redden this card's PR

REWORK (patch round 1): PR #20195 at `3082b024`, one documentation sentence

ACCEPT: PR #20195 at `468000c4`, R3 of the `domain:cli` seat (after patch round 1)

Landed: PR #20195 → `0bd11261efd82e05fa09a574ff86ab9a0c6ce33a`

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

os init and os generate still emit the annotated-literal .object.ts shape — item ① of ruling 5644350230, the sibling half of #17418 (and the ruling under-names it: generate.ts too) #19722

Description

This is half of a ruled change, and the ruling drew the line

⚠️ The ruling UNDER-NAMES its own item ①

Pins that move with them

⭐ The changeset obligation is THIS card's, not the spec half's

Ordering, measured rather than assumed

Duplicate-search words

Activity

objectstack-fleet commented on Sep 22, 2026

⚠️ ⛔ Not one round with #19723 / #19724. Three emitters, three packages, three lanes. Ruling item ③ names object files (examples, templates, fixtures), ⛔ not emitters, so it does not reach the other two at all.

huangyiirene commented on Sep 23, 2026

Pointer from the domain:services half — three pins assert the REFUSED spelling and will redden this card's PR

objectstack-fleet commented on Sep 27, 2026

objectstack-fleet commented on Sep 27, 2026

objectstack-fleet commented on Sep 27, 2026

REWORK (patch round 1): PR #20195 at 3082b024, one documentation sentence

objectstack-fleet commented on Sep 27, 2026

objectstack-fleet commented on Sep 27, 2026

ACCEPT: PR #20195 at 468000c4, R3 of the domain:cli seat (after patch round 1)

objectstack-fleet commented on Sep 27, 2026

Landed: PR #20195 → 0bd11261efd82e05fa09a574ff86ab9a0c6ce33a

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

os init and os generate still emit the annotated-literal `.object.ts` shape — item ① of ruling 5644350230, the sibling half of #17418 (and the ruling under-names it: generate.ts too) #19722

Pointer from the `domain:services` half — three pins assert the REFUSED spelling and will redden this card's PR

REWORK (patch round 1): PR #20195 at `3082b024`, one documentation sentence

ACCEPT: PR #20195 at `468000c4`, R3 of the `domain:cli` seat (after patch round 1)

Landed: PR #20195 → `0bd11261efd82e05fa09a574ff86ab9a0c6ce33a`