Release Proof
=============

.. This page is generated from docs/source/data/release_proof.toml by
   tools/release_proof_report.py. Edit the TOML and rerender.

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
----------------------

.. list-table::
   :header-rows: 1
   :widths: 24 76

   * - Item
     - Public evidence
   * - Package version
     - ``agilab==2026.05.05.post2`` on `PyPI <https://pypi.org/project/agilab/>`__
   * - GitHub release
     - `v2026.05.06 <https://github.com/ThalesGroup/agilab/releases/tag/v2026.05.06>`__
   * - Hosted demo
     - `jpmorard/agilab <https://huggingface.co/spaces/jpmorard/agilab>`__ at Space commit ``63d4f2ebcf649246118b2e9f346551dab82e39f6``
   * - Public guardrails
     - `repo-guardrails run 25223901208 <https://github.com/ThalesGroup/agilab/actions/runs/25223901208>`__ passed repository guardrails and clean package first-proof jobs
   * - Docs source guard
     - `docs-source-guard run 25223361024 <https://github.com/ThalesGroup/agilab/actions/runs/25223361024>`__ passed docs mirror and release-proof consistency checks
   * - Docs publish
     - `docs-publish run 25223720649 <https://github.com/ThalesGroup/agilab/actions/runs/25223720649>`__ built the public documentation from the managed docs mirror
   * - Coverage
     - `coverage run 25223720635 <https://github.com/ThalesGroup/agilab/actions/runs/25223720635>`__ passed component coverage and badge freshness checks

What was proved
---------------

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

  .. code-block:: bash

     python -m pip install agilab==2026.05.05.post2
     agilab first-proof --json --max-seconds 60

- The public GitHub Actions matrix validated the packaged first proof on
  Ubuntu, macOS, and Windows runners.
- The hosted Hugging Face Space opened the public AGILAB demo route during the
  release guardrail run.
- The public demo scope includes the lightweight ``flight_project`` and
  ``meteo_forecast_project`` routes documented in :doc:`agilab-demo`.
- 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:

.. code-block:: bash

   python -m venv .venv
   . .venv/bin/activate
   python -m pip install --upgrade pip
   python -m pip install agilab==2026.05.05.post2
   agilab first-proof --json --max-seconds 60

Use :doc:`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:

.. code-block:: bash

   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.

Scope and limits
----------------

This evidence proves the public package smoke, hosted demo availability at the
time of validation, and documented first-proof routes. 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 :doc:`compatibility-matrix`.

Related pages
-------------

- :doc:`quick-start`
- :doc:`demos`
- :doc:`agilab-demo`
- :doc:`compatibility-matrix`
- :doc:`agilab-mlops-positioning`