chore(straymark): upgrade framework fw-4.22.0 → fw-4.23.0 + cli-3.20.0

.agent/workflows/straymark-followups.md

@@ -53,11 +53,13 @@ Review the registry entries the just-closed Charter resolved:
 
 ```bash
 straymark followups list --status suspected-closed   # entries awaiting confirm-or-reopen
+straymark followups recount                          # reconcile the CLI-owned counters after manual status flips (cli-3.20.0+)
 straymark followups promote FU-NNN                   # FU → TDE elevation (operator-approved)
 ```
 
 - Mark resolved entries `closed` (with the closing Charter id in `Notes`) or `superseded`.
 - Confirm or reopen any `suspected-closed` entries that the Charter's AILOGs produced.
+- After flipping statuses by hand, run `straymark followups recount` so the CLI-owned counters ride the same commit as the triage.
 - For un-resolved entries that meet the TDE criteria of `AGENT-RULES.md §3` (heritage, transversal, dedicated Charter, human prioritization), **propose** promotion via `straymark followups promote FU-NNN` — promotion itself is operator-approved, per the autonomy limits of §3.
 
 ### 4. Report result
@@ -74,7 +76,7 @@ StrayMark: registry synced — commit it together with the AILOG.
 
 ## What this skill does NOT do
 
-- **It does not edit the frontmatter counters** (`total_open`, `total_promoted`, `total_suspected_closed`, …). They are CLI-owned: every write command recomputes them. Hand-editing them is a §13 violation.
+- **It does not edit the frontmatter counters** (`total_open`, `total_promoted`, `total_suspected_closed`, …). They are CLI-owned: `straymark followups recount` (or any write command) recomputes them. Hand-editing them is a §13 violation.
 - **It does not promote without the operator.** `straymark followups promote` is proposed, never auto-run — prioritization and assignment stay human (`AGENT-RULES.md §3`).
 - **It does not delete `suspected-closed` entries.** The operator confirms (→ `closed`) or reopens them at the next triage.
 - **It does not re-scan AILOGs to answer "what's pending?"** when the registry exists — the registry is canonical; `drift` tells you when it is not trustworthy.

.claude/skills/straymark-followups/SKILL.md

@@ -55,11 +55,13 @@ Review the registry entries the just-closed Charter resolved:
 
 ```bash
 straymark followups list --status suspected-closed   # entries awaiting confirm-or-reopen
+straymark followups recount                          # reconcile the CLI-owned counters after manual status flips (cli-3.20.0+)
 straymark followups promote FU-NNN                   # FU → TDE elevation (operator-approved)
 ```
 
 - Mark resolved entries `closed` (with the closing Charter id in `Notes`) or `superseded`.
 - Confirm or reopen any `suspected-closed` entries that the Charter's AILOGs produced.
+- After flipping statuses by hand, run `straymark followups recount` so the CLI-owned counters ride the same commit as the triage.
 - For un-resolved entries that meet the TDE criteria of `AGENT-RULES.md §3` (heritage, transversal, dedicated Charter, human prioritization), **propose** promotion via `straymark followups promote FU-NNN` — promotion itself is operator-approved, per the autonomy limits of §3.
 
 ### 4. Report result
@@ -76,7 +78,7 @@ StrayMark: registry synced — commit it together with the AILOG.
 
 ## What this skill does NOT do
 
-- **It does not edit the frontmatter counters** (`total_open`, `total_promoted`, `total_suspected_closed`, …). They are CLI-owned: every write command recomputes them. Hand-editing them is a §13 violation.
+- **It does not edit the frontmatter counters** (`total_open`, `total_promoted`, `total_suspected_closed`, …). They are CLI-owned: `straymark followups recount` (or any write command) recomputes them. Hand-editing them is a §13 violation.
 - **It does not promote without the operator.** `straymark followups promote` is proposed, never auto-run — prioritization and assignment stay human (`AGENT-RULES.md §3`).
 - **It does not delete `suspected-closed` entries.** The operator confirms (→ `closed`) or reopens them at the next triage.
 - **It does not re-scan AILOGs to answer "what's pending?"** when the registry exists — the registry is canonical; `drift` tells you when it is not trustworthy.

.codex/skills/straymark-followups/SKILL.md

@@ -54,11 +54,13 @@ Review the registry entries the just-closed Charter resolved:
 
 ```bash
 straymark followups list --status suspected-closed   # entries awaiting confirm-or-reopen
+straymark followups recount                          # reconcile the CLI-owned counters after manual status flips (cli-3.20.0+)
 straymark followups promote FU-NNN                   # FU → TDE elevation (operator-approved)
 ```
 
 - Mark resolved entries `closed` (with the closing Charter id in `Notes`) or `superseded`.
 - Confirm or reopen any `suspected-closed` entries that the Charter's AILOGs produced.
+- After flipping statuses by hand, run `straymark followups recount` so the CLI-owned counters ride the same commit as the triage.
 - For un-resolved entries that meet the TDE criteria of `AGENT-RULES.md §3` (heritage, transversal, dedicated Charter, human prioritization), **propose** promotion via `straymark followups promote FU-NNN` — promotion itself is operator-approved, per the autonomy limits of §3.
 
 ### 4. Report result
@@ -75,7 +77,7 @@ StrayMark: registry synced — commit it together with the AILOG.
 
 ## What this skill does NOT do
 
-- **It does not edit the frontmatter counters** (`total_open`, `total_promoted`, `total_suspected_closed`, …). They are CLI-owned: every write command recomputes them. Hand-editing them is a §13 violation.
+- **It does not edit the frontmatter counters** (`total_open`, `total_promoted`, `total_suspected_closed`, …). They are CLI-owned: `straymark followups recount` (or any write command) recomputes them. Hand-editing them is a §13 violation.
 - **It does not promote without the operator.** `straymark followups promote` is proposed, never auto-run — prioritization and assignment stay human (`AGENT-RULES.md §3`).
 - **It does not delete `suspected-closed` entries.** The operator confirms (→ `closed`) or reopens them at the next triage.
 - **It does not re-scan AILOGs to answer "what's pending?"** when the registry exists — the registry is canonical; `drift` tells you when it is not trustworthy.

.cursor/rules/straymark.md

@@ -477,8 +477,8 @@ Follow-ups originate not only from planning (ex-ante) but from **execution reali
 | Stage | What happens | CLI |
 |-------|--------------|-----|
 | **Extraction** | New AILOG with `§Follow-ups` / `R<N> (new)` content → entries auto-extracted into `## Bucket: ready` (or `suspected-closed` when the AILOG text marks them resolved in-Charter). | `straymark followups drift --apply` |
-| **Triage** | Operator reclassifies bucket/trigger/destination, fills `Severity`/`Labels`, confirms or reopens `suspected-closed` entries. Typically once per stage close (~1h per 4-8 Charters at reference-adopter scale). | (manual edit + `followups list`) |
-| **Consumption** | Entries feed Charter planning; when a Charter addresses an entry, mark `in-progress` → `closed` with provenance in `Notes`. | (manual edit) |
+| **Triage** | Operator reclassifies bucket/trigger/destination, fills `Severity`/`Labels`, confirms or reopens `suspected-closed` entries. Typically once per stage close (~1h per 4-8 Charters at reference-adopter scale). | (manual edit + `followups list`; then `followups recount` to reconcile the CLI-owned counters) |
+| **Consumption** | Entries feed Charter planning; when a Charter addresses an entry, mark `in-progress` → `closed` with provenance in `Notes`. | (manual edit + `followups recount`) |
 | **Promotion** | Entries meeting the transversal-debt criteria (AGENT-RULES.md §3) are elevated to a TDE document with full traceability. | `straymark followups promote FU-NNN` |
 
 ### How it relates to existing artifacts
@@ -493,6 +493,7 @@ Follow-ups originate not only from planning (ex-ante) but from **execution reali
 straymark followups list                  # enumerate entries (filters: --bucket, --status, --severity, --label)
 straymark followups status [FU-NNN]       # registry pulse (counters recomputed on the fly) / entry detail
 straymark followups drift [--apply|--scan-all]   # detect/extract AILOGs not yet in the registry
+straymark followups recount               # recompute the CLI-owned counters after a manual-triage session (cli-3.20.0+)
 straymark followups promote FU-NNN        # automate FU → TDE promotion
 ```
 

.cursorrules

@@ -477,8 +477,8 @@ Follow-ups originate not only from planning (ex-ante) but from **execution reali
 | Stage | What happens | CLI |
 |-------|--------------|-----|
 | **Extraction** | New AILOG with `§Follow-ups` / `R<N> (new)` content → entries auto-extracted into `## Bucket: ready` (or `suspected-closed` when the AILOG text marks them resolved in-Charter). | `straymark followups drift --apply` |
-| **Triage** | Operator reclassifies bucket/trigger/destination, fills `Severity`/`Labels`, confirms or reopens `suspected-closed` entries. Typically once per stage close (~1h per 4-8 Charters at reference-adopter scale). | (manual edit + `followups list`) |
-| **Consumption** | Entries feed Charter planning; when a Charter addresses an entry, mark `in-progress` → `closed` with provenance in `Notes`. | (manual edit) |
+| **Triage** | Operator reclassifies bucket/trigger/destination, fills `Severity`/`Labels`, confirms or reopens `suspected-closed` entries. Typically once per stage close (~1h per 4-8 Charters at reference-adopter scale). | (manual edit + `followups list`; then `followups recount` to reconcile the CLI-owned counters) |
+| **Consumption** | Entries feed Charter planning; when a Charter addresses an entry, mark `in-progress` → `closed` with provenance in `Notes`. | (manual edit + `followups recount`) |
 | **Promotion** | Entries meeting the transversal-debt criteria (AGENT-RULES.md §3) are elevated to a TDE document with full traceability. | `straymark followups promote FU-NNN` |
 
 ### How it relates to existing artifacts
@@ -493,6 +493,7 @@ Follow-ups originate not only from planning (ex-ante) but from **execution reali
 straymark followups list                  # enumerate entries (filters: --bucket, --status, --severity, --label)
 straymark followups status [FU-NNN]       # registry pulse (counters recomputed on the fly) / entry detail
 straymark followups drift [--apply|--scan-all]   # detect/extract AILOGs not yet in the registry
+straymark followups recount               # recompute the CLI-owned counters after a manual-triage session (cli-3.20.0+)
 straymark followups promote FU-NNN        # automate FU → TDE promotion
 ```
 

.gemini/skills/straymark-followups/SKILL.md

@@ -54,11 +54,13 @@ Review the registry entries the just-closed Charter resolved:
 
 ```bash
 straymark followups list --status suspected-closed   # entries awaiting confirm-or-reopen
+straymark followups recount                          # reconcile the CLI-owned counters after manual status flips (cli-3.20.0+)
 straymark followups promote FU-NNN                   # FU → TDE elevation (operator-approved)
 ```
 
 - Mark resolved entries `closed` (with the closing Charter id in `Notes`) or `superseded`.
 - Confirm or reopen any `suspected-closed` entries that the Charter's AILOGs produced.
+- After flipping statuses by hand, run `straymark followups recount` so the CLI-owned counters ride the same commit as the triage.
 - For un-resolved entries that meet the TDE criteria of `AGENT-RULES.md §3` (heritage, transversal, dedicated Charter, human prioritization), **propose** promotion via `straymark followups promote FU-NNN` — promotion itself is operator-approved, per the autonomy limits of §3.
 
 ### 4. Report result
@@ -75,7 +77,7 @@ StrayMark: registry synced — commit it together with the AILOG.
 
 ## What this skill does NOT do
 
-- **It does not edit the frontmatter counters** (`total_open`, `total_promoted`, `total_suspected_closed`, …). They are CLI-owned: every write command recomputes them. Hand-editing them is a §13 violation.
+- **It does not edit the frontmatter counters** (`total_open`, `total_promoted`, `total_suspected_closed`, …). They are CLI-owned: `straymark followups recount` (or any write command) recomputes them. Hand-editing them is a §13 violation.
 - **It does not promote without the operator.** `straymark followups promote` is proposed, never auto-run — prioritization and assignment stay human (`AGENT-RULES.md §3`).
 - **It does not delete `suspected-closed` entries.** The operator confirms (→ `closed`) or reopens them at the next triage.
 - **It does not re-scan AILOGs to answer "what's pending?"** when the registry exists — the registry is canonical; `drift` tells you when it is not trustworthy.