Flip: Publish

Read https://flip-sdk-proposal.vercel.app/sdk/guides/creator-tools.md for installation and the complete direct-delivery workflow. No Git or GitHub is required.

1. Use the copied private environment or flip create and creator approval. flip reconnect renews access. Never request an account session or wallet key.
2. Run flip status immediately, before questions or planning. Preserve the existing game; if code is missing, use flip history and flip pull --revision N --out NEW_DIRECTORY.
3. Send available creator-chosen identity fields in game-metadata.json with flip metadata --dir GAME_DIRECTORY while questions are pending. Establish the controls and core loop using flip-game and the gameplay intent guide, then settle remaining fields before locking the economy or building. Preserve creator overrides and published ticker. Include devices (and orientation when phones must hold it one way) from what you built; the creator's Plays on choice in Create wins.
4. Build and test. flip push --dir GAME_DIRECTORY --message "Describe the change" runs preflight and atomically uploads a private version. It resumes interrupted transfers and reuses unchanged assets. A concurrent revision conflict requires reconciliation, never blind overwrite.
5. Verify accepted revision/build hash, run actual gameplay assertions and browser scenarios against the agreed controls, player actions and progression. A paid security/SDK audit does not verify design intent. A smoke pass is configuration evidence only.
6. Run flip audit --revision N --wait on the ready build. It requires local preflight; Flip reruns independent checks before paid AI. flip review and flip results only read the audit.
7. Fix, upload and audit again, at most three attempts before asking the creator for direction. Only report ready with a passed audit for the exact version. State untested checks. flip launch --revision N asks the creator; only their final button publishes.

Post one line at each delivery milestone with flip note --message "…" (MCP: flip_note): access approved, each version uploaded, the audit's result and what you are fixing, launch requested. Create already lists each version and audit, so say what changed or what comes next: flip note --message "Version 3 uploaded: two-player rooms and shorter rounds". One line, at most 200 characters, 12 a minute; never a credential, grant, key or wallet address. A note never uploads, audits or publishes.

Keep tools, tests and credentials outside the playable build. Scope the token to its Flip origin and draft; never print it or put it in argv, URLs, source or reports. JSON results include status; --json adds progress events. Exit codes 0/1/2 mean result/failure/could not run. Local MCP shares these operations; web chat remains Coming soon.

After the playable upload and hosted gameplay/browser checks, explicitly submit the ready build with flip audit --dir GAME_DIRECTORY --revision N --wait. This reruns local preflight; Flip independently checks the accepted files before its paid AI review. Uploading or polling alone never starts an audit. Read flip results --revision N, fix findings, push a new version and audit it again. Limit one autonomous fix-and-audit sequence to three attempts total, then explain unresolved findings and wait for the creator’s direction; the creator can resume with Run audit on the Audit page. Do not loop on quota/provider errors. The server allows 250 paid audits per account per rolling 24 hours, with a $1,000 platform-wide spending cap. Repeated active requests and valid unchanged results are reused. Only the creator launches. Share the preview as soon as playable; after a passed exact-version audit, give a short summary of changes, checks and anything untested, and ask what the creator would like changed.