Declarative argument contracts for seam CLIs #147

New issue

Closed

opened 2026-08-15 14:33:46 +00:00 by john · 1 comment

john commented

2026-08-15 14:33:46 +00:00

Owner

Source: deep dive, broader design B3
Verdict: AGREE - proposal

Claim as reviewed

The repository has strict and permissive flag readers, but each CLI chooses manually and unknown flags are often ignored. A small declarative parser could define required values, defaults, duplicates, enums and mutating-target flags in one place, eliminating the present-but-valueless class across seams.

At HEAD `f354864` (v3.3.0)

Two readers exist side by side at cadence-core/bin/lib/seam-input.mjs:45-60 and :63-89; the choice is per-call-site and currently wrong in the mutating seams.

Note

Weigh against the zero-dependency constraint and against simply switching the mutating seams to flagValue, which is a much smaller change and closes the reported defect on its own.

**Source:** deep dive, broader design B3 **Verdict:** AGREE - proposal ### Claim as reviewed The repository has strict and permissive flag readers, but each CLI chooses manually and unknown flags are often ignored. A small declarative parser could define required values, defaults, duplicates, enums and mutating-target flags in one place, eliminating the present-but-valueless class across seams. ### At HEAD f354864 (v3.3.0) Two readers exist side by side at `cadence-core/bin/lib/seam-input.mjs:45-60` and `:63-89`; the choice is per-call-site and currently wrong in the mutating seams. ### Note Weigh against the zero-dependency constraint and against simply switching the mutating seams to `flagValue`, which is a much smaller change and closes the reported defect on its own.