Recognize the Agent Zero 3.4.2 activation contract

[TerminallyLazy]

Agent Zero 3.4.2 raises its minimum CLI to 0.15.12 for guarded DOX persistence, but the core capability allowlist did not recognize the new pair. Its real plugin preflight reported needs-plugin and could not issue a recall receipt.

Register the exact 3.4.2 / 0.15.12 / 0.15 contract without broadening descriptor trust or changing the passive binding model. A real CLI acceptance test verifies init, activation, recall receipt persistence and active status; mismatched versions/minimums and disabled plugins cannot create or reuse proof. Document paired validation as a release requirement.

Validation: all 592 workspace tests, formatting, package/ZIP validation, shell syntax, and diff checks passed. The actual upcoming plugin manifest/descriptor also passed its five live Python bridge tests against the candidate binary, including Agent Zero preflight and receipt-backed activation. Its native release workflow now repeats that pairing before uploading either architecture.

High-level PR Summary

This PR registers the Agent Zero version 3.4.2 activation contract by adding the 3.4.2 / 0.15.12 / 0.15 capability entry to the core allowlist and bumping the CLI version to 0.15.12. This pairing allows the plugin to pass preflight checks and issue recall receipts. The change includes comprehensive acceptance tests that verify initialization, activation, receipt persistence, and proper rejection of mismatched or disabled plugin versions, along with updated documentation emphasizing the importance of coordinating plugin descriptors and runtime versions before release.

⏱️ Estimated Review Time: 5-15 minutes

💡 Review Order Suggestion

Order	File Path
1	Cargo.toml
2	Cargo.lock
3	crates/tree-ring-memory-cli/src/activation/adapters.rs
4	crates/tree-ring-memory-cli/src/activation/AGENTS.md
5	crates/tree-ring-memory-cli/tests/agent_zero_342_acceptance.rs

[coderabbitai]

Warning

Review limit reached

Next included review available in 27 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: a669c2fa-4fa2-469a-aab3-78f0601e316a

📥 Commits

Reviewing files that changed from the base of the PR and between 1187969 and c3df685.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (4)

• Cargo.toml
• crates/tree-ring-memory-cli/src/activation/AGENTS.md
• crates/tree-ring-memory-cli/src/activation/adapters.rs
• crates/tree-ring-memory-cli/tests/agent_zero_342_acceptance.rs

---

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.}

[qodo-code-review]

PR Summary by Qodo

Recognize Agent Zero 3.4.2 activation contract

🐞 Bug fix 🧪 Tests 📝 Documentation ⚙️ Configuration changes 🕐 10-20 Minutes

AI Description

• Registers the exact Agent Zero 3.4.2 and CLI 0.15.12 capability contract.
• Verifies valid preflight activation and rejects mismatched, unsupported, or disabled descriptors.
• Documents paired plugin and CLI validation as a release requirement.

Diagram

sequenceDiagram
  actor AgentZero as Agent Zero
  participant CLI as Tree Ring CLI
  participant Descriptor as Plugin Descriptor
  participant Allowlist as Contract Allowlist
  participant ReceiptStore as Receipt Store
  AgentZero->>CLI: Run preflight
  CLI->>Descriptor: Read capability
  Descriptor-->>CLI: Version and status
  CLI->>Allowlist: Match exact tuple
  Allowlist-->>CLI: Accept or reject
  alt Exact enabled contract
    CLI->>ReceiptStore: Persist proof
    CLI-->>AgentZero: Active status
  else Mismatch or disabled
    CLI-->>AgentZero: Reject preflight
  end

Loading

High-Level Assessment

The exact tuple allowlist is the appropriate approach because it extends compatibility without weakening descriptor trust or changing passive binding. Semver-range acceptance or relying on a version probe would admit unvalidated plugin/runtime combinations and was correctly avoided.

Files changed (5) +253 / -4

Bug fix (1) +1 / -0

adapters.rsAllowlist the Agent Zero 3.4.2 contract +1/-0

Allowlist the Agent Zero 3.4.2 contract

• Registers Agent Zero 3.4.2 with minimum Tree Ring CLI 0.15.12 in the 0.15 minor series. Existing exact descriptor validation and passive binding behavior remain unchanged.

crates/tree-ring-memory-cli/src/activation/adapters.rs

Tests (1) +243 / -0

agent_zero_342_acceptance.rsExercise Agent Zero 3.4.2 activation end to end +243/-0

Exercise Agent Zero 3.4.2 activation end to end

• Adds Unix CLI acceptance coverage for initialization, guarded activation, real preflight, receipt persistence, and active status. Negative cases prove mismatched versions, unsupported minimums, and disabled plugins cannot create or reuse activation proof.

crates/tree-ring-memory-cli/tests/agent_zero_342_acceptance.rs

Documentation (1) +5 / -0

AGENTS.mdDocument paired Agent Zero contract validation +5/-0

Document paired Agent Zero contract validation

• Requires coordinating exact plugin and runtime contracts before release and validating activation, preflight, and receipt-backed status with the actual pair.

crates/tree-ring-memory-cli/src/activation/AGENTS.md

Other (2) +4 / -4

Cargo.lockLock workspace crates at version 0.15.12 +3/-3

Lock workspace crates at version 0.15.12

• Updates the locked versions of the CLI, core, and SQLite workspace packages from 0.15.11 to 0.15.12.

Cargo.lock

Cargo.tomlBump the workspace release to 0.15.12 +1/-1

Bump the workspace release to 0.15.12

• Sets the shared workspace package version to the minimum CLI release required by Agent Zero 3.4.2.

Cargo.toml

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. Skills advertise the previous release 🐞 Bug ≡ Correctness

Description

Cargo.toml advances the workspace to 0.15.12, but both distributed SKILL.md front matters still
declare metadata.version: "0.15.11". The repository skill and the plugin ZIP copy therefore expose
stale release metadata when consumers inspect the 0.15.12 sources or install a ZIP built from them.

Code

Cargo.toml[10]

+version = "0.15.12"

Relevance

●●● Strong

Release precedents update skill metadata alongside runtime versions; stale distributed copies expose
inconsistent package versions.

PR-#46
PR-#51

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The workspace metadata establishes 0.15.12 as the current release, while both skill copies retain
0.15.11. The Codex ZIP builder copies the plugin skill directory directly into the distributable
archive, so the stale value reaches packaged consumers.

Cargo.toml[9-11]
skills/tree-ring-memory/SKILL.md[2-7]
plugins/tree-ring-memory/skills/tree-ring-memory/SKILL.md[2-7]
plugins/tree-ring-memory/packaging/build-codex-skills-only.py[26-36]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The workspace release is now 0.15.12, but the repository and plugin copies of the Tree Ring skill still advertise metadata version 0.15.11.

## Fix Focus Areas
- skills/tree-ring-memory/SKILL.md[5-7]
- plugins/tree-ring-memory/skills/tree-ring-memory/SKILL.md[5-7]

## Recommended Fix
Change `metadata.version` to `"0.15.12"` in both skill files so repository and packaged plugin consumers receive release-consistent metadata.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Context sources

✅ Cross-repo context — repo relationships

  Explored: repo: TerminallyLazy/tree-ring-memory-agent-zero (sha: e8712174)

Review mode: ⚖️ Balanced: This changes runtime capability-contract validation and adds substantial CLI integration tests across activation, preflight, receipt persistence, and version/enablement checks, warranting a careful single-pass review.

Tip of the day

💡 Did you know, you can reply 'qodo' on any finding to push back, ask questions, or dig deeper

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-code-review]

1. Skills advertise the previous release 🐞 Bug ≡ Correctness

Cargo.toml advances the workspace to 0.15.12, but both distributed SKILL.md front matters still
declare metadata.version: "0.15.11". The repository skill and the plugin ZIP copy therefore expose
stale release metadata when consumers inspect the 0.15.12 sources or install a ZIP built from them.

Agent Prompt

## Issue description
The workspace release is now 0.15.12, but the repository and plugin copies of the Tree Ring skill still advertise metadata version 0.15.11.

## Fix Focus Areas
- skills/tree-ring-memory/SKILL.md[5-7]
- plugins/tree-ring-memory/skills/tree-ring-memory/SKILL.md[5-7]

## Recommended Fix
Change `metadata.version` to `"0.15.12"` in both skill files so repository and packaged plugin consumers receive release-consistent metadata.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools