chore(framework): fw-4.16.1 — docs polish (Issue #156 follow-up) (#158)

Documentation-only patch addressing the two non-blocking observations raised
in the Issue #156 closure comment after the adopter pulled fw-4.16.0:

1. STRAYMARK.md §Directive Injection Markers — clarified missing-target
   behavior per command: `init` and `update-framework` create the target
   file if missing (walk manifest.injections end-to-end); `repair` re-injects
   only when STRAYMARK.md itself is missing. Adopter who deleted a single
   target while keeping STRAYMARK.md should re-run `update-framework`, not
   `repair`. Resolves the AGENTS.md observation.

2. CLI-REFERENCE.md (EN/ES/zh-CN) — clarified that --threshold N is the
   only override path for `charter refresh-suggest` in v0.2; there is no
   config.yml field for the heuristic threshold yet.

Also fixes a pre-existing asymmetry: EN CLI-REFERENCE versioning row was
left at fw-4.15.0 through the fw-4.16.0 cycle.

No CLI bump — docs-only. cli-3.14.0 from the fw-4.16.0 cycle remains current.

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

Author: montfort

CHANGELOG.md

@@ -7,6 +7,23 @@ and this project uses [independent versioning](README.md#versioning) for Framewo
 
 ---
 
+## Framework 4.16.1 — docs polish (Issue #156 follow-up)
+
+Documentation-only patch addressing two non-blocking observations raised in the [Issue #156 closure comment](https://github.com/StrangeDaysTech/straymark/issues/156#issuecomment-4465050814) after the adopter pulled `fw-4.16.0` / `cli-3.14.0`. No CLI bump.
+
+### Changed (Framework)
+
+- **`dist/STRAYMARK.md §Directive Injection Markers`** — added an explicit clarification of how each command treats a missing injection target. `straymark init` and `straymark update-framework` walk `dist-manifest.yml::injections:` end-to-end and create the target file if it does not exist. `straymark repair` is narrower: it re-injects directives only when `STRAYMARK.md` itself is missing. The practical guidance for an adopter who deleted a single target while keeping `STRAYMARK.md` is to re-run `straymark update-framework`, not `straymark repair`. Resolves the AGENTS.md observation from the closure comment.
+- **`docs/adopters/CLI-REFERENCE.md` (EN + ES + zh-CN)** — clarified that the `--threshold N` flag is the only override path for `straymark charter refresh-suggest` in v0.2; there is no `config.yml` field for the heuristic threshold yet (tuning lives at the operator-invocation level until a second adopter validates a project-wide default).
+- **Versioning tables** in `README.md` + i18n and `CLI-REFERENCE.md` + i18n bumped to `fw-4.16.1`. EN CLI-REFERENCE versioning row had been left at `fw-4.15.0` through the `fw-4.16.0` cycle — fixed in this patch.
+- **Governance footers** bumped to `v4.16.1` across `QUICK-REFERENCE.md`, `AGENT-RULES.md`, `DOCUMENTATION-POLICY.md`, `C4-DIAGRAM-GUIDE.md` (EN + ES + zh-CN).
+
+### Adopter guidance
+
+`straymark update-framework` brings the clarifications. No CLI install required — `cli-3.14.0` from the `fw-4.16.0` cycle remains current.
+
+---
+
 ## Framework 4.16.0 / CLI 3.14.0 — Charter-chain evolution patterns (Issue #156)
 
 Codifies two patterns surfaced by the Sentinel adopter after seven consecutive CommsHub Charters (Issue [#156](https://github.com/StrangeDaysTech/straymark/issues/156)): a **pre-declare SpecKit refresh** that absorbs accumulated chain-level learnings before the next Charter is declared, and a **post-close audit-driven Batch N.4 amendment** that handles bounded external-audit findings on the same execute branch without opening a new Charter. Both are operator-driven; the framework ships canonical guidance in `00-governance/CHARTER-CHAIN-EVOLUTION.md` (EN/ES/zh-CN), opt-in telemetry slots in the schema, and two new read-only/scaffolding CLI helpers. Also fixes the `straymark charter audit --merge-into` bug where the v0 re-audit guard rejected the empty-array placeholder `external_audit: []`, breaking the post-close audit-cycle round-trip.

README.md

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

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

@@ -379,4 +379,4 @@ When a project accumulates a high volume of AILOGs across multiple Charters and
 
 ---
 
-*StrayMark v4.16.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark v4.16.1 | [Strange Days Tech](https://strangedays.tech)*

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

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

dist/.straymark/00-governance/CHARTER-CHAIN-EVOLUTION.md

@@ -193,4 +193,4 @@ This document is itself the output of the acceptance flow Sentinel walked throug
 
 ---
 
-*StrayMark fw-4.16.0 | [GitHub](https://github.com/StrangeDaysTech/straymark) | Issue [#156](https://github.com/StrangeDaysTech/straymark/issues/156)*
+*StrayMark fw-4.16.1 | [GitHub](https://github.com/StrangeDaysTech/straymark) | Issue [#156](https://github.com/StrangeDaysTech/straymark/issues/156)*

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

@@ -318,4 +318,4 @@ See also [ADR-2025-01-20-001] for architectural context.
 
 ---
 
-*StrayMark v4.16.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark v4.16.1 | [Strange Days Tech](https://strangedays.tech)*

dist/.straymark/00-governance/QUICK-REFERENCE.md

@@ -241,4 +241,4 @@ Mark `review_required: true` when:
 
 ---
 
-*StrayMark v4.16.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark v4.16.1 | [Strange Days Tech](https://strangedays.tech)*

dist/.straymark/00-governance/i18n/es/AGENT-RULES.md

@@ -379,4 +379,4 @@ Cuando un proyecto acumula un volumen alto de AILOGs a lo largo de múltiples Ch
 
 ---
 
-*StrayMark v4.16.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark v4.16.1 | [Strange Days Tech](https://strangedays.tech)*

dist/.straymark/00-governance/i18n/es/C4-DIAGRAM-GUIDE.md

@@ -234,4 +234,4 @@ Usar un diagrama de Nivel 1 (Contexto) para ilustrar:
 
 ---
 
-*StrayMark v4.16.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark v4.16.1 | [Strange Days Tech](https://strangedays.tech)*

dist/.straymark/00-governance/i18n/es/CHARTER-CHAIN-EVOLUTION.md

@@ -193,4 +193,4 @@ Este documento es por sí mismo el output del flujo de aceptación que Sentinel
 
 ---
 
-*StrayMark fw-4.16.0 | [GitHub](https://github.com/StrangeDaysTech/straymark) | Issue [#156](https://github.com/StrangeDaysTech/straymark/issues/156)*
+*StrayMark fw-4.16.1 | [GitHub](https://github.com/StrangeDaysTech/straymark) | Issue [#156](https://github.com/StrangeDaysTech/straymark/issues/156)*