[winnieworld]

Summary

• Align the example WebApp with the ClairveilJS 0.3.1 Cosmos wallet contract, including active-profile denomination handling, typed scans, deposit proofs, transfer/withdraw preparation, exact fees, and disclosure review.
• Add crash-safe encrypted note, reservation, operation, and pending-transaction recovery with cross-tab account fencing, signed Cosmos transaction identity, uncertain-broadcast reconciliation, and safe reset/rescan flows.
• Harden relay-withdraw preparation and handoff with lease renewal, durable handoff markers, authoritative chain-time validation, expiry checks, and fail-closed payload exposure.
• Harden local and production deployment boundaries through loopback-only helpers, configuration parity verification, CSP/CORS checks, immutable ClairveilJS selection, and bundle freshness checks.
• Reject unsupported legacy lifecycle stores atomically. This unreleased v0.3.1 WebApp supports fresh-state initialization only; migration and in-place downgrade are not supported.
• Keep one-proof batch transfer disabled in the example WebApp with serverFeatures.batchTransfer=false.

Type

• Core module / keeper
• CLI / SDK / wallet contract
• Prover / ZK artifact tooling
• Docs / release process
• CI / packaging

Validation

• make docs-check
• make ci
• make vulncheck
• make release-check if release-critical behavior changed

Downstream Impact

• No downstream-facing contract changes
• Proto, fixture, schema, CLI, or prover contract changed and docs were updated
• Security/trust boundary changed and security docs were updated
• English/Korean documentation pairs and indexes were updated together
• User-visible/release-facing changes were recorded under Unreleased in both changelogs

Notes

• Target base: feat/wip_0.3.1.
• npm --prefix examples/clairveil-dapp run check:dapp passed, including bundle freshness.
• npm --prefix examples/clairveil-dapp run test:dapp passed: 307 tests.
• make docs-check currently fails because both changelogs lack the dated v0.4.0 heading; this was intentionally left for a separate update.
• make vulncheck currently fails on GO-2026-6099 (webtransport-go) and GO-2026-6165 (pion/dtls/v3).
• Consequently, full make ci and make release-check are not claimed as passing.