17efc4f656
Make the project's documentation match the code and remove the sprawl. The docs
claimed Phase 2.8 (drug interactions) was 'planning/0%' and the backend '~91%
complete' — both wrong: 2.8 is implemented and live, plus the P0/P1 security
and test work is done. Five root CI/CD docs described a 'docker-build' CI job
that was removed; ~18 backend/ status snapshots and ~24 docs/implementation
duplicates cluttered the tree.
Deletions (85 files):
- Root: 4 stale CI/CD reports (CI-CD-{COMPLETION-REPORT,IMPLEMENTATION-SUMMARY,
STATUS-REPORT,FINAL-STATUS}.md) — all describe the removed docker-build job.
- backend/: 18 phase/build/fix snapshots and code-dump .txt files.
- docs/: the 3 one-time reorg reports; ~17 docs/implementation duplicates and
process artifacts; 4 stale docs/development CI docs + git snapshots;
redundant deployment/testing files.
- thoughts/: STATUS.md (said Phase 2.4 in-progress), superseded phase notes and
duplicative research inputs. tmp/ (928KB of CI debug logs, gitignored).
Moves (18 files):
- 9 genuine decision records -> docs/adr/ (Architecture Decision Records),
date-prefixes stripped, with an index README.
- 8 historical-but-valuable phase plans/specs + the old CI-CD-FINAL-SOLUTION ->
docs/archive/ (now-populated, with a README explaining it's superseded
material). thoughts/ tree removed.
Rewrites (13 files) to match reality:
- Drop the fake '% complete' figures everywhere in favor of Implemented /
In-Progress / Planned with concrete endpoint/feature lists.
- Phase 2.8 -> Implemented; add /api/interactions/* and /api/auth/{refresh,
logout} to the endpoint lists; fix 'Rust 1.93' -> edition 2021.
- Add a Security section (token_version validation, hashed refresh-token
persistence, fail-fast config, real-IP audit) and correct the test-coverage
and deployment claims to reality.
- New canonical docs/development/CI-CD.md (4 jobs: format/clippy/build/test,
mongo service, no docker-build + why).
- README, docs/README, product/{STATUS,ROADMAP,PROGRESS,README,introduction},
implementation/README, development/README, testing/README, AI_AGENT_GUIDE,
.cursorrules, .gooserules all updated.
Verified: greps for 'Phase 2.8 (Planning)', 'PLANNING (0%)', 'Rust 1.93',
'91%/10%/85% complete', and 'docker-build' return nothing outside docs/archive;
all internal doc links resolve; backend/src untouched (cargo build clean).
61 lines
2.2 KiB
Markdown
61 lines
2.2 KiB
Markdown
# Implementation Documentation
|
|
|
|
Phase-by-phase implementation completion records. Each phase that's been built
|
|
has a canonical completion note here; original plans and specs are in
|
|
[../archive/](../archive/README.md).
|
|
|
|
## By Phase
|
|
|
|
### Phase 2.3 — JWT Authentication ✅
|
|
- [PHASE-2-3-COMPLETION-REPORT.md](./PHASE-2-3-COMPLETION-REPORT.md)
|
|
|
|
### Phase 2.4 — User Management ✅
|
|
- (completion notes folded into [../product/STATUS.md](../product/STATUS.md))
|
|
|
|
### Phase 2.5 — Access Control ✅
|
|
- [PHASE-2-5-COMPLETE.md](./PHASE-2-5-COMPLETE.md)
|
|
|
|
### Phase 2.6 — Security Hardening ✅
|
|
- [PHASE_2.6_COMPLETION.md](./PHASE_2.6_COMPLETION.md)
|
|
|
|
### Phase 2.7 — Health Data Features ✅
|
|
- [PHASE27_COMPLETION_REPORT.md](./PHASE27_COMPLETION_REPORT.md) - Completion report
|
|
- [MVP_PHASE_2.7_SUMMARY.md](./MVP_PHASE_2.7_SUMMARY.md) - MVP prioritization
|
|
- [MEDICATION_MANAGEMENT_IMPLEMENTATION_SUMMARY.md](./MEDICATION_MANAGEMENT_IMPLEMENTATION_SUMMARY.md) - Medication CRUD
|
|
- Original plans: [../archive/](../archive/README.md)
|
|
|
|
### Phase 2.8 — Drug Interactions ✅
|
|
- [PHASE28_FINAL_STATUS.md](./PHASE28_FINAL_STATUS.md) - Completion (interactions live)
|
|
- Original plan + specs: [../archive/](../archive/README.md)
|
|
|
|
### Frontend 🚧
|
|
- [FRONTEND_STATUS.md](./FRONTEND_STATUS.md) - Current frontend status
|
|
|
|
## Implementation Progress
|
|
|
|
| Phase | Status |
|
|
|-------|--------|
|
|
| 2.3 | ✅ Implemented |
|
|
| 2.4 | ✅ Implemented |
|
|
| 2.5 | ✅ Implemented |
|
|
| 2.6 | ✅ Implemented |
|
|
| 2.7 | ✅ Implemented |
|
|
| 2.8 | ✅ Implemented (drug interactions) |
|
|
| P0/P1 Security + Tests | ✅ Implemented |
|
|
| Frontend (Phase 3) | 🚧 Early |
|
|
|
|
## Key Features Implemented
|
|
|
|
- JWT authentication with token rotation + `token_version` invalidation
|
|
- User management (profiles, settings, password change/recovery)
|
|
- Permission-based access control + share management
|
|
- Security hardening (audit logging, account lockout, session management)
|
|
- Medication management (CRUD, dose logging, adherence)
|
|
- Health statistics tracking + trends
|
|
- Drug interaction checking (OpenFDA-based ingredient mapping)
|
|
- Refresh-token persistence (hashed, revocable) + `/refresh` and `/logout`
|
|
- Fail-fast production config + real client-IP audit logging
|
|
|
|
---
|
|
|
|
*Last Updated: 2026-06-27*
|