On the booking form, show the selected date in the confirmation.
Keep the existing hosting and data model.
Verify the change on mobile and on the deployed site.Check the current app#
Read the project instructions, source, uncommitted changes, deployment settings, and checks. Find the code responsible for the behavior. Preserve unrelated edits and the existing architecture.
If account access is needed, run godmode help, read the provider guide, and check the intended account and resource. Use only the credentials this change needs.
Make the change#
Reuse existing components and conventions. Handle useful error states. Add a service only if the task needs it.
For data changes, prefer additions that keep the current app working. Test recovery before destructive changes. Never replace live data with fixtures.
Test and deploy#
Run checks suited to the change. Try the actual user action, including phone and keyboard use where relevant. Review the diff for unrelated edits, secrets, and inaccurate claims.
If deployment was requested, deploy the reviewed revision to the correct project. Check that revision and the changed behavior at the live URL.
Record the result#
Save what changed, the revision and live URL, actual test results, remaining limits, and recovery steps. If the release fails, use Recover a failed deploy.