Bump version to 0.6.1, update release plan

[waltsims]

v0.6.1 combines: C-order migration, 29 ported examples, 47 parity tests, 3D PML fix, docs cleanup, infra removal.

Renumber: old v0.6.2 (examples) merged into v0.6.1, old v0.6.3 (features) becomes v0.6.2, old v0.6.4 (axisymmetric) becomes v0.6.3.

Greptile Summary

This PR bumps the package version to 0.6.1 and updates the release strategy document to reflect the consolidated scope of v0.6.1 (C-order migration + 29 ported examples + 47 parity tests + docs cleanup) and the downstream renumbering (old v0.6.3 → new v0.6.2 Tier 2 Features; old v0.6.4 → new v0.6.3 Axisymmetric).

• kwave/__init__.py — clean single-line bump; pyproject.toml uses dynamic = [\"version\"] with path = \"kwave/__init__.py\", so the build system will pick up the new version correctly without any additional changes.
• plans/release-strategy.md — the version roadmap table and the new "Phase 2.x: v0.6.x Point Releases" summary section are correctly updated. However, the older detailed subsections (## Phase 2.1, ## Phase 2.2, ## Phase 2.3) and the Testing Strategy / Implementation Order blocks further down the document still carry the old version labels and old scope descriptions, creating internal inconsistency in the planning document.

Confidence Score: 5/5

Safe to merge — only a version bump and planning document update with no production code risk.

The only code change is a one-line version string bump that is correctly sourced by the build system. The sole finding is a P2 documentation inconsistency in a planning file (stale Phase 2.1/2.2/2.3 sections not reconciled after renumbering), which does not affect runtime behavior or release correctness.

plans/release-strategy.md — stale Phase 2.1/2.2/2.3 sections, Testing Strategy version labels, and Implementation Order list should be cleaned up to match the new numbering.

Important Files Changed

Filename	Overview
kwave/init.py	Single-line version bump from 0.6.0 to 0.6.1; pyproject.toml dynamically sources version from this file via hatchling, so no other version files need updating.
plans/release-strategy.md	Version roadmap table and Phase 2.x summary block updated to reflect merged v0.6.1 scope and renumbered v0.6.2/v0.6.3; however Phase 2.1/2.2/2.3 detailed sections, Testing Strategy version labels, and Implementation Order list were not updated, leaving stale content inconsistent with the new numbering.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[v0.6.0\nPython Solver + Unified API] --> B[v0.6.1 ✅ released 2026-03-29\nC-order + 29 Examples + Docs]
    B --> C[v0.6.2\nTier 2 Features + Examples\ntime-reversal, rect sensors, sound_speed_ref]
    C --> D[v0.6.3\nAxisymmetric Support\nkspaceFirstOrder axisymmetric=True]
    D --> E[v0.7.0\nCLI kwp]
    E --> F[v1.0.0\nClean Release\n-79% code reduction]
    F --> G[v2.0.0\nPerformance & Scale\nnanobind CUDA, MPI, Devito]

    subgraph "Renumbering in this PR"
        OLD1["old v0.6.1 C-order only"] -. merged into .-> B
        OLD2["old v0.6.2 Examples"] -. merged into .-> B
        OLD3["old v0.6.3 Tier 2 Features"] -. renumbered .-> C
        OLD4["old v0.6.4 Axisymmetric"] -. renumbered .-> D
    end

Loading

Comments Outside Diff (1)

1. plans/release-strategy.md, line 127-218 (link)

   Stale Phase 2.1/2.2/2.3 sections not updated to match renumbering

   The PR correctly updated both the version roadmap table (lines 9–18) and the "Phase 2.x: v0.6.x Point Releases" summary block (lines 221–274). However, the three detailed phase sections further up in the document were not reconciled with the renumbering:

   • Line 127 — ## Phase 2.1: v0.6.1 - C-order Migration (Helpers) still describes v0.6.1 as only the C-order helpers migration (the old scope). The combined scope (C-order + examples + docs) shipped in this release is only reflected in the new "Phase 2.x" block below.
   • Line 159 — ## Phase 2.2: v0.6.2 - Example Migration describes work that was folded into v0.6.1 in this PR. It no longer corresponds to any future release.
   • Line 192 — ## Phase 2.3: v0.6.3 - Axisymmetric Support still uses the old v0.6.3 label; the roadmap now calls this v0.6.3 (previously v0.6.4), so the section title is accidentally correct — but its content duplicates/diverges from the updated "Phase 2.x" block.

   Additionally, the Testing Strategy (v0.6.1 (C-order migration):, v0.6.2 (example migration):, v0.6.3 (axisymmetric):) and the Implementation Order list at the bottom both still reference the old version numbers, making those sections inconsistent with the updated roadmap.

   Consider either removing the now-redundant Phase 2.1/2.2/2.3 sections (since "Phase 2.x" covers the same ground in updated form) or updating them in place to match the new numbering. Similarly, update the version labels in the Testing Strategy and Implementation Order sections to reflect the merged release.

_{Reviews (1): Last reviewed commit: "Bump version to 0.6.1, update release pl..." | Re-trigger Greptile}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.40%. Comparing base (22c4c8e) to head (047b1bf).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #694   +/-   ##
=======================================
  Coverage   74.40%   74.40%           
=======================================
  Files          56       56           
  Lines        8026     8026           
  Branches     1570     1570           
=======================================
  Hits         5972     5972           
  Misses       1437     1437           
  Partials      617      617           

Flag	Coverage Δ
3.10	74.40% <100.00%> (ø)
3.11	74.40% <100.00%> (ø)
3.12	74.40% <100.00%> (ø)
3.13	74.40% <100.00%> (ø)
macos-latest	74.38% <100.00%> (ø)
ubuntu-latest	74.38% <100.00%> (ø)
windows-latest	74.39% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.