docs: add followups recount to README command bullets (×3) and CLAUDE.md command table (#224)

Docs-sync follow-up of #223: the cli-3.20.0 recount subcommand was
documented in CLI-REFERENCE/CHANGELOG/pattern doc but the README
command-summary bullet (EN/ES/zh-CN) and the CLAUDE.md CLI commands
table still listed <list|status|drift|promote> only.

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

Author: montfort

CLAUDE.md

@@ -238,7 +238,8 @@ Users can now run `straymark update-framework` to get the new version.
 | `straymark analyze declared-vs-wired [path]` | Flag declared symbols (IPC/RPC proxy methods) with no implemented wiring counterpart — config-driven set-difference (POLISH-CHARTER-PATTERN sub-class 5) |
 | `straymark followups list [--bucket] [--status] [--severity] [--label]` | List follow-ups registry entries with filters |
 | `straymark followups status [FU-NNN]` | Registry pulse (counters recomputed on the fly) or entry detail |
-| `straymark followups drift [--apply] [--scan-all]` | Detect/extract AILOGs with unextracted follow-up content (native, anti-noise `suspected-closed`, recomputes CLI-owned counters, upgrades v0→v1) |
+| `straymark followups drift [--apply] [--scan-all]` | Detect/extract AILOGs with unextracted follow-up content (native, anti-noise `suspected-closed`, recomputes CLI-owned counters even with zero extractions, upgrades v0→v1) |
+| `straymark followups recount` | Recompute the CLI-owned counters after a manual-triage session (no AILOG scan, idempotent) |
 | `straymark followups promote FU-NNN` | Elevate an entry to a TDE document with `promoted_from_followup` traceability |
 | `straymark audit [path]` | Generate audit trail reports with timeline and traceability |
 | `straymark explore [path]` | Interactive TUI documentation browser |

README.md

@@ -149,7 +149,7 @@ Built-in safeguards ensure humans stay in control:
 Built-in commands that turn the discipline into actionable feedback:
 
 - **`straymark charter <new|list|status|close|drift|batch-complete|audit|refresh-suggest|amend>`** — Bounded units of work declared ex-ante, audited ex-post. `close` records post-execution telemetry; `drift` detects file-vs-commit drift with AILOG-aware suppression and (cli-3.13.0+) gates on `### Batch N (pending)` entries in the AILOG `## Batch Ledger`; `batch-complete` (cli-3.13.0+) marks a batch as complete in the ledger for multi-batch Charters (3+ batches or >1 day); `audit` orchestrates a multi-model external review (3-step prepare/calibrate/finalize, orchestration-only — no LLM API calls); `refresh-suggest` (cli-3.14.0+) prints a heuristic recommendation for a pre-declare SpecKit refresh when a multi-Charter module's rolling `r_n_plus_one_emergent_count` mean exceeds a threshold; `amend` (cli-3.14.0+) scaffolds a post-close Batch N.4 amendment (audit-driven remediation) on the same execute branch without opening a new Charter. For IDE-driven workflows, the inline skills `/straymark-audit-prompt` and `/straymark-audit-review` wrap the CLI to surface prompts in the conversation and merge findings into telemetry.
-- **`straymark followups <list|status|drift|promote>`** *(cli-3.19.0+)* — First-class follow-ups backlog registry (`.straymark/follow-ups-backlog.md`, schema v1 experimental): `drift --apply` extracts `§Follow-ups` / `R<N> (new)` entries from AILOGs per-AILOG (closure-marked bullets land as `suspected-closed`), counters are CLI-owned and recomputed on every write, and `promote` elevates entries to TDE documents with full traceability. See `STRAYMARK.md §16` and `FOLLOW-UPS-BACKLOG-PATTERN.md`.
+- **`straymark followups <list|status|drift|recount|promote>`** *(cli-3.19.0+; `recount` cli-3.20.0+)* — First-class follow-ups backlog registry (`.straymark/follow-ups-backlog.md`, schema v1 experimental): `drift --apply` extracts `§Follow-ups` / `R<N> (new)` entries from AILOGs per-AILOG (closure-marked bullets land as `suspected-closed`), counters are CLI-owned and recomputed on every write, `recount` reconciles them after a manual-triage session, and `promote` elevates entries to TDE documents with full traceability. See `STRAYMARK.md §16` and `FOLLOW-UPS-BACKLOG-PATTERN.md`.
 - **`straymark approve <doc-id>`** — Record a formal human approval (writes `reviewed_by` / `reviewed_at` / `review_outcome` and the `## Approval` body section in one edit; closes the gap canonized in DOCUMENTATION-POLICY §3.5)
 - **`straymark validate`** — 25+ validation rules for document correctness (12 China-specific are scope-aware); `--include-charters` extends to `.straymark/charters/`; `--check-pending-reviews` lists approval backlog (warn-only)
 - **`straymark metrics`** — Governance KPIs, review rates, risk distribution, trends

docs/i18n/es/README.md

@@ -143,7 +143,7 @@ Salvaguardas incorporadas que aseguran que los humanos mantengan el control:
 Comandos integrados que convierten la disciplina en feedback accionable:
 
 - **`straymark charter <new|list|status|close|drift|batch-complete|audit|refresh-suggest|amend>`** — Unidades acotadas declaradas ex-ante, auditadas ex-post. `close` registra telemetría; `drift` detecta drift archivos-vs-commits con supresión AILOG-aware y (cli-3.13.0+) hace gate sobre entradas `### Batch N (pending)` en `## Batch Ledger` del AILOG; `batch-complete` (cli-3.13.0+) marca un batch como completado en la ledger para Charters multi-batch (3+ lotes o >1 día); `audit` orquesta revisión externa multi-modelo (flujo de 3 pasos prepare/calibrate/finalize, orchestration-only — sin invocación de APIs de LLM); `refresh-suggest` (cli-3.14.0+) imprime una recomendación heurística para un refresh SpecKit pre-declare cuando la media móvil de `r_n_plus_one_emergent_count` de un módulo multi-Charter supera un umbral; `amend` (cli-3.14.0+) hace scaffolding de una enmienda post-close Batch N.4 (remediación dirigida por auditoría) sobre la misma rama de execute sin abrir un Charter nuevo. Para flujos IDE-driven, las skills inline `/straymark-audit-prompt` y `/straymark-audit-review` envuelven al CLI para mostrar prompts en la conversación y mergear findings en la telemetría.
-- **`straymark followups <list|status|drift|promote>`** *(cli-3.19.0+)* — Registro de backlog de follow-ups de primera clase (`.straymark/follow-ups-backlog.md`, schema v1 experimental): `drift --apply` extrae las entradas `§Follow-ups` / `R<N> (new)` de los AILOGs por-AILOG (los bullets con marcador de cierre aterrizan como `suspected-closed`), los contadores son propiedad del CLI y se recalculan en cada escritura, y `promote` eleva las entradas a documentos TDE con trazabilidad completa. Ver `STRAYMARK.md §16` y `FOLLOW-UPS-BACKLOG-PATTERN.md`.
+- **`straymark followups <list|status|drift|recount|promote>`** *(cli-3.19.0+; `recount` cli-3.20.0+)* — Registro de backlog de follow-ups de primera clase (`.straymark/follow-ups-backlog.md`, schema v1 experimental): `drift --apply` extrae las entradas `§Follow-ups` / `R<N> (new)` de los AILOGs por-AILOG (los bullets con marcador de cierre aterrizan como `suspected-closed`), los contadores son propiedad del CLI y se recalculan en cada escritura, `recount` los reconcilia tras una sesión de triage manual, y `promote` eleva las entradas a documentos TDE con trazabilidad completa. Ver `STRAYMARK.md §16` y `FOLLOW-UPS-BACKLOG-PATTERN.md`.
 - **`straymark approve <doc-id>`** — Registra una aprobación humana formal (escribe `reviewed_by` / `reviewed_at` / `review_outcome` y la sección body `## Approval` en una sola edición; cierra el gap canonizado en DOCUMENTATION-POLICY §3.5)
 - **`straymark validate`** — 25+ reglas de validación para corrección documental (12 específicas de China son scope-aware); `--include-charters` extiende a `.straymark/charters/`; `--check-pending-reviews` lista el backlog de aprobaciones (warn-only)
 - **`straymark metrics`** — KPIs de gobernanza, tasas de revisión, distribución de riesgo, tendencias

docs/i18n/zh-CN/README.md

@@ -143,7 +143,7 @@ StrayMark 的产品决策基于十二条明确的原则。它们按层级排序
 将纪律转化为可执行反馈的内置命令：
 
 - **`straymark charter <new|list|status|close|drift|batch-complete|audit|refresh-suggest|amend>`** — 事前声明、事后审计的有界工作单元。`close` 记录执行后遥测；`drift` 以 AILOG-aware 抑制方式检测文件-与-commit 的偏差，并（cli-3.13.0+）对 AILOG `## Batch Ledger` 中的 `### Batch N (pending)` 条目进行门控；`batch-complete`（cli-3.13.0+）将批次标记为已在多批次章程（3+ 批次或 >1 天）的台账中完成；`audit` 编排多模型外部审查（三步骤 prepare/calibrate/finalize，仅编排——不调用 LLM API）；`refresh-suggest`（cli-3.14.0+）当多 Charter 模块的 `r_n_plus_one_emergent_count` 滚动均值超过阈值时，输出预声明 SpecKit 刷新的启发式建议；`amend`（cli-3.14.0+）为关闭后审计驱动的 Batch N.4 修订做脚手架，在原 execute 分支上落地而不开启新 Charter。对于 IDE 驱动的工作流，内联 skills `/straymark-audit-prompt` 和 `/straymark-audit-review` 封装 CLI，在对话中展示 prompts 并将 findings 合并到遥测中。
-- **`straymark followups <list|status|drift|promote>`** *(cli-3.19.0+)* — 一等的后续事项积压注册表（`.straymark/follow-ups-backlog.md`，schema v1 实验性）：`drift --apply` 按 AILOG 从 AILOG 中提取 `§Follow-ups` / `R<N> (new)` 条目（带闭合标记的 bullet 落为 `suspected-closed`），计数器由 CLI 拥有并在每次写入时重新计算，`promote` 将条目提升为带完整溯源的 TDE 文档。详见 `STRAYMARK.md §16` 与 `FOLLOW-UPS-BACKLOG-PATTERN.md`。
+- **`straymark followups <list|status|drift|recount|promote>`** *(cli-3.19.0+；`recount` cli-3.20.0+)* — 一等的后续事项积压注册表（`.straymark/follow-ups-backlog.md`，schema v1 实验性）：`drift --apply` 按 AILOG 从 AILOG 中提取 `§Follow-ups` / `R<N> (new)` 条目（带闭合标记的 bullet 落为 `suspected-closed`），计数器由 CLI 拥有并在每次写入时重新计算，`recount` 在手动分诊会话后调和计数器，`promote` 将条目提升为带完整溯源的 TDE 文档。详见 `STRAYMARK.md §16` 与 `FOLLOW-UPS-BACKLOG-PATTERN.md`。
 - **`straymark approve <doc-id>`** — 记录一次正式的人工审批（一次性写入 `reviewed_by` / `reviewed_at` / `review_outcome` 与 `## Approval` body 章节；闭合 DOCUMENTATION-POLICY §3.5 中规范化的缺口）
 - **`straymark validate`** — 25+ 条文档正确性验证规则（其中 12 条针对中国法规、按 scope 启用）；`--include-charters` 可同时检查 `.straymark/charters/`；`--check-pending-reviews` 列出审批积压（仅警告）
 - **`straymark metrics`** — 治理 KPI、审查率、风险分布、趋势