convex-optimize

Run the optimize workflow, which delegates to launch-readiness for a single scored, deduplicated report across authz, reviewer, advisor, and insights passes. It returns an ordered fix plan prioritizing security and data-loss risks, applied only after your confirmation.

The workflow runs check-updates against your pinned @convex-dev/* components and folds staleness findings into the same remediation plan as the security audit. Upgrades are presented for confirmation and never auto-applied to a production app.

No. It is read-only first: it presents a combined prioritized plan and applies changes only on explicit confirmation. After applying fixes, it re-runs the launch-readiness assessment to show the score delta.

Yes. If the readiness report flags an observability gap such as missing production error capture, the workflow offers to install the sentinel component as part of the confirmed remediation plan.

Avoid it for brand-new apps without an existing convex/ directory and schema, since it is designed to remediate existing deployments. It also does not re-implement the audit itself; use launch-readiness directly if you only need a scored report without remediation actions.