fix(agent): harden managed app verification

[iamjr15]

Why

Production app-builder runs could emit a browser action containing only the operational timeout, then claim interaction verification even though no action was possible. Managed template runs also still exposed a generic dev-server capability, allowing a model to replace the prepared Next.js/Expo contract and launch a competing server.

What changed

• Replace the nested browser-action union with a flat strict model contract whose four fields are always present; unused value/target refs are explicit null, while timeout remains internal policy.
• Track managed-preview ownership in checkpointed Workflow state and exclude the generic dev-server tool from every managed template model turn.
• Enforce the same ownership at execution time so stale calls cannot start alternate servers or replace/delete root framework manifests.
• Preserve source edits, package add/remove commands, and full framework/startup ownership for imported repositories.
• Clarify the managed template prompt and package architecture documentation.

Verification

• pnpm lint
• pnpm typecheck
• pnpm turbo build --force
• pnpm deadcode
• pnpm architecture:check
• pnpm turbo skills:build
• Direct schema assertion: required fields are exactly method, ref, targetRef, value; timeout-only input fails; valid click/fill inputs pass.
• Direct policy assertions: managed templates block dev starts and framework-manifest writes while source edits/package changes pass; imported repositories retain both capabilities.

Architecture / migration effects

• No database migration or environment change.
• Worker Workflow state gains one checkpointed boolean derived from app-builder preparation.
• No sandbox snapshot change is required.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
cheatcode	Skipped		Aug 12, 2026 8:23pm