Clarify Near Intents refund and settlement recovery

[mikedotexe]

Summary

Revise the Near Intents charge draft from -00 to -01 and align its normative safety/recovery behavior with implementation hardening in IkerAlus/mpp-nearintents#9.

• resolve and challenge-bind the refund destination before requesting a wet quote; clients validate it before paying
• match the presented origin transaction hash before consuming it or retiring a terminal quote
• separate terminal backend outcomes from transport and polling timeouts
• document the extra unauthenticated retry when a framework has already computed the terminal 402 challenge
• require chain-canonical transaction identifier comparison rather than blind lowercasing
• separate payment replay protection from application response idempotency

No wire fields or method identifiers change.

Validation

• frontmatter and external-section-reference lint
• 25 repository tests
• full XML, HTML, TXT, and PDF generation
• rfclint and git diff check

Docker Desktop was unavailable, so the same local generation and validation scripts ran with the repository dependencies installed into temporary Ruby and Python environments.

AI assistance disclosure

Codex was used to help compare the implementation and specification, draft the edits, and run the validation workflow. I reviewed the resulting normative text and am responsible for its correctness.