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.

Note

The source checkout is intentionally ahead of the public release 2026.10.13. The package and links below still describe that exact published release.

Current public release

Item

Public evidence

Package version

agilab[examples]==2026.10.13 on PyPI

GitHub release

v2026.10.13

Dataset release

datasets-82d4b1accb144409 for 13 tracked dataset files; manifest 82d4b1accb144409af883b3600dab54400aa30cb65034e2c122307020b070d75

Hosted demo

jpmorard/agilab at Space commit 6a8e5051045111ce3908d775d48938a35d4a5364

Public guardrails

repo-guardrails run 38274133339 at commit a331e22acc1f passed repository guardrails for the release-proof metadata merge; skipped jobs remain out of scope unless separately evidenced

Docs source guard

docs-source-guard run 38274133146 at commit a331e22acc1f passed docs mirror and release-proof consistency checks for the release-proof metadata merge; canonical private-source drift is not checked by public CI

Docs publish

docs-publish run 38274133371 at commit a331e22acc1f deployed the release-proof metadata merge to public documentation

Coverage

coverage run 38254954532 at commit bb343922fc2d historical 2026.10.12 coverage baseline; project coverage 95.08%, agi-gui 95.92%; this is not a coverage measurement for the current release source

PyPI publish

pypi-publish run 38471746516 at commit 8dd841b0246f publication workflow for the recorded release commit; see the linked attempt for its final result

What was proved

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

    python -m pip install "agilab[examples]==2026.10.13"
    python -m agilab.lab_run first-proof --json --max-seconds 60
    
  • The pinned GitHub Actions rows record successful repository, documentation, coverage, and release-publication workflows at their exact commits. A successful workflow is not presented as proof for jobs that the workflow skipped.

  • The repository, documentation, and coverage rows retain historical baselines at their displayed commits. They do not qualify the current release source. The publication row is bound to the current release commit and attempt.

  • 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 a successful historical UI robot baseline. It is not release-bound UI proof for this release because its commit is not the release tag commit, even when its exact app inventory matches the 14-app release inventory. Use tools/ui_robot_coverage_contract.py --json and the local ui-robot-matrix profile to verify the current checkout. Historical UI robot baseline: run 30646957592, commit adf8c597b5e4, generated 2026-07-31T17:20:14Z. It records 14 apps while this release expects 14; it is not UI proof for this release.

  • 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.10.13"
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 React 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. Set ui_robot.mode = "release" only when the evidence head commit and app count match the represented release; otherwise keep the artifact labeled as a historical baseline.

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. The checked-in UI robot artifact is a historical baseline and does not prove the current release UI matrix. This page 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.