feat: add trailer, docs site, diagrams and a hardened redeployed contract

[salazarsebas]

Summary

Prepares the submission: the trailer and README media (#24), a hardened and redeployed contract, a docs site at /docs, architecture diagrams, and the documentation pass behind issue #25.

What changed

Contract (contracts/deepmark-contract)

• transfer(a, a, id) is an authorized no-op, so a self transfer no longer duplicates an id.
• The two unwrap() calls became a typed NotInitialized error.
• start_run renews the shared storage entries and a veteran's records.
• A failed relic mint now returns MintFailed and reverts the whole finish_run, so the run stays open and can be retried.
• 80 contract tests plus the 600 golden vectors pass. The simulation is unchanged.
• Redeployed on testnet with a locked issuer, and the instance and wasm rent is paid at deploy time. The first start_run now costs about 0.9 XLM instead of 183.9 XLM. New ids are in docs/deployments.md and client/src/stellar/config.ts.

Client (client)

• Retries on transient network errors, a failed start_run is re-simulated, and finish_run keeps the saved run on MintFailed or a lost response.
• A clear back control and a loading screen on the public stats page, scrollable end screens on phones, a skip for the practice fallback wait, and practice runs no longer count as records.
• Recovery code flow for the browser key, with a confirmation step.
• vercel.json with a Content-Security-Policy and security headers.
• game-app.ts went from 957 to 130 lines, and the code now lives in src/app/ modules. Biome and cargo fmt and clippy run in CI. 134 client tests.
• A static docs site at /docs, built from the repository markdown with no client JavaScript, and kept out of the game bundle.

Diagrams (diagrams): seven diagrams generated from code, with a CI check that fails when the committed output drifts.

Trailer (trailer): a Remotion workspace that renders the 30 second and 90 second trailers and the animated share card from gameplay recorded on the production build, plus the README screenshots and GIF. The videos are linked from the README.

Docs: README with explorer links, a "verify a run in 60 seconds" block and a measured costs table, an updated threat model, a roadmap and a business model.

Verification

• bun run typecheck, lint, format:check, bun test (134) and bun run build pass in client.
• cargo fmt --check, cargo clippy -D warnings and cargo test pass in the contract.
• Six real runs on the new deployment, played through the client on fresh accounts, cover an early extraction, a death, an extraction that mints DMRARE, two full clears and a veteran run. Every transaction hash linked in the README is successful on Horizon, and verify_run matches the run_finished event.
• gitleaks finds nothing in the versioned files, and a search for Stellar secret keys is clean.

Known limits

• Testnet only. The admin key can still upgrade the contract, and renouncing it is a separate decision.
• A bot with many funded accounts can farm the ladder. This is documented in docs/threat-model.md.
• New players who start in the same ledger can collide. The client retries, and a registry keyed by address would remove it in a later contract version.
• The six finished runs on the new deployment were played by the team.

Closes #24. Refs #25: the remaining items there need the owner (submission, pitch video, real device checks).

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
deepmark	Ready	Preview	Oct 12, 2026 8:25pm UTC