Skip to content

R1: prepare v0.2.0 public release readiness#150

Merged
samrusani merged 1 commit intomainfrom
codex/release-r1-v0-2-0-readiness
Apr 14, 2026
Merged

R1: prepare v0.2.0 public release readiness#150
samrusani merged 1 commit intomainfrom
codex/release-r1-v0-2-0-readiness

Conversation

@samrusani
Copy link
Copy Markdown
Owner

Summary

  • package the shipped Alice surface through Phase 11 and Bridge B1 through B4 into a credible pre-1.0 v0.2.0 release boundary
  • add the v0.2.0 release checklist, tag plan, and public release runbook
  • align README, release-facing docs, policy docs, and sprint-owned smoke harnesses with the actual shipped baseline

Release Boundary

  • version target: v0.2.0
  • release framing: pre-1.0
  • shipped baseline covered: Phases 9 through 11 plus Bridge B1 through B4
  • explicitly out of scope: new features, reopened Phase 11 work, reopened bridge implementation work, and any 1.0 stability/support claims

Verification

  • python3 scripts/check_control_doc_truth.py
  • ./.venv/bin/python -m pytest tests/unit tests/integration -q
  • pnpm --dir apps/web test
  • ./.venv/bin/python scripts/run_hermes_memory_provider_smoke.py
  • ./.venv/bin/python scripts/run_hermes_mcp_smoke.py
  • ./.venv/bin/python scripts/run_hermes_bridge_demo.py

Upgrade Overview

Protected Areas

  • continuity APIs
  • memory schema
  • trust rules
  • evidence pipeline

Compatibility Impact

This is a release-readiness packaging sprint. It does not widen the shipped product surface; it documents the actual shipped baseline and prepares the repo, checklists, and runbooks for a pre-1.0 public release.

Migration / Rollout

Merge this sprint to main first, then execute docs/release/v0.2.0-tag-plan.md from main to create the v0.2.0 tag in the documented order. No feature migration is introduced beyond release doc and evidence alignment.

Operator Action

Use the new release checklist and runbook as the public release gate, follow the documented provider_plus_mcp recommended path and mcp_only fallback where referenced, and use the documented smoke/demo commands as the final release verification set.

Validation

Branch-local verification passed:

  • python3 scripts/check_control_doc_truth.py -> PASS
  • ./.venv/bin/python -m pytest tests/unit tests/integration -q -> 1191 passed in 206.68s (0:03:26)
  • pnpm --dir apps/web test -> 62 files passed, 199 tests passed
  • ./.venv/bin/python scripts/run_hermes_memory_provider_smoke.py -> PASS
  • ./.venv/bin/python scripts/run_hermes_mcp_smoke.py -> PASS
  • ./.venv/bin/python scripts/run_hermes_bridge_demo.py -> PASS

Rollback

Revert the squash merge commit to restore the pre-R1 release docs and smoke harness state, then rerun the release verification set before attempting the tag procedure again.

@samrusani samrusani merged commit 988761c into main Apr 14, 2026
4 checks passed
@samrusani samrusani deleted the codex/release-r1-v0-2-0-readiness branch April 14, 2026 10:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant