Skip to content

fix(acp): publish reliable turn lifecycle state - #7763

Open
jaxxon33 wants to merge 1 commit into
block:mainfrom
jaxxon33:agent/sol-lifecycle-status
Open

jaxxon33 wants to merge 1 commit into
block:mainfrom
jaxxon33:agent/sol-lifecycle-status

Conversation

@jaxxon33

Copy link
Copy Markdown

Summary

  • Clear this agent identity’s orphaned working reactions at harness startup with a bounded query and signed deletion events before subscriptions begin.
  • Add a stable typed reason to every turn_error observer payload while preserving the raw adapter code and diagnostic text.
  • Classify only narrow operator-actionable diagnostics (auth, quota, model, transient provider); adapter-specific numeric codes cannot mislabel unrelated failures.
  • Cover both changes through the production observer and signed REST bridge seams.

Related issue

None found after searching block/buzz issues and pull requests for stale ACP reactions and turn_error reasons.

Testing

  • cargo test -q -p buzz-acp: 946 passed, 1 ignored; pool_lifecycle_state: 9 passed.
  • cargo fmt --all -- --check: passed.
  • cargo clippy -p buzz-acp --all-targets -- -D warnings: passed.
  • just ci: attempted; repository-wide clippy could not start because this host lacks pkg-config and OpenSSL development headers. No code failure was reported before that environment dependency stopped the gate.

Signed-off-by: Paul <paul@x.net.au>
@jaxxon33
jaxxon33 requested a review from a team as a code owner September 20, 2026 01:44
@github-actions

Copy link
Copy Markdown

🔐 Codex Security Review

Status: review required for the current range.

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

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