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

Closes the loop between Charter close and the follow-ups registry — the last
open tier of the follow-ups automation roadmap (#135), unblocked now that
drift detection is reliable (cli-3.21.0, #229/#231).

After an interactive `charter close`, the command runs the default
`followups drift` scan (committed git range ∪ working tree) over the
just-written AILOGs, extracts any §Follow-ups / R<N> (new) content not yet in
the registry into `## Bucket: ready`, then offers per-entry TDE promotion
against the four AGENT-RULES.md §3 criteria. Declining leaves the follow-up
extracted (captured, not promoted); accepting runs the `followups promote`
flow. No-op without a registry or when nothing is unextracted; skipped on the
--from-template paths. The scan reuses the stabilized default drift, not
`originating_ailogs` (that field is the ex-ante seed, not the execution
AILOGs where follow-ups live).

Refactors `followups drift` into reusable side-effect-free cores —
detect_drift_candidates() and apply_candidates() (returns the created FU ids)
— shared by `followups drift` and the close integration. drift output
unchanged.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: montfort

CHANGELOG.md

@@ -7,6 +7,20 @@ and this project uses [independent versioning](README.md#versioning) for Framewo
 
 ---
 
+## CLI 3.22.0 — `charter close` reconciles follow-ups and offers TDE promotion (RFC #135 Tier 3)
+
+Closes the loop between Charter close and the follow-ups registry — the last open tier of the follow-ups automation roadmap ([#135](https://github.com/StrangeDaysTech/straymark/issues/135)), unblocked now that drift detection is reliable (cli-3.21.0, #229/#231).
+
+### Added (CLI)
+
+- **`charter close` follow-ups integration**: after an **interactive** close, the command runs the default `followups drift` scan (committed git range ∪ working tree) over the just-written AILOGs, extracts any `§Follow-ups` / `R<N> (new)` content not yet in the registry into `## Bucket: ready`, and then offers **per-entry TDE promotion** against the four AGENT-RULES.md §3 criteria. Declining a prompt leaves the follow-up extracted (captured, not promoted); accepting runs the `followups promote` flow (creates the TDE with `promoted_from_followup` traceability). No-op when there is no registry or nothing is unextracted; skipped on the `--from-template` paths (no interactive prompt context). The scan reuses the stabilized default drift (not scoped to `originating_ailogs`, which is the ex-ante seed rather than the execution AILOGs where follow-ups live).
+
+### Changed (CLI)
+
+- Refactored `followups drift` into reusable, side-effect-free cores — `detect_drift_candidates()` (scan + per-follow-up hash dedup) and `apply_candidates()` (write + return the created `FU-NNN` ids) — shared by `followups drift` and the new `charter close` integration. `followups drift` output is unchanged.
+
+---
+
 ## Framework 4.25.0 / CLI 3.21.0 — follow-ups drift correctness: see the working tree + catch appended follow-ups
 
 Two silent-data-loss bugs in `straymark followups drift`, both surfaced by the reference adopter (Sentinel) and both prerequisites for wiring drift into the Charter-close flow (RFC [#135](https://github.com/StrangeDaysTech/straymark/issues/135) Tier 3).

README.md

@@ -278,7 +278,7 @@ StrayMark uses independent version tags for each component:
 | Component | Tag prefix | Example | Includes |
 | --- | --- | --- | --- |
 | Framework | `fw-` | `fw-4.25.0` | Templates (12 types), governance, directives, Charter template + schema |
-| CLI | `cli-` | `cli-3.21.0` | The `straymark` binary |
+| CLI | `cli-` | `cli-3.22.0` | The `straymark` binary |
 
 Check installed versions with `straymark status` or `straymark about`.
 

cli/Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "straymark-cli"
-version = "3.21.0"
+version = "3.22.0"
 edition = "2021"
 description = "CLI for StrayMark — the cognitive discipline your AI-assisted projects need"
 license = "MIT"

cli/Cargo.toml

@@ -21,6 +21,7 @@ use colored::Colorize;
 use std::path::{Path, PathBuf};
 
 use crate::charter::{self, charters_dir, Charter, CharterStatus};
+use crate::followups;
 use crate::prompts;
 use crate::telemetry_schema::TelemetrySchema;
 use crate::utils;
@@ -134,9 +135,92 @@ pub fn run(
             );
         }
     }
+
+    // Tier 3 (RFC #135): in the interactive close, scan recent AILOGs for
+    // unextracted follow-ups, extract them into the registry, and offer to
+    // promote each to a TDE. Only the interactive flow has a confirmed TTY
+    // (require_interactive ran above) and a finalized close; the --from-template
+    // paths are skipped — run `straymark followups drift --apply` there.
+    if !from_template {
+        offer_followup_promotions(path, project_root)?;
+    }
+
+    Ok(())
+}
+
+/// Reconcile the follow-ups registry against the work just closed, then offer
+/// per-entry TDE promotion. No-op when the project has no registry or when the
+/// recent AILOGs carry no unextracted follow-up content. (Tier 3, RFC #135.)
+fn offer_followup_promotions(path: &str, project_root: &Path) -> Result<()> {
+    use crate::commands::followups::{drift, promote};
+
+    let registry_path = followups::registry_path(project_root);
+    if !registry_path.exists() {
+        // Project hasn't adopted the follow-ups registry — nothing to reconcile.
+        return Ok(());
+    }
+    let registry = followups::parse_registry(&registry_path)?;
+    // Default scan (git range ∪ working tree): at close time this is exactly the
+    // Charter's just-written AILOGs. Not scoped to `originating_ailogs` — that
+    // field is the ex-ante seed, not the execution AILOGs where follow-ups live.
+    let drifted = drift::detect_drift_candidates(project_root, &registry, false, None);
+    if drifted.is_empty() {
+        return Ok(());
+    }
+
+    let today = Local::now().format("%Y-%m-%d").to_string();
+    let report = drift::apply_candidates(&registry_path, &registry, &drifted, &today)?;
+
+    println!();
+    println!("{}", "── Follow-ups ──".bold());
+    utils::success(&format!(
+        "Extracted {} follow-up{} from {} AILOG(s) into the registry (`## Bucket: ready`).",
+        report.applied.len(),
+        if report.applied.len() == 1 { "" } else { "s" },
+        report.ailogs
+    ));
+    if report.suspected > 0 {
+        println!(
+            "  {} {} carried a closure marker → extracted as suspected-closed; confirm at triage.",
+            "!".magenta().bold(),
+            report.suspected
+        );
+    }
+    println!(
+        "  Review against the TDE-promotion criteria (AGENT-RULES.md §3): prior-Charter heritage, spans multiple modules/Charters, needs a dedicated Charter, or needs human prioritization."
+    );
+
+    for fu in &report.applied {
+        // suspected-closed entries are likely already resolved in-Charter, so
+        // they are rarely transversal debt — flag that context in the prompt.
+        let marker = if fu.suspected_closed {
+            " [suspected-closed]"
+        } else {
+            ""
+        };
+        let label = format!(
+            "Promote {} — {}{} to a TDE?",
+            fu.fu_id,
+            truncate_desc(&fu.description, 60),
+            marker
+        );
+        if prompts::prompt_bool(&label, false)? {
+            promote::run(path, &fu.fu_id, None)?;
+        }
+    }
     Ok(())
 }
 
+/// Single-line, length-bounded version of a follow-up description for prompts.
+fn truncate_desc(s: &str, max: usize) -> String {
+    if s.chars().count() <= max {
+        s.to_string()
+    } else {
+        let truncated: String = s.chars().take(max).collect();
+        format!("{}…", truncated.trim_end())
+    }
+}
+
 /// Build the `.straymark/charters/CHARTER-NN.telemetry.yaml` path for a Charter.
 fn telemetry_path_for(charters_state_dir: &Path, charter: &Charter) -> PathBuf {
     // Strip optional slug suffix to keep the telemetry filename stable across