* fix(deploy): let webhooks and CLI accept reviewed Compose changes
Webhook and CLI deploys hit COMPOSE_REVIEW_REQUIRED with no way through the gate, and the refusal hid what changed. Accept the current Compose source explicitly per deploy (--accept-compose-changes, or acceptComposeChanges on the hook), and surface the added/changed/removed services in the CLI error and the webhook delivery record.
* test(contracts): include acceptComposeChanges in deployment schema flags
The Compose review gate added acceptComposeChanges to
CreateDeploymentSchema without updating the contract test that
enumerates the schema's public flags, so the contracts suite failed
on CI. Add the flag to the expected list.
* docs(cli): list --accept-compose-changes in the deploy reference
The new deploy flag was missing from the generated CLI reference,
so docs:check failed with a stale reference. Add the row in
declaration order.
* Retain explicit Compose approval through shared deployment admission
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
Cover full published-stack upgrades, retained data and signed sessions, cold restart and fresh installation. Reuse runtime preflight in advisory views and expose source-redeploy prerequisites. Refs #1461 and #1462.
Scoped token grants can carry capabilities in permissions, held on a
project: domains:read|write|delete and deployments:read|trigger. Route tags
map onto them through one table in @repo/core, and the permission check
accepts the root grant when its level permits the action or it holds the
mapped capability. Levels are unchanged and imply the same capabilities.
Mint checks the minter's reach per capability and rejects a capability on
the wrong type. MCP tools/list advertises tools by held capability. The CLI
--grant parser keeps the capability's colon.
CLI domain registration created rows without routing targets.
Attach custom public endpoints through the shared project update flow,
mirroring the dashboard while preserving existing routes.
Fixes#1021
`openship api /api/projects/<id>` requested /api/api/... because the
client always prefixes /api; a leading /api segment is now stripped.
`project env set <id> KEY=VALUE` failed with "too many arguments"; the
pairs are now accepted next to --set. A 401 from a project command now
adds "Run `openship login` first.", as server and service commands do.
Fixes#1023
Route API, platform, deployment, background, Desktop, CLI and browser failures through a bounded redacting reporter with request and operation correlation. Preserve operation behavior and provider-specific credential sanitizers.
Add public browser intake, safe exporter and shutdown behavior, coverage audits in CI and release gates, and regression tests for correlation, privacy, stream semantics, backpressure and real API/browser delivery.