Vericore

Vericore 0.8.2 Release Readiness

Status: Published — historical release record.

v0.8.2 was published on 2026-10-04. This document preserves the certification contract and final release evidence for that immutable release; the current main branch contains later, unreleased hardening.

Release identity

Field	Published release
Version	0.8.2
Previous published release	v0.8.1
Release line	0.8.x
Published tag	v0.8.2
Published SHA	9b76f01501998324e59dc8a406c7e893a074ca59
Publication date	2026-10-04

Release scope

This patch release contains the post-0.8.1 audit remediation and release hardening that was certified for the published v0.8.2 artifact set.

Functional remediation

• Diagnostic failures use meaningful non-zero exit semantics.
• Validation failures use controlled application/CLI errors rather than raw stack traces.
• Repository-QA evidence retains concrete dependency/dependent paths.
• Architecture dependency edges are persisted deterministically.
• Architecture drift detects explicit EDGE_ADDED and EDGE_REMOVED changes.
• Organization-analysis hotspots serialize as explicit {file, score} objects.
• Regression coverage protects the historical 0.8.1 audit findings.

Machine-readable contract changes

• Organization-analysis hotspot output uses objects with explicit file and score fields instead of Kotlin Pair serialization.
• Architecture Intelligence artifacts use schema 1.1 and persist dependencyEdges so edge-level drift is deterministic.
• Historical schema 1.0 references remain historical where they describe older artifacts or fixtures.

Release engineering

• Application and Gradle version contracts are aligned to 0.8.2.
• Linux x64, Windows x64, macOS x64, and macOS ARM64 packaging is required.
• Bundled Java 21 runtime verification is required for packaged artifacts.
• SHA-256 checksums are generated by the release workflow.
• The exact candidate passed final release certification before packaging/publication.

Required certification

The release is ready only when all applicable checks are green on the exact candidate SHA:

• DCO
• deterministic release audit
• complete test suite
• CLI audit
• MCP protocol/gateway audit
• REST audit
• adversarial/safety contract audit
• onboarding E2E
• Phase 1 regression
• Phase 4 regression
• live-repository gate
• live output-quality audit
• Spring Petclinic live-project validation
• RuneLite live-project validation
• Linux x64 artifact build + bundled-runtime smoke
• Windows x64 artifact build + bundled-runtime smoke
• macOS x64 artifact build + bundled-runtime smoke
• macOS ARM64 artifact build + bundled-runtime smoke
• exact-candidate SHA/ref/version readiness verification
• generated artifact checksums

Version consistency

The following current-release sources must resolve to 0.8.2:

• build.gradle.kts
• src/main/kotlin/com/vericore/core/Version.kt
• current-version tests
• active release-preparation scripts
• current release documentation
• generated distribution metadata

Historical 0.8.1 release notes, audit fixtures, and the published v0.8.1 record must remain unchanged in meaning.

Observed certification evidence

The published v0.8.2 tag points to 9b76f01501998324e59dc8a406c7e893a074ca59. The exact tag SHA had successful Release Audit and Release workflow runs on 2026-10-04. The published release contains Linux x64, Windows x64, macOS x64, macOS ARM64 archives, and SHA256SUMS.

• Release Audit run
• Release run

Release rule

The published v0.8.2 tag was created only after release certification succeeded on the exact commit used for the published artifacts. Do not rewrite that tag or rebuild the historical release from a different commit.

main is now ahead of v0.8.2; post-release commits are development work and are not part of the published v0.8.2 artifact set.

This site is open source. Improve this page.