Summary
The pk-doctor release_integrity check probes up to 50 local v* tags by running gh release view once per tag. In the aibox workspace on 2026-06-06 this made the check take about 31 seconds by itself and made a bounded full pk-doctor --json run appear hung.
Evidence
timeout 12 uv run context/skills/processkit/pk-doctor/scripts/doctor.py --json --no-log --category=release_integrity timed out.timeout 60 ... --category=release_integrity completed cleanly after about 31.4s with release_integrity.all-tags-released for 50 tags.- The rest of the doctor categories completed cleanly under the same sweep.
Suggested fix
Query releases once with gh release list --limit <n> --json tagName and compare local tags in memory. A local patch in aibox reduced the category duration to about 1.5s and allowed full pk-doctor to complete in about 14.8s with 0 ERROR / 0 WARN / 68 INFO.
Impact
This is not an aibox repository-health problem; it is a pk-doctor implementation/performance issue that can cause agents to misclassify the full doctor run as stuck or timed out.
Summary
The pk-doctor
release_integritycheck probes up to 50 localv*tags by runninggh release viewonce per tag. In the aibox workspace on 2026-06-06 this made the check take about 31 seconds by itself and made a bounded fullpk-doctor --jsonrun appear hung.Evidence
timeout 12 uv run context/skills/processkit/pk-doctor/scripts/doctor.py --json --no-log --category=release_integritytimed out.timeout 60 ... --category=release_integritycompleted cleanly after about 31.4s withrelease_integrity.all-tags-releasedfor 50 tags.Suggested fix
Query releases once with
gh release list --limit <n> --json tagNameand compare local tags in memory. A local patch in aibox reduced the category duration to about 1.5s and allowed full pk-doctor to complete in about 14.8s with0 ERROR / 0 WARN / 68 INFO.Impact
This is not an aibox repository-health problem; it is a pk-doctor implementation/performance issue that can cause agents to misclassify the full doctor run as stuck or timed out.