Mosoo v0.7.0 (Alpha): over-engineering trim & leaner codebase

Alpha pre-release. Deployed to production (cloud.mosoo.ai) at commit dadfb757b2.

Highlights

• refactor(repo): trim over-engineering and slim docs (#665) — a repository-wide cleanup. ~90K lines of dead code, retired-feature residue (Pet/Cattle, legacy kind, App Deployment, per-turn budgets), duplicated validation, unmeasured caches/retries, and source-text tests removed, with first-principles re-audit and ~6–10% deliberate add-back. Docs slimmed from 66 files/7.8K lines to 31/2.8K. No DB migration, no DDL; public Thread API v1/v2 wire unchanged.
• ci(ops): monitor every sandbox container application (#662)
• fix(runtime): bound container lifetime and capacity failures (#663)

Production rollout

• Pure code deploy; production D1 already at migration 0018 (no migration applied).
• API + Web Workers redeployed; all five Sandbox container images rebuilt and pushed; per-minute maintenance cron verified firing.
• Targeted staging acceptance beforehand: all four runtime transports (OpenAI runtime, OpenCode, Pi, DeepSeek) green end-to-end, plus the direct v2 Session path, DO-RPC control plane, usage, idempotency, cancel, and static model-availability admission.

Coordination

• mosoo-cli-go must be regenerated and released in lockstep: the console GraphQL schema (internal surface) dropped operations/fields the current CLI selects (startAgentRun, sessionMessages, controlPlaneOverview/mosoo ls, organizationBillingCostCard, createEnvironmentFork, …). The public Thread API is unaffected.

Version numbering

The preceding Host release was initially published as v0.6.0 and corrected to v0.5.1. Its original v0.6.0 Git tag remains at 48ea069f37956a723380636407a4ad6b15291aaa for traceability. This explains the gap in the published release list; there is no missing intermediate Host feature release. CLI v0.6.0 has an independent version number. This clarification changes no source tags or production deployment.

Full changelog: v0.5.1...v0.7.0