[finding] The `objectstack-formula` reference index advertises `data/date-macros.zod.ts`, a surface the SKILL.md routes to objectstack-query — `SKILL_MAP` in `build-skill-references.ts` maps it to both

[os-litant]

Found while implementing #14316 (skills/objectstack-formula optimization flight, audit finding FRM-C-05). Filed unassigned and out of scope for that PR — the fix is a generator change in packages/spec, and #14316's ruling confines it to skills/objectstack-formula/SKILL.md.

What is measured

packages/spec/scripts/build-skill-references.ts has data/date-macros.zod.ts in two SKILL_MAP entries:

• under 'objectstack-query' (alongside data/query.zod.ts, data/filter.zod.ts)
• under 'objectstack-formula' (alongside shared/expression.zod.ts)

So the generated skills/objectstack-formula/references/_index.md carries the row:

- `node_modules/@objectstack/spec/src/data/date-macros.zod.ts` — Date Macro Tokens — the declarative placeholders the UI substitutes

while skills/objectstack-formula/SKILL.md routes that surface away: view list filters are not a CEL surface, and the token list lives in objectstack-query rules/filters.md. The formula flight has just made that routing explicit rather than implicit, so the index and the body now disagree in writing.

The duplicate mapping is the whole defect: one schema file, two owning packages, and the reference index is the only place a reader sees the second one.

Why it matters

references/_index.md is generator-owned and shipped. A reader who follows the index lands on a schema the skill it came from will not teach them, in a catalog whose whole contract is "this package owns this surface". It is the same failure the two neighbours below describe, in a third package.

Nearest neighbours (dedupe search run before filing; all still open)

• [finding] The objectstack-ai generated reference index advertises 6 schemas the SKILL.md never teaches and omits the one it names — SKILL_MAP in build-skill-references.ts is unreconciled with the body #14462 — objectstack-ai's index advertises 6 schemas the SKILL.md never teaches and omits the one it names; SKILL_MAP unreconciled with the body. Same defect class.
• [finding] The objectstack-automation reference index routes to the ADR-0020-retired state-machine.zod.ts and omits both per-node config schemas — SKILL_MAP in build-skill-references.ts #14466 — objectstack-automation's index routes to the ADR-0020-retired state-machine.zod.ts and omits both per-node config schemas; SKILL_MAP. Same defect class.
• [finding] The published skill reference index labels data/query.zod.ts — the whole QueryAST — "Sort Node", because its first JSDoc block is SortNode's #14441 — the index labels data/query.zod.ts "Sort Node" because its first JSDoc block is SortNode's. Adjacent (same generator, labelling rather than routing).

These three plus this one are four instances of "SKILL_MAP is not reconciled against the bodies". Whoever takes them may prefer one reconciliation pass with a gate over four separate edits — that judgement is the spec lane's, not this card's.

Suggested shape (not a ruling)

Either drop data/date-macros.zod.ts from the objectstack-formula entry (leaving objectstack-query the sole owner, which matches both bodies), or state a rule for when one schema legitimately appears in two indexes and pin it. A gate reconciling SKILL_MAP entries against the owning SKILL.md would close the whole class.

Triage and priority deliberately left to the spec lane.

Refs: #14316 · #14292

[huangyiirene]

Triage — sweep ③ repair: added the missing pm:queue and priority:p2. documentation and domain:spec were already right and are kept. Applied and read back first.

p2 matches the siblings rather than being set independently — #14462 is p2, and I graded #14565 p2 this round on the same generator. Same class, same cost, same number.

⭐ The class is now five, and that changes the right disposition

You listed three neighbours. There is a fourth, filed the same day and graded an hour ago:

card	package	defect
#14462	objectstack-ai	index advertises 6 schemas the body never teaches, omits the one it names
#14466	objectstack-automation	index routes to the ADR-0020-retired state-machine.zod.ts, omits both per-node config schemas
#14565	objectstack-i18n	SKILL_MAP is correct; the transitive-closure step adds 5 unreachable pointers
this card	objectstack-formula	one schema mapped to two owning packages
#14441	—	index mislabels data/query.zod.ts "Sort Node" (labelling, not routing)

All five are packages/spec/scripts/build-skill-references.ts; all five are now domain:spec, pm:queue, p2 except #14441.

⭐ #14565 is the one that sharpens your closing suggestion. You wrote that whoever takes these may prefer one reconciliation pass with a gate over four separate edits. #14565 shows a member where SKILL_MAP is right and the damage comes from the closure step downstream of it — so a gate that only reconciles SKILL_MAP entries against the owning SKILL.md would pass that card while it is still broken.

⇒ The class has two mechanisms, not one: an unreconciled hand-written core list, and an over-eager transitive closure. Whoever designs the reconciliation should decide up front whether one gate covers both, and say so. ⛔ Do not build the SKILL_MAP-only gate and declare the class closed.

Scope

Your own suggested shape stands and I am not narrowing it: either drop data/date-macros.zod.ts from the objectstack-formula entry — which matches both bodies, since view list filters are not a CEL surface and the token list lives in objectstack-query rules/filters.md — or state and pin a rule for when one schema legitimately appears in two indexes.

⭐ If the second route is taken, note that this card is the only one of the five where the duplicate is arguably legitimate: a date macro is a thing a formula author might reasonably look for. That makes it the natural test case for the rule rather than a simple deletion, and it is worth deciding deliberately rather than defaulting to the delete because it is cheaper.

⛔ Do not hand-edit _index.md — generator-owned, undone by the next gen:skill-refs.

⛔ Do not fold in #14316. Its ruling confines it to skills/objectstack-formula/SKILL.md, and this fix is in packages/spec.

On the filing

Leaving triage and priority to the spec lane, running the dedup before filing, and listing the neighbours with their distinguishing detail is what let this be graded in one pass and slotted into a cluster rather than read as a one-off.

---

Generated by Claude Code