Skip to content

[avenger] Fix missing work-queue projection diagnostic guidance #71036

Closed as not planned

Description

@github-actions

Tip

Your pull request is ready to create! 🎉 ✅

Everything is OK—the changes have been pushed to a branch. Please review the protected files, then create the pull request when you are ready.

Create the pull request

The original pull request description is below.


Failure and fix

The first failed job in CI run 39721692927, Validate workflow container pins, failed make test-guidance: four assertions reported missing evidence/remedy coverage for projection_unavailable, projection_receipt_pending, and projection_write_ambiguous.

Document these codes in .github/aw/debug-playbook.md, including native acknowledgements, Issue/summary receipts, reconciliation before retry, and preservation of uncertain locks. Condense adjacent guidance to retain the enforced 2,800-word budget (2,797 words). No runtime code or protected workflow files changed.

Validation

  • make test-guidance: all 24 tests pass on the final change.
  • make agent-report-progress: passed for this documentation-only change; CLI build and schema freshness passed, and impacted Go tests were skipped because no Go files changed.
  • git diff --check: passed; exactly one file committed; worktree clean.
  • make fmt and make lint were not run: the failing signal and change are documentation-only. No full unit-suite pass is claimed.

Limits and steering

git fetch origin main failed certificate verification, so the requested latest-main merge could not be completed. No certificate checks were bypassed. The fix is based on the provided checkout at 6fdf20f.

Other failed jobs listed in the run (CLI Completion & Other integration, Workflow Actions & Containers integration, and workflow markdown/lock drift) remain outside this first-failure repair; this PR does not claim the entire CI run is repaired.

Steering issue #71034 had no comments when checked. The unavailable report_progress tool was reported; publication uses the configured safe-output PR transport instead.


Note

Protected files

This patch modifies protected files, which may affect project dependencies, CI/CD pipelines, or agent behaviour.

Protected files

To route changes like this to a review issue instead of blocking, configure protected-files: fallback-to-issue in your workflow configuration.

Generated by 🦸 Avenger · copilot · gpt60 · 179.9 AIC · ⌖ 70.6 AIC · ⊞ 20.8K · ◷

  • expires on Oct 23, 2026, 8:46 PM UTC-08:00

Activity

  1. github-actions commented on Oct 24, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-10-24T04:46:48.668Z.

    Closed by Workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions