chore: recombobulate 2026-06-28 — doc reconciliation, dead code, refactor plans#22
Merged
Merged
Conversation
…lan refactors
Full-scope GLaDOS recombobulate (report + plans in
specs/2026-06-28_recombobulate/).
Docs reconciliation (Group A):
- PROJECT_STATUS.md: Planning → active dev / v1.0 MVP deployed; fix auth
(authlib JWT, not Auth.js/Apple); flip 7 shipped-feature checkboxes;
resync compliance-debt summary (CD-001..014).
- ROADMAP.md: check off Wizard/Balance/Call-Log/CallerID; OAuth login
shipped (Apple pending); bump Last Updated.
- standards: timezone-strategy (per-line tz shipped, CD-006 partial);
type-flow + frontend-state-management (orval is target-state, CD-007);
backend-layered-architecture (service owns I/O, repo = translator+persistence).
Dead code (Group B):
- remove unused frontend exports getStepPath, Set{Timezone,ContactEmergency,
Schedules}Request; demote parseCallerName to non-export.
- delete orphaned backend/uv.lock (uv not wired into CI/Docker/Railway).
Consistency refactor plans (Group D): specs/.../plans/ 00-04 covering router
error-handling, typed domain exceptions, repository domain models, and
frontend query conventions. No source refactors applied yet.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Full-scope GLaDOS recombobulate. Findings + plans in
specs/2026-06-28_recombobulate/. Compliance fixes (Group C) are split into a separate PR (fix/voipms-error-leaks, CD-015).Group A — documentation reconciliation
timezone-strategy(per-line tz shipped, CD-006 now partial);type-flow+frontend-state-management(orval is target-state, CD-007; documented exceptions added);backend-layered-architecture(service owns I/O, repo = translator + persistence).Group B — dead code
getStepPath,Set{Timezone,ContactEmergency,Schedules}Request; demoteparseCallerNameto non-export.backend/uv.lock(uv not wired into CI/Docker/Railway;pyproject.tomlkept for ruff+pytest config).Group D — consistency refactor PLANS (no code changes)
specs/2026-06-28_recombobulate/plans/00–04: router error-handling wrapper, typed domain exceptions, repository domain models, frontend query conventions. Sequenced with effort estimates; several deferred to bundle with the CD-007 orval work.Not included
Observations were empty (nothing to promote). Consistency implementations are plans only, pending review.
Tests green: 654 backend + 250 frontend, typecheck/lint clean.
🤖 Generated with Claude Code