[wolfgang-aura]

Two more cases of the #85 pattern: a surface that stops after one level, or reports COMPLETE when the capsule doesn't.

#91: three completeness verdicts disagreed. The unattended complete field came from the strict assessment, which is always clean on the ok: true path, so it said true for capsules whose Status: line said INCOMPLETE. The receipt modal had its own rule: it ignored truncated text and missing quoted posts, and it flagged poster-only videos that the capsule accepts. Both now use captureVerdict, the same captureGaps verdict the capsule prints. The CLI warnings carry the capsule's gap summary.

#92: reply context kept only the direct parent. A payload names only its own parent, so exporting a reply deep in a conversation kept one ancestor. Live example: hibtc37/status/2111300625627783421 kept @Xinbtc20's question and dropped the root post it asks about. The pass now walks up one fetch per ancestor, prepends ancestors oldest first, and labels only the direct parent "In reply to"; older ones read "Earlier in the conversation". Past 8 posts a note links onward to X. A 404 or a failed fetch ends the walk with an honest tombstone. The cap note and the tombstones are not capture gaps; truncated text or a missing image inside a context card still is, as in any embedded post. Inside a thread export, ancestors go directly above the exported post, never above an earlier thread post.

#25 follow-through. A reply-context tombstone from a failed (non-404) fetch kept an honest notice, but the HTML card, the .llm.md line and the receipt note still said "already gone on X". They now say the fetch failed, and a failed fetch no longer feeds the "gone on X" counter behind the receipt and the CLI's "deleted on X" warning.

v1.6.13 bump included.

Verification:

• New test/capture-verdict.test.mjs drives a real unattended capture-share into a stub Worker and asserts ok: true, complete: false against an uploaded .md that says INCOMPLETE, plus the modal-agrees cases. Five DOM tests cover the ancestor walk, the cap, a mid-chain failure, placement inside a thread, and the Reply-context card claims the parent is gone on any fetch failure #25 copy and counters. All failed before the fix.
• npm test, lint and format pass locally.
• Seen in a screenshot at 375 px (light): the real 3-post conversation rendered from live syndication. No horizontal scroll; labels read "Earlier in the conversation" then "In reply to".
• Not yet live-verified through an export; that follows the merge.

Fixes #91
Fixes #92

🤖 Generated with Claude Code