chore(release): publish Dispatch 0.13.0

[galligan]

Context

main at e734dac carries the full stations/providers stack (#111–#122) on top of 0.12.0 with no published release. Releases are cut by CI only when pyproject.toml carries an untagged version, so this PR is the bump.

What changed

• pyproject.toml: 0.12.0 → 0.13.0
• uv.lock: project version line only

No code changes. When this merges, main CI tags v0.13.0, creates the GitHub Release, and dispatches the PyPI publish workflow.

Since v0.12.0

Provider-binding identity (schema v24), guarded binding-qualified routing, frozen provider requests (v25), correlated receipt observations (v26), independent provider startup/recovery, the Hermes local adapter with lane_launches (v27) and generation quarantine, operator diagnostics, packaged skills/docs, and the installed-wheel smoke. Registry schema moves 23 → 29; the release notes carry the migrate-before-start upgrade step.

Verification

• just check on this branch: ruff, format, mypy --strict, 1,367 tests (17 live tests deselected), wheel/sdist build reporting 0.13.0, package-content check.
• just release-status reports create GitHub Release v0.13.0.

Refs: DIS-96

[linear-code]

DIS-96

[galligan]

• chore(release): publish Dispatch 0.13.0 #124 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[galligan]

Merge activity

• Sep 14, 12:25 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Sep 14, 12:25 AM UTC: @galligan merged this pull request with Graphite.

[cursor]

PR Summary

Low Risk
Version-metadata-only change with no runtime code; risk is limited to release automation tagging or publishing the wrong version.

Overview
This PR only bumps the published package version from 0.12.0 to 0.13.0 in pyproject.toml and the matching outfitter-dispatch entry in uv.lock. There are no application or test changes in the diff.

That bump is the release gate: when it lands on main, CI should tag v0.13.0, create the GitHub Release, and run the PyPI publish workflow for the stations/providers work already merged since 0.12.0.

^{Reviewed by Cursor Bugbot for commit f35dc44. Configure here.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_19592f67-7aa8-4352-a77e-9ff4a633ff28)

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-14T00:27:56.720715Z	f35dc44	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.