[believetimothy]

What changed

Which ROADMAP.md item does this close/progress?

(required — see AGENTS.md doc-update rules)

Docs updated in this PR (check all that apply)

• ROADMAP.md
• ARCHITECTURE.md
• ARCHITECTURE_ESSENTIALS.md
• PRD.md
• N/A for this change

Closes #13
Closes #14
Closes #15
Closes #16

[drips-wave]

@believetimothy 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]

@believetimothy fix CI

[afeezorobsco-cyber]

@believetimothy

CI is red on typecheck:

• App.tsx: AppointmentDetailPage is imported but never used. The route was never added.
• Test fixtures don't match the Appointment type: they're missing patientName, startsAt and endsAt (RescheduleDialog.test.tsx, useReschedule.test.tsx, cutoff.test.ts).
• QueuePanel.test.tsx: "checked_in" isn't a valid AppointmentStatus.

The Appointment model in src/types/models.ts changed on main. Please rebase onto the latest main, update the fixtures, and run npm run typecheck locally.

[afeezorobsco-cyber]

@believetimothy Thanks for the PR. It can't be merged yet. To unblock it:

CI is failing. Here's what broke:

Frontend (typecheck + test + build):

src/App.tsx(14,10): error TS6133: 'AppointmentDetailPage' is declared but its value is never read.
src/features/appointments/components/RescheduleDialog.test.tsx(38,3): error TS2739: Type '{ id: string; patientProfileId: string; doctorProfileId: string; availabilitySlotId: string; status: "scheduled"; origin:
src/features/appointments/cutoff.test.ts(9,3): error TS2322: Type '{ intake?: IntakeSummary | null; patientName?: string | undefined; startsAt?: string | undefined; endsAt?: string | undefined; reason?: string |
src/features/appointments/hooks/useReschedule.test.tsx(13,7): error TS2739: Type '{ id: string; patientProfileId: string; doctorProfileId: string; availabilitySlotId: string; status: "scheduled"; origin: "direct

Please fix these errors and run the same steps locally before pushing (npm run typecheck && npm test && npm run build, or cargo test for contracts).

Merge conflicts: this branch conflicts with main. Please rebase onto the latest main (git fetch upstream && git rebase upstream/main), resolve the conflicts (often ROADMAP.md, ARCHITECTURE*.md or prisma/schema.prisma), and force-push.

Push to this same branch and CI will re-run. Once it's green and conflict-free, it'll be reviewed for merge.

[github-actions]

@believetimothy This PR now has merge conflicts with main, most likely because #157 (feat(platform): complete W7 API client, errors, PWA, and i18n) was just merged, so it can't be merged until it's rebased:

git fetch upstream            # upstream = https://github.com/DocForum/docforum-web.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.}

[afeezorobsco-cyber]

@believetimothy CI is failing at npm run typecheck with a syntax error in the test helper:

src/test/render.tsx(14,10): error TS1005: ':' expected.
src/test/render.tsx(14,51): error TS1005: ',' expected.
src/test/render.tsx(14,100): error TS1011: An element access expression should take an argument.
src/test/render.tsx(17,5): error TS1005: ',' expected.

Line 14 of src/test/render.tsx looks like a half-resolved merge (two versions of the wrapper merged into one line). Please fix it, run npm run typecheck && npm test, and push.

[github-actions]

@believetimothy This PR now has merge conflicts with main, most likely because #210 (chore(changelog): fold changelog.d fragments into ROADMAP.md) was just merged, so it can't be merged until it's rebased:

git fetch upstream            # upstream = https://github.com/DocForum/docforum-web.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.}