chore: release v1.5.1

[RNA4219]

Bump package/runtime metadata to 1.5.1, update README/CHANGELOG/distribution status, and prepare the security-gate hardening release package.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e0a6b17cbe

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Do not mark v1.5.1 as published before it exists

When users follow this distribution source of truth after the release bump, this row says v1.5.1 was already published on GitHub, but the public GitHub releases page currently lists v1.5.0 as the latest release and has no v1.5.1 entry. Until the v1.5.1 tag/release is actually available, README.md and this table point users to a non-existent release and make the GitHub/source install evidence misleading; publish the release first or keep the status at v1.5.0/pending.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Add the 1.5.1 release approval record

For the new v1.5.1 alignment section, the document still claims the Release Approval Record is synchronized, but docs/releases/INDEX.md stops at 1.5.0 and rg '1\.5\.1' docs/releases has no matches. The release checklist requires creating a docs/releases/RA-YYYYMMDD-XX.md record and adding the approval mapping, so release evidence consumers cannot verify approval for the advertised release; add the 1.5.1 RA/index entry or mark approval as pending.

Useful? React with 👍 / 👎.

[github-actions]

code-to-gate PR Review

Gate Verdict

• Status: pass
• Readiness: passed
• Findings: 1 total, 0 critical, 0 high

Blocking Reasons

• No blocking reason was found.

Acceptable Risks

• [info] Readiness verdict is passed: All policy conditions met, release ready
• [info] No unsupported claims are present: LLM or imported claims that lack evidence are not present in findings.unsupported_claims.
• [info] Public docs, CLI, schema, and schema coverage are aligned: 8 spec drift checks passed without failures.

Suggested Tests

• [medium] Run src/cli/tests/exit-codes.test.ts: Test path matched changed source path. Command: npm test -- src/cli/tests/exit-codes.test.ts Source: test-plan-001, src/cli/exit-codes.ts
• [medium] Run src/core/tests/database-analyzer.test.ts: Test path matched changed source path. Command: npm test -- src/core/tests/database-analyzer.test.ts Source: test-plan-002, src/core/database-analyzer.ts

Spec Drift

• No spec drift was found or no spec-drift artifact was provided.

Drift Budget

• No drift budget summary is available.

Evidence Links

• Release readiness: .qh/release-readiness.json schema: release-readiness@v1 hash: 3e6a1684b7eafa72
• Findings: .qh/findings.json schema: findings@v1 hash: 93454816f4f81431
• Auto test plan: .qh/test-plan.json schema: test-plan@v1 hash: 36f7656d9f0f530e
• Spec drift: .qh/spec-drift.json schema: spec-drift@v1 hash: b112da43c76694d8
• Evidence DAG: .qh/evidence-dag.json schema: evidence-dag@v1 hash: a07a0790fa4187be
• QEG evidence input: .qh/qeg-code-to-gate.json schema: ctg.qeg-input/v1 hash: 77d4be15ff92536a
• Published quality report: https://github.com/RNA4219/code-to-gate/actions/runs/29904287067

Suppression / Baseline Summary

• No baseline summary is available.

Gate Explainability

• No gate explainability summary is available.

---

Generated by code-to-gate v1.5.1