Repository navigation
threenative login and deploy: publish from the terminal like Studio's Publish button (PRD-904) - #712
Conversation
… device flow and push
…ds borrow established CLI names (owner, 2026-11-21)
…is the site device flow in TypeScript
…rule on CLI tokens, .threenative/ link, device page keeps the code
…h to the Studio share link (PRD-904) login runs the threenative.com device flow and saves a 0600 token (THREENATIVE_TOKEN overrides); logout revokes it on the site; deploy runs build:web, packs dist/ in Studio's share archive format, PUTs it to Studio's /api/cli/share and keeps the link in .threenative/share.json.
PRD-904 AC-6 run log (local site + Studio Workers, scaffolded starter)Site: |
…omic 0600 token write; a dropped body exits 5 (PRD-904 Sol review)
…, first deploy carries a key so a lost reply retries onto one game (PRD-904 Sol re-review)
|
AC-6 rerun after the Sol 6.2 review fixes (site 3db86c6, Studio rebased + cc0c1b0/0015 migration, engine 4a288db): login exit 0 ( |
…d renamed, so an interrupted write cannot lose the deploy key (PRD-904 Sol review 3)
…e deploy key through an atomic link (PRD-904 Sol review 4)
…still holds the revoked token (PRD-904 Sol review 8)
… and login writes it once, so neither loses or revives the other's token (PRD-904 Sol review 9)
…en in its claimed file and retries it next time; an empty whoami reply still saves the token (PRD-904 Sol review 10)
… a file it cannot read; empty replies exit 4; the deploy key claim works without hard links (PRD-904 Sol review 11)
…ved, and logout claims auth.json in a directory it cannot list (PRD-904 Sol review 12)
…g directory and has nothing to claim, instead of saying signed out (PRD-904 Sol review 13)
|
The merge queue stopped on
Fix, push, re-enqueue. |
… instruction cap (PRD-904 merge-queue red)
What is this PR about?
threenative loginsigns in to a threenative.com account from the terminal, andthreenative deploypublishes the game to the same share link Studio's Publish button makes.threenative logoutrevokes the token. PRD:docs/PRDs/tooling/PRD-904-threenative-login-and-deploy-publish-like-studio-share.md.Why does it matter?
A game built outside Studio had no command to put it online, so an agent stopped at a local build.
Companion branches (other repos)
ThreeNativeHQ/threenative-sitebranchprd-904-cli-token:StudioAccounts.tokenAccount, bearerDELETE /api/store/token, device page keeps the code through verify and terms.ThreeNativeHQ/threenative-studiobranchprd-904-cli-share:PUT /api/cli/share.Checklist (mirrors the PRD)
login/logoutagainst a fake site (17/17)deploy.spec.ts5/5)