[patchstackdave]

Fixes the P3 from #183's review, and a second instance of the same defect found while doing it.

The completeness assertion asserted nothing

expect(new Set(cases.map((c) => c.space))).toEqual(new Set(['body', 'query', 'cookie', 'header', 'file']));

One hard-coded set against another hard-coded set — the file agreeing with itself. A sixth addressable source would not have failed it, which is the gap it was written to close.

The root cause was that the vocabulary could not be asked. InputSource was a bare type union, and a union cannot be enumerated at runtime, so a test wanting "every source the map can address" had no option but to restate the list. Every sibling vocabulary in capabilities.ts is a runtime array with its type derived from it; this one was the exception.

Now INPUT_SOURCES is that array and InputSource derives from it. The assertion computes its expectation from production: a source is addressable when runtimeCoordinate yields a parameter, and every addressable source must have a case driven through the real engine.

Two supporting assertions so the grouping can't hide anything:

• the body-shaped sources are asserted to collapse to post.<path>, not assumed to;
• the unaddressable ones are asserted to stay unaddressable with a stated reason — a coordinate appearing for a route parameter would compile a rule the resolver cannot resolve.

Verified by adding a sixth addressable source (trailer → server.TRAILER_*): the new assertion fails, the old one passed.

A second instance, found on the way

Adding INPUT_SOURCES to CAPABILITY_MANIFEST did not put it in capabilities.json — emit-capabilities.mjs assembles the JSON from its own restated list of vocabulary names.

And emit-capabilities --check reported "up to date" throughout, because both sides omitted the field, so they agreed. A vocabulary could be declared, typed, used, and never ship, with the check built to catch exactly that saying nothing.

Demonstrated directly — with the emitter's line removed:

emit --check says:  capabilities.json is up to date.
the new guard says: Tests  1 failed | 31 passed (32)

The new guard asserts over the source: every exported as const vocabulary must reach the manifest with the same members. That is the only form of the assertion that cannot be satisfied by two files agreeing to be wrong together. It carries a floor on how many vocabularies it found, so an empty match cannot pass either.

State

Capability version 1.1.0 → 1.2.0; check-capability-version reads it as "additive change with a minor bump — added: field inputSources".

Full suite: 1670 passed, 6 skipped; typecheck, template typecheck and emit-capabilities --check clean.

🤖 Generated with Claude Code

[coderbuds]

Adds comprehensive input-source vocabulary integration with robust manifest and tests.

🎯 Quality: 100% Elite · 📦 Size: Medium

📈 This month: Your 145th PR — above team average · Averaging Excellent

_{See how your team is trending →}

[patchstackdave]

/review