Release Tree Ring 0.14.0 harness activation - #45
Conversation
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (33)
📝 WalkthroughWalkthroughThis change adds project-local harness activation with manifests, receipts, preflight, launch, status, deactivation, and certification flows. It updates CLI and TUI integration handling, adds fixtures and acceptance tests, documents the protocol, and adds tagged release packaging and GitHub release publication checks. ChangesHarness activation
Release automation
Estimated code review effort: 5 (Critical) | ~120 minutes Sequence Diagram(s)sequenceDiagram
participant User
participant CLI
participant SQLiteStore
participant ReceiptStore
User->>CLI: run integrations preflight
CLI->>SQLiteStore: bounded recall for session identity
SQLiteStore-->>CLI: filtered recall results
CLI->>ReceiptStore: persist activation receipt
ReceiptStore-->>CLI: receipt metadata
CLI-->>User: rendered context and activation state
sequenceDiagram
participant Tag
participant ReleaseWorkflow
participant PackageScript
participant GitHubRelease
Tag->>ReleaseWorkflow: trigger tagged release
ReleaseWorkflow->>PackageScript: build with TREE_RING_RELEASE_TAG
PackageScript-->>ReleaseWorkflow: verified archives and checksums
ReleaseWorkflow->>GitHubRelease: create or update release with assets
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
What changed
Adds project-local harness activation for Codex, Claude Code, Pi, and Agent Zero; receipt-backed activation certification; safe multi-agent bridge handling; and tag-gated release asset publication.
Validation
Release follow-up
After CI passes, merge this PR, create immutable tag
v0.14.0, and let the Release Artifacts workflow publish the verified archives and checksums.Summary by CodeRabbit
New Features
Release Improvements
Documentation