Refresh the hackathon-era claims in the README and full_product_breakdown

[Otaiki1]

Context

README.md (24KB) and full_product_breakdown.md (40KB) were written for a hackathon submission and
carry claims that are now stale or unverified:

• YOUR_VIDEO_URL is still a placeholder, in a line that appears twice (lines 51 and 52).
• The demo-GIF comment block at lines 44–50 describes a GIF that does not exist.
• The "48.0M / 100M instructions" figure is hand-maintained prose that no test checks.
• The on-chain evidence table cites specific testnet transactions that a testnet reset will erase.
• The contract described in the breakdown predates cancel_circle, get_circle_count, has_claimed, RoundFull, Overflow, and CircleCancelled.

The repo has moved on; its front page has not.

Where to build it

• README.md — lines 44–52 (the GIF block and duplicated link line), the evidence table, and the "why this was hard" section.
• full_product_breakdown.md — the contract API and error-code sections.
• docs/hackathon/ — the genuinely hackathon-specific material can stay as an archive; say so.

What to do

• Remove the duplicated link line and either record the demo video or drop the placeholder.
• Either produce the demo GIF or delete the comment block describing where it would go.
• Replace the inline instruction-count figure with a link to contracts/BENCHMARKS.md.
• Add a dated note to the evidence table explaining that testnet artifacts do not survive a reset, and link the reset runbook.
• Update the breakdown's contract API section to the current eight error codes and full entrypoint list.
• Mark docs/hackathon/* explicitly as a point-in-time archive that is not maintained.

Acceptance criteria

• No placeholder text remains on the README's front page.
• Every factual claim on the README is either checked by a test or dated.

[elonwachineke-dot]

@elonwachineke-dot has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

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

ℹ️ Repo Maintainers: To accept this application, review their application or assign @elonwachineke-dot to this issue.

[chikawobishie-sketch]

@chikawobishie-sketch has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

hello maintainer, i will love to work on this issue, kindly assign it to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @chikawobishie-sketch to this issue.

[ositaemmanuel653-netizen]

@ositaemmanuel653-netizen has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Trust me to deliver a very clean job.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ositaemmanuel653-netizen to this issue.

[dotmantissa]

@dotmantissa has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Please, assign this issue to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @dotmantissa to this issue.

[odinakaikpakingsley-alt]

@odinakaikpakingsley-alt has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Please assign this issue to me maintainer

ℹ️ Repo Maintainers: To accept this application, review their application or assign @odinakaikpakingsley-alt to this issue.

[ibochielizabeth-spec]

@ibochielizabeth-spec has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

pls assign to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ibochielizabeth-spec to this issue.

[drips-wave]

Congratulations, @dotmantissa! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @dotmantissa: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @dotmantissa as part of the Stellar Wave Program's 8th Wave 🥳

Moderator's reason: [Auto-assessed] The PR #416 is open, has no maintainer objections or review comments across any channel, and cleanly addresses issue #345 by removing placeholders, updating benchmarks, documenting testnet caveats, and updating the full product breakdown. Evidence: no maintainer response across any of the four channels, and the diff correctly implements the requested documentation updates.

😎 @dotmantissa: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.