docs(studio): align demo packaging with current IVR truth

[CapuchaRojo]

Summary

Aligns Studio/demo packaging truth with the current IVR route matrix.

This PR:

• Updates the live config cancellation/reschedule cutoff from 12 to 24 hours.
• Keeps docs aligned with the current 24-hour / 0 reschedule-or-cancellation policy.
• Does not change runtime behavior.
• Does not touch payment internals.
• Does not touch Acuity mutation behavior.
• Does not edit Studio UI or launchpad.pptx.

Validation

• git diff --check passed
• docs-only change
• final git status clean

Notes

The Studio/demo package is mostly honest and non-live. Remaining later polish is to refresh the launchpad/demo narrative so the new IVR route-matrix proof is more visible.

Guardrails

• Config-truth alignment only.
• No IVR routing behavior changed.
• No payment behavior changed.
• No Acuity mutation behavior changed.
• No Studio UI or launchpad.pptx changes.
• Added a consistency assertion to prevent JSON/TypeScript live-config drift.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 78dc79c78a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep live-config seeds aligned with runtime manifest

This JSON seed now reports cancelRescheduleCutoffHours as 24, but the canonical runtime cutover manifest still exports 12 in api/src/lib/cutover/marijuanaExpressLiveConfig.ts line 174. That leaves packaging/readiness consumers that read docs/a17/marijuanaexpress.live-config.json disagreeing with API tests and runtime code that import MARIJUANA_EXPRESS_LIVE_CONFIG; if 24 hours is the intended truth, update the TypeScript manifest or add a consistency assertion so the two manifests cannot diverge.

Useful? React with 👍 / 👎.