[issue #53] Prepare the v0.1.0 release

[Saber5656]

Summary

• add a v0.1.0 changelog grouped by Contracts, Runtime, Safety, Viewer, CLI, and Docs, with every merged pull request recorded
• add matching English and Japanese release guidance and link both README surfaces to the changelog
• document the shipped authority boundary, supported-checkout contract, and human-owned publication steps without claiming that the release is already published

Release boundary

The frontend/main agent remains limited to typed submission, redacted reads, and acknowledgement. A host-owned executor may derive a capability from an approved work order and start a bounded worker in the planned task worktree. The shipped scoped-worker executor rejects network and provider grants, while commit, push, and pull-request publication remain separate gates.

This PR does not merge itself, create or push a tag, publish a GitHub Release, announce a release, or close #17/#53. Those actions remain human-owned after merge and release-commit CI verification.

Validation

• python3 scripts/validate_all.py — 34 suites, contracts, and Python compilation passed; 83.574 seconds
• exact README offline quickstart — completed on the release candidate commit with a fake provider and final decision=complete
• clean supported linked-checkout smoke — complete; initial and final worktree status clean
• local dashboard — HTTP 200; /api/config returned JSON
• literal arbitrary clone — correctly failed closed with checkout_identity_invalid when the primary catalog was supplied
• merged PR coverage — 46/46 represented once in CHANGELOG.md
• English/Japanese command, path, API, environment-token parity — passed
• relative links and anchors — passed
• git diff --check — passed
• independent reviews — tech-docs: PASS, tech-qa: qa_pass, tech-security: security_clear (max_priority=none)
• current main CI — validate and CodeQL passed at 5818fd6390ca61ce8b7f076f27ed51db0f8cfc6c

Detailed smoke and security evidence: #53 (comment)

Tracks #53.

Summary by CodeRabbit

• Documentation
  • Added a v0.1.0 changelog covering Contracts, Runtime, Safety, Viewer, CLI, and Docs.
  • Documented operational authority boundaries, including frontend capabilities, host-owned execution, scoped-worker restrictions, approval gates, and checkout requirements.
  • Clarified that scheduling, credential provisioning, distribution, and publication activities are outside the v0.1.0 runtime scope.
  • Added release guidance to both English and Japanese README files.
  • Corrected the Japanese README’s Offline quickstart anchor link.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ff5cd489-e78d-45ee-8809-756a0796104e

📥 Commits

Reviewing files that changed from the base of the PR and between 5818fd6 and be2bf09.

📒 Files selected for processing (3)

• CHANGELOG.md
• README.ja.md
• README.md

---

📝 Walkthrough

Walkthrough

Documents the prepared v0.1.0 release contents, runtime authority boundaries, executor restrictions, publication gates, checkout requirements, excluded runtime activities, operator documentation, and a corrected Japanese README anchor.

Changes

v0.1.0 release documentation

Layer / File(s)	Summary
Release contents and operational documentation CHANGELOG.md	Adds categorized v0.1.0 entries for contracts, runtime, safety, viewer, CLI, and operator documentation.
Authority boundary and README synchronization CHANGELOG.md, README.md, README.ja.md	Documents agent and executor capabilities, publication and checkout gates, excluded runtime behavior, release-history linkage, and the corrected Japanese anchor.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• Saber5656/Saihai#59: Updates README documentation for agent and runtime authority boundaries.
• Saber5656/Saihai#91: Updates README and Japanese README boundary guidance.

Suggested labels: documentation

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR adds release docs, but #17 requires orchestrator/runtime functionality that isn't implemented here.	Implement the typed orchestrator/runtime capabilities and regression coverage required by #17, or remove the link if this PR is documentation-only.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: preparing the v0.1.0 release.
Out of Scope Changes check	✅ Passed	The changes stay focused on release-prep docs and changelog content, with no unrelated functional scope introduced.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/v0.1.0-release-readiness

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}