v0.7.0

v0.7.0 — Public-fixture CI gate

Version 0.7.0 adds a gate for two explicitly public CI fixtures. Publication requires both live fixture gates and sanitized evidence retention to succeed after the existing tag, CI and artifact checks. Use the versioned release for installation and inspect its run and retained evidence; the validation matrix records historical checks and their limits.

Version 0.7 integrates the public CI pilot. It adds a reference driver, two fixed 488-byte public skill versions, their SHA256 manifest and a release gate. It does not scan the product distribution, source, logs or dependencies, and does not execute the fixture's instructions.

• The driver reuses the existing consent-bound submission, durable receipt recovery and selected-analysis CLI. It permits no automatic POST retry or substitution of a newer file report for a selected analysis.
• Policy public-fixture-v1 distinguishes allow, review, block, pending, unknown and error. It requires explicit coherent evidence and at least one completed harmless/undetected engine; partial failures remain visible. Allow is not a safety guarantee.
• CI runs eight synthetic policy cases without a VTAI secret and checks whether a simulated publication marker was actually created. These tests do not claim live intelligence or publish anything.
• Release installs the exact previously verified CI wheel before exposing the stable VTAI_CI_TOKEN to either live fixture step. Both fixture gates and sanitized evidence retention must succeed before publication. Existing tag, commit, manifest and distribution checks remain required; release reuses the reviewed artifacts without rebuilding.

The package keeps its five read-only MCP tools, explicit local submission CLI and opt-in Codex guard. Durable recovery and Linux kernel seal checks remain part of this version. Default invocation still starts stdio; no upload tool, daemon, client-specific SDK or new dependency is added.

The gate depends on the compatible deployed VTAI analysis API, a dedicated stable credential configured outside model context, ordinary quota and the two exact public files. Missing access, permanently unknown receipt state or an unfinished analysis prevents publication. No automatic registration or identity rotation bypasses those limits.

Validation and distribution

Check	Evidence or requirement
Eight synthetic policy cases in actual GitHub Actions	Observed; no live VTAI submission or real publication
Live gate for both public fixture versions	Required for each release, with both allow decisions and retained evidence
Artifact review, publication and installation from the release	Verify the selected tag/run, exact checksums and installation result

Consumer guides and configuration examples are included in the sdist. The CI
driver, fixtures and workflows require the complete tagged source checkout,
with the matching verified wheel; neither the wheel nor installation sdist
includes them. See driver setup.

This documentation describes the implemented contracts. It does not turn a
synthetic pass into live acceptance or an existing report into a new submission.