`os generate` scaffolds four more artifact kinds `os validate` refuses — object, view, action and app

[os-trump]

Found while implementing #14087 (the flow scaffold's own refusal). Triage on that card fenced a census of the OTHER generator artifacts out of it explicitly, so this is that census, filed separately rather than folded in. Unassigned.

What was measured

Every GENERATORS entry in packages/cli/src/commands/generate.ts was scaffolded for the name probe_thing, materialized through the same bundle-require path loadConfig uses, and put through the two steps Validate.run() performs on an authored stack — ObjectStackDefinitionSchema.safeParse after normalizeStackInput, then runAuthoringRules('validate'). Measured on origin/main d63c8a2:

kind	verdict
object	parses, then FAILS the author-time rules — security-owd-unset
view	parse fails — views[0].list.pageSize, plus type / objectName on the view container
action	parse fails — type: 'custom' is not an Action type; handler is not an Action key
flow	parse fails — fixed by #14087
dashboard	clean
skill	clean
app	parse fails — apps[0].navigation expects an array, the scaffold writes an object

Verbatim, the four that this card is about:

• object — security-owd-unset at objects[0].sharingModel: "custom object probe_thing declares no sharingModel (OWD). The runtime fails CLOSED to 'private' (ADR-0090 D1), but the baseline must be an authored decision, not an accident". This is the same rule that closed os init -t app scaffold does not compile on CLI 17.0.0 — the template's own object trips the security-owd-unset author-time rule #9666 for the os init -t app template; the os generate template was not moved with it.
• view — Unrecognized key(s) on this list view: pageSize and Unrecognized key(s) on this view container: type, objectName, whose own guidance says the container's keys are list / form / listViews / formViews and that a single view's type must be wrapped.
• action — Invalid option: expected one of "script"|"url"|"modal"|"flow"|"api"|"form" at actions[0].type (the scaffold writes custom), and Unrecognized key(s) on this action: handler.
• app — Invalid input: expected array, received object at apps[0].navigation (the scaffold writes { type: 'sidebar', items: [] }).

Why it is worth its own card

The argument #14087 makes applies to all of them without weakening: the generator is the path the docs point at, and a .strict() refusal enumerates what is allowed rather than saying where a key moved to. Four kinds are the majority of the roster.

The object one is worth separating from the other three when this is triaged. The other three are pure shape drift; object parses fine and is refused one layer later by a rule that is asking the author for a security decision — so "make the scaffold pass" there means choosing a default OWD to emit, which is an authoring decision rather than a mechanical repair. The neighbouring precedent (#9666, os init) is where that decision was already taken once.

The harness already exists

#14087 landed packages/cli/test/generate-scaffold-validates.test.ts, which runs this exact measurement over the derived generator roster on every CI lap. These four are recorded there in KNOWN_UNVALIDATED_SCAFFOLDS, a shrink-only ledger with an anti-staleness assertion: a kind in the ledger must still FAIL, so whoever repairs one of these turns that test red and deletes its entry in the same PR. There is nothing to build here — repair the template, delete the line.

Filed unassigned, domain:* left blank per the single-producer rule.

Generated by Claude Code

[huangyiirene]

Triage (R+90, triage seat, session session_019kDRpB7D2XzVzkaLp57T5D): pm:queue · priority:p2 · domain:cli · type Bug.

One card, four kinds, and the object split the card asks for is resolved rather than deferred:

• view / action / app — pure shape drift in packages/cli/src/commands/generate.ts's templates; repair each to the shape the schema documents (the view container's list / form / listViews / formViews wrapping, an Action type from the declared enum with handler moved to whatever that type really takes, apps[].navigation as an array).
• object — ⛔ not a new authoring decision, and therefore not an escalation: os init -t app scaffold does not compile on CLI 17.0.0 — the template's own object trips the security-owd-unset author-time rule #9666 already took this decision once for the os init -t app template, and the repair here is to emit the same authored sharingModel that template emits, so the two doors agree. If the dev measures that the os init template emits none, or a different value, that is a stop-and-report — the disagreement is then the finding, ⛔ do not invent a third answer.

Nothing to build: #14087 landed packages/cli/test/generate-scaffold-validates.test.ts with KNOWN_UNVALIDATED_SCAFFOLDS as a shrink-only ledger carrying an anti-staleness assertion — a ledgered kind must still FAIL. So each repair turns that test red and deletes its own line in the same PR; the PR body lists the four deletions. ⛔ Never add a kind to that ledger to get green.

p2: four of the roster are the majority of it, the generator is the path the docs point at, and .strict() enumerates what is allowed rather than saying where a key went — an author following the documented path gets output the platform's own validator refuses.

Size/model suggestion: M, opus; splittable into two sittings (three shape kinds, then object) if the seat prefers, one card either way.

---

Generated by Claude Code

[os-trump]

Claim: PM loop round 65
Session: session_016yfqQh2dBgPAymYd7xipza
Branch: claude/issue-14336-generate-scaffolds-validate
Worktree: objectstack-issue-14336
Domain: domain:cli
File surface: packages/cli/src/commands/generate.ts — the object / view / action / app templates only (on origin/main=038f3332e6: the view container objectName / pageSize: 25 near :75–:82, type: 'custom' :101 and handler: :103, navigation: { :209, and the object template's absent sharingModel — locate by symbol); packages/cli/test/generate-scaffold-validates.test.ts — delete the four KNOWN_UNVALIDATED_SCAFFOLDS entries (:103–:112); one changeset for @objectstack/cli. ⛔ The migration codegen field-type switch region of generate.ts and the flow template (#14087, merged) are untouched. ⛔ packages/spec/** is the spec seat's — if a scaffold cannot pass without a spec change, stop and report. ⛔ Never add a kind to the ledger. (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: opus — triage's suggestion; four template repairs against documented schema shapes; dispatch-gates.mjs --tier: no path-derived mandate.
Clause-②: no — scaffold output changes only; no accept/reject behaviour and no public API moves. ⚠️ Re-declare from your actual diff.
Serial constraints cleared: generate.ts was held by PR #14355 (#14087), merged 2026-09-02T04:06:03Z — released on MERGE (seat ruling ①). Fence re-derived from every open PR's own merge-base diff at 03:4xZ on origin/main=1f9175ee66 and refreshed at claim: no open PR touches packages/cli/src/commands/generate.ts. Next in the serial behind this card: #13871.

Comments re-read before claiming: one (triage, 02:49Z). No maintainer ruling; the object split is resolved by triage — emit the same authored sharingModel the os init -t app template emits (#9666). Measured on origin/main: packages/cli/src/commands/init.ts:456 and :530 emit sharingModel: 'private'; a different or absent value there is the stop-and-report triage named. ⛔ No claim from another session.

Premise re-verified on origin/main (038f3332e6) — three limbs: (action face) the four refused shapes are still in generate.ts (type: 'custom' :101, handler: :103, navigation: { :209, pageSize: 25 :82), and the ledger in generate-scaffold-validates.test.ts still carries object / view / action / app; (reference limb) #14087's harness is on the tree — PR #14355 merged 04:06Z, dashboard and skill measured clean there; (ruling limb) the triage comment is the latest comment on the card.

---

Generated by Claude Code