Skip to content

Research: which Auth & server config issues are resolved or obsolete? #957

Closed

Description

@tdstein

Question

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.

Issues (14): #165, #215, #220, #377, #413, #541, #646, #699, #716, #791, #799, #842, #843, #858

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.

Activity

  1. tdstein commented on Nov 10, 2026

    @tdstein
    CollaboratorAuthor

    🤖 Research is done. The verdict table is in research/groom-auth.md on branch research/groom-auth.

    Verdicts (14 issues): Resolved 2, Obsolete 0, Still valid 12, Unclear 0.

    Proposed for closing (both as completed):

    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.

  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