Release versioned merges automatically #68

Outcome

Automatically publish the exact Model Router version merged into main, then let existing Toolybara reconciliation promote the release. This advances the Objective's released, installable routing contract.

Acceptance criteria

• A VERSION change on main runs complete deterministic proof and exact-commit version validation before an annotated tag or stable GitHub Release is created.
• Use githubReleasePolicy: on-version-commit. Keep source release, Marketplace promotion and local installation as distinct verified states.
• Reuse released AgentsMD versionctl at a pinned commit; preserve existing tags and releases. Resume partial publication only for the same annotated tag and exact commit.
• Use the repository token for source publication and Toolybara's existing hourly scan for promotion. Add no credentials or host services.
• Run the complete suite with disposable dependency fixtures in read-only PR CI and before release. Keep production validation and negative dependency tests active.
• Document release and recovery. Preserve routes, role kits, runner behavior and Project Direction. Complete tests, version validation, workflow lint and independent exact-candidate Astra/high review pass.

Delivery and proof

PR #70 merged as ce936626a59422ab91ba2835fa0b7d90009883bf. Automatic release run 35879925964 passed complete proof and published v0.25.1.

Exact reviewed head: f5f67d9f3eece67b21194317735f82c7f01e87f2; independent Astra/high review found no issues. Full suite: 515 tests passed locally and in Ubuntu CI, with documented opt-in/platform skips. Compile, version validation and workflow lint passed. Release uses the same read-only proof workflow before publication.

The user explicitly authorized the remaining marketplace prerequisite, promotion and host installation. Marketplace v1.5.0 is now published at 7e93c11d17b9bb0a6143f379468280d4ec703c0d. Toolybara is reconciling. Installation and real-task evidence belongs to #17; source-release acceptance is complete. No model calls or host services were started.

Task worktree and proof are retained until installation completes. Website impact: none, release tooling and repository documentation only.