release: v0.3.0 — governance leaderboard, 60-case corpus, Apache-2.0

[bkd-dotcom]

Cuts signetry-eval v0.3.0: the Agent Governance Leaderboard, the 60-case OWASP
detection corpus, and the Apache-2.0 relicense.

Unreleased → [0.3.0] — 2026-09-01, pyproject.toml → 0.3.0, the signetry-core
dependency moves to the v0.8.0 release, and uv.lock is regenerated against it
(rev=v0.8.0#ee974f3). Local ruff + pytest green on that lock.

The leaderboard's version label is left alone on purpose

docs/LEADERBOARD.md and docs/LEADERBOARD.json say signetry-core 0.7.0. That is not
a stale pin to sweep — it is the version the numbers were measured against, and
hand-editing it to 0.8.0 would assert a measurement that never ran. It is the same
mistake as scoring a scanner that did not run as zero, which this repo exists to avoid.

leaderboard.yml already triggers on release: types: [published] and installs core
from pyproject.toml, so publishing this release re-measures against v0.8.0 and the
label updates itself, derived rather than declared.

One false claim corrected

SECURITY.md's supported-versions table read:

0.2.3 | ✅ current — 7-language detection corpus, pinned real-repo cases, signetry-core v0.7.0

But "Fixed — pinned real-repo cases were not actually pinned" is in this release's
changelog section, not 0.2.3's. So 0.2.3 was being advertised as having a fix it
did not have, on the page a security reader trusts most. It moves into the superseded
range (0.2.0–0.2.3), whose note already describes exactly that defect.

[github-actions]

Signetry Reviewer — 🟣 Escalate to a designated reviewer

Escalate to a designated reviewer — this PR touches security-sensitive surface (.github/workflows/reviewer.yml). No blocking issue was found automatically, but a human owner should sign off.

Deterministic gates (the authority)

Gate	Status
Required status check	— unknown
Secret scan	✅ clean
CI permission / OIDC	✅ no forbidden change
Dependency skew	✅ ok
All green	❌

Findings (2, 0 blocking)

• 🟡 Change touches a protected path: .github/workflows/reviewer.yml .github/workflows/reviewer.yml (via cross-check)
  • .github/workflows/reviewer.yml matches a protected pattern (.github/workflows/*). Changes here alter shared/foundational surface and warrant a designated reviewer.
  • Fix: Route to a code owner / architecture reviewer.
• 🟡 Change touches a protected path: pyproject.toml pyproject.toml (via cross-check)
  • pyproject.toml matches a protected pattern (pyproject.toml). Changes here alter shared/foundational surface and warrant a designated reviewer.
  • Fix: Route to a code owner / architecture reviewer.

Sensitive surface

This PR changes security-sensitive paths that warrant a designated reviewer:

• .github/workflows/reviewer.yml

Merge

A designated reviewer / code owner should sign off before merge (sensitive surface).

This review is advisory. It never merges on its own judgement — the deterministic gates + a human are the authority. Findings can have false negatives; a green bot verdict is not a guarantee.