TODO.md

Second Chance outcomes

• Responsive editorial landing experience: Build a responsive web experience inspired by the supplied dating-app landing-page reference without copying it, with romantic storytelling, parallax-inspired scrolling, layered depth, glassy panels, and floating heart or 3D-style decorative elements.
• Opening heartbreak narrative: Establish the heartbreak and frame reconciliation as a possibility rather than an expected outcome.
• Interactive apology journey: Provide polished, playful prompts that encourage sincerity and emotional reflection.
• Promise-making step: Let her compose or select meaningful commitments for a renewed relationship.
• Name-entry personalization: Let her enter her name and use it in the apology/reconciliation message.
• Explicit-consent checkpoint: Confirm that her promises are sincere and that she respects either final outcome.
• Validation and progression: Prevent the acceptance choice from appearing until all required steps are completed.
• Balanced final decision: Give the guy clear accept-reconciliation and decline/not-ready choices using non-coercive microcopy.
• Playful responsive microinteractions: Add responsive hearts, hover/tap reactions, depth shifts, and restrained celebration that adapt across desktop and mobile.
• Server-side sincerity reading: After the name, promise bouquet, apology note, and consent are complete, call the requested OpenRouter model server-side, return a nuanced score/read/care signal, and clearly label the result as an impression rather than a lie detector, with a transparent offline fallback when the provider rejects the credential.
• Owner-only private reveal: After submission, seal the answers and sincerity result in the interface; reveal the private dossier and enable the final decision only after the server verifies the configured owner passphrase.
• Reconnection journey transitions: Organize the experience into four visible reconnection chapters with active progress navigation, animated bridge dividers, scroll-aware chapter state, pointer-reactive hero art, reduced-motion-aware scrolling, and a gentle advance into the naming chapter after three promises are chosen.