chore: versioning hygiene pass

[PAMulligan]

Summary

Versioning hygiene pass across Aurelius: reconciles package.json with the
latest tag, audits open milestone descriptions, reviews the CHANGELOG, and
confirms the release config is aligned with Nerva's canonical setup.

No feature code, CI workflows, CHANGELOG history, or tags were touched.

Sub-task status

• Sub-task 1 — Reconcile package.json with latest tag — Applied.
  Bumped "version" from 0.5.0 to 1.0.0 to match the existing v1.0.0
  tag. No workspace packages exist (no pnpm-workspace.yaml, no workspaces
  field), so package.json is the only file updated.

• Sub-task 2 — Milestone descriptions — Applied (proposals only).
  Captured both open milestones (v1.1.0 Pixel-perfect Figma alignment for Score and Setup pages #1, v2.0.0 chore(deps): Bump undici from 7.22.0 to 7.24.4 in /app #2) and drafted
  proposed canonical-format rewrites in docs/milestones-proposed.md.
  Neither current description matches the canonical
  one-sentence-summary + bullet-list + Focus: format, so both are
  proposed rewrites with rationale. No milestone descriptions on GitHub
  were edited.

• Sub-task 3 — CHANGELOG audit — Already correct (no action required).
  gh api repos/PMDevSolutions/Aurelius/milestones?state=closed --paginate
  returned an empty array — there are no closed milestones. Therefore no
  CHANGELOG sections needed appending. The existing [0.5.0] - 2026-03-23
  section was left untouched as instructed.

• Sub-task 4 — Release config — Already correct.

  • All six release* scripts in package.json match Nerva exactly
    (release, release:minor, release:major, release:patch,
    release:dry, release:first).
  • commit-and-tag-version ^12.7.1 is present in devDependencies (Nerva
    is on ^12.7.3 — see ambiguity note below).
  • .versionrc.json matches Nerva structurally (same header, types,
    commitUrlFormat, compareUrlFormat, tagPrefix). The only
    divergence is an intentional Aurelius-specific
    scripts.postchangelog hook that runs scripts/extract-release-notes.js
    (the script exists in the repo). Left as-is because removing it would
    delete intentional functionality.

Discrepancies and ambiguities flagged for human review

1. Tag v1.0.0 has no matching milestone and no matching CHANGELOG section.

   • The v1.0.0 tag points at commit e3d50b9 dated 2026-03-19.
   • There is no closed milestone titled v1.0.0 (no closed milestones at
     all).
   • CHANGELOG.md has a [0.5.0] - 2026-03-23 section but no [1.0.0]
     section. The 0.5.0 section's date (2026-03-23) is after the v1.0.0
     tag date (2026-03-19), which suggests the CHANGELOG and tags may have
     drifted out of sync historically.
   • Question: Should a [1.0.0] CHANGELOG section be written manually
     based on commits between repo init and the v1.0.0 tag? I did not
     invent one per the hard constraints.

2. commit-and-tag-version version drift vs Nerva.

   • Aurelius: ^12.7.1. Nerva: ^12.7.3. Both satisfy ^12, but if you
     want exact alignment, bump Aurelius to ^12.7.3 in a follow-up
     dependency-bump PR (out of scope for this hygiene pass).

3. Open milestone v1.1.0 due date has passed.

   • Due 2026-05-31, with 4 open issues and 49 closed issues. Not in
     scope to change here, but flagging for visibility — may want to
     extend the due date or close the milestone.

Files changed

• package.json — version bump 0.5.0 → 1.0.0
• docs/milestones-proposed.md — new file with canonical-format proposals

The following pre-existing untracked files were intentionally left
untracked, per the task instructions:

• .claude/visual-qa/dashboard/dashboard.html
• docs/plans/2026-04-14-stryker-mutation-testing.md
• docs/plans/2026-04-15-storybook-auto-generation-design.md
• docs/plans/2026-04-15-storybook-auto-generation.md

Test plan

• Confirm package.json version 1.0.0 matches the latest published tag.
• Review docs/milestones-proposed.md and decide whether to apply each
  proposal to the GitHub milestone descriptions (v1.1.0, v2.0.0).
• Decide on action for the v1.0.0 CHANGELOG gap (write a backfilled
  section, leave as-is, or create a milestone retrospectively).
• No tags created, no git push --tags ran, no CI workflows touched,
  no CHANGELOG history rewritten.

---

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com