v1.1.0-beta.1 — Hosted beta checkpoint

Hosted beta checkpoint

This prerelease captures the production-hardening work since v1 and the deployed Vercel web application. Public previews and the demo are available; authenticated production acceptance remains pending. This is not a general-availability release.

Highlights since v1

• Separate the Next.js web application from long-running Vercel Sandbox jobs, with owner-scoped private Blob records, compact history, bounded concurrency, cancellation markers, retention, and a versioned worker protocol.
• Bound provider/GitHub requests and local helper processes; improve retries, cancellation recovery, stale-state handling, and fail-closed behavior when runtime dependencies are unavailable.
• Improve navigation, discovery, issue actions, Settings, PR review, graph entry flows, desktop/mobile layouts, keyboard interaction, and accessibility.
• Harden user credential isolation, account-bound provider-key encryption, worker environment/tool allowlists, generated-change secret scanning, and private-repository access checks.
• Run on Node.js 24 with patched Next.js/React dependencies and repeatable app, MCP, graph, worker, container, browser, and full-history secret checks.
• Rewrite the README around product capabilities, setup, environments, validation, and current limits; add the MIT license file consistent with the existing README declaration.
• Add permanent missing-Auth0 browser regression coverage to CI and align both private package versions to 1.1.0-beta.1.

Verification

Release commit: eea68c19d56286bbf992bc2cc6bbc4ef7637eedd

• Exact-commit CI: 158 application tests, MCP tests, typecheck, lint, dependency audits, worker build, restricted real Claude CLI, optimized app build, graph runtime, non-root production container boot, and HTTP/browser/concurrency smoke suites.
• Exact-commit CodeQL: JavaScript/TypeScript security-extended analysis completed successfully.
• Both Vercel deployment checks passed for the release commit.
• Public production HTTP checks passed. Missing-Auth0 browser coverage checked 12 page states at 1440px and 390px, with no client errors, overflow, unexpected auth navigation, or serious/critical Axe findings.
• GitHub reported zero open secret-scanning and Dependabot alerts at this checkpoint. Five medium CodeQL findings remain open for review; successful analysis does not mean all findings are resolved.

Environments

• Production tracks main and offers a public preview and demo.
• Staging tracks the stable staging domain and remains protected by Vercel authentication.

Setup and upgrade notes

• Configure environment-specific Auth0 tenants/apps, private Blob storage, and worker snapshots before enabling authenticated hosted workflows. Keep AUTH0_SECRET stable and different between environments.
• Build the worker snapshot from the exact release commit using node scripts/create-worker-snapshot.mjs <full-sha>; older snapshots may be rejected by the worker protocol.
• Users with legacy unbound provider-key cookies must enter their keys again in Settings. Keys are now bound to the account and expire after 30 days; logout removes the cookie.
• Local development can use AUTH_DISABLED=1 with a unique encryption secret. That bypass is refused in production.
• See the README and deployment guide for setup and acceptance steps.

Outstanding release gates

• Provision Auth0, private storage, and worker snapshots in both environments; verify real login/logout, GitHub token scopes, saved keys, preview, controlled PR creation, cancellation, and private-org access.
• Verify the full cloud worker lifecycle and load-test authenticated requests/jobs against an agreed workload and provider budget. Health-endpoint concurrency results are smoke evidence, not a production capacity estimate.
• Review the five open medium CodeQL findings before general multi-tenant release.
• Hosted target-repository install/test commands remain disabled until isolated from worker credentials. Generated patches remain unverified until target CI or a separate credential-free sandbox validates them.
• Docker mode has no durable queue or restart recovery. Do not use rolling deployments while local jobs are active.

Full changes since v1

v1

Version 1