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 Deploy & bundling issues are resolved or obsolete? #961
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.
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.
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.
Activity
tdstein commentedon Nov 10, 2026
🤖 Research done. The verdict table is in
research/groom-deploy.mdon branchresearch/groom-deploy.Checked against
mainat2ea5fdd2, using local CLI repros only. No live server was contacted.Proposed for closing in #962:
uv buildworks from agit archiveexport.deploy bundle(feat: add deploy bundle command for downloaded bundles #793) pluscontent download-bundlecover promoting the same bundle between servers. There is still no local build-only command.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.