chore(release): prepare v4.7.6

[BenSheridanEdwards]

Why does this feature exist?

StyleProof PR #347 has landed on main, but the fixed report-consistency and Action behavior is not yet available through the deployed npm/Action release boundary. Fleet cannot safely consume the fix until StyleProof publishes a version whose immutable source revision includes that merged code.

This metadata-only release preparation moves the already-tested main state into v4.7.6. Merging this PR is the publish signal for the release workflow.

What changed?

• Bumped package.json from 4.7.5 to 4.7.6.
• Updated both root version entries in package-lock.json.
• Promoted the existing Unreleased report-consistency fix to [4.7.6] - 2026-08-06 in CHANGELOG.md.
• No runtime code changes are introduced by this commit.

Behavioural Proof (with video and screenshots)

Not applicable — this PR changes release metadata only. Runtime behavior was implemented and proven on the merged PR #347 exact head 4369af018af9f7bc62a65bce4e8d049a728af284; this release packages that main state.

Verification Summary

• npm ci --no-audit --no-fund — PASS
• npm test — PASS, 658/658
• npm run typecheck — PASS
• npm run lint — PASS
• npm run format:check — PASS
• npm run privacy:check — PASS
• npm run demo:check — PASS
• npm audit --audit-level=high — PASS, 0 vulnerabilities
• npm pack --dry-run --json — PASS; styleproof@4.7.6, expected dist and CLI bins included
• Runtime export import from dist/index.js — PASS
• git diff --check — PASS

Release boundary

• Current deployed npm release before merge: styleproof@4.7.5
• Current Action tags before merge: v4 / v4.7.5 at a40ad2631a9bd01f4967141b5847d4eaae12f697
• Intended release after merge: styleproof@4.7.6 with package gitHead matching the release commit, plus v4.7.6 and v4 tags moved by the release workflow.

[github-actions]

🗺️ StyleProof report

📊 View the side-by-side visual report →

---

Coverage, determinism, or report/diff consistency evidence is incomplete — repair the capture or reflow source; visual approval cannot clear this failure.