Vericore

Vericore 0.8.0 Release Readiness & Release Record

Status: Released — Vericore v0.8.0 was published on 2026-10-04.

This document preserves the pre-release certification contract and records the final published release state. The checklist and workflow descriptions below are historical release evidence for v0.8.0; future releases should use the same release workflow and certification model with their target version.

Published release state

• Release: v0.8.0
• Published: 2026-10-04
• Published release: v0.8.0
• 0.8.0 preparation PR: #131 — merged
• 0.8.0 release hardening PR: #132 — merged
• Certified release ref: main
• Certified and released SHA: ccf15df7ec4cfd378465862fab9d926c1ac756c1
• Git tag: v0.8.0
• Release publication: completed by release.yml after release certification passed
• Local end-to-end execution: not required for release certification; GitHub Actions is the authoritative clean-environment execution path

The final candidate was certified before publication. The published tag points to the certified main commit above. Post-release documentation is maintained separately from the immutable release commit.

Workflow responsibility matrix

Workflow	Class	Responsibility	Unique value	Release-certification role
dco.yml	Governance	Commit sign-off enforcement	DCO compliance	Independent governance gate
ci.yml	Reusable permanent CI	Windows build, tests, and distribution verification	Windows CI environment	Called by release certification
verification.yml	Reusable product verification	Linux build, tests, CLI, intelligence, REST, and security boundaries	Broad product verification	Called by release certification
platform.yml	Reusable platform verification	Linux, Windows, macOS Intel, macOS ARM distribution smoke	Cross-platform packaging	Called by release certification
onboarding-e2e.yml	Reusable product E2E	Fresh-user setup/doctor and clean Git fixture	Onboarding coverage	Called by release certification
phase1-regression.yml	Reusable regression	Repository-scoped configuration/output/failure semantics	Historical regression coverage	Called by release certification
phase4-regression.yml	Reusable regression/security	Repository scope, traversal, and evidence containment	Engineering-workflow safety	Called by release certification
live-output-quality.yml	Reusable release E2E	Real-repository CLI/output quality	User-visible output validation	Direct certification dependency
live-repository-gate.yml	Reusable release E2E/security	Real-repository contracts, stale state, mutation detection, MCP/REST, immutability	Adversarial release validation	Direct certification dependency
release-audit.yml	Release certification	Composes the complete product/release verification graph	One authoritative candidate decision	Authoritative certification workflow
release.yml	Publishing	Version verification, packaging, checksums, GitHub Release publication	Actual release publication	Runs certification before publication

Workflow architecture

                    release-audit
                          │
       ┌──────────────────┼──────────────────┐
       │                  │                  │
 product/platform    regressions        live E2E
 onboarding/Windows                       │
       │                           Petclinic/RuneLite
       └──────────────────┬──────────────────┘
                          │
                 readiness certificate
                          │
                     release.yml

The reusable workflows own their execution logic. release-audit.yml composes them rather than duplicating their tests. DCO remains independent because repository governance is separate from product certification.

Certification contract used for 0.8.0

release-audit.yml certified, at minimum:

1. deterministic build/test/distribution behavior;
2. Windows CI;
3. Linux product verification;
4. Linux/Windows/macOS packaging smoke;
5. onboarding E2E;
6. Phase 1 regressions;
7. Phase 4 safety regressions;
8. Spring Petclinic live repository integrity;
9. RuneLite live repository integrity;
10. Spring Petclinic output quality;
11. RuneLite output quality.

Only after every required dependency succeeded could the readiness-certificate job produce overallReady: true.

Machine-readable readiness certificate

The release audit produces release-readiness-<version>.json, defined by docs/release-readiness.schema.json and generated by scripts/audit/release-readiness.py.

The certificate binds:

• exact candidate SHA;
• candidate ref;
• application version;
• required certification-job results;
• certificate schema version;
• generation timestamp;
• final overallReady decision.

It fails closed: a failed, cancelled, skipped, neutral, or missing required certification cannot produce a ready certificate.

For 0.8.0, the final readiness evidence certified the release candidate before publication.

Publication gate used for 0.8.0

release.yml invoked the release audit before version resolution, packaging, or publication.

main candidate
      ↓
release-audit
      ↓
all required verification
      ↓
readiness certificate
      ↓
version/package verification
      ↓
platform artifacts + checksums
      ↓
GitHub Release

Certification initially encountered a live AI output-quality failure. The release was not published until the failed certification was rerun successfully. This preserved the fail-closed release boundary rather than weakening the gate.

Documentation policy used for 0.8.0

The 0.8.0 documentation freeze occurred before publication. The final certification candidate included:

• the complete CLI reference;
• current architecture and safety contracts;
• current REST and MCP contracts;
• current implementation-status documentation;
• current release-readiness information;
• no duplicate or superseded internal release-planning documents presented as public product documentation.

The documentation changes in the separate post-release documentation branch update release-state language without modifying the published v0.8.0 commit.

Final release gate — completed

• all required GitHub Actions checks were green on the exact final candidate;
• the readiness certificate identified the exact candidate SHA, ref, and version;
• real-repository gates proved expected behavior and repository immutability;
• platform, onboarding, Windows, Linux, regression, and live-repository evidence were included;
• CLI documentation matched the implemented command surface;
• release.yml published only after successful certification;
• v0.8.0 was published successfully from the certified candidate.

This site is open source. Improve this page.