chore(release): 0.11.1 — nav CTA contrast, contrast-optimal on-fill text

[bytesbrains]

Patch release for the #69 / #70 contrast fixes. Version bump + CHANGELOG only; tests green (180/180).

• nav CTA cascade fix (:not(.cta)) — CTA text keeps --on-primary in every state
• readableOn now picks the higher-contrast side (black/white) — mid-tone fills reach AA
• Measured: nav CTA 1.04–3.29:1 → 4.87–18.88:1 across all 6 presets; 133 templates inherit the fix

After merge: dev → main PR, then tag v0.11.1 on the merge commit.

🤖 Generated with Claude Code

[wrokin]

🤖 wrokin code review

The diff bumps package.json and package-lock.json to 0.11.1 and adds a CHANGELOG entry for two WCAG contrast fixes. No source-code changes are included, so there are no code-level bugs, security issues, or design violations to review.

• No high-signal issues detected in the version bump or changelog.
• The version is a non-breaking patch increment, consistent with semver and the described fixes.
• The changelog accurately describes the two accessibility fixes and links to issue nav CTA text renders in --muted instead of --on-primary — unreadable on all 6 presets and 133/160 templates (WCAG AA fail) #69.

Since no implementation diff is shown, a deeper SOLID/DRY assessment is not possible.

🌾 wrokin contribution signal

• The diff bumps version numbers in package.json, package-lock.json, and adds a changelog entry, but contains no source code or test changes — the nav CTA and readableOn fixes described in the title and description are not present.
• The PR claims to fix contrast issues, yet no CSS, logic, or test modifications appear; the diff alone does not deliver the stated intent. This could be a version-only release PR, but it is misrepresented as containing the fixes.
• If the actual fixes were merged in separate prior commits, the PR description should be updated; otherwise the changelog entry references changes that are not part of this diff and the PR cannot be verified as a valid release. Worth checking the branch history to confirm the fixes exist before accepting.

_{Advisory — signals worth a closer look, not a verdict or a score.}

_{Model: deepseek/deepseek-v4-pro · your key, your model (BYOK)}

[wrokin]

🤖 wrokin security audit

No security-relevant findings in this diff. The changes are limited to version bumps and a changelog describing CSS contrast fixes; there are no new code paths, no injection vectors, no authentication/authorization changes, no exposure of secrets, and no deserialization or other security-sensitive modifications.

_{Model: deepseek/deepseek-v4-pro · your key, your model (BYOK)}

[wrokin]

🤖 wrokin code review

Version bump only; no code changes in this diff. No bugs, security, or correctness issues to report.

🌾 wrokin contribution signal

• The diff includes only version bumps (package.json, package-lock.json, catalog files) and a CHANGELOG entry; it contains no CSS or logic changes for the "nav CTA cascade fix" or "readableOn" contrast improvements described in the title and description. Worth a closer look — the claimed fixes are not present in the PR.

_{Advisory — signals worth a closer look, not a verdict or a score.}

_{Model: deepseek/deepseek-v4-pro · your key, your model (BYOK)}

[wrokin]

🤖 wrokin security audit

No security-relevant findings in this diff. The PR is a version bump from 0.11.0 to 0.11.1, updating metadata in catalog, changelog, and package files; the changelog describes two WCAG contrast fixes with no security impact. No code paths related to injection, authz, secrets, unsafe deserialization, or other security concerns were changed.

_{Model: deepseek/deepseek-v4-pro · your key, your model (BYOK)}