Release gate: v0.3.0

[flyingrobots]

Tracks the v0.3.0 release cut. Issues in this release must carry lane:v0.3.0; goalpost issues stay on their goalpost milestones and this gate closes only when the scheduled v0.3.0 lane is complete and release policy passes.

[flyingrobots]

Initial future-release triage slate from the oldest-50 pass: #77, #88, #89, #90, #91, #92, #93, #94, #104, #105, and #106. Rationale: these are generic Holmes/reporting/security assurance hardening tasks that still belong in Wesley, but are later than the current residue cleanup and platform/onramp work.

[flyingrobots]

Triage update: this pass added #184 and #192 to lane:v0.3.0 / Goalpost: Make It Truthful. Rationale: both are generic Holmes/schema-hash assurance and adoption documentation work.

[flyingrobots]

Backlog triage update for v0.3.0.

Added or confirmed scheduled issues from the final inbox purge:

• Render SCS/TCI trendline in PR comment using MORIARTY history.json #228
• test(cert): cover negative SHIPME and certificate verification paths #442
• feat(evidence): make certified HOLMES/WATSON citations exact-span and digest-backed #448
• feat(holmes): make PR comments plain-English and glossary-backed #466
• HOLMES Moriarty option sharing #553
• EVIDENCE v2 certified evidence cutover and placeholder bundle removal #587
• schema(json): unify IR/evidence schema drafts across the spec family #456
• cool-ideas: add a Holmes evidence review CLI over weslaw artifacts #542
• cool-ideas: publish structured Holmes finding output for PR bots and CI #543
• Holmes Artifact Diagnostic Sidecar #577

These are evidence/HOLMES/schema-truth items that belong with the Make It Truthful release lane.

[flyingrobots]

Release workflow cleanup before rerun:

The tag publish workflow uses a broad open-issue search that also matches stale comments. This release gate is valid future work and remains open for its own scheduled release. I am only rewriting stale comment wording that names the current tag; issue state, labels, milestone, and scope are unchanged.

[flyingrobots]

Release workflow hygiene before editing stale comments:

This issue is scheduled future-release work, not unfinished work for the current tag. The tag publish workflow performs a broad open-issue search that also matches old comments, so I am replacing stale current-release wording in prior comments only. Issue state, labels, milestone, and scope are unchanged.