docs(llms.txt): explain how agents resolve a "resolved" swap outcome#79
Merged
Conversation
The CLI's `alw view swap <id>` falls back to `resolved (completed or timed out)` once the contract prunes the swap state. Document the two ways an agent can recover the actual terminal outcome — the events API (SwapCompleted vs SwapTimedOut, persisted indefinitely by the indexer) and a destination-wallet cross-check — so agents stop guessing. Also note the new `alw swap resume-reservation --send` flag in the non-interactive cheat sheet so scripted agents know they can complete a resume without broadcasting source funds manually.
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
1 participant
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.
Summary
Companion to the allways
cli/agent-feedback-followupsPR.When a swap reaches a terminal state the on-chain contract prunes its row to keep storage bounded, so
alw view swap <id>falls back toresolved (completed or timed out)and an agent has no way to tell from the CLI alone whether they got their funds. Rather than make the CLI track this client-side, document the recovery path so agents know where to look:GET /events?swapId=<id>) still has the terminalSwapCompleted/SwapTimedOutevent — that's authoritative and persists indefinitely from the indexer's perspective.FULFILLEDblock.Also wires the new
alw swap resume-reservation --sendflag (added in the allways CLI PR) into the non-interactive cheat sheet so scripted agents know they can finish a resume without broadcasting source funds by hand.Test plan
npm run buildclean