`MAZENG-FT-40` · Publish named semantic versions of a project

Feature intent

A team needs to mark meaningful project-file milestones with stable version identities and release notes.

Why it matters

A team needs to mark meaningful project-file milestones with stable version identities and release notes.

A correctly calculated tag and release identify the exact reviewed project files represented by a milestone.

Choose a major, minor, or patch increment from the latest semantic release.
Retain optional release name and notes.
Create a Git tag and release against the exact reviewed commit and report the immutable reference.

Acceptance

01
The user chooses major, minor, or patch incrementing.
02
Maze calculates the next version from the latest release, beginning at v0.0.0.
03
Optional release name and notes are retained.
04
A Git tag and release point to the exact committed project files.
05
Version publication reports the resulting version and immutable Git reference.

None recorded.

Version publication must follow completion of the reviewed file change rather than pull-request creation alone.
Legacy orchestration pushes, auto-merges, and releases immediately.
Legacy fixed-position version parsing fails for multi-digit components.

No authoritative Architecture tasks are linked.