[vladvrx]

BeatForge adds an authenticated remote MCP/REST gateway backed by durable jobs and an outbound local worker. Studio can upload audio, inspect assistant-created maps with synchronized previews, revise a selected passage without changing its parent, compare charts, and save explicit feedback and presets. The branch also improves the local premium pipeline, RL evaluation and Studio presentation, including the transparent neon logo.

The gateway is separate from the privileged local game-control API. Shared REST/MCP operations enforce ownership and scopes. Jobs use leases and idempotency; artifacts use bounded storage and expiring links. Stalled transfers clean up partial data, expired pending uploads reclaim quota, and an offline dry-run recovery command handles interrupted audio uploads after a crash. Render targets the isolated gateway with persistent storage; Vercel builds static Studio assets. Setup guides cover Meta Muse/Muse Code, GPT/ChatGPT, Claude and Grok.

Validation:

• Full local non-browser regression before the final artifact/maintenance additions: 316 passed, 2 skipped, 3 deselected. Subsequent artifact tests: 5 passed; maintenance tests: 3 passed. Five JavaScript upload-retry unit tests passed and now run in CI.
• Real HTTP MCP SDK initialization, discovery, REST/MCP parity and four artifact hash checks passed.
• Browser submitted synthetic audio; the real worker generated a Hard chart and a section revision. Parent identity and content outside the selection were preserved, full-map QA had zero errors, and A/B switching retained playback position.
• Browser renewed a two-second expired audio link and started playback. Connected feedback/comparison controls were visually reviewed at 390, 768 and 1440 pixels without horizontal page overflow. No ratings were submitted.
• GitHub CI run 35531444730 passed all three jobs for head f630404: app tests, portable-skill verification and skill tests.

This remains a draft. Hosted OAuth/provider registration, actual assistant-account verification, browser OAuth sign-in and retention policy for completed data remain unfinished. Revisions require the original worker cache. Synthetic timing was explicitly unconfirmed and no human playtest evidence was invented. No cloud resources were provisioned and no Render/Vercel credits were spent. See docs/CONNECTOR_RELEASE_STATUS.md for the release audit and docs/CONNECTOR_RECOVERY.md for operator recovery.