[abrichr]

Prepares the openadapt launcher 1.18.0. Nothing is published by this PR.

The release BOM pins openadapt-flow 2.3.0, openadapt-types 0.24.0 and openadapt-agent 2.2.1 from their monorepo release tags.

What changes

• Version: pyproject.toml is 1.18.0, and so is the editable entry in uv.lock.
• Flow floor: >=2.2.0,<3.0.0 in the base dependency and every extra, and in openadapt doctor / openadapt deploy (_SUPPORTED_FLOW_RANGE). tests/test_flow_floor.py and tests/test_cli_smoke.py follow. uv.lock resolves Flow 2.3.0, openadapt-types 0.24.0 and openadapt-agent 2.2.1.
• Changelog: ## v1.18.0 (2026-10-20) covers:
  • the three-act quickstart (feat(quickstart): show it once, run it, break it #1408) and its older-launcher-on-PATH warning;
  • openadapt pull (Add openadapt pull for registry workflows #1173);
  • uvx-aware next-step hints (fix(cli): quickstart's next steps reach the same version under uvx #1404);
  • copy and help fixes (Copy: describe the break-it run as a failed save, not an app that lies #1236, docs: fix approval-mode default, agent approval tools, and launcher serve help #1238, fix: CLI help and built-in URLs point at the docs glossary and the monorepo #1200).

Why Flow 2.2, not 2.0 or 2.3

I checked every openadapt_flow import, module attribute and keyword argument in openadapt/ against the Flow v2.0.0, v2.1.0 and v2.2.0 release tags.

• Missing in 2.0.0 and 2.1.0, used without a guard:

  • openadapt_flow._prewarm and openadapt_flow.backends._browser_process.shared_browser (FlowEngine.__enter__, the quickstart workers);
  • _browser_setup.BROWSER_ENV, installed_browser_channel and _bundled_present (worker browser choice).

  On 2.0 or 2.1 the quickstart fails with ImportError or AttributeError before Act 1.

• Missing in 2.0.0 and 2.1.0, guarded: openadapt_flow.offline_seal (no Seal is printed).

• Missing in 2.0.0 and 2.1.0, by subprocess: openadapt pull forwards to openadapt-flow pull, which first shipped in Flow 2.2.0.

• Present in 2.2.0: every import, attribute and keyword argument the launcher uses.

• The only Flow 2.3.0 addition used: run_tutorial_workflow(params=), which the quickstart feature-detects (_accepts). On 2.2.0 every run in Act 2 uses the demonstrated note.

Publish

After this merges and release-and-publish.yml is green on main:

gh workflow run release-and-publish.yml --repo OpenAdaptAI/OpenAdapt --ref main -f version=1.18.0

The workflow's only input is version, which must equal pyproject.toml. It first checks that the Flow and agent releases pinned in platform-manifest.json exist on PyPI with matching digests. Then the release App creates the v1.18.0 tag, and the tag push builds, publishes to PyPI and creates the GitHub Release. v1.18.0 doesn't exist on origin.

• BOM: platform-manifest.json and the report are regenerated with flow=2.3.0, types=0.24.0, agent=2.2.1. Launcher, capture, privacy and desktop keep their published pins. The BOM has one more dependency edge (13), because Flow 2.3.0 depends on openadapt-types.
• verify_release_components.py accepts a monorepo release (<package>-v<version> under packages/<dir>) as well as a standalone v<version> release. Tests cover both forms and three mismatches.

Local checks

• tests/test_flow_floor.py: 15 passed.
• The test_cli_smoke.py metadata, extras and preflight tests pass. One doctor test needs openadapt_flow installed and was left to CI.
• validate_platform_manifest.py --require-compatible --launcher-candidate passes online and offline.
• verify_release_components.py reports openadapt-flow 2.3.0 and openadapt-agent 2.2.1 matching PyPI and the manifest.
• The manifest, release-lock, component and flow-floor suites: 102 passed.
• verify_release_lock.py passes, and the prospect-name check is clean.

🤖 Generated with Claude Code