chore: back-merge main into dev to clear v0.2.13 release-PR conflicts

[w7-mgfcode]

Problem

The dev → main release PR (#201) reports merge conflicts. main carries 2 commits not on dev — the chore(main): release 0.2.13 release-please commit and the prior release-cut merge — and the post-v0.2.13 work on dev (inventory-status endpoint, Demand Planner / PRP-22, INITIAL relocation) touches regions that main's squashed release history represents differently, producing phantom conflicts.

Resolution

Back-merge origin/main into dev via this PR. Analysis confirmed all 11 conflicted files resolve cleanly to dev's version — dev is a strict superset of main (every "main-unique" line is a reformatted/relocated form of content dev already carries in newer shape). The resolved merge tree is byte-identical to dev's tip; the merge only records main's history as a second parent.

Effect

Once merged, dev contains main, and release PR #201 becomes conflict-free.

[w7-mgfcode]

Done in #203 (merged to dev). Closed manually — the PR targeted dev, not the default branch.

[w7-mgfcode]

Reopening — PR #203 was squash-merged, which flattened the two-parent merge commit into a single-parent commit (6c728e7). main therefore never became an ancestor of dev, and release PR #201 still reports the same 11 conflicts. A back-merge only works if it lands as a real merge commit. Redoing via a new PR that must be merged with "Create a merge commit".

[w7-mgfcode]

Done in #204 (admin-merged to dev as a merge commit). main is now an ancestor of dev.