docs(changelog): add 0.9.14 release notes

[flora131]

Summary

Prepares the release notes for 0.9.14. Changelog-only; no code, manifest, lockfile, or Cargo changes.

Each package gains a dated ## [0.9.14] - 2026-08-19 section under [Unreleased], summarizing the cumulative prereleases. Per-change detail stays in the existing prerelease sections, which are untouched.

Package	Prereleases covered
coding-agent	alpha.1 – alpha.5
workflows	alpha.1 – alpha.6
subagents	alpha.2 – alpha.5
web-access	alpha.3 – alpha.4
mcp	alpha.3

intercom and natives had empty [Unreleased] sections and were left alone.

Release-base invariants

• Diff is purely additive: 182 insertions, 0 deletions, across 5 CHANGELOG.md files only.
• No already-released version section was modified.
• Every shipped package manifest, package-lock.json workspace entry, Cargo workspace version, and generated natives version check remains at the 0.0.0 placeholder.
• scripts/cut-release.ts stamps the real version on the detached Release 0.9.14 commit after this PR merges. Pushing that tag starts publish.yml; no publication is dispatched from here.

Validation

• Changelog-only working tree vs origin/main at 9426abc99827eb3a065df6d4e63c42f0ee8762c0.
• bun run check passed (biome, tsc --noEmit, coding-agent tsgo build typecheck, shrinkwrap check).
• bun run test:unit passed: 6756 passed, 2 skipped, 0 failed.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

Greptile Summary

This change publishes cumulative 0.9.14 release notes for the coding-agent, MCP, subagents, web-access, and workflows packages. The subagents release preamble was verified to claim an alpha.2-through-alpha.5 sequence while no alpha.4 release section exists. The new released sections also leave Unreleased empty rather than following the repository-required changelog workflow.

Confidence Score: 4/5

Not ready to merge until the changelog workflow requirement and inaccurate subagents prerelease range are corrected.

There are two independent P2, non-security findings. The prerelease-history mismatch was confirmed by an executed range check; the other finding enforces an explicit repository rule.

Files Needing Attention: packages/subagents/CHANGELOG.md needs its cumulative prerelease statement corrected or an alpha.4 section added. All five changed changelogs need to follow the required Unreleased-first workflow.

T-Rex Logs

What T-Rex did

• T-Rex ran the narrow changelog alpha-range validation script to explore the P2 finding.
• T-Rex reviewed the Raw 0.9.14-alpha heading enumeration log to verify how headings were counted during the check.
• T-Rex observed an inclusive alpha-range validation failure, confirming the failure condition noted in the finding.

_{Ran code and verified through T-Rex}

Prompt To Fix All With AI

### Issue 1
packages/coding-agent/CHANGELOG.md:5
**Released sections bypass Unreleased**

These newly authored notes are placed directly in released `0.9.14` sections while leaving `Unreleased` empty, bypassing the repository's required changelog workflow across all five changed files.

### Issue 2
packages/subagents/CHANGELOG.md:7
**Cumulative prerelease range includes a missing alpha**

The cumulative-release preamble says this package covers every prerelease from `0.9.14-alpha.2` through `0.9.14-alpha.5`, but the release history contains only alpha.2, alpha.3, and alpha.5. Add an alpha.4 section if it was released, or enumerate the actual prereleases so the published history is accurate.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "docs(changelog): add 0.9.14 release note..." | Re-trigger Greptile}

Greptile also left 2 inline comments on this PR.

Context used:

• Context used - CLAUDE.md (source)

[greptile-apps]

Released sections bypass Unreleased

These newly authored notes are placed directly in released 0.9.14 sections while leaving Unreleased empty, bypassing the repository's required changelog workflow across all five changed files.

Context Used: CLAUDE.md (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: packages/coding-agent/CHANGELOG.md
Line: 5

Comment:
**Released sections bypass Unreleased**

These newly authored notes are placed directly in released `0.9.14` sections while leaving `Unreleased` empty, bypassing the repository's required changelog workflow across all five changed files.

**Context Used:** CLAUDE.md ([source](https://github.com/bastani-inc/atomic/blob/main/CLAUDE.md))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Cumulative prerelease range includes a missing alpha

The cumulative-release preamble says this package covers every prerelease from 0.9.14-alpha.2 through 0.9.14-alpha.5, but the release history contains only alpha.2, alpha.3, and alpha.5. Add an alpha.4 section if it was released, or enumerate the actual prereleases so the published history is accurate.

Artifacts

Narrow changelog alpha-range validation script

• This Python script parses the stated 0.9.14 alpha range and checks every expected heading, providing the executable validation method.

Raw 0.9.14-alpha heading enumeration

• This executed grep capture lists alpha.5, alpha.3, and alpha.2 headings and shows that alpha.4 is absent.

Inclusive alpha-range validation failure

• This executed validation output reports alpha.4 as the missing member of the stated alpha.2-through-alpha.5 range, confirming the claim.

_{Ran code and verified through T-Rex}

Prompt To Fix With AI

This is a comment left during a code review.
Path: packages/subagents/CHANGELOG.md
Line: 7

Comment:
**Cumulative prerelease range includes a missing alpha**

The cumulative-release preamble says this package covers every prerelease from `0.9.14-alpha.2` through `0.9.14-alpha.5`, but the release history contains only alpha.2, alpha.3, and alpha.5. Add an alpha.4 section if it was released, or enumerate the actual prereleases so the published history is accurate.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.