Release health - unreleased work or an incomplete publish

[github-actions]

Automated release-health check. This issue is rewritten in place on every run and closed automatically once every gap below is closed; it is never duplicated.

Last evaluated: 2026-08-30T23:49:22.231620+00:00 (run)

unreleased-work — 1 releasable commit(s) unpublished for 1d 4h

main has been carrying 1 releasable commit(s) for 1d 4h past v1.16.0. main CI is green and no release run is in flight, so nothing is going to publish these on its own.

Next version would be a minor bump.

commit	bump	age	subject
e9e6c775	minor	1d 4h	feat: print the Day-1 partner kit after quickstart

Most recent release run: 32995182459 — completed/success.

Publish with:

# First merge the reviewed version, changelog, lockfile, and candidate state. Then create the tag from exact main.
gh workflow run release-and-publish.yml --repo OpenAdaptAI/OpenAdapt --ref main -f version=<reviewed-version>
# If that exact tag run partially failed, rerun it. Do not create a recovery tag.
gh run rerun --repo OpenAdaptAI/OpenAdapt <tag-run-id>

Everything the check considered and cleared

• [launcher] tag v0.36.1 has no release object; acknowledged: 2024-07-06 legacy monorepo tag. No release object was ever created and 0.36.1 was never published to PyPI (the index jumps 0.35.x -> 0.39.1). Permanently historical: acknowledged here rather than left to alert forever, because a guard that is always red is a guard nobody reads.
• [launcher] openadapt 1.16.0 is on PyPI.

Reproduce locally with python scripts/check_release_health.py.