[avenger] Fix work-queue diagnostic guidance coverage #70209

CI failure and repair

CI run 39222667917 failed in Validate workflow container pins at Run agentic-workflows guidance tests. The diagnostic-coverage test found five missing codes: work_expired, hard_clear_not_paused, hard_clear_unresolved, hard_clear_snapshot_invalid, and hard_clear_conflict.

Added evidence/remedy rows for all five codes in .github/aw/debug-playbook.md, matching their work-queue implementations. Condensed existing prose to retain the 2,800-word contract without increasing limits or weakening tests. Only this documentation file is included; no protected workflow files changed.

Validation

• make test-guidance: all 15 tests pass, including diagnostic coverage and word/byte limits.
• make agent-report-progress: passed, including the CLI build and change-scoped checks. Its make test-unit stage skipped Go tests because no Go files changed.
• git diff --check: passed.
• Standalone make fmt and make lint were not run: this is a documentation-only guidance-test fix. Workflow recompilation was not needed.

Limitations

git fetch origin main failed certificate verification, so no merge was performed and transport security settings were left unchanged. The available checkout matched the failing CI commit a5a5d0435cbb59b69fefe5741ba91e3a3e12a79f. No valid steering-issue number was supplied, so steering comments could not be queried. The runtime does not expose report_progress; this committed branch is submitted through the configured safe-output PR transport.

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 · 213.7 AIC · ⌖ 105.1 AIC · ⊞ 20.7K · ◷

• expires on Oct 21, 2026, 12:58 AM UTC-08:00