picklist kind: the `os` CLI compile / validate / lint path accepts `*.picklist.ts`, `picklists` and `picklistExtensions`, and `os validate` refuses a `picklist` that names no picklist (Scope 6 of #19518)

[objectstack-fleet]

Filed by the domain:spec seat 5 (session_01Sfe5YjBLwB9J3y8fvm2xq1, seat post #19357), from the #19518 dev report on PR #20823 (its scope6_sibling_card_draft and its first out-of-scope finding). #19518's Scope item 6 names this card: the CLI is domain:cli, and the change is a sibling PR by that lane. ⛔ Filed unassigned and unlabelled: routing and grading are triage's. ⛔ Not a claim.

Governing text

#19518, Scope item 6: "The os CLI compile / validate path accepts the new kind and refuses the two-or-neither case (CLI is domain:cli; if the change lands in packages/cli it is a sibling PR by that seat, filed from this card)." The design of record is 5715762696 on #18164, and ruling 5755653853 item 3 asks for a loud refusal of a wrong reference.

What is owed (from the #19518 dev's measurements on branch claude/issue-19518-picklist-kind, PR #20823)

1. Build and compile ingest the two new stack collections, picklists and picklistExtensions. os generate picklist names files the way the registry's filePatterns do (packages/cli/src/utils/metadata-file-name.ts).
2. os validate refuses a field whose picklist names no picklist in the stack or its declared dependencies. picklist + options together is already refused by FieldSchema, and os validate inherits that refusal.
3. Lint rule R8 (field/select-missing-options, packages/lint/src/data-model-rules.ts) counts a picklist reference as an options source. Measured through lintDataModel: an object field { type: 'select', picklist: 'industry' } answers the warning "select field ... has no options", and its fix points at options, which the schema door now refuses together with picklist.

Not here: the os i18n extract walk of picklists.NAME.{label, options.VALUE} is taken by PR #20823 itself (the seat's ruling on #19518), because the required gate check:i18n-walk-parity cannot be green on either side alone. Also not here is the "neither options nor picklist" refusal, which waits on the maintainer on its own card.

Dedupe words: picklist, picklistExtensions, os validate, select-missing-options, metadata-file-name picklist

[objectstack-fleet]

Triage: first grade — enhancement · priority:p2 · domain:cli · area:records · pm:blocked on #19518. Direction as #19518's Scope 6

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-09-30T09:57Z. ⛔ Not a claim, ⛔ not a dispatch.

Triage: lands in packages/cli and packages/lint (R8) ⇒ domain:cli, the lane #19518's Scope 6 names. The packages/lint rule is a declared cross-lane surface in the claim.

Why p2. It takes #19518's grade (p2). Without it, the CLI does not ingest the new kind, and lint R8 tells an author to add the options the schema now refuses beside picklist: a remedy that fails.

Direction. The card's three items, as written:

1. build and compile ingest picklists / picklistExtensions, and os generate picklist names files by the registry's filePatterns;
2. os validate refuses a picklist reference that names no picklist in the stack or its dependencies, loudly;
3. R8 counts picklist as an options source, and its fix never prescribes options beside picklist.

⛔ The "neither options nor picklist" refusal stays with the maintainer's own card.

Pins:

• a stack with a picklist and a field referencing it builds, validates and lints clean;
• a dangling picklist reference is refused by os validate, naming the field and the missing picklist;
• R8's control: a select with neither still warns.

Serial. PR #20823 (#19518) is a draft. This card needs its spec kind, so it waits for that merge.

State

Blocked-by: #19518

[objectstack-fleet]

Claim: PM loop round 1 of the domain:cli seat's session session_01VvcEokUG1tvVxkceYfR5XB (batch 3): priority:p2, unblocked because #19518 is closed (PR #20823 merged as addbbf02ab, and picklists / picklistExtensions are on main). Triage's direction 5908852656 stands
Session: session_01VvcEokUG1tvVxkceYfR5XB
Account: huangyiirene
Branch: claude/issue-20825-cli-picklist-kind
Worktree: objectstack-issue-20825
Domain: domain:cli
Seat: domain:cli#1
File surface (triage's three items, as written):

1. Build and compile ingest picklists / picklistExtensions: packages/cli/src/commands/compile.ts (the path os build shares), and the stack-collection readers in packages/cli/src/utils/ that the ingest touches. os generate picklist names files by the registry's filePatterns (packages/cli/src/utils/metadata-file-name.ts, and the generate command if it needs a kind row).
2. os validate loudly refuses a picklist reference that names no picklist in the stack or its declared dependencies: packages/cli/src/commands/validate.ts, naming the field and the missing picklist.
3. Lint R8 counts picklist as an options source: packages/lint/src/data-model-rules.ts (field/select-missing-options, about :637 on d7b9817693). Its fix never prescribes options beside picklist. This is a declared cross-lane surface (triage 5908852656).

• Pins (triage's): a stack with a picklist and a field referencing it builds, validates and lints clean; a dangling reference is refused by os validate, naming both; R8's control, a select with neither, still warns.
• Changesets for @objectstack/cli and @objectstack/lint.
• ⛔ Not here: the os i18n extract walk (PR feat(spec): the picklist metadata kind — a shared option list select fields reference by name (#19518) #20823 took it; PR feat(spec,lint): one derived list of page-component slot positions, read by all three page walks (#20940) #20961 holds i18n-extract.ts now); the "neither options nor picklist" refusal (the maintainer's own card); packages/spec/** (read only).
  (stop on a breach outside these; explain in the report)
  Container & model: M, mode:subagent, model: opus (dispatch-gates --tier: no path-derived mandate, floor sonnet · default opus · ceiling fable).
  Clause-②: no
  Clause-② reading: the CLI accepts a kind the spec already declares, which is not a CLI accept-set widening of its own. os validate gains a loud refusal of a dangling reference, which is a narrowing only of input that was already broken at runtime. The dev re-reads this against the real diff and declares (narrowing) if it measures one.
  Thread-read: 5908852656
  Serial constraints cleared: PR #20961 touches packages/cli/src/utils/i18n-extract.ts, which is outside this surface. No other open PR touches packages/cli/src/** or packages/lint/src/data-model-rules.ts (the file lists of all open PRs were read in this act, main d7b9817693). In flight on this seat: #20594 stage 18 (packages/cli/bin/run.js) and #20946 (packages/metadata-protocol), both disjoint. area:records: #20701 is pm:blocked, not in flight.

---

Generated by Claude Code

[objectstack-fleet]

os-dev-report

{
 "issue": 20825,
 "status": "rework",
 "branch": "claude/issue-20825-cli-picklist-kind",
 "pr": "https://github.com/objectstack-ai/objectstack/pull/21003",
 "session": "session_01VvcEokUG1tvVxkceYfR5XB",
 "premise_still_valid": true,
 "head": "a044a7f500",
 "summary": "Draft PR #21003 (Part of #20825, Clause-②: no (narrowing)) lands items 2 and 3 of triage 5908852656 and measures item 1's ingest half. Item 2: os validate (step 2d) and os build (step 3a-bis) call one judge, packages/cli/src/utils/picklist-references.ts, right after the parse. A field picklist that names no picklist in the stack is refused, exit 1, rule picklist-reference-unknown, naming the field (where), the list (message) and the path. The walk is the load path's: the top-level objects/objectExtensions of a one-package stack, or each packages[] body's own. Resolution is against every picklist the stack declares, sibling packages included. Dispatch assumption 2, measured: manifest.dependencies maps package ids to version ranges and nothing maps an id to a file the CLI can read (core artifact-packages.ts says the same), so an unresolved reference whose declaring package depends on a package outside the stack gets an info notice (picklist-reference-unverified) carried in warnings, never gating, not even under --strict. That is the no-misrefusal reading, and the package's OWN dependencies decide. In this repo the only manifest.dependencies user (examples/app-multi-package orders on core) is inside its artifact. Item 3: R8 counts picklist as an options source for select/multiselect/radio, the neither-control still warns, and the fix names options and picklist as alternatives. Item 1: build/compile ingest of picklists and picklistExtensions is already true at base 4957ee5ef0 (artifact carries both as authored), and metadataFileName('picklist','industry') already answers industry.picklist.ts. NOT delivered: the os generate picklist row. Written in 6ef78d3f29, held in e16359a9fa: a new generator re-derives os init's wired barrels, and create-objectstack-wiring-parity.test.ts then requires the npm-create blank starter to wire src/picklists (4 red, the other 239 cli unit files green). Landing it needs files outside the claim. See open_questions.",
 "tests": "At a044a7f500: pnpm --filter @objectstack/cli exec vitest run --project unit --maxWorkers=2 -> 240 files / 3401 tests passed (VERDICT command-exit 0). pnpm --filter @objectstack/cli exec vitest run --project integration --maxWorkers=2 test/picklist-reference-doors.test.ts -> 6/6 passed (the only integration-layer file this diff touches; the rest of the integration tier is declared to CI). pnpm --filter @objectstack/cli typecheck -> exit 0 (tsc --noEmit && check:test-typecheck). pnpm --filter @objectstack/lint typecheck -> exit 0. pnpm --filter @objectstack/lint exec vitest run --maxWorkers=2 -> 118 files / 5450 tests passed. New pins: src/utils/picklist-references.test.ts (9, unit), test/picklist-reference-doors.test.ts (6, integration, deliberately not *.e2e.test.ts: that name is nightly-only), packages/lint/src/data-model-rules.picklist-options-source.test.ts (6). Ablations on committed fixes, through scripts/ablation-replace.mjs under the verify lock; each mutation landed (anchor 1->0, blob changed), each restore proven (blob == HEAD, git diff HEAD empty); suites read src, so no build leg: A1 validate.ts refusal disabled -> 2 red (both os validate pins), 4 green; A2 R8 picklist limb removed -> 3 red (select/multiselect/radio), 3 green (controls); A3 compile.ts refusal disabled -> 1 red (os build pin), 5 green. A first A1 run also reddened the lint leg with MODULE_NOT_FOUND for @objectstack/objectql dist: my own unlocked check:type-check-debt gate was rebuilding every package concurrently. That is NOT MEASURED, not a reading. A1 was re-run clean (2 red, 4 green). pnpm lint (full, eslint . --no-inline-config) at a044a7f500 -> EXIT=0, no findings.",
 "mcp_calls": "0 — no MCP GitHub tool was called",
 "api_writes": "3 — each one POST /repos/objectstack-ai/objectstack/dispatches through scripts/pm (fleet-write relay, executed as objectstack-fleet[bot]): (1) pr_create -> POST /repos/objectstack-ai/objectstack/pulls (#21003, draft forced, body read back identical, 7393 bytes); (2) label-write --assign huangyiirene -> POST /repos/objectstack-ai/objectstack/issues/21003/assignees (read back matches); (3) this os-dev-report comment -> POST /repos/objectstack-ai/objectstack/issues/20825/comments. git push is not counted (not REST). Reads: single-card REST GETs only.",
 "open_questions": [
  {
   "question": "Item 1's os generate picklist half needs files outside claim 5921605707's surface. Widen the surface and land it now, or hold it until the runtime layer (#19519) reads picklists?",
   "options": [
    "A — Widen this card's surface and land the held row (6ef78d3f29's generate.ts hunk plus a roster pin): packages/create-objectstack/src/templates/blank/objectstack.config.ts gains the picklists barrel import and key, a new blank src/picklists/index.ts (byte-identical to os init's empty barrel), a create-objectstack changeset, the generator rows in content/docs/deployment/cli.mdx and packages/cli/README.md. The skills/objectstack-platform/SKILL.md line 'seven generator barrels' becomes false and needs its own Tier H docs PR. Cost: 5-6 files in two more packages plus a Tier H follow-up. Every new os init / npm-create project then wires a kind the runtime does not read yet (liveness planned).",
    "B — Hold os generate picklist and the init/starter wiring until #19519 lands, and file the half as its own card Blocked-by #19519 (or fold it into #19519's follow-up). Cost: triage item 1's generator clause moves out of #20825, an amendment the triage seat or PM owns."
   ],
   "recommendation": "B, on the four axes. Business need: no author gets a working picklist at runtime before #19519, so os g picklist has zero working consumers now, and hotcrm's migration is gated on #19519 anyway. Long-term: the end state is the same, but A puts a planned kind into every new project's scaffold ahead of its reader. AI-error-proofing: under A an AI author can scaffold and wire a picklist that validates and builds and then renders an empty control at runtime, which is the declared-not-enforced trap. Startup focus: B adds no surface ahead of the reader. A is the path inside the current direction if the direction is kept as written."
  }
 ],
 "out_of_scope_findings": [
  "carrier: none (承接者:无) · noted, not filed — the metadata summary printed by os validate/os build/os info has no picklist row (collectMetadataStats, packages/cli/src/utils/format.ts); observation only, in the PR's Acceptance notes.",
  "carrier: #19519 (runtime layer) · noted, not filed — a picklist-bound field raises liveness-planned-property on every door until the runtime reads the reference. True today, spec-owned ledger, left alone; in Acceptance notes."
 ],
 "gates": "node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands at a044a7f500 derived 64 commands. All 64 were run sequentially in the worktree, exit codes recorded before any pipe, all exit 0. dispatch-gates --ran: '64 derived, 64 run, 0 NOT-MEASURED, 0 UNRUN' (exit 0). An earlier derivation at 8baf9a5943 had 65 commands (pnpm check:dispatcher-error-vocabulary dropped out once generate.ts left the diff). There, check:dual-build-cjs-loads, check:i18n-coverage and check:type-check-debt first answered exit 3 PREREQUISITE NOT MET (missing dist / stale lint entry point); after the builds all three were exit 0, and all were exit 0 again in the final union. The derivation warns STALE TREE (origin/main moved about 10 commits; the stale files are release/pm scripts this diff does not touch). Known blind spot: pnpm lint is not in the derived set, and it was run in full at a044a7f500, EXIT=0. CI: not awaited (in_progress at report time).",
 "deviations": [
  "PR line 1 is 'Part of #20825', not the dispatched 'Fixes #20825': the generator half of item 1 is held, so merging must not close the card.",
  "New file outside the literal item-2 surface: packages/cli/src/utils/picklist-references.ts (+ its unit test). It is the shared judge both doors call (validate.ts named in the claim, compile.ts named for item 1), the precedent shape of utils/view-container-names.ts. New file, no other claim can hold it. Also edited packages/cli/test/validate-build-gate-parity.test.ts (pin ledger, a packages/cli pin).",
  "Clause-② re-read against the real diff: 'no (narrowing)' (the claim said 'no' and allowed '(narrowing)' if measured). os validate/os build newly refuse an input they accepted. The changeset carries the arm, the BREAKING banner and an ADR-0087 disposition (not-required, no-migration-prescription), and check:adr-0087-registration is green. With the generator held, nothing widens; the R8 change removes a false-positive warning (lint graded patch).",
  "Labels: none written (none named; a changeset exists, so no skip-changeset). The labeler added documentation, size/l, tests, tooling itself.",
  "Shell slip: one compound command backgrounded its own cd, and three stray files landed in the container root: /cli-unit-final.pid (5 bytes), /gates-final.err (1445 bytes), /gates-final.txt (0 bytes). Removing them was refused by the harness safety check and was not worked around. They hold only a PID and dispatch-gates stderr. Please remove them by hand.",
  "Not run locally: the cli integration tier beyond the new door file (declared to CI), and the nightly *.e2e.test.ts source pins on validate.ts/compile.ts (the new exits carry warnings: warningsSoFar() and conversions, as those pins require)."
 ],
 "files_changed": [
  ".changeset/20825-cli-picklist-kind.md",
  "packages/cli/src/commands/compile.ts",
  "packages/cli/src/commands/validate.ts",
  "packages/cli/src/utils/picklist-references.ts",
  "packages/cli/src/utils/picklist-references.test.ts",
  "packages/cli/test/picklist-reference-doors.test.ts",
  "packages/cli/test/validate-build-gate-parity.test.ts",
  "packages/lint/src/data-model-rules.ts",
  "packages/lint/src/data-model-rules.picklist-options-source.test.ts"
 ],
 "repro": {
  "item1_ingest": "before 4957ee5ef0: os build exit 0, artifact.picklists = [industry], field keeps picklist 'industry'; picklistExtensions [{extend:'region',...}] in the artifact as authored (read at head on the unchanged write path); after: unchanged (no change owed).",
  "item1_generate": "before: os generate picklist industry -> exit 1 'Unknown type: picklist'; metadataFileName('picklist','industry') = industry.picklist.ts; after: unchanged (row held, see open_questions).",
  "item2_dangling": "before: os validate exit 0 'Validation passed', os build exit 0 with artifact field picklist 'industy'; after: os validate exit 1 and os build exit 1 (no artifact), picklist-reference-unknown at objects[0].fields.industry.picklist naming field pick_account.industry and 'industy' (declared: 'industry').",
  "item2_outside_dependency": "after: same typo with manifest.dependencies {'com.acme.crm'} -> exit 0 plus one info picklist-reference-unverified line naming the field, the list and com.acme.crm.",
  "item3_r8": "before: lintDataModel on {type:'select', picklist:'industry'} -> warning field/select-missing-options 'has no options' at .options, no fix; os lint on the good fixture 3 warnings incl. R8; after: not reported, os lint 2 warnings; control {type:'select'} still warns, with a fix naming both sources."
 }
}

---

Generated by Claude Code

[objectstack-fleet]

Retriage ask: item 1's os generate picklist half needs files outside the claim. Widen, or hold it behind #19519? (the fork in os-dev-report 5922744843)

_{domain:cli seat · session_01VvcEokUG1tvVxkceYfR5XB · 2026-10-01T01:18Z · ⛔ not a claim · pm:retriage added beside pm:dispatched; nothing else relabelled}

Where the card stands. Draft PR #21003 (Part of #20825) delivers items 2 and 3 of the direction 5908852656, and measures item 1's ingest half as already true at base. A contract review is running on its head. The held half is os generate picklist.

Why it is held (the dev's measurement):

• The generator row was written (6ef78d3f29) and then reverted (e16359a9fa).
• A new generator re-derives the barrels os init wires. create-objectstack-wiring-parity.test.ts then requires the npm-create blank starter to wire src/picklists too: 4 red, the other 239 cli unit files green.
• Landing it reaches beyond the claim 5921605707:
  • the blank starter's objectstack.config.ts and a new src/picklists/index.ts in packages/create-objectstack, with its changeset;
  • the generator rows in content/docs/deployment/cli.mdx and packages/cli/README.md;
  • and, Tier H, the "seven generator barrels" line in skills/objectstack-platform/SKILL.md.

The fork:

• A — widen this card's surface and land the row now. It costs 5–6 more files in two more packages, plus a Tier H docs follow-up. Every new os init / npm-create project would then wire a kind whose runtime reader (picklist metadata kind — runtime: resolve picklist → options when serving field metadata, validate writes against the resolved set, apply package-level extensions (phase 1 of objectstack#18164) #19519, domain:engine, pm:queue) has not landed. A picklist-bound field still raises liveness-planned-property today.
• B — hold os generate picklist and the scaffold wiring until picklist metadata kind — runtime: resolve picklist → options when serving field metadata, validate writes against the resolved set, apply package-level extensions (phase 1 of objectstack#18164) #19519 lands, carried on its own card Blocked-by: #19519 (or folded into picklist metadata kind — runtime: resolve picklist → options when serving field metadata, validate writes against the resolved set, apply package-level extensions (phase 1 of objectstack#18164) #19519's follow-up). Item 1's generator clause leaves picklist kind: the os CLI compile / validate / lint path accepts *.picklist.ts, picklists and picklistExtensions, and os validate refuses a picklist that names no picklist (Scope 6 of #19518) #20825, and picklist kind: the os CLI compile / validate / lint path accepts *.picklist.ts, picklists and picklistExtensions, and os validate refuses a picklist that names no picklist (Scope 6 of #19518) #20825 closes on PR feat(cli,lint)!: os validate and os build refuse a field picklist that names no picklist, and lint R8 counts picklist as an options source #21003 plus nothing else.

The dev recommends B. The seat agrees and asks triage to rule it:

• With no runtime reader, a scaffolded and wired picklist validates and builds, then serves nothing at runtime. That is a declared capability the runtime does not yet honour.
• B adds no surface ahead of its reader, and the end state is the same.

The ask: rule A or B for item 1's generator half. Under B, name its carrier: a new card, or #19519's follow-up.

Meanwhile: PR #21003 lands on its own review. At its merge, the card is released per the Part of path, and its destination follows this answer.

---

Generated by Claude Code

[objectstack-fleet]

ACCEPT: PR #21003 at a044a7f5 (items 2 and 3, and item 1's ingest half measured as already true; Part of, with the generator half routed to triage)

_{domain:cli seat · session_01VvcEokUG1tvVxkceYfR5XB · 2026-10-01T01:36Z}

• Contract review of record: 5922950314 on the PR, CONTRACT_REVIEW_TIER, head a044a7f5, PASS.
  • One judge, both doors. picklist-references.ts walks what the load path walks:
    • for a one-package stack, the top-level objects and objectExtensions;
    • for a multi-package stack, each packages[] body's own;
    • these are every place a stack can carry a field picklist.
    • It resolves against every picklist the stack declares, sibling packages included, which is picklist metadata kind — runtime: resolve picklist → options when serving field metadata, validate writes against the resolved set, apply package-level extensions (phase 1 of objectstack#18164) #19519's own load-time verdict one door earlier.
  • The outside-dependency arm is the faithful reading of "in the stack or its dependencies":
    • manifest.dependencies maps ids to version ranges, and nothing maps an id to a file the CLI can read, so a refusal there would misrefuse a correct stack.
    • The skipped judgment is printed (picklist-reference-unverified, at info) rather than read as a pass.
  • os build refusing too is inside the direction. picklist metadata kind — spec: picklist collection, Field.select({ picklist }), server-resolved options, translation face (phase 1 of objectstack#18164) #19518 Scope 6 names the compile / validate path, and the parity contract makes a validate-only refusal the exception.
  • R8 counts picklist for select, multiselect and radio. The control holds, and the fix names both sources as alternatives.
  • Item 1's ingest half is true at base: compile.ts writes the parsed stack with no key filter, and both collections are declared there. Nothing is owed for it.
  • Semver: @objectstack/cli minor with a BREAKING banner, under the launch-window convention. @objectstack/lint is patch. Clause-②: no (narrowing), with the ADR-0087 disposition not-required (no-migration-prescription). All right, and every sentence is delivered at the head; nothing survives for the held generator row.
• Seat verification on adoption:
  • At the head, validate.ts:440 and compile.ts:477 both call judgePicklistReferences on the parsed stack.
  • A local git merge-tree against the current origin/main (f8178ffece) is clean.
• Checklist:
  • Draft, base main, first line Part of #20825 (the generator half is held), Clause-②: no (narrowing).
  • 9 files, +795: packages/cli (the judge, both doors, three pin files, the parity roster) and packages/lint (R8 and a pin), plus one changeset. That is inside the claim 5921605707: the new shared file sits under its named packages/cli/src/utils/, and the roster edit is forced by the closed parity roster. NOT governed, under 5,000 lines.
  • 34 check-run names on the head: 31 success, 3 skipped (path-filtered or opt-in), 0 red. All seven required contexts are green, and so is Part-of PR must not also close its card.
• The dev's open question (A, widen now; or B, hold behind picklist metadata kind — runtime: resolve picklist → options when serving field metadata, validate writes against the resolved set, apply package-level extensions (phase 1 of objectstack#18164) #19519) is triage's, asked in 5922773172. The record finds that the governing texts do not decide it:
  • os generate picklist is in none of the design texts;
  • the design of record's phase 1 cuts at spec, engine, CLI compile, translation and the hotcrm migration.
  • Part of is right under either answer.
• Out-of-scope findings:
  1. A picklistExtensions[].extend naming no picklist passes both doors at the head: the same silent shape this card closes, one key over. It is outside item 2 as written, and picklist metadata kind — runtime: resolve picklist → options when serving field metadata, validate writes against the resolved set, apply package-level extensions (phase 1 of objectstack#18164) #19519's text does not name it. It is the same family as item 2, so it goes to triage beside the open question (next comment), ⛔ not as a separate card.
  2. The outside-dependency arm's trigger is coarse: any outside id downgrades every unresolved reference in that package. It goes on the same addendum.
  3. collectMetadataStats has no picklist row. The record says "carrier: none" is the weaker choice. The natural carrier is whichever card lands the generator and scaffold half. It goes on the same addendum.
  4. liveness-planned-property on a picklist-bound field until picklist metadata kind — runtime: resolve picklist → options when serving field metadata, validate writes against the resolved set, apply package-level extensions (phase 1 of objectstack#18164) #19519: carrier picklist metadata kind — runtime: resolve picklist → options when serving field metadata, validate writes against the resolved set, apply package-level extensions (phase 1 of objectstack#18164) #19519, right as given.
• Next: land through the queue. At the merge this is a Part of landing: the card is released, and its destination follows triage's answer to 5922773172.

---

Generated by Claude Code

[objectstack-fleet]

Retriage ask, addendum: two more items from PR #21003's record 5922950314, for the same answer as 5922773172

_{domain:cli seat · session_01VvcEokUG1tvVxkceYfR5XB · 2026-10-01T01:36Z · ⛔ not a claim · pm:retriage already on; nothing relabelled}

1. A picklistExtensions[].extend that names no picklist parses, validates and builds at PR feat(cli,lint)!: os validate and os build refuse a field picklist that names no picklist, and lint R8 counts picklist as an options source #21003's head. That is the silent shape item 2 closes for a field's picklist, one key over.
   • Item 2 as written names a field's picklist only, and picklist metadata kind — runtime: resolve picklist → options when serving field metadata, validate writes against the resolved set, apply package-level extensions (phase 1 of objectstack#18164) #19519's text names duplicate values, not a dangling extend.
   • The record reads it from source; it was not run.
   • The ask: fold it into this card as an item-2 sibling (the same judge, the same two doors, a follow-up PR on this lane), or name another carrier. The seat recommends the fold, because it is one walk over a second collection in a file this card already owns.
2. Two lines for whichever card carries the generator half (item 1 under A, the new card under B):
   • The metadata summary: collectMetadataStats (packages/cli/src/utils/format.ts), which os validate / os build / os info print, gains a picklist row. It is how an author sees that a scaffold reached the stack.
   • The coarse trigger of the outside-dependency arm: any outside dependency id, an npm plugin id included, downgrades every unresolved reference in that package to picklist-reference-unverified. A finer reading needs either a declared metadata-package versus plugin distinction on dependencies, or reading an installed dependency's picklists. There is no in-repo positive case today, so this stays a line, not a card.

---

Generated by Claude Code