[Feature] Persist freelance-escrow demo state across page reloads

[collinsezedike]

Summary

JobsProvider (JobsContext.tsx) holds all job/milestone state, including the assertionId mapping to real on-chain assertions, in plain useState(seedJobs). There's no backend and no client-side persistence, so refreshing the page discards every job created and every milestone submitted/disputed/resolved in the session, reverting to the three seed jobs. A visitor's real activity against the live contract leaves no lasting trace in the app itself.

Scope

• Persist jobs (including each milestone's assertionId/submittedAt) across reloads. No backend exists for this app, and none should be introduced just for this; a client-side store is sufficient and consistent with job metadata already living entirely off-chain in the browser.
• Independent of the on-chain state reconciliation issue, this can be built in either order. Without reconciliation in place yet, a persisted status is only as accurate as the optimistic status the app currently sets, no worse than today's in-session behavior, just no longer lost on reload.

Proposed approach

Back JobsProvider's state with localStorage (read on mount, write on every jobs change), keyed so it doesn't collide with other apps' storage. If the on-chain state reconciliation work has landed by the time this is picked up, reconcile any milestone with an assertionId against get_assertion_state on mount, after loading persisted state and before rendering, so a stale persisted status never outlives a real state change that happened while the tab was closed. If not, plain persistence of the current optimistic status is still a real improvement on its own.

[prosperceed]

Let me handle this task. I have a clear understanding about the implementation. Thank you

[xtep103]

Hey Maintainer, I have gone through the details of the issue and i am capable of resolving it, I would love to be assigned to work on it ASAP. Thanks in advance

[playmaker410]

i would love to take this on. I have hands on experience with Rust, Soroban, Cairo, and TypeScript, and I am confident I can deliver a solid solution within 24 hours

[Sharon-dev-create]

Please assign this issue to me, I am a good fit.

[samueldoo]

Hello Maintainer, I’d love to take ownership of this issue and submit a high-quality pull request once completed.

[grantfox-oss]

🦊 GrantFox — @playmaker410 has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #148)
2. Your PR will be reviewed by the drydocs maintainers

Good luck! Track your progress on GrantFox.

[collinsezedike]

@playmaker410 Checking in, any progress on this? Let us know if you're still working it or need to hand it off.

[playmaker410]

@collinsezedike Please you will see my pr today. Was very busy.