You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Research: which Docs, build, CI & dev tooling issues are resolved or obsolete? #965
For each open issue in the Docs, build, CI & dev tooling batch, is it already resolved, obsolete, still valid, or unclear? Find the evidence and propose a closing comment for each one marked resolved or obsolete.
Output: a verdict table on branch research/groom-devtools with these columns: issue, verdict, evidence (PR/commit/code ref/CLI output), proposed close reason (completed / not planned / duplicate-of), and draft 🤖 closing comment. Follow the verdict rules in the map's Notes.
Activity
tdstein commentedon Nov 10, 2026
🤖 Research done. The verdict table, with evidence and draft closing comments, is in
research/groom-devtools.mdon branchresearch/groom-devtools.Proposed for closing:
semver<4.0.0, released in 1.25.0.--disable-env-management*flags, and they are searchable.docs/Makefileis gone. Docs now build withjust docs/just docs-serve, documented in AGENTS.md.preview.make devand vetiver-testing setup was removed in Modernize tooling: uv build/test, just, ruff (drop Docker for Python envs & Make) #808 and Drop vetiver test baggage; mock system-caches CLI test #809.No duplicates to close. #592 overlaps #949 (keep #949). #354/#419 and #241/#522/#573 are related but distinct.