Skip to content

Research: which Docs, build, CI & dev tooling issues are resolved or obsolete? #965

Closed

Description

@tdstein

Question

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.

Issues (15): #241, #354, #448, #502, #513, #514, #515, #592, #605, #649, #741, #774, #780, #781, #833

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

  1. tdstein commented on Nov 10, 2026

    @tdstein
    CollaboratorAuthor

    🤖 Research done. The verdict table, with evidence and draft closing comments, is in research/groom-devtools.md on branch research/groom-devtools.

    Verdict Count Issues
    Resolved 6 #502, #513, #514, #515, #592, #649
    Obsolete 2 #448, #605
    Still valid 7 #241, #354, #741, #774, #780, #781, #833
    Unclear 0 —

    Proposed for closing:

    No duplicates to close. #592 overlaps #949 (keep #949). #354/#419 and #241/#522/#573 are related but distinct.

  2. self-assigned this
    on Nov 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions