v0.1.0 Release Candidate

[flyingrobots]

Migrated from Method backlog

This issue was created from a legacy filesystem backlog card. GitHub Issues are now the live work tracker; repository docs remain Method evidence.

Source backlog: docs/method/backlog/v0.1.0/RELEASE_v0.1.0-release-candidate.md
Original lane: v0.1.0
Original legend: RELEASE

Original backlog card

v0.1.0 Release Candidate

Status: terminal v0.1.0 release blocker.

Depends on:

• v0.1.0 replay and DIND proof
• Release-grade quickstart
• Authority boundary audit
• Versioned contract and API compatibility
• jedit real Echo release gate

Why now

This card closes the release lane after the implementation, proof, docs, and
authority checks are merged. It should not be pulled until the remaining
v0.1.0/ cards are complete or explicitly removed from the release bar.

Release candidate criteria

A v0.1.0 release candidate exists when:

• all Required Feature Clusters have merged tests;
• the jedit-on-Echo release gate passes on clean Echo and jedit checkouts;
• the quickstart is executable from scratch;
• the authority-boundary audit is green;
• the replay/DIND proof is green;
• package/version metadata is stable;
• no P1 backlog item targets the v0.1.0 feature bar.

Acceptance criteria

• The release plan is up to date and links every blocking card.
• The release lane is empty, closed, or contains only explicitly deferred
  post-release cards.
• CI and local release witnesses pass.
• CHANGELOG and release notes describe the supported contract-host surface.
• Version tags and package publish steps are documented before execution.

Non-goals

• Do not expand the release bar during release-candidate work.
• Do not merge release work with unrelated implementation slices.
• Do not publish without explicit user approval.

[coderabbitai]

🔗 Related PRs

#329 - Stack Witness 0001 fixture-backed jedit walking skeleton [merged]
#369 - docs: add Echo v0.1.0 release plan [merged]
#380 - feat(core): expose retained evidence posture on readings [merged]
#385 - docs(backlog): two follow-ups from the 2026-05-30 merge session [merged]
#388 - docs(method): add backlog cards and hook failure note [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!