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 Auth & server config issues are resolved or obsolete? #957
For each open issue in the Auth & server config 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-auth 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.
Overlap to decide:#646 partly overlaps #542 (content batch): both cover redeploy after the content was deleted. The file recommends keeping both. No backlog issues were touched.
Activity
tdstein commentedon Nov 10, 2026
🤖 Research is done. The verdict table is in
research/groom-auth.mdon branchresearch/groom-auth.Verdicts (14 issues): Resolved 2, Obsolete 0, Still valid 12, Unclear 0.
Proposed for closing (both as
completed):-nnow prints a clear error.--no-wait/--finish/--timeoutforloginandadd --connect-cloudshipped in Add resumable device login and Python/Node.js preflight #859 (1.32.0).Still valid: #165, #215, #220, #377, #413, #646, #699, #716, #791, #799, #842, #843. #377, #413 and #699 were reproduced locally on current
main, without a server.Overlap to decide: #646 partly overlaps #542 (content batch): both cover redeploy after the content was deleted. The file recommends keeping both. No backlog issues were touched.