docs(tasks): sync 004 status markers with implemented code

[Catrya]

Summary by CodeRabbit

• Documentation
  • Updated implementation status for seller trade details, encrypted chat, and dispute flows.
  • Marked several chat features as ready or partially ready, including live room updates and incoming message handling.
  • Clarified that dispute screens and lists still need data wiring before they function end to end.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 031291f2-17cb-498e-86ba-a9096506d104

📥 Commits

Reviewing files that changed from the base of the PR and between 3078994 and f450881.

📒 Files selected for processing (1)

• specs/004-mostro-p2p-client/tasks.md

---

Walkthrough

Task documentation is revised to reflect updated implementation status for seller active trade, encrypted chat, and dispute flows. The notes now mark some items complete, clarify gift-wrap message and room behavior, and mark several dispute UI paths as partial.

Changes

Task status corrections

Layer / File(s)	Summary
Seller trade detail status specs/004-mostro-p2p-client/tasks.md	T067 now describes the seller active-order trade view as complete, with role and status derived from providers and incoming trade-state routing.
Encrypted chat and room readiness specs/004-mostro-p2p-client/tasks.md	T070–T081 updates mark the Blossom client complete, describe gift-wrap message handling and incoming decrypt/store routing, mark chat rooms live through upsertRoom, and leave the info and attachment widgets partial.
Dispute screens remain unwired specs/004-mostro-p2p-client/tasks.md	T088–T093 are marked partial because the disputes list is still empty and the chat, message, and resolution screens are stubbed without live bridge or admin-flow wiring.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• MostroP2P/app#68: Adjacent provider/UI wiring changes for privacy mode and reputation display may correspond to the task-tracking updates in this spec.

Poem

🐇 I hopped through the task scroll bright,
Marked some paths as done tonight.
A gift-wrap whisper, rooms awake,
Some dispute trails still merely fake.
Thump-thump—docs now point the way.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly states that task status markers are being synced to match the implemented code.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch update-tasks

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[mostronatorcoder]

I reviewed the current head and I do not see a blocking issue.

What I checked:

• The task-marker changes are not just hand-wavy wording shifts; the stronger claims around P2P chat now match the code more closely. In particular, send_message, on_new_message, and subscribe_incoming_chat are present in Rust, and ChatRoomScreen / incomingMessageProvider do consume that path.
• The dispute-related tasks are now marked partial in the places where the Dart side is still obviously stubbed or unwired (userDisputeDataProvider sourced only from the local notifier, dispute chat send/attach stubs, resolved-state branches unreachable without bridge-fed dispute state).
• The file-attachment UI tasks also now describe the real boundary correctly: Rust/Blossom support exists, but the Dart consumers are still stubbed.

So the task status document looks materially more honest and better aligned with the implemented code on this revision.

Approved on the current revision.