Release Proof

This page is the public verification index for the current AGILAB release. It records install, CI, demo, and scope evidence in one place so reviewers can check the release without inferring status from scattered badges.

Current public release

Item

Public evidence

Package version

agilab[examples]==2026.06.02 on PyPI

GitHub release

v2026.06.02

Hosted demo

jpmorard/agilab at Space commit 16550e41fef275c591f0bb61fa8d047f8445c177

Public guardrails

repo-guardrails run 26689378396 passed repository guardrails and clean package first-proof jobs

Docs source guard

docs-source-guard run 26689378393 passed docs mirror and release-proof consistency checks

Docs publish

docs-publish run 26689378410 built the public documentation from the managed docs mirror

Coverage

coverage run 26688486033 passed component coverage and badge freshness checks

PyPI publish

pypi-publish run 26688683355 passed the public release proof workflow gate

What was proved

  • A clean package install can run the public first proof:

    python -m pip install "agilab[examples]==2026.06.02"
python -m agilab.lab_run first-proof --json --max-seconds 60

  • The public GitHub Actions matrix validated the packaged first proof on Ubuntu, macOS, and Windows runners.

  • The release proof records the hosted Hugging Face Space URL and commit. Live public-demo availability is checked only when a public-demo-smoke run is pinned or supplied separately.

  • The checked-in docs/source/data/ui_robot_evidence.json records the pinned release UI robot matrix evidence, including app/page/widget counts and zero detected UI failures for that run. Use tools/ui_robot_coverage_contract.py --json and the local ui-robot-matrix profile to verify the current checkout after apps are added or removed.

  • The public demo scope includes the lightweight flight_telemetry_project and weather_forecast_project routes documented in AGILAB Demo and aligned with the packaged examples catalog.

  • The release tag, PyPI package, public documentation, and hosted demo point to the same public product story: browser preview, local first proof, then source-checkout expansion.

How to verify it again

Use the package route when you want to prove the released artifact rather than the current source checkout:

python -m venv .venv
. .venv/bin/activate
python -m pip install --upgrade pip
python -m pip install "agilab[examples]==2026.06.02"
python -m agilab.lab_run first-proof --json --max-seconds 60

Use Quick-Start when you want the fuller source-checkout path with the built-in app installation and Streamlit UI.

Maintainer refresh

Maintainers can refresh the manifest from local release evidence and GitHub Actions evidence, render the page, and run the same consistency checks with one command:

uv --preview-features extra-build-dependencies run python tools/ui_robot_evidence.py --compact
uv --preview-features extra-build-dependencies run python tools/release_proof_report.py --refresh-from-local --refresh-from-github --render --check --check-github-runs --compact

Pass --github-release-tag, --github-release-url, --hf-space-commit, or --github-head-sha only when public evidence changes outside the default local repository and latest successful main workflow state. Use tools/ui_robot_evidence.py --run-id <run> when the release should pin a specific UI robot evidence run.

Scope and limits

This evidence proves the public package smoke, hosted demo identity, and documented first-proof routes. It proves live hosted-demo availability only when a public-demo-smoke run is pinned or supplied separately. It does not certify every remote cluster topology, every GPU stack, private app repositories, cloud accounts, security posture, or long-running production operations. Those areas remain environment-dependent and are tracked in Compatibility Matrix.