[abrichr]

What kind of change does this PR introduce?

Release preparation: openadapt (launcher) 1.21.0 on openadapt-flow 2.7.0.

Summary

Versions: openadapt 1.20.0 -> 1.21.0 (minor). The Flow floor moves to >=2.7.0,<3.0.0 in the base install and every Flow extra.

This PR is stacked on #2123 (Flow 2.7.0). Until #2123 merges, its diff includes that PR's commits. Main already has the launcher's openadapt wrap command, but it only works with a Flow that ships openadapt_flow.wrap, and Flow 2.6.0 doesn't. The launcher's help also uses replay --demo-app, which is new in Flow 2.7. Launcher features since 1.20.0 justify a minor bump.

Changelog (CHANGELOG.md, ## v1.21.0):

• openadapt wrap runs one agent task once, checks the saved record, then replays the compiled program with new inputs and no model calls. --serve offers it as a local stdio MCP tool.
• openadapt record, compile and run forward to Flow, and run summaries show the result, next step and report location.
• openadapt --help groups commands into the same 15 tasks as Flow. Earlier names still work.
• openadapt doctor checks macOS Accessibility and Screen Recording access. --recording checks Capture and FFmpeg, and --install-browser downloads Chromium.
• Upgrade notes: abbreviated long options are rejected. Replay needs --url, backend.url or --demo-app.

Blocked until Flow 2.7.0 is on PyPI

Two required release inputs can't be produced before that, so this stays a draft:

1. Root uv.lock: it resolves openadapt-flow from PyPI, so uv lock can't select 2.7.0 yet. uv lock --check currently fails. The editable launcher entry is already stamped at 1.21.0 (scripts/verify_release_lock.py passes).
2. platform-manifest.json and docs/platform-compatibility-report.md: generate_platform_manifest.py reads PyPI and refuses an unpublished version. validate_platform_manifest.py --offline --launcher-candidate currently fails on launcher_requires drift (>=2.6.0 vs >=2.7.0). Regenerate with --component-version flow=2.7.0 and the other current published versions. The manifest still records launcher 1.19.0 and Desktop 0.25.1, while PyPI serves 1.20.0 and 0.28.1. Pick the reviewed Desktop version at that point.

After #2123 publishes: run uv lock, regenerate the manifest and report, re-run the checks below, mark this ready, and get approval. Then dispatch release-and-publish.yml -f version=1.21.0.

Checklist

• Built Flow 2.7.0 and launcher 1.21.0 wheels into a fresh Python 3.12 venv. openadapt wrap --help exits 0 and lists every option. openadapt doctor reports [OK] openadapt_flow.
• Launcher tests: 1422 passed, 8 skipped (pytest tests). Ruff check passed, and the changed files are formatted.
• scripts/verify_release_lock.py and scripts/release_platform_versions.py --launcher-version 1.21.0 passed. scripts/check_source_boundary.py passed.
• scripts/check_release_health.py --self-test passed. The live run gives one expected alert: launcher work unpublished since 1.20.0, which this release clears.
• Lock and manifest refreshed against the published Flow 2.7.0 (blocked, see above)
• CI passes (the manifest check is expected to fail until then)

[abrichr]

The founder approved launcher 1.21.0 with Desktop 0.28.1 in the platform manifest. The manifest was regenerated at 93077ae. This merges on green, and the release is then dispatched from main.