PREWAVE-BE-100 — Complete Dispute Read-Model Appeal and Settlement Projections #801

Problem context

The dispute read-model view currently leaves the appeal deadline null, and the service leaves settlement outcome/bond disposition as placeholders pending settlement projection integration. These fields must not remain misleadingly incomplete or be inferred from unrelated timestamps/statuses.

Technical scope

Consume the canonical verification-round appeal deadline and finalized settlement/bond-disposition projections. Bind every value to chain, release, event provenance, and finality checkpoint. Represent genuinely unavailable or not-yet-final values explicitly; never infer a final outcome from a provisional status or updatedAt.

Required tests

• Open appeal, expired appeal, appealed, provisional settlement, finalized settlement, reorg, stale projection, and unavailable source fixtures.
• Verify exact chain/release provenance and finality gating.
• Assert unknown values remain unknown rather than being fabricated.
• Contract/API fixture compatibility tests.

Security and architecture constraints

• Contracts and finalized canonical events remain authoritative for protocol state.
• The API remains a projection/read and notification-delivery layer; it must not invent protocol outcomes.
• Fail closed on missing, stale, ambiguous, unauthorized, or incomplete state.
• Do not expose secrets, device tokens, email verification tokens, private evidence, or unnecessary personal data.
• Preserve strict typing, idempotency, privacy, observability redaction, and existing CI/security gates.

Acceptance criteria

• The identified placeholder or unsafe behavior is replaced by a production-quality implementation.
• Provider/recipient/ownership behavior is explicit and documented.
• Every required failure mode is covered by automated tests.
• No synthetic success, cross-user data exposure, or secret leakage remains in the affected path.
• The pull request links exactly this issue and maps evidence to every acceptance criterion.
• Exact-head required CI passes and independent human review is recorded.

Dependencies

• API V2-BE-100 — Establish the Projection Readiness Gate #453 — Projection Readiness Gate.
• Contract canonical dispute/appeal and settlement event projections must be pinned before implementation.

Non-goals

Changing contract settlement logic, dispute policy, or API mutation authority.

Complexity and points

• High — 200 points

Candidate only. Activation remains maintainer-controlled; do not apply Stellar Wave as part of implementation.