Update Tweetle video link

[kronosapiens]

Update the Tweetle game jam entry with the new demo video link.

Co-Authored-By: Claude Haiku 4.5 noreply@anthropic.com

[github-actions]

Submission Screening

🚨 Flagged for Manual Review

Project: Tweetle
Repository: https://github.com/crackedstudio/Tweetle_dojo

Dojo Usage: Strong — 18 #[dojo::model] definitions and 5 #[dojo::contract] systems found in contracts/src/, with dojo = "1.8.0" declared in Scarb.toml. Real deployment manifest (manifest_sepolia.json) with world address 0x45b2841cbd334ae7cb39c89fdea585341b4b7688e215076aede41fc354c3f8d on Starknet Sepolia.

Client-Contract Integration: Contracts are the source of truth. main.tsx mounts DojoProvider which calls setupWorld() from contracts.gen.ts; useGameActions.ts calls client.actions.startGame() and client.actions.submitGuess() for classic/daily modes, useTournamentActions.ts calls client.tournament_manager.submitGuess() with ZK proof calldata. Game state is read back from Torii via Apollo/GraphQL — the client depends on contract outcomes.

Cartridge Controller: Fully integrated — @cartridge/controller is imported in WalletProvider.tsx and instantiated with session key policies covering all 4 deployed contracts (Actions, Daily Game, Tournament Manager, Player System). Passkey/social login flow is used for player onboarding.

Timeline: Jam ratio ≈ 8% (8 of 104 commits fall within the March 5–9 buffered window). The jam-window diff is substantial: 791 insertions / 269 deletions across 16 files, covering the stateless HMAC refactor, Docker base image fix, HowToPlay modal, and mobile layout fixes. Feature submission — the core ZK pipeline and contracts predate the jam; the jam contribution is a meaningful extension.

Frontmatter: 🚨 Flagged — the submission file contains YAML frontmatter, and this PR modifies the video_url field within it directly. Frontmatter is generated and owned by the enrichment agent; submitters should not edit it. The video URL update in the Markdown body (line 73) is the canonical location — the frontmatter will be stripped and regenerated by the enrichment agent after merge, which will pick up the corrected URL from the body.

---

Automated screening — a maintainer will perform final review.