What — pyproject.toml declares https://uibcdf.org/lindelint, but the public URL returns HTTP 404 and the active sphinx_docs_to_gh_pages.yaml workflow has no recorded run.
How — Run the documentation workflow against the current default branch, repair build or Pages configuration if needed, verify the final public URL and repository identity, and then add the documentation badge under the MolSysSuite badge policy.
Why — Package metadata currently advertises a user-facing surface that does not exist. Workflow presence alone is not deployment evidence, so the badge rollout must omit documentation until the public result is verified.
Evidence — MolSysSuite badge audit on 2026-09-20; gh run list --workflow sphinx_docs_to_gh_pages.yaml returned no runs and an anonymous request to the declared URL returned 404.
Blocked presentation — uibcdf/molsyssuite#23.
What —
pyproject.tomldeclareshttps://uibcdf.org/lindelint, but the public URL returns HTTP 404 and the activesphinx_docs_to_gh_pages.yamlworkflow has no recorded run.How — Run the documentation workflow against the current default branch, repair build or Pages configuration if needed, verify the final public URL and repository identity, and then add the documentation badge under the MolSysSuite badge policy.
Why — Package metadata currently advertises a user-facing surface that does not exist. Workflow presence alone is not deployment evidence, so the badge rollout must omit documentation until the public result is verified.
Evidence — MolSysSuite badge audit on 2026-09-20;
gh run list --workflow sphinx_docs_to_gh_pages.yamlreturned no runs and an anonymous request to the declared URL returned 404.Blocked presentation —
uibcdf/molsyssuite#23.