v0.1.12 tightens the integration lane without changing the operator-first story.
The latest public tag now packages the named-host attach proof, the public skills packet, and the MCPB delivery lane as a second shelf around the same control room.
The public surface keeps moving in visible, tagged steps.
Start with the latest public tag, then read older release notes as the trail behind it. GitHub Releases now keeps only the latest public release object, while this page and the CHANGELOG preserve the older tagged story.
v0.1.11 made the side rooms feel like one exhibition.
That release tightened Proof, Security, Support, Community, and Troubleshooting into one cleaner public rhythm.
v0.1.10 made the front door feel intentionally designed.
That release concentrated the second-pass curation polish across Home, Proof, For Agents, Releases, and Quickstart.
Start with the latest tag
| Version | What it focused on | Links |
|---|---|---|
| v0.1.12 | Named-host attach proof, a standalone public control-room skill packet, and the MCPB delivery lane, all tightened without changing the operator-first product identity. | Release notes | GitHub release |
| v0.1.11 | Release-truth closure plus side-room routing polish across Proof, Security, Support, Community, and Troubleshooting so the whole docs site reads like one exhibited public surface. | Release notes |
| v0.1.10 | Second-pass curation polish across Home, Proof, For Agents, Releases, and Quickstart, turning the exhibit-like public storytelling into tagged truth. | Release notes |
| v0.1.9 | Proof page, sharper control-room-first front door, release-truth sync, and helper extraction for AI/Web/status internals without expanding the public contract. | Release notes |
| v0.1.8 | Canonical public-repo hard cut for `xiaojiou176-open/apple-notes-snapshot`, keeping the control-room, AI Diagnose, Local Web API, MCP, and governance surfaces aligned on the rebuilt public baseline. | Release notes |
| v0.1.7 | Codex and Claude Code starter packs, a tracked public-skills pack, and a cleaner split between GitHub-controlled and external-only launch work. | Release notes |
| v0.1.6 | Switchyard-backed AI Diagnose, deterministic fallback preservation, and tighter builder-proof wording for named hosts. | Release notes |
| v0.1.5 | Examples, troubleshooting, and a smoother first-successful-run path for new visitors. This tag predates AI Diagnose, Local Web API, and MCP public entry pages on main. | Release notes |
| v0.1.4 | Roadmap visibility, stale-link cleanup, and a clearer "what next?" path for visitors. | Release notes |
| v0.1.3 | Support routing, issue-triage tightening, and a dedicated public support surface. | Release notes |
| v0.1.2 | Community hub, release-history navigation, and changelog-backed public maintenance story. | Release notes |
| v0.1.1 | Discovery hardening, `security.txt`, and a start-here community entry point. | Release notes |
| v0.1.0 | Initial public launch surface: README overhaul, docs site, assets, release, and discussions. | Release notes |
Keep the layers separate
The latest public tag is currently v0.1.12. GitHub Releases now keeps only that current public tag, while this page keeps the older tag notes. At the current baseline, the latest public tag and current main can move at different speeds. Keep treating CHANGELOG Unreleased as the moving main-branch preview after the next tag is cut, and do not collapse local branch freshness into tagged release truth.
Read the latest tag as the stable public exhibit. Read current main as the workshop next door. When you need evidence behind a release claim, jump to Proof instead of turning the release table into a substitute for verification.
Where the official history lives
- GitHub releases for the current latest public object only
- CHANGELOG.md
- CHANGELOG Unreleased
- Announcements discussions
If you are preparing a public update from current main
- Proof for the repo-side gates, GitHub-controlled evidence, and live-boundary summary
- Share kit for the punchline, demo clip, and compare card
- 30-second overview for the shortest accurate summary
- External launch prep for the repo-ready checklist versus manual-only actions
- Codex starter pack, Claude Code starter pack, and Public skills pack for the builder-side tagged truth
- Community for the announcements lane and discussion routing
- Support so release notes and announcements can still point people to the right help surface
Treat this as a repo-side preparation stack. It does not mean Search Console, domain changes, video uploads, or platform distribution are already complete.