Skip to content

Add Tree Ring v0.13 multi-agent guidance - #1

Merged
TerminallyLazy merged 3 commits into
mainfrom
codex/v0.13-multi-agent-guidance
Jul 23, 2026
Merged

Add Tree Ring v0.13 multi-agent guidance#1
TerminallyLazy merged 3 commits into
mainfrom
codex/v0.13-multi-agent-guidance

Conversation

@TerminallyLazy

@TerminallyLazy TerminallyLazy commented Jul 23, 2026

Copy link
Copy Markdown
Owner

Summary

  • bump the Claude plugin wrapper from 0.1.0 to 0.2.0
  • add Tree Ring v0.13 same-host identity, idempotency, fan-in, coordinator-policy, capability-handling, and schema-v3 upgrade guidance
  • make /tree-ring-capture safe for ordinary workers in Coordinated mode
  • add workflow/session/scope-aware coordinator fan-in recall
  • make audit defaults genuinely non-mutating on an upgraded store and reserve pre-upgrade inspection for policy status/policy audit
  • remove the unsupported tree-ring forget --mode supersede example and point to the TUI lifecycle action
  • replace shape-only CI checks with contract validation plus a checksum-pinned v0.13 runtime smoke

Why

The bundled fallback guidance predated Tree Ring v0.13. It hardcoded project-scoped capture, which ordinary workers are denied in Coordinated mode, described FTS repair as non-destructive, and documented a CLI forget mode that does not exist. It also omitted the v0.13 mixed-version/schema-v3 fence and capability isolation rules.

Supported boundary

The shared-root guidance is explicitly limited to cooperative Tree Ring processes on one host using a local filesystem. Identity and scope are routing fields, not read ACLs. This does not claim cross-host, network-filesystem, or adversarial host safety.

Validation

  • python3 scripts/validate.py
  • python3 -m py_compile scripts/validate.py
  • claude plugin validate . with Claude Code 2.1.154
  • JSON and YAML parsing
  • Bash syntax and git diff --check
  • checksum-pinned public Tree Ring v0.13.0 Linux archive and exact version check in CI
  • reusable Coordinated-mode smoke: worker write allowed, shared write denied, exact retry idempotent, conflict rejected, filtered fan-in recalled the worker record, coordinator publication succeeded, and plaintext capability was absent from store/status/audit
  • missing-root and schema-v2 policy preflight left store bytes and sidecars untouched
  • audit, consolidation dry-run, report-only maintenance, and policy inspection left an upgraded schema-v3 store byte-identical

@gemini-code-assist

Copy link
Copy Markdown

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@TerminallyLazy, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 49 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 12a75bda-4348-4f81-8518-830e09aeedc6

📥 Commits

Reviewing files that changed from the base of the PR and between ce5d995 and a216d87.

📒 Files selected for processing (3)
  • .github/workflows/validate.yml
  • scripts/smoke_v013.sh
  • scripts/validate.py
📝 Walkthrough

Walkthrough

The plugin version was updated to 0.2.0. CI now runs a Python validator covering manifests and safety guidance. Documentation adds Tree Ring Memory v0.13 coordinated-mode requirements, identity and retry conventions, lifecycle policies, shared-root limits, and coordinator-token handling.

Changes

Coordinated mode guidance

Layer / File(s) Summary
Wrapper version and centralized validation
.claude-plugin/*, scripts/validate.py, .github/workflows/validate.yml, .gitignore
Manifests declare version 0.2.0, CI runs scripts/validate.py, and the validator checks metadata plus required guidance and security markers.
Coordinated skill and command guidance
skills/tree-ring-memory/SKILL.md, commands/tree-ring-capture.md, commands/tree-ring-audit.md
Documentation adds v0.13 prerequisites, coordinated identity and retry conventions, coordinator capability requirements, lifecycle restrictions, and token-handling rules.
Recall and security boundary documentation
commands/tree-ring-recall.md, README.md, SECURITY.md
Recall guidance expands local policy retrieval and fan-out/fan-in filtering; project documentation defines shared-root, routing, version, and coordinator-token boundaries.

Estimated code review effort: 3 (Moderate) | ~20 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: adding Tree Ring v0.13 multi-agent guidance.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/v0.13-multi-agent-guidance

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

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/validate.yml:
- Around line 15-16: Add a pinned Tree Ring 0.13.0 setup to the validation
workflow near the existing “Validate plugin guidance” step, then invoke fixtures
or scripts that exercise CLI behavior, smoke-test integration, and inspect
upgraded stores without mutating them. Keep the existing scripts/validate.py
documentation checks, and ensure the new CI steps install and run the required
Tree Ring 0.13.0 test coverage.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: a8685ae6-e644-4a46-9fc7-587a310411dd

📥 Commits

Reviewing files that changed from the base of the PR and between c670579 and ce5d995.

📒 Files selected for processing (11)
  • .claude-plugin/marketplace.json
  • .claude-plugin/plugin.json
  • .github/workflows/validate.yml
  • .gitignore
  • README.md
  • SECURITY.md
  • commands/tree-ring-audit.md
  • commands/tree-ring-capture.md
  • commands/tree-ring-recall.md
  • scripts/validate.py
  • skills/tree-ring-memory/SKILL.md

Comment thread .github/workflows/validate.yml
@TerminallyLazy
TerminallyLazy merged commit e13d55a into main Jul 23, 2026
2 checks passed
@TerminallyLazy
TerminallyLazy deleted the codex/v0.13-multi-agent-guidance branch July 23, 2026 22:01
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