Skip to content

Research: which Deploy & bundling issues are resolved or obsolete? #961

Closed

Description

@tdstein

Question

For each open issue in the Deploy & bundling 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 (16): #178, #371, #382, #414, #419, #516, #520, #522, #573, #587, #634, #702, #720, #824, #829, #831

Output: a verdict table on branch research/groom-deploy 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 is in research/groom-deploy.md on branch research/groom-deploy.

    Checked against main at 2ea5fdd2, using local CLI repros only. No live server was contacted.

    Verdict Count Issues
    Resolved 2 #520, #634 (partial: please confirm)
    Obsolete 1 #178
    Still valid 10 #371, #414, #522, #573, #587, #702, #720, #824, #829, #831
    Unclear 3 #382, #419, #516

    Proposed for closing in #962:

    Possible overlap: if the maintainers decide to remove deploy_python_fastapi (#573), #522 can close as a duplicate of #573. #382 may share #414's symlink root cause.

  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