v0.1.12 closes the builder-side proof and packaging gap.
The latest public tag now carries fresh Codex/OpenClaw attach proof, a standalone public skill packet, and a real MCP Registry packaging lane.
The public surface keeps moving in visible, tagged steps.
Start with the latest public tag, then read older releases as the trail behind it. GitHub Releases and the CHANGELOG remain the deeper evidence path; this page is the short exhibit wall text.
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 | Fresh Codex/OpenClaw attach proof, a standalone public control-room skill packet, and the MCP Registry packaging lane with a real MCPB artifact path. | 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 | GitHub release |
| 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 | GitHub release |
| 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 | GitHub release |
| 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 | GitHub release |
| 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 | GitHub release |
| v0.1.6 | Switchyard-backed AI Diagnose, deterministic fallback preservation, and tighter builder-proof wording for named hosts. | Release notes | GitHub release |
| 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 | GitHub release |
| v0.1.4 | Roadmap visibility, stale-link cleanup, and a clearer "what next?" path for visitors. | Release notes | GitHub release |
| 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. At the current baseline, main and the latest public tag point at the same hard-cut release commit. Future commits may move ahead again, so keep treating CHANGELOG Unreleased as the moving main-branch preview after the next tag is cut.
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
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.