v1.15.0 🔥 Ignition

🎯 Headline — Inheritance Plan Schema v6: Closing the Heir-Stranding Gotchas

This release is about the moment you're not there to answer questions. The in-app inheritance plan builder (desktop) went through a full review hunting "2FA-deadlock-class" gaps — situations where an heir holds one required piece and doesn't know a second piece exists — and every finding shipped in one pass. Plus: Bob now speaks knowledgeably about the 2026 Coldcard entropy incident, and a restore-screen usability fix.

✨ What's New

Inheritance plan schema v6 (desktop)

New fields that prevent silent dead-ends for heirs:

• Password-is-a-hint flag — a hint typed verbatim as a password fails identically to a wrong password. Plans now label hints honestly in the form and the PDF.
• Keyfile yes/no — a missing keyfile also fails as "wrong password." A blank location line is no longer ambiguous between "no keyfile" and "keyfile undocumented."
• BIP-39 passphrase question — a seed restored without its "25th word" opens an empty wallet. The question itself is the guard against heirs concluding the funds are gone.
• Multisig capture — wallet kind, derivation path, descriptor location, and co-signer list. Multisig recovery needs the descriptor, not just seeds; without it, reconstruction can be impossible even for a professional.

"Recreating the Wallets" PDF appendix

The exported plan PDF now ends with a recovery walkthrough written for an heir who has never heard the word "multisig": why an empty balance doesn't mean the funds are gone, passphrase handling, single-sig steps, descriptor-based multisig recovery, custodial-exchange estate process (including the legal note about not logging into a deceased person's account), and "call the Technical Contact first." Numerous PDF rendering fixes landed alongside (page-break font-state leak, clipped info line, cross-references by section name, vanishing name-only rows).

Plans migrate automatically v1→v6. User-written content is never rewritten by migration — new fields simply start blank, making no claim either way.

Bob understands the Coldcard incident

Users are asking hard questions about entropy, and Bob now has verified, sourced facts about the July 2026 Coldcard seed-generation flaw: the build-flag guard bug that silently routed seed generation onto a software PRNG, the ~40-bit / ~72-bit effective-security collapse by model, the offline sweep mechanics, affected firmware ranges, and the two takeaways that matter to an affected owner (a firmware update does not repair an existing seed; a strong BIP-39 passphrase protected funds). He'll also explain the structural contrast: seQRets' entropy path has no software fallback to fail onto — it either returns OS randomness or throws.

Restore-screen fix

The numbered seed-word reveal grid now reads top-to-bottom down each column (1,2,3 / 4,5,6 / …) instead of across rows — matching how every hardware wallet and backup card lays out a phrase. Verified with real 12-, 20-, 24-, and 33-word restores.

🤝 Compatibility

• ✅ All existing Qards — share format, integrity hash, and every cryptographic primitive are unchanged. Restores are unaffected.
• ✅ All existing inheritance plans — decrypt and migrate forward automatically; stored text is never modified.
• ✅ recover.html — no changes required.

🛡️ Security Note

No cryptographic primitives changed in this release. Seed phrases, passwords, keyfiles, salts, and nonces continue to draw full-strength entropy from the operating system's CSPRNG, with no fallback path. The independent code review in docs/SECURITY_ANALYSIS.md was conducted at an earlier version; changes since have not been independently reviewed.