fix(cli): resolve charter drift/audit adopter friction (closes #207, closes #208)

[montfort]

Adopter feedback from lnxdrive (CHARTER-01-road-to-v0-1-0-alpha-1). Both verified unaddressed against current code before fixing. Consolidating before the combined release that already carries #215.

#207 — charter drift

Part	Fix
Template ships a rejected command	The Charter template's ## Verification block instructed the positional range charter drift CHARTER-NN origin/main..HEAD (the CLI rejects it) wrapped in stale "when Phase 2 ships" language. Now --range origin/main..HEAD, Phase-2 conditionals dropped (EN/es/zh-CN).
charter status lists drift as unavailable	Removed the "Phase 2 features (not yet available)… (planned cli-3.7.0)" block — both charter drift and charter close shipped ~16 versions ago.

#208 — charter audit --prepare silent under-coverage

On a multi-batch Charter whose earlier phases already merged to the base branch, the default range origin/main..HEAD silently excludes the merged commits, so a phase-scoped audit prompt under-covers.

• Warning (the core fix): --prepare now detects completed batches in the Charter body / referenced AILOGs' Batch Ledgers (reusing cli::ailog::{parse_batch_ledger, BatchEntry}) and, when no explicit --range was given, warns that the audit may under-cover and to pass an explicit range. With --range the warning is suppressed.
• Docs: the pitfall is documented in charter audit --help, CLI-REFERENCE (EN/es/zh-CN), and the straymark-audit-prompt skill (4 variants, codex regenerated).

The issue's alternative — defaulting the lower bound to the Charter's first commit — was not taken (it would change the default for all audits and needs Charter metadata); the warning + docs make the silent case loud without that risk.

Scope

• CLI: commands/charter/audit.rs (warning + completed_batch_numbers), commands/charter/status.rs (remove stale block), main.rs (--range help).
• Framework: charter template (EN/es/zh-CN), straymark-audit-prompt skill (claude/gemini/agent + codex).
• Docs: CLI-REFERENCE (EN/es/zh-CN).
• No version bumps or tags — combined release (core/cli/fw, with [adopter] Three validator gaps from a 150-doc housekeeping pass: OBS-001 false positives (19/19), exactly-one originating_* vs documented AILOG aggregation (N=5), CHARTER-FILES-EXIST exemption markers #215) prepared separately.

Verification

• cargo test — full workspace green (348 lib + integration; 2 new tests: status omits stale block; audit warns on multi-batch without --range and stays silent with it).
• cargo build --release clean; cargo clippy no new warnings in touched files; gen_codex_skills --check in sync.
• Dogfood on a temp project: charter status no longer prints "not yet available"; charter drift … --range HEAD~1..HEAD accepted; charter audit --prepare on a Charter with a completed batch warns without --range, silent with it.

🤖 Generated with Claude Code