buzz-acp: report startup permission outcomes and capture returned state

[p4jrj4b9nh-lab]

Buzz silently skips unsupported startup permission modes and captures session configuration before applying supported modes. For example, a bypassPermissions request can fail to match the adapter’s advertised IDs without an explicit skip result.

This patch records requested and advertised IDs with an explicit startup outcome, then captures the adapter-returned configuration after a successful mode request. Missing returned fields stay unknown; effective mode is not inferred from the requested value. Unsupported modes still cause no mutation, and transport failures remain fatal.

Related: #3710, #3715 and #5322. This does not close those broader issues. See also Codex #21975 for the separate human-fallback proposal.

Scope and security

This is a reporting fix. It does not implement a narrow-operation grant, verify the provider’s final reviewer/sandbox/rule sources, or change mode mappings. The receipt explicitly marks provider policy as unverified; applied denotes adapter RPC acceptance. Unsupported IDs are never translated into broader-access modes.

Source and validation

• Base: 44316ff72f5f7de014c66b01cbf534298a70c249 on main.
• Commit: aa387aa08e561d2413749abea0884a723a80b6ba.
• Tree: 0d5dc44dc82653b4d81a1c57d41a1b1cc24cb723.
• Exactly two files: crates/buzz-acp/README.md and crates/buzz-acp/src/pool.rs.
• Full cargo test -p buzz-acp: 924 unit and 9 integration tests passed.
• cargo fmt -p buzz-acp -- --check, cargo clippy -p buzz-acp --all-targets -- -D warnings, and diff/applicability checks passed.
• Test subprocesses omit BUZZ_ACP_LAZY_POOL and BUZZ_ACP_IDLE_POOL_SLEEP so default-config tests exercise defaults.
• Repository-wide just ci passed.
• Independent security/correctness review found no blocking issues on this exact tree. Regression tests exercise the production startup path and inspect ACP writes and captured frames. Live managed-provider validation is not claimed.

Attribution

Implementation author: Portfolio Supervisor <a14f1f84a157b4bedc2e0090a270d88fca5668111e1268663461def9df3ebdd8@agents.invalid>. This deliberately non-personal identifier derives from the verified agent identity and does not attribute implementation to a GitHub account. PB <256599840+p4jrj4b9nh-lab@users.noreply.github.com> is the submitting committer and sole DCO signatory, not the implementation author.

Rollback and deployment

The patch is uninstalled. Rollback of a later deployment is to restore the previous binary or revert this reporting change. Startup reporting changes require a fresh affected adapter session. Installing this reporting fix does not authorize retrying rejected operations.

[github-actions]

🔐 Codex Security Review

Status: review required for the current range.

The current range is 44316ff72f5f7de014c66b01cbf534298a70c249...aa387aa08e561d2413749abea0884a723a80b6ba.
A new review must complete for this exact range. When manual authorization
is required, a Block organization member must comment exactly
@buzz-security-review aa387aa08e561d2413749abea0884a723a80b6ba to authorize a new review.
Any previous review applies only to its recorded range.