chore: bump Framework 4.30.0 / CLI 3.29.0 / Core 0.9.0 (#300)

Combined release for the adopter-feedback consolidation already merged to main:
#215 (four validator gaps), #207 + #208 (charter drift/audit friction).

- core 0.8.0 → 0.9.0 (Charter execution_ailogs/context_spec fields, FileExemption)
- cli 3.28.2 → 3.29.0 (validator + audit-warning + status changes)
- framework 4.29.0 → 4.30.0 (schema, templates, skills, docs)
- straymark-core dependency bound moved to 0.9.0 in cli/ AND experiment-loom/
  atomically (release lesson from #282)
- CHANGELOG, governance footers (EN/es/zh-CN), and versioning tables updated

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

Author: montfort

CHANGELOG.md

@@ -7,6 +7,59 @@ and this project uses [independent versioning](README.md#versioning) for Framewo
 
 ---
 
+## Framework 4.30.0 / CLI 3.29.0 / Core 0.9.0 — 2026-06-20
+
+Adopter-feedback consolidation: four validator gaps from a 150-doc housekeeping
+pass (#215) plus two Charter-workflow friction fixes (#207, #208), reported by
+the Sentinel and lnxdrive adopters.
+
+### Added (CLI)
+
+- **META-003 now suggests the nearest canonical status** (#215 Gap 4). Invalid
+  `status:` values get a `Did you mean '<x>'?` hint via a semantic alias map
+  (`done`/`completed`/`closed` → `accepted`, …) with a Levenshtein fallback for
+  typos.
+- **`charter audit --prepare` warns on multi-batch under-coverage** (#208). When
+  the Charter (or its referenced AILOGs) has completed batches in the Batch
+  Ledger and no explicit `--range` was given, the CLI warns that the default
+  `origin/main..HEAD` excludes already-merged phases and recommends an explicit
+  range — turning a silent under-coverage into a visible one.
+
+### Changed (CLI)
+
+- **OBS-001 vocabulary widened** (#215 Gap 1). The observability content check is
+  now case-insensitive over a broad term set (`otel`, `metric`/`métrica`, `span`,
+  `trace`, `dashboard`, `collector`, `alert`, `slog`, `histogram`, `telemetr`, …),
+  eliminating the false positives the narrow literal set produced.
+- **`charter status` no longer advertises shipped commands as unavailable**
+  (#207). Removed the stale "Phase 2 features (not yet available)" block that
+  listed `charter drift` / `charter close` as `planned cli-3.7.0`.
+
+### Added (Core)
+
+- **Charter `execution_ailogs` + `context_spec` fields** (#215 Gap 2) — bless the
+  documented close-time AILOG aggregation and area-context spec for dual-origin
+  Charters, keeping `originating_ailogs`/`originating_spec` mutually exclusive.
+  Wired into the architecture `implemented` overlay and the knowledge-graph edges;
+  `CHARTER-AILOG-REF`/`CHARTER-SPEC-REF` cover the new fields.
+- **`CHARTER-FILES-EXIST` exemption markers** (#215 Gap 3) — `(external)`,
+  `(removed)`, `(relocated: <path>)` alongside `(new)`, so a closed Charter's
+  historical table can carry cross-repo / relocated / removed paths. Unmarked
+  missing paths (e.g. unsubstituted placeholders) are still flagged.
+
+### Changed (Framework)
+
+- **Charter schema** gains `execution_ailogs` + `context_spec` (mutual-exclusion
+  unchanged); **charter + AILOG templates** (EN/es/zh-CN) document the new fields,
+  the `status:` lifecycle vocabulary inline, and the `charter drift --range`
+  syntax (dropping stale "Phase 2" language).
+- **Skills**: `straymark-charter-new` documents the dual-origin fields;
+  `straymark-audit-prompt` documents the multi-batch `--range` pitfall.
+- **Docs**: CLI-REFERENCE (EN/es/zh-CN) documents the `charter audit --range`
+  multi-batch pitfall.
+
+---
+
 ## Framework 4.29.0 — 2026-06-20
 
 Agent-native skills for the architecture model and the Loom lifecycle (#281) —

Cargo.lock

@@ -277,8 +277,8 @@ StrayMark uses independent version tags for each component:
 
 | Component | Tag prefix | Example | Includes |
 | --- | --- | --- | --- |
-| Framework | `fw-` | `fw-4.29.0` | Templates (12 types), governance, directives, Charter template + schema |
-| CLI | `cli-` | `cli-3.28.2` | The `straymark` binary |
+| Framework | `fw-` | `fw-4.30.0` | Templates (12 types), governance, directives, Charter template + schema |
+| CLI | `cli-` | `cli-3.29.0` | The `straymark` binary |
 | Loom (EXPERIMENTAL) | `loom-` | `loom-0.4.2` | The `straymark-loom` visualization server, downloaded on demand by `straymark loom serve` |
 
 Check installed versions with `straymark status` or `straymark about`.

README.md

@@ -1,6 +1,6 @@
 [package]
 name = "straymark-cli"
-version = "3.28.2"
+version = "3.29.0"
 edition = "2021"
 description = "CLI for StrayMark — the cognitive discipline your AI-assisted projects need"
 license = "MIT"
@@ -25,7 +25,7 @@ path = "src/bin/gen_codex_skills.rs"
 required-features = ["dev-tools"]
 
 [dependencies]
-straymark-core = { version = "0.8.0", path = "../core" }
+straymark-core = { version = "0.9.0", path = "../core" }
 clap = { version = "4", features = ["derive"] }
 reqwest = { version = "0.12", features = ["blocking", "rustls-tls", "json"] }
 serde = { version = "1", features = ["derive"] }

cli/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "straymark-core"
-version = "0.8.0"
+version = "0.9.0"
 edition = "2021"
 description = "Shared document model and knowledge graph for StrayMark — parses governance documents and builds their typed traceability graph"
 license = "MIT"

core/Cargo.toml

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

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

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

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

@@ -319,4 +319,4 @@ See also [ADR-2025-01-20-001] for architectural context.
 
 ---
 
-*StrayMark fw-4.29.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark fw-4.30.0 | [Strange Days Tech](https://strangedays.tech)*

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

@@ -314,4 +314,4 @@ Contributed via [issue #111](https://github.com/StrangeDaysTech/straymark/issues
 
 ---
 
-*StrayMark fw-4.29.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark fw-4.30.0 | [Strange Days Tech](https://strangedays.tech)*

dist/.straymark/00-governance/FOLLOW-UPS-BACKLOG-PATTERN.md

@@ -262,4 +262,4 @@ Mark `review_required: true` when:
 
 ---
 
-*StrayMark fw-4.29.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark fw-4.30.0 | [Strange Days Tech](https://strangedays.tech)*