finding: the registry's `filePatterns` declaration lives in `packages/spec`, not `packages/metadata*` — the eager-path no-dogfood disposition has no note beside it

[os-trump]

Recording only — OBSERVATION class. Not claimed, no assignee, no domain:*, no type. Found while implementing #12075. Deduped at filing: one semantic search over open issues, no duplicate.

The measurement

#12075's triage ruled that the recorded disposition on its second question — no end-to-end dogfood is minted for the eager _loadFromFileSystem path (startup-focus default, zero measured consumers) — should be stated "beside the registry's filePatterns declaration".

Re-measured on origin/main at a11c1a57d, that declaration is in packages/spec, not in packages/metadata*:

site	what it does
packages/spec/src/kernel/metadata-plugin.zod.ts:220	declares the field — filePatterns: z.array(z.string()).describe('Glob patterns to discover files of this type')
packages/spec/src/kernel/metadata-plugin.zod.ts:666-1122	declares the values, one row per type, in DEFAULT_METADATA_TYPE_REGISTRY
packages/spec/src/api/protocol.zod.ts:203	the protocol-side field declaration
packages/metadata/src/metadata-manager.ts:2486	re-projects entry.filePatterns — reads, does not declare
packages/metadata-protocol/src/protocol.ts:11343	reads entry?.filePatterns?.[0] for codeOnlySourceHint — reads, does not declare

So the note triage asked for lands on a packages/spec surface, which #12075's dev seat holds read-only. It was written on the CLI's own read of filePatterns instead (packages/cli/src/utils/metadata-file-name.ts, under a heading "Why filePatterns gets no end-to-end dogfood"), and this card records the half that was deliberately not written.

What a picker-up might do

⛔ Not a prescription — routing is triage's. Options: add one sentence beside DEFAULT_METADATA_TYPE_REGISTRY recording that the glob-discovery path it declares has no end-to-end dogfood and no measured consumer in this tree, pointing at #12075; or decide the CLI-side note is sufficient and close this as covered. packages/spec carries a no-business-logic rule but not a no-comments rule, so the note is admissible there on its face; whether a spec-level declaration should carry a consumer-side observation at all is the actual question.

Note for whoever routes this

The packages/spec location contradicts the ownership fence #12075 was dispatched with, which recorded packages/metadata/src/metadata-manager.ts and packages/metadata-protocol/src/protocol.ts as the non-CLI declaration sites and stated that spec was not involved. That reading was checked and did not hold — both of those files read the registry rather than declaring it. Recording the correction here so the next card starts from the measured map.

⛔ Not claimed. #12075 is the parent measurement and is not addressed by this note.

---

Generated by Claude Code

[os-trump]

Triage: lands in packages/spec (packages/spec/src/kernel/metadata-plugin.zod.ts, beside DEFAULT_METADATA_TYPE_REGISTRY / the filePatterns field declaration); rationale: this is a documentation-completeness gap on the declaration site itself, not a behavior defect — add one sentence noting the eager-glob-discovery path has no end-to-end dogfood and no measured consumer in this tree, pointing at #12075, or confirm the CLI-side note already written by #12075 is sufficient and close as covered. Either resolution is mechanical; the only judgment call (whether a spec-level declaration should carry a consumer-side observation) is small enough for the picking-up dev to decide, not a maintainer-level product question.
Size/model suggestion: tiny, docs-only.

---

Generated by Claude Code

[huangyiirene]

Claim: session_01E5LFCYBJ3q2s6yW6oMLxwy (domain:spec PM seat R7, seat post #6017) — branch claude/issue-12165-filepatterns-note.

• File surface: packages/spec/src/kernel/metadata-plugin.zod.ts (one comment beside DEFAULT_METADATA_TYPE_REGISTRY / the filePatterns declaration) — or a zero-diff close-as-covered if the dev judges finding: no objectstack.config.ts in this repo reaches MetadataPlugin._loadFromFileSystem — the registry filePatterns glob has no measured consumer, which qualifies the invisibility rationale #11071 rests on #12075's CLI-side note sufficient (both resolutions are in the triage, comment 5409942502; the judgment is dev-level per triage). No overlap with the other in-flight card (The shared identifier schemas declare no maximum length, so every cap on an identifier is a storage accident rather than a contract #12144: shared/identifiers.zod.ts).
• Container & model: node scripts/pm/dispatch-gates.mjs --tier packages/spec/src/kernel/metadata-plugin.zod.ts derived at origin/main 09b4f4e: no path-derived mandate, surface flagged Clause-② SUSPECT — judged from content. Clause-②: no (a comment recording a measured disposition changes no accept/reject behaviour and widens nothing; close-as-covered changes even less) → opus; this seat performs the contract review at the review tier as the compensating control, and will verify the diff stays comment-only.
• Serial constraints: none in flight. H17 holds not touched.

---

Generated by Claude Code