Add authentication and user management — Phase 4: Files Affected #41

Closed
opened 2026-05-28 00:47:24 +00:00 by Mark · 1 comment
Owner

Phase 4: Files Affected

  • src/pages/Settings.tsx (add user management UI)
  • src/store/index.ts (auth state)
  • src/lib/api.ts (auth endpoints)
  • New: src/store/auth.ts

Decomposed from docker_backup#3

## Phase 4: Files Affected - `src/pages/Settings.tsx` (add user management UI) - `src/store/index.ts` (auth state) - `src/lib/api.ts` (auth endpoints) - New: `src/store/auth.ts` --- _Decomposed from [docker_backup#3](https://forgejo.tail018ac4.ts.net/Mark/docker_backup/issues/3)_
Author
Owner

⏸ Needs Decision

Blocking factors:

  • Didn't meet auto-approve criteria — scope=small, risk=medium, spec=aligned

Scope: small Risk: medium Spec: aligned Type: feature
Summary: Add user management UI to the Settings page, auth state management to the Zustand store (new module + store/index.ts), and auth-related API endpoints.
Suggestion: Implement a separate Zustand auth slice in src/store/auth.ts (following the planned new file), expose auth mutations and queries via src/lib/api.ts, and add a 'User Management' section to the existing Settings page (src/pages/Settings.tsx) using shadcn/ui table/form components. Use React 19's useActionState for form actions. Run npm run build after implementation to verify TS compiles cleanly.
Rationale: Small scope (3 existing files + 1 new file, no new subsystem). Medium risk because authentication is security-sensitive and the project has no test coverage per AGENTS.md. Aligned with project patterns (Zustand state, shadcn/ui, React 19 patterns) and the decomposed Phase 4 plan from the original issue #3.

Action: Review each blocking factor above. Remove blocked:needs-decision label to route back to triage.

## ⏸ Needs Decision **Blocking factors:** - **Didn't meet auto-approve criteria** — scope=small, risk=medium, spec=aligned --- **Scope:** small **Risk:** medium **Spec:** aligned **Type:** feature **Summary:** Add user management UI to the Settings page, auth state management to the Zustand store (new module + store/index.ts), and auth-related API endpoints. **Suggestion:** Implement a separate Zustand auth slice in src/store/auth.ts (following the planned new file), expose auth mutations and queries via src/lib/api.ts, and add a 'User Management' section to the existing Settings page (src/pages/Settings.tsx) using shadcn/ui table/form components. Use React 19's useActionState for form actions. Run npm run build after implementation to verify TS compiles cleanly. **Rationale:** Small scope (3 existing files + 1 new file, no new subsystem). Medium risk because authentication is security-sensitive and the project has no test coverage per AGENTS.md. Aligned with project patterns (Zustand state, shadcn/ui, React 19 patterns) and the decomposed Phase 4 plan from the original issue #3. **Action:** Review each blocking factor above. Remove `blocked:needs-decision` label to route back to triage.
Mark 2026-05-28 07:18:39 +00:00
Sign in to join this conversation.
No description provided.