[adopter] charter drift rejects the git-range its own Charter template ships (and status lists it as unavailable)

[montfort]

Adopter project

lnxdrive

Adoption discussion link

#205

Finding type

Format friction — a template/workflow got in the way

Charter / telemetry reference

CHARTER-01-road-to-v0-1-0-alpha-1

N-context

n/a

Description

Two related observations on straymark charter drift (cli-3.16.0, fw-4.19.0):

1. The Charter template ships a command the CLI rejects. The Charter
   template's ## Verification block instructs adopters to run:

   straymark charter drift CHARTER-01-road-to-v0-1-0-alpha-1 origin/main..HEAD
   

   but the CLI rejects the range argument:

   $ straymark charter drift CHARTER-01-road-to-v0-1-0-alpha-1 origin/main..HEAD
   error: unexpected argument 'origin/main..HEAD' found
   Usage: straymark charter drift [OPTIONS] <CHARTER_ID>
   

   Run without the range it works, defaulting to HEAD~1..HEAD. So the command
   the template tells adopters to run fails verbatim, and the useful range
   (origin/main..HEAD, the whole branch) is not expressible.

2. charter status labels the command as unavailable.
   straymark charter status <CHARTER-ID> prints, under
   "Phase 2 features (not yet available)":
   drift-check — straymark charter drift (planned cli-3.7.0) — yet the command
   runs and produces output on cli-3.16.0. The status message is stale/misleading.

Expected: the documented command runs as written; status reflects actual
availability. Actual: documented command errors on the range arg; status
flags a working command as not-yet-available.

Proposed upstream change

Either (a) add an optional <RANGE> / --range to charter drift so the
template's command works and is consistent with charter audit --range, or
(b) update the Charter template's ## Verification block to drop the range and
document the HEAD~1..HEAD default. Independently, refresh the charter status
"Phase 2 features" list so drift is not reported as unavailable on ≥cli-3.7.0.