Changelog

This page records meaningful customer-facing changes after they ship. Entries describe the result, the affected surface, and where to learn more.

Planned work belongs in Availability & Roadmap, not in the changelog.

July 24, 2026

Public contracts and deployment guidance

The CLI, API, SDK, MCP, data, domain, release, and deployment guides now match the shipped platform contracts.

• API key examples use the current msk_u_*, msk_p_*, and msk_a_* families.
• API examples use the canonical https://api.miosa.ai/api/v1 base URL.
• CLI examples use the current @miosa/cli command tree.
• Sandbox snapshot create, list, inspect, restore, delete, and fork operations are documented.
• Release inspection, exact promotion, rollback, and deployment proof are documented as separate steps.
• Managed database lifecycle, recovery, credentials, backups, restores, branches, replicas, logs, metrics, and placement are documented.
• The interactive OpenAPI page is labeled as the Sandbox V1 subset.
• The wider platform contract remains in the written API reference.

The docs build now rejects known stale key formats, API paths, CLI commands, deployment hostnames, snapshot claims, and audit routes.

Documentation navigation

Product readiness and roadmap information now has one canonical home in Availability & Roadmap.

Deployment and recovery

Publishing guidance now separates candidate creation, exact promotion, runtime activation, public proof, and rollback. An application is not considered live until the selected release, running artifact, route, bindings, and public response agree.

App Engine guidance now describes one workspace-scoped host serving multiple deployments. Updates preserve the deployment identity, stable URL, environment, database bindings, release history, and rollback path.

CLI operating contract

The CLI reference now covers the shipped high-level application workflow:

1. Inspect the application.
2. Generate a plan.
3. Link the source directory to one deployment.
4. Preview in a sandbox.
5. Publish a candidate release.
6. Promote the exact release.
7. Prove production.
8. Roll back to an exact prior release when required.

Capability manifests, immutable change plans, approvals, placement, policy checks, drift detection, evidence receipts, incidents, durable waits, and operator memory are documented as additive command families.

Platform controls

The Action Authority console now supports exact grants for constrained operations. CLI approval flows require an unambiguous organization.

Usage and billing surfaces now use consistent USD and credit meanings. The usage explorer provides clearer cost analysis and sandbox spend controls.

Managed database screens now expose deployment and recovery status instead of reducing health to a single generic state.

July 18 - 19, 2026

Sandbox contract and customer-cloud capacity

Sandbox product UI and documentation were aligned with the public contract. Capacity, resource sizes, persistence, and readiness are catalog-driven instead of inferred from frontend defaults.

AWS BYOC sandbox guidance now distinguishes the supported workflow from gated customer capacity. Production claims require accepted capacity, certified artifacts, tenant policy, and current catalog readiness.

Sandbox spend controls were added to the billing experience.

July 13 - 16, 2026

Organizations, domains, and navigation

Organization switching now survives refreshes and invite recovery. Account and workspace views resolve the established organization context before mutations.

Domain settings were consolidated into one clearer product story covering previews, deployment domains, and custom domains.

Header behavior was corrected across intermediate viewport widths. Landing-page landmarks and workspace brand assets were restored.

July 7 - 8, 2026

App Engine and deployment proof

App Engine became the customer-facing name for the workspace container runtime. Legacy compatibility command names and wire values remain only where the executable contract requires them.

Deployment proof was added to the product and documentation. For App Engine deployments, metadata alone is not proof of a live application.

The quickstart and deployment guides now use this sequence:

1. Build and verify in a sandbox.
2. Publish to the selected production runtime.
3. Use the API-returned URL.
4. Prove the running deployment.

The documentation header, sidebar, footer, Mermaid rendering, SDK versions, preview URLs, and custom-domain references were also refreshed.

June 23 - 25, 2026

Launch benchmark and security fixes

The launch benchmark documentation was clarified so readers can distinguish the server-run path from the client-managed lifecycle.

TypeScript SDK installation guidance was updated to the then-current registry release.

Session refresh now rejects refresh tokens with the correct client error. JWTs are verified before being mirrored into cookies. Email campaign previews are sanitized before rendering. Protected voice-session mutations require platform authentication.

June 13 - 19, 2026

Agent workflows and data operations

Documentation added durable Agent Runs, run groups, queued dispatch, cancellation, runtime profiles, runtime environment inheritance, artifacts, and backend orchestration patterns.

Data documentation was aligned with shipped auth, storage, volumes, and managed service operations. The frontend added volume create, attach, detach, delete, and metering surfaces.

Pricing gained a live cost calculator and plan comparison matrix.

A production deployment guard was added so frontend releases must come from a clean, approved worktree at the exact origin/main commit.

Missing public documentation pages and navigation entries were restored.

June 9 - 12, 2026

Production V1 and onboarding

The unified V1 backend entered production. Production sandbox benchmarks completed 100 of 100 test lifecycles without capacity rejection.

Onboarding completion became durable across the tenant record, authentication payload, and browser fallback. Completed users return directly to their workspace.

The final onboarding screen now links users to CLI and agent setup.

See Benchmarks for current benchmark methodology and results.

May 26, 2026

White-label integration release

The 1.1.0 integration release added:

• Sandbox slugs, external attribution, metadata, and updates.
• Scoped preview tokens and sandbox lifecycle webhooks.
• Tenant branding and preview-domain operations.
• Advanced file, environment, process, template, and fork primitives.
• Usage rollups, quotas, audit logs, and tenant event streams.
• Revocable preview sharing.
• React, Vue, and Svelte embedding packages.

The release was additive and did not require a data migration.

Package snapshot

Versions verified on July 24, 2026:

Use unpinned installation commands when you want the latest compatible release. Pin an exact version in production lockfiles.

Historical archive