release: prepare v0.4.0

[voorhs]

Prepares the v0.4.0 release.

0.3.3.dev0 was a development pre-release and was never promoted; 0.4.0 supersedes it and ships the compute feasibility advisor on top.

Changes

• pyproject.toml version → 0.4.0
• docs/source/conf.py release → 0.4.0
• CHANGELOG.md section for 0.4.0, covering everything merged since v0.3.3.dev0:
  • Feat/feasibility check #291 — compute feasibility advisor: new autointent.advisor subpackage, autointent-advisor console script, Pipeline.fit(preflight="off"|"warn"|"strict") gate, psutil promoted to a core dependency, new docs/source/advisor.rst page
  • the section intro also records that 0.4.0 promotes the 0.3.3.dev0 pre-release contents (OpenSearch copy-on-dump feat(vector-index): OpenSearch copy-on-dump into immutable generation indices (#343) #346, clear_ram()/reset() split fix(vector-index): split reset() from clear_ram(); restore fit-replaces for OpenSearch (#342) #345, inference_config.yaml tuple fix fix(pipeline): write inference_config.yaml with yaml.safe_dump so tuple-valued config fields reload #344, metadata-driven require(extra) feat(deps): metadata-driven require(extra) dependency guard #339) to a stable release

The changelog additionally flags one behavior change from #291 that is easy to miss: Pipeline.fit now runs validate_modules before building the Context, so preflight prices the modules that will actually run.

Verification

• make schema produces no diff — nothing since v0.3.3.dev0 altered the generated optimizer JSON schema.
• uv sync + importlib.metadata.version("autointent") reports 0.4.0.
• autointent-advisor --help and import autointent both work in the synced env.
• Every claim in the changelog section was checked against the source (advisor __all__, CLI flags, PRESET_COST_ORDER, the DataConfig findings in advisor/_runner.py, and the Pipeline.fit diff). PreflightMode is defined next to Pipeline, not re-exported from top-level autointent — the note is worded accordingly.
• Docs build (make test-docs, make docs) left to CI on this PR.

Notes for release day

• Tag v0.4.0 on the merge commit and publish a GitHub Release — that triggers the PyPI publish (.github/workflows/release.yaml) and the multi-version docs deploy.
• Unlike v0.3.3.dev0, this tag will appear in the docs version switcher (versions_generator.py matches ^v\d+\.\d+\.\d+$), so it becomes stable on the live site.
• The advisor is documented as experimental: its estimates are heuristic, validated end to end on one hardware class only, and its Python surface may change in a minor release.

🤖 Generated with Claude Code