fix: O3 — devtrail charter drift --no-ailog-suppress always emits INFO line (#92)

Closes the last pending design discussion from issue #81 (option (c) per
Sentinel CHARTER-06 telemetry on issue #91).

Resolution: --no-ailog-suppress now always emits at least one line at end
of output, regardless of N. Default mode is unchanged.

  Default + N=0:    silent (no new noise — the common case)
  Default + N>0:    AILOG-suppressed: N path(s) block (existing behavior)
  --flag + N=0:     INFO: AILOG-aware suppression bypassed
                          (would have suppressed: 0 paths)
  --flag + N>0:     INFO: AILOG-aware suppression bypassed
                          (would have suppressed: N path(s) listed above)
                    + per-path list with documenting AILOG ID

Implementation: compute_ailog_suppressions now runs unconditionally so the
count is available regardless of whether suppression is applied. The flag
controls only whether suppression mutates the rendered drift list.

The asymmetry matches `git diff --stat` — silent default, signal on
explicit opt-in. Operators with dispatch suspicion have a one-flag debug
path that always says something.

Tests: 3 new integration tests (N=0 with flag emits INFO; N>0 with flag
emits INFO + per-path list; default at N=0 stays silent — negative test
that we didn't add noise). 414/414 pass.

Bumps cli-3.8.1 / fw-4.7.1 across canonical surface (governance footers,
README + CLI-REFERENCE versioning tables, ADOPTION-GUIDE references).

Inline-annotation observation from the same Sentinel telemetry (paths in
WARNING block don't carry [suppressed] inline) is NOT bundled — flagged
as separate UX polish item, tracked in a follow-up issue, deferred for
empirical confirmation in a future cycle before changing.

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

Author: montfort

CHANGELOG.md

@@ -7,6 +7,75 @@ and this project uses [independent versioning](README.md#versioning) for Framewo
 
 ---
 
+## Framework 4.7.1 / CLI 3.8.1 — O3 resolved (`--no-ailog-suppress` always emits INFO line)
+
+Closes the last `pending design discussion` carried forward from issue #81:
+**O3** — when `devtrail charter drift --no-ailog-suppress` was passed and there
+was nothing for the AILOG-aware filter to suppress (N=0), the output was
+**byte-identical** to the default. Operators couldn't tell whether the
+suppression logic ran and found nothing, or whether the flag was wired
+incorrectly.
+
+Resolution voted by Sentinel CHARTER-06 telemetry on issue #91 (option (c)
+"--no-ailog-suppress only", with the N=0 confirming-line extension):
+
+- Default mode stays silent at N=0 — no new noise in the common case.
+- `--no-ailog-suppress` always emits at least one line confirming dispatch:
+  - At N=0: `INFO: AILOG-aware suppression bypassed (would have suppressed: 0 paths)`
+  - At N>0: `INFO: AILOG-aware suppression bypassed (would have suppressed: N path(s) listed above as drift)` followed by a per-path list with the AILOG ID that documents the risk.
+
+The asymmetry matches the `git diff --stat` shape — silent default, signal on
+explicit opt-in. Operators with dispatch suspicion now have a one-flag debug
+path that always says something.
+
+### Fixed (CLI)
+
+- **`devtrail charter drift --no-ailog-suppress`** — emits a confirming
+  `INFO:` line at end of output regardless of N. The line names the count
+  and (when N>0) lists each path that would have been suppressed with its
+  documenting AILOG ID. Default mode (suppression on) is unchanged: silent
+  at N=0, existing `AILOG-suppressed: N path(s)` block at N>0.
+
+  Implementation: `compute_ailog_suppressions` now runs unconditionally so
+  the count is available regardless of whether suppression is applied. The
+  flag controls only whether the suppression mutates the rendered drift
+  list.
+
+### Tests
+
+- 3 new integration tests:
+  - `charter_drift_no_ailog_suppress_emits_info_line_when_n_zero` (the
+    primary case the issue is about).
+  - `charter_drift_no_ailog_suppress_emits_info_line_when_n_nonzero`
+    (count + per-path listing).
+  - `charter_drift_default_stays_silent_when_n_zero` (negative test:
+    confirms we did NOT add noise to the common case).
+- 414/414 tests pass (3 new on top of 411 from cli-3.8.0).
+
+### Empirical signal that drove this decision
+
+Sentinel CHARTER-06 was constructed deliberately to exercise the
+N>0 path (`subscriber.go` declared in the Charter, named in
+AILOG-2026-05-03-034's `## Risk` section, not modified during execution).
+The captured outputs confirmed the byte-identical-at-N=0 ambiguity and
+voted for option (c) with a one-line N=0 confirmation. Full telemetry is
+on issue #91.
+
+A secondary observation from the same run — that paths in the WARNING
+block don't carry an inline `[suppressed]` annotation, forcing the reader
+to scan top-to-bottom to know a WARNING was OK'd — is **not bundled here**.
+It's a UX polish item flagged for separate validation; tracked in a
+follow-up issue rather than rolled into this patch to keep the change
+surgical.
+
+### What's NOT in this release
+
+- Inline `[suppressed]` annotation on WARNING block items (separate issue).
+- HTTP API clients for `charter audit` (Phase 3 v1).
+- Inter-family heterogeneity auto-enforcement.
+
+---
+
 ## Framework 4.7.0 / CLI 3.8.0 — Phase 3 (multi-model external audit, orchestration-only) + open frictions F2/F5/F7
 
 The first feature-bearing release since Phase 2 (fw-4.6.0/cli-3.7.0). Lands the

README.md

@@ -259,8 +259,8 @@ DevTrail uses independent version tags for each component:
 
 | Component | Tag prefix | Example | Includes |
 |-----------|-----------|---------|----------|
-| Framework | `fw-` | `fw-4.7.0` | Templates (12 types), governance, directives, Charter template + schema |
-| CLI | `cli-` | `cli-3.8.0` | The `devtrail` binary |
+| Framework | `fw-` | `fw-4.7.1` | Templates (12 types), governance, directives, Charter template + schema |
+| CLI | `cli-` | `cli-3.8.1` | The `devtrail` binary |
 
 Check installed versions with `devtrail status` or `devtrail about`.
 
@@ -292,7 +292,7 @@ See [CLI Reference](https://github.com/StrangeDaysTech/devtrail/blob/main/docs/a
 ```bash
 # Download the latest framework release ZIP from GitHub
 # Go to https://github.com/StrangeDaysTech/devtrail/releases
-# and download the latest fw-* release (e.g., fw-4.7.0)
+# and download the latest fw-* release (e.g., fw-4.7.1)
 
 # Extract and copy to your project
 unzip devtrail-fw-*.zip -d your-project/

cli/Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "devtrail-cli"
-version = "3.8.0"
+version = "3.8.1"
 edition = "2021"
 description = "CLI for DevTrail — the cognitive discipline your AI-assisted projects need"
 license = "MIT"

cli/Cargo.toml

@@ -89,17 +89,28 @@ pub fn run(
     let stderr = String::from_utf8_lossy(&output.stderr).into_owned();
     let raw_exit = output.status.code().unwrap_or(-1);
 
-    // Parse the script output to identify declared-but-not-modified paths so
-    // we can apply AILOG-suppression. Scope-expansion ("Modified but NOT
-    // declared") is informational and not suppressed — those paths are not
-    // in the Charter's declared list and rarely overlap with documented
-    // risks.
+    // Parse the script output to identify declared-but-not-modified paths.
+    // Scope-expansion ("Modified but NOT declared") is informational and not
+    // suppressed — those paths are not in the Charter's declared list and
+    // rarely overlap with documented risks.
     let omitted = extract_omitted_paths(&stdout);
-    let suppressions: Vec<(String, String)> = if no_ailog_suppress || omitted.is_empty() {
+
+    // O3 (cli-3.8.1, issue #91): always compute what AILOG-aware suppression
+    // would have done, regardless of the flag. The flag only controls
+    // whether to APPLY that suppression to the rendered output. This lets us
+    // emit a confirming INFO line when --no-ailog-suppress is passed (the
+    // operator opted into the diagnostic mode and deserves visible signal,
+    // even when N=0).
+    let would_have_suppressed: Vec<(String, String)> = if omitted.is_empty() {
         Vec::new()
     } else {
         compute_ailog_suppressions(project_root, &charter, &omitted)?
     };
+    let suppressions: Vec<(String, String)> = if no_ailog_suppress {
+        Vec::new()
+    } else {
+        would_have_suppressed.clone()
+    };
     let suppressed_paths: std::collections::HashSet<String> =
         suppressions.iter().map(|(p, _)| p.clone()).collect();
     let omitted_after: Vec<String> = omitted
@@ -127,6 +138,35 @@ pub fn run(
         }
     }
 
+    // O3 (cli-3.8.1): when --no-ailog-suppress is passed, always emit at
+    // least one line confirming dispatch — closes the "default and
+    // --no-ailog-suppress produce byte-identical output at N=0" ambiguity
+    // reported in Sentinel CHARTER-02 telemetry. Issue #91 vote: option
+    // (c) "--no-ailog-suppress only", with explicit confirmation when N=0.
+    if no_ailog_suppress {
+        println!();
+        let n = would_have_suppressed.len();
+        if n == 0 {
+            println!(
+                "{} AILOG-aware suppression bypassed (would have suppressed: 0 paths)",
+                "INFO:".cyan().bold()
+            );
+        } else {
+            println!(
+                "{} AILOG-aware suppression bypassed (would have suppressed: {} path(s) listed above as drift)",
+                "INFO:".cyan().bold(),
+                n
+            );
+            for (path, ailog_id) in &would_have_suppressed {
+                println!(
+                    "  - {} [would suppress: {}]",
+                    path,
+                    ailog_id.dimmed()
+                );
+            }
+        }
+    }
+
     // Final exit code: if AILOG-suppression cleared all omitted paths, the
     // script-reported exit is overridden to 0 (the user did the right thing
     // by documenting the risk in an AILOG).

cli/src/commands/charter/drift.rs

@@ -279,6 +279,149 @@ review_required: false
         .stdout(predicate::str::contains("Declared in Charter but NOT modified"));
 }
 
+// ── O3 (cli-3.8.1): --no-ailog-suppress always emits INFO line ──────
+
+#[test]
+fn charter_drift_no_ailog_suppress_emits_info_line_when_n_zero() {
+    // O3 (issue #91): when --no-ailog-suppress is passed AND there's
+    // nothing the AILOG-aware filter would have suppressed (N=0), we
+    // still emit one INFO line confirming the flag was honored. Closes
+    // the byte-identical-output ambiguity Sentinel CHARTER-02 reported.
+    if !bash_available() {
+        eprintln!("skipping: bash not available");
+        return;
+    }
+    let dir = TempDir::new().unwrap();
+    setup_devtrail(dir.path());
+    write_charter_with_files(dir.path(), &["src/foo.rs"], None);
+    std::fs::create_dir_all(dir.path().join("src")).unwrap();
+    std::fs::write(dir.path().join("src/foo.rs"), "// initial\n").unwrap();
+    git(dir.path(), &["init", "-q", "-b", "main"]);
+    git(dir.path(), &["add", "."]);
+    git(dir.path(), &["commit", "-q", "-m", "initial"]);
+    std::fs::write(dir.path().join("src/foo.rs"), "// edited\n").unwrap();
+    git(dir.path(), &["add", "."]);
+    git(dir.path(), &["commit", "-q", "-m", "edit foo"]);
+
+    Command::cargo_bin("devtrail")
+        .unwrap()
+        .args([
+            "charter",
+            "drift",
+            "CHARTER-01",
+            "--no-ailog-suppress",
+            "--path",
+        ])
+        .arg(dir.path().to_str().unwrap())
+        .assert()
+        .success()
+        .stdout(predicate::str::contains(
+            "AILOG-aware suppression bypassed (would have suppressed: 0 paths)",
+        ));
+}
+
+#[test]
+fn charter_drift_no_ailog_suppress_emits_info_line_when_n_nonzero() {
+    // When --no-ailog-suppress is passed AND there's something the filter
+    // would have suppressed (N>0), the INFO line names the count and
+    // lists each path that was bypassed (with the AILOG ID that documents
+    // the risk). The drift itself is still surfaced as failure exit.
+    if !bash_available() {
+        return;
+    }
+    let dir = TempDir::new().unwrap();
+    setup_devtrail(dir.path());
+
+    let ailog_path = dir
+        .path()
+        .join(".devtrail/07-ai-audit/agent-logs/AILOG-2026-05-03-001-document-bar.md");
+    std::fs::write(
+        &ailog_path,
+        r#"---
+id: AILOG-2026-05-03-001
+title: Document bar
+agent: test
+confidence: high
+risk_level: low
+review_required: false
+---
+
+## Risk
+
+- **R3**: `src/bar.rs` documented as scope-simplified.
+"#,
+    )
+    .unwrap();
+
+    write_charter_with_files(
+        dir.path(),
+        &["src/foo.rs", "src/bar.rs"],
+        Some("AILOG-2026-05-03-001"),
+    );
+    std::fs::create_dir_all(dir.path().join("src")).unwrap();
+    std::fs::write(dir.path().join("src/foo.rs"), "// initial\n").unwrap();
+    std::fs::write(dir.path().join("src/bar.rs"), "// initial\n").unwrap();
+    git(dir.path(), &["init", "-q", "-b", "main"]);
+    git(dir.path(), &["add", "."]);
+    git(dir.path(), &["commit", "-q", "-m", "initial"]);
+    std::fs::write(dir.path().join("src/foo.rs"), "// edited\n").unwrap();
+    git(dir.path(), &["add", "."]);
+    git(dir.path(), &["commit", "-q", "-m", "edit foo only"]);
+
+    Command::cargo_bin("devtrail")
+        .unwrap()
+        .args([
+            "charter",
+            "drift",
+            "CHARTER-01",
+            "--no-ailog-suppress",
+            "--path",
+        ])
+        .arg(dir.path().to_str().unwrap())
+        .assert()
+        .failure()
+        // INFO line names the count.
+        .stdout(predicate::str::contains(
+            "AILOG-aware suppression bypassed (would have suppressed: 1 path(s)",
+        ))
+        // And lists each would-have-been-suppressed path.
+        .stdout(predicate::str::contains("src/bar.rs"))
+        .stdout(predicate::str::contains("would suppress: AILOG-2026-05-03-001"));
+}
+
+#[test]
+fn charter_drift_default_stays_silent_when_n_zero() {
+    // The flip side of O3: the DEFAULT (suppression on) must NOT emit
+    // an INFO line when there's nothing to suppress. The common-case
+    // output stays minimal — adding ceremony there is what (a)
+    // "always-on" would have done, which we explicitly rejected per
+    // the Sentinel CHARTER-06 vote.
+    if !bash_available() {
+        return;
+    }
+    let dir = TempDir::new().unwrap();
+    setup_devtrail(dir.path());
+    write_charter_with_files(dir.path(), &["src/foo.rs"], None);
+    std::fs::create_dir_all(dir.path().join("src")).unwrap();
+    std::fs::write(dir.path().join("src/foo.rs"), "// initial\n").unwrap();
+    git(dir.path(), &["init", "-q", "-b", "main"]);
+    git(dir.path(), &["add", "."]);
+    git(dir.path(), &["commit", "-q", "-m", "initial"]);
+    std::fs::write(dir.path().join("src/foo.rs"), "// edited\n").unwrap();
+    git(dir.path(), &["add", "."]);
+    git(dir.path(), &["commit", "-q", "-m", "edit foo"]);
+
+    Command::cargo_bin("devtrail")
+        .unwrap()
+        .args(["charter", "drift", "CHARTER-01", "--path"])
+        .arg(dir.path().to_str().unwrap())
+        .assert()
+        .success()
+        .stdout(predicate::str::contains("OK No drift detected"))
+        // No INFO line in default mode at N=0.
+        .stdout(predicate::str::contains("AILOG-aware suppression bypassed").not());
+}
+
 #[test]
 fn charter_drift_resolves_glob_wildcards_in_declared_paths() {
     // fw-4.6.2: bulk Charters can declare `prefix*suffix` glob patterns

cli/tests/charter_drift_test.rs

@@ -270,4 +270,4 @@ When a change modifies API endpoints:
 
 ---
 
-*DevTrail v4.7.0 | [Strange Days Tech](https://strangedays.tech)*
+*DevTrail v4.7.1 | [Strange Days Tech](https://strangedays.tech)*

dist/.devtrail/00-governance/AGENT-RULES.md

@@ -234,4 +234,4 @@ Use a Level 1 (Context) diagram to illustrate:
 
 ---
 
-*DevTrail v4.7.0 | [Strange Days Tech](https://strangedays.tech)*
+*DevTrail v4.7.1 | [Strange Days Tech](https://strangedays.tech)*

dist/.devtrail/00-governance/C4-DIAGRAM-GUIDE.md

@@ -307,4 +307,4 @@ See also [ADR-2025-01-20-001] for architectural context.
 
 ---
 
-*DevTrail v4.7.0 | [Strange Days Tech](https://strangedays.tech)*
+*DevTrail v4.7.1 | [Strange Days Tech](https://strangedays.tech)*

dist/.devtrail/00-governance/DOCUMENTATION-POLICY.md

@@ -213,4 +213,4 @@ Mark `review_required: true` when:
 
 ---
 
-*DevTrail v4.7.0 | [Strange Days Tech](https://strangedays.tech)*
+*DevTrail v4.7.1 | [Strange Days Tech](https://strangedays.tech)*