Hive #40: apply revisioned company-agent responder policy

[100yenadmin]

Closes #40

Outcome

Adds the thin company-agent responder-policy adapter on top of native Buzz Agents and buzz-acp behavior.

• Owner/admin-only action on registered Company VM agent cards selects existing native non-DM rooms and active company humans.
• Tauri sends only the registered agent instance UUID, optimistic revision, native room IDs, and opaque company membership IDs to dashboard Allow owners to read agent memories block/buzz#727. Tenant, public keys, and VM scope remain server-resolved.
• buzz-acp optionally pulls and acknowledges payload-bound NIP-98 policy with the exact agent key.
• Managed mode fails closed before first pull and after 15 seconds without a valid refresh.
• The VM gate requires exact allowed author, exact selected non-DM room, current native agent membership, and existing static subscription rules.
• Policy changes drain queued work; in-flight turns may finish. Hermes-owned model, memory, tools, provider, credentials, profile, and private identity are untouched.
• No endpoint configured preserves native/static buzz-acp behavior.

Focused proof

• buzz-acp unit tests: 622 passed.
• Desktop unit tests: 3,573 passed.
• Managed Tauri company-policy tests: 7 passed.
• TypeScript typecheck, Biome changed-file check, Rust format, and desktop file-size gate passed.
• Strict local clippy exposed two unchanged queue.rs question-mark lints under the locally newer toolchain. With only those pre-existing lints allowed, all changed buzz-acp targets pass warnings-as-errors.

Proof boundary

Source and local test proof only. This does not deploy dashboard block#727, configure a VM policy endpoint, install the updated buzz-acp, prove runtime revocation, merge, release, or authorize customer rollout. The installed allowed/denied-author and non-member-room canary remains a separate gate.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 2 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 0f38169d-88d7-4ba4-920a-1cc4fe5d906b

📥 Commits

Reviewing files that changed from the base of the PR and between a58809e and e56b859.

⛔ Files ignored due to path filters (2)

• Cargo.lock is excluded by !**/*.lock
• desktop/src-tauri/Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (20)

• crates/buzz-acp/README.md
• crates/buzz-acp/src/config.rs
• crates/buzz-acp/src/lib.rs
• crates/buzz-acp/src/relay.rs
• crates/buzz-acp/src/responder_policy.rs
• desktop/src-tauri/src/evaos_teams.rs
• desktop/src-tauri/src/evaos_teams/company_agent_policy.rs
• desktop/src-tauri/src/evaos_teams/company_directory.rs
• desktop/src-tauri/src/evaos_teams/tests.rs
• desktop/src-tauri/src/lib.rs
• desktop/src/features/agents/AGENTS.md
• desktop/src/features/agents/lib/companyAgentCatalog.test.mjs
• desktop/src/features/agents/lib/companyAgentCatalog.ts
• desktop/src/features/agents/lib/companyAgentResponderPolicy.test.mjs
• desktop/src/features/agents/lib/companyAgentResponderPolicy.ts
• desktop/src/features/agents/ui/AgentsView.tsx
• desktop/src/features/agents/ui/CompanyAgentResponderPolicyDialog.tsx
• desktop/src/features/agents/ui/UnifiedAgentsSection.tsx
• desktop/src/features/evaosTeams/api.ts
• desktop/src/features/evaosTeams/hooks.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/40-company-agent-responder-policy

---

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

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​nostr@​0.44.4 ⏵ 0.44.5

View full report

[100yenadmin]

Hive #40 stable source-gate evidence

• Exact head: e56b859
• Focused proof: buzz-acp library 624/624; managed Tauri policy 3/3; non-managed Tauri check passed; exact Rust 1.95 formatting passed; clippy passed with only the two recorded pre-existing question-mark lints allowed; cargo-deny passed.
• Canonical CI: success on attempt 2: https://github.com/electricsheephq/evaOS-Hive/actions/runs/30288942786
• Docker workflow: success: https://github.com/electricsheephq/evaOS-Hive/actions/runs/30288943219
• Independent exact-head delta review: PASS, no P0/P1/P2 findings.

Terminal dispositions:

• Monotonic policy watermark loss: fixed.
• Final invocation gate missing current native membership: fixed.
• Join-before-later-policy-selection required restart: fixed.
• Managed-only import broke ordinary Tauri builds: fixed.
• RUSTSEC-2026-0216: fixed with lock-only nostr 0.44.5 update.
• First-attempt virtualization smoke failure in unchanged upstream message-list code: CI flake; no code change. Same exact-head shard passed on attempt 2.
• Existing cargo-deny warnings and newer-toolchain queue question-mark lints: accepted existing/out-of-scope; configured canonical gates pass.

Proof boundary: source, exact-head CI, and semantic review only. No merge, deploy, release, VM mutation, live policy pull/ACK, installed canary, or customer claim.