[hmhidey111-collab]

Summary

• add a patient-owned IntakeForm model and migration with validated structured symptom entries
• add self-only intake creation and history endpoints, PHI read logging, and patient export support
• document the module and record issue [Phase 2] IntakeForm model + structured symptom entry #1's remaining booking linkage as issue [Phase 2] Booking flow requires intake before confirmation #2

Closes #1

Verification

Not run in this contribution.

[drips-wave]

@hmhidey111-collab Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[afeezorobsco-cyber]

@hmhidey111-collab CI is failing on this branch against the latest main, so it can't be merged yet. The errors from the latest run:

Backend (typecheck + test + build)

 FAIL  tests/integration/access-control.test.mts > Access-control test suite: who may read intake, consultation and payment data
Error: Command failed: npx prisma migrate deploy
Error: P3018
 FAIL  tests/integration/admin-lifecycle.test.mts > admin account lifecycle
 FAIL  tests/integration/admin-referrals.test.mts > admin referral operations
 FAIL  tests/integration/audit.test.mts > AuditEvent foundation
 FAIL  tests/integration/booking.test.mts > booking concurrency
 FAIL  tests/integration/csrf.test.mts > CSRF protection for cookie-authenticated routes

prisma migrate deploy fails with P3018, so one of this PR's migrations doesn't apply on top of main's migrations; every integration suite then fails at setup. Check the migration SQL against the current schema (a column or table it touches may already exist or have been renamed on main), and regenerate it with node scripts/gen-migration.mjs if needed.

[github-actions]

@hmhidey111-collab This PR now has merge conflicts with main, most likely because #176 (feat(consultations): close an appointment's consultation exactly once…) was just merged, so it can't be merged until it's rebased:

git fetch upstream            # upstream = https://github.com/DocForum/docforum-core.git
git rebase upstream/main
# resolve the conflicts, re-run the tests, then:
git push --force-with-lease

The usual culprits are shared docs like ROADMAP.md and ARCHITECTURE*.md. If the conflict is in the ROADMAP.md changelog, move your entry into a new file under changelog.d/ (see changelog.d/README.md) rather than resolving it in place, so it can't conflict again. CI re-runs when you push, and the needs-rebase label is removed automatically once the conflicts are resolved.

_{Automated message. It won't repeat unless the PR conflicts again after your next push.}