feat(cli): cli-3.22.0 — charter close reconciles follow-ups + offers TDE promotion (#135 Tier 3)

[montfort]

Summary

Implements RFC #135 Tier 3 — the last open tier of the follow-ups automation roadmap. After an interactive charter close, the CLI reconciles the follow-ups registry against the just-closed work and offers to promote new entries to TDEs. Unblocked now that drift detection is reliable (cli-3.21.0, #229/#231 in #235).

CLI-only release: cli-3.22.0 (no framework change).

Behavior

After an interactive charter close (the --from-template paths are skipped — no prompt context):

1. Detect — runs the default followups drift scan (committed git range ∪ working tree) over the recently-written AILOGs. No-op if the project has no follow-ups registry or nothing is unextracted.
2. Extract — writes any §Follow-ups / R<N> (new) content not yet in the registry into ## Bucket: ready (same semantics as followups drift --apply, so nothing is lost).
3. Promote inline — for each new entry, prompts Promote FU-NNN — <desc> to a TDE? [y/N] against the four AGENT-RULES.md §3 criteria. Declining leaves it extracted (captured, not promoted); accepting runs the followups promote flow (creates the TDE with promoted_from_followup traceability). Entries extracted as suspected-closed are flagged in the prompt (likely already resolved → rarely transversal debt).

Design note — scan scope

The scan reuses the stabilized default drift (git range ∪ working tree), not originating_ailogs. That field is the ex-ante seed of the Charter (the AILOGs that motivated it), not the execution AILOGs where follow-ups are written — and it is empty for greenfield (originating_spec) Charters. At close time the default scan captures exactly the just-written work, with no fragile attribution logic.

Implementation

Refactored followups drift into two reusable, side-effect-free cores, shared by followups drift and the close integration (drift's own output is unchanged):

• detect_drift_candidates(project_root, registry, scan_all, range) -> Vec<…> — scan + per-follow-up content-hash dedup, no stdout/exit.
• apply_candidates(registry_path, registry, drifted, today) -> ApplyReport — writes the registry and returns the created FU-NNN ids (the handle the close hook needs for the promotion prompts).

The close hook (offer_followup_promotions) lives in charter/close.rs, guarded to the interactive flow (TTY already confirmed by require_interactive).

Tests

• tier3_detect_apply_dedup_roundtrip — end-to-end of the core without git/TTY: detect → apply → assert the returned FU-001 id + Source-hash written → re-detect is empty (dedup).
• Existing followups drift integration suite (21 tests) green — the refactor preserved behavior.
• Full suite: 24 suites green. New code clippy-clean.

Note: the interactive close prompt path can't be integration-tested (assert_cmd has no TTY; require_interactive rejects), same limitation as the existing interactive-close tests. Coverage lives in the unit test of the extracted cores.

Closes #135

🤖 Generated with Claude Code