familygaps

Overview ¶

Command familygaps reports, for one behavior family, which upstream PORT_MAP entries fall within its scope and which lack behavioral verification. Weak scenarios (boot-only, smoke-only, deferred, and provider registration-only outside registry paths) do not mark an entry as covered.

Usage:

go run ./test/parity/cmd/familygaps                       # all families
go run ./test/parity/cmd/familygaps -family slash-commands # one family
go run ./test/parity/cmd/familygaps -strict               # exit 1 if any family has untested entries

Output for a single family:

Family: slash-commands
Scope: 2 PORT_MAP entries
Description: Slash command registry, dispatch, and individual command handlers.

In-family scenarios: 4

✅ Behaviorally covered by in-family scenario (1):
   packages/coding-agent/src/core/slash-commands.ts → 4 scenario(s)

🟡 Covered only by other-family scenario (0):

⬜ Untested (1):
   packages/coding-agent/src/utils/changelog.ts

Run at the start of a family loop to see the scope; run at the end to verify no behaviorally-required entry in scope was silently skipped. Every entry in the ⬜ section must either be covered before the loop ends OR justified in the commit message with one of:

• covered elsewhere (cite the scenario)
• numbered divergence (cite the DN)
• explicit user deferral
• undefined upstream behavior (cite probe evidence)

"Silent skip" is no longer allowed.