Context
Two booking docs now contradict the code in load-bearing ways. docs/booking/07-rescheduling-flow.md claims concurrent reschedules are harmless and predates both the stale-tab race (audit R2) and the cleanup-grace fix; docs/booking/08-cancellation-flow.md still describes delete-on-cancel, no authentication, and no automatic refunds, all three of which are false against the current cancel route (app/api/appointments/[appointmentId]/cancel/route.ts:119-155, 262-287, 303-357).
Proposed approach
Rewrite the stale sections of both chapters against the current routes and the lifecycle-correctness PR, and add the audit's reschedule/cancellation findings register so the docs point at the open issues rather than asserting solved behavior. Full-sentence prose per the docs convention.
Audit id C10/R8-doc; found alongside #998.
Context
Two booking docs now contradict the code in load-bearing ways.
docs/booking/07-rescheduling-flow.mdclaims concurrent reschedules are harmless and predates both the stale-tab race (audit R2) and the cleanup-grace fix;docs/booking/08-cancellation-flow.mdstill describes delete-on-cancel, no authentication, and no automatic refunds, all three of which are false against the current cancel route (app/api/appointments/[appointmentId]/cancel/route.ts:119-155, 262-287, 303-357).Proposed approach
Rewrite the stale sections of both chapters against the current routes and the lifecycle-correctness PR, and add the audit's reschedule/cancellation findings register so the docs point at the open issues rather than asserting solved behavior. Full-sentence prose per the docs convention.
Audit id C10/R8-doc; found alongside #998.