Release v0.3.0

[schiste]

Summary

• Cut a ## [0.3.0] - 2026-05-17 section from the [Unreleased] block in apps/chau7-macos/docs/CHANGELOG.md.
• Restore the missing apps/chau7-macos/Scripts/extract-changelog helper that .github/workflows/release.yml calls to populate the release body from CHANGELOG.md.

Version rationale

Last tagged release is v0.2.1. Minor bump (0.3.0) reflects substantial new feature surface in the Unreleased block:

• Grapheme-cluster-aware Rust→Swift terminal FFI (ZWJ emoji, regional flags, NFD sequences preserved end-to-end; CHG1 → CHG2 wire format).
• Per-repository proxy prompt injection (~/.chau7/prompt-rules.json, all four upstream providers).
• MCP observer contract: snapshot, subscription feed, replay bounds, heartbeat.
• Spanish (es) locale.
• Adaptive render-loop throttling + tier-based graphics memory release.
• Plus a long list of Metal / restore / scrollback / Codex fixes (see CHANGELOG).

Cutting the release after merge

Tag pushes are blocked from this environment (HTTP 403 at the git proxy), and the GitHub MCP surface here does not expose release/tag creation. To trigger the release workflow once this is merged, either:

git tag -a v0.3.0 -m "v0.3.0 — Grapheme-Aware Terminal, Per-Repo Prompt Injection & MCP Observability"
git push origin v0.3.0

…or use Releases → Draft a new release in the GitHub UI, target the merge commit, choose new tag v0.3.0, and click Publish (the workflow listens on push: tags: 'v*').

Test plan

• Local dry-run of Scripts/extract-changelog 0.3.0 returns the new section body (264 lines).
• On tag push, release.yml builds the DMG/ZIP/PKG, generates SLSA attestations, creates the release with extracted notes, and updates the Homebrew tap.

https://claude.ai/code/session_01He4PWyYCfPyeeMAosKDV6P

---

Generated by Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7454014660

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Avoid duplicating the 0.3.0 release section

This adds a second ## [0.3.0] entry even though the same changelog already contains ## [0.3.0] - 2026-01-19 later in the file, after documented 0.4.0 and 0.5.0 sections. Any changelog anchor or release-note tooling that resolves by version now has ambiguous 0.3.0 content, and cutting a new v0.3.0 here would make the version history move backwards relative to the existing entries; this release section should use the next unreleased version or the older duplicate should be reconciled.

Useful? React with 👍 / 👎.