From 73e2bd8771de22f767cda015fd3c2eb04b1011d0 Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Wed, 6 May 2026 22:57:58 -0400 Subject: [PATCH] followups: status snapshot for the Open section MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit After F52 closed, every entry in the Open section except F3 has a `**Status:**` line documenting its own resolution (Resolved 2026-05-06, or Out-of-scope). At a glance the section misleadingly looks like 8 live items. Add a header snapshot calling out that only F3 — cross-domain NTLM fixture, externally blocked on a second AD domain — is genuinely open. The other entries stay where they are because the F-numbers in their analysis are referenced from other followups; moving them to `## Resolved` would orphan that context. Co-Authored-By: Claude Opus 4.7 (1M context) --- design/followups.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/design/followups.md b/design/followups.md index bb804f5..85a1061 100644 --- a/design/followups.md +++ b/design/followups.md @@ -6,6 +6,8 @@ move to `## Resolved` with a date + commit hash. ## Open +> **Status snapshot (2026-05-06):** Of the 8 entries in this section, only **F3** is genuinely open work. Every other entry's `**Status:**` line documents its closure (resolved with a date + commit pointer, or marked out-of-scope). They stay in this section as load-bearing context for future contributors who hit the same problems — moving them to `## Resolved` would orphan their analysis from the F-numbers other followups reference. New work goes here; status lines are authoritative for whether an entry needs further action. + ### F48 — Execute `cargo publish` for the V1 release cut **Status:** **Out of scope — internal usage only, no crates.io publish planned.** Confirmed 2026-05-06 by maintainer. The workspace stays at `version = "0.0.0"` indefinitely; consumers depend via path or git, not crates.io. F43's dry-run validation (`design/F48-publish-dry-run.md`) is retained as a workspace-hygiene check (each crate's `cargo package --list` produces a clean tarball, no accidental captures/big files), not as release prep.