[Bug] Demo app seed data claims milestone outcomes that never happened on-chain

[collinsezedike]

Summary

demos/freelance-escrow/src/data/jobs.ts's seed jobs include milestones marked status: "released" (e.g. job-1-m1, job-3-m1) with no assertionId set. That status is only ever supposed to be reached by a real assert_outcome -> finalize/resolve sequence against the live contract (see JobsContext.tsx's voteOnMilestone/finalizeMilestone), but these seed entries never went through it. The app ships presenting fabricated outcomes as if they were real activity.

Scope

• Remove hardcoded terminal statuses (released, disputed, returned, submitted) from seed data. Seed milestones should start at in_progress only, since that's the one status that doesn't imply a contract interaction happened.
• Keep the seed jobs themselves (titles, descriptions, client/freelancer names) as realistic placeholder content, only the fabricated outcomes are the problem.

Proposed approach

Edit the milestones arrays in src/data/jobs.ts so every entry has status: "in_progress" and no submittedAt/assertionId. Any further-along milestone state a visitor sees should come from actually calling submitMilestone/disputeMilestone/voteOnMilestone/finalizeMilestone in their own session, not from the seed file.

[JohnArayaE]

I would like to work on this issue because seed data should accurately reflect what has actually happened on-chain and should not present fabricated milestone outcomes as real contract activity. I can update the milestone seed data so every entry starts in in_progress, remove any hardcoded submittedAt and assertionId values, and preserve the existing job titles, descriptions, clients, and freelancers so the demo remains realistic while ensuring all terminal states are reached only through actual user interactions with the contract.

[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

[drah9991]

Helloo repo maintainer i'd like to work on this

[samueldoo]

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

[collinsezedike]

@JohnArayaE assigning this to you too, your comment correctly identified the actual problem (fabricated milestone outcomes presented as real activity). Go ahead and dig in, let me know if anything's unclear.

[grantfox-oss]

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

Next steps:

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

Good luck! Track your progress on GrantFox.

[JohnArayaE]

@collinsezedike Changes are up in #175, ready for your review.

[JohnArayaE]

@collinsezedike Changes are up in #175, ready for your review.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@JohnArayaE's PR #175 was approved and merged by @collinsezedike.

🏆 @JohnArayaE: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (70 total points). Track your full progress on GrantFox.

👏 Great work, @JohnArayaE! Keep contributing to drydocs.