Repository navigation
Document claim delivery diagnostics - #69987
Merged
pelikhan merged 2 commits intoOct 18, 2026
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Document unverified claim delivery diagnostics to fix CI
Document claim delivery diagnostics
Oct 18, 2026
pelikhan
marked this pull request as ready for review
October 18, 2026 20:11
pelikhan
deleted the
copilot/avengerclaim-delivery-guidance-3107-399c290f4bbaa0
branch
October 18, 2026 20:11
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The requested diagnostics and recovery safeguards are covered; remaining feedback is minor.
1 open issue
What changed in this PR
Updates gh-aw’s work-queue troubleshooting guidance to cover unverified claim delivery.
Changes:
- Adds three delivery diagnostic codes and relevant evidence checks.
- Documents reconciliation before retry without forcing terminal state.
- Condenses wording to preserve the 2,800-word budget.
| File | Description |
|---|---|
.github/aw/debug-playbook.md |
Expands delivery diagnostics and condenses surrounding guidance. |
Review effort: Max
| | `checkpoint_invalid`, `credential_generation_reused` | Checkpoint proof/ancestry; unique credential generation. | Recover verified checkpoint/authorized new generation; no stale authority. | | ||
| | `dispatch_invalid`, `dispatch_missing`, `launch_started`, `launch_unresolved` | Reservation, receipt, possibly started child. | Reconcile immutable dispatch identity; no duplicate launch. | | ||
| | `delivery_conflict`, `delivery_barrier_conflict`, `delivery_contract_required`, `delivery_evidence_required`, `evidence_invalid`, `evidence_required`, `terminal_evidence_required`, `nonlaunch_evidence_required` | Barrier/contract; authoritative receipts. | Supply verified matching evidence; never force terminal state. | | ||
| | `claim_delivery_unverified`, `delivery_failed`, `verification_unresolved`, `delivery_conflict`, `delivery_barrier_conflict`, `delivery_contract_required`, `delivery_evidence_required`, `evidence_invalid`, `evidence_required`, `terminal_evidence_required`, `nonlaunch_evidence_required` | Claim state/effects; independent receipts; barrier/contract. | Reconcile before retry; never force terminal state. | |
Contributor
|
🎉 This pull request is included in a new release. Release: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The guidance contract flagged
claim_delivery_unverifiedas missing an evidence/remedy row. Update the work-queue diagnostics to cover it alongsidedelivery_failedandverification_unresolved.