Build the local-first Anti-Planner

[yo4e]

Summary

Builds the complete browser-local Maybe Tomorrow. Anti-Planner approved in Issue #3, then applies the Issue #5 refinement that puts the ordinary decision back at the center: Quick Check first, calendar context optional, sample day tertiary.

What changed

Core Anti-Planner

• preserves exactly three deterministic verdicts and the standalone seven-question Quick Check plus final shrinkability check;
• adds bounded browser-local .ics and Google Calendar ZIP import, recurrence handling, human event labels, Today Map, room-making previews, transparent verdict alternatives, and a validated local Decision Journal;
• keeps event meaning human-authored and never edits an imported calendar.

Issue #5 refinement

• makes Check one thing the direct hero action with an activity field in the first viewport;
• carries that activity through Back navigation and into optional calendar context;
• places Add calendar context second and Try the sample day third;
• adds in-app Google Calendar desktop export instructions, supported-format guidance, local-processing disclosure, and refresh-by-reimport guidance;
• replaces primary Counterfactual, Solver, terse event classes, and day grades with plain action language and factual Today Map copy;
• redesigns the interface as after-hours stationery / an indie magazine: cream paper, midnight ink, cobalt hierarchy, small citron markers, and sparing coral;
• completes a US-English polish pass covering result grammar, quoted activity names, answer scales, import guidance, calendar labels, and punctuation, while slightly neutralizing the paper tone;
• preserves keyboard, touch, focus, reduced-motion, forced-colors, and 360 px behavior.

Privacy and product boundaries

• no runtime model or AI calls;
• no external API calls;
• no backend, authentication, analytics, tracking, account sync, or writeback;
• imported file bytes and complete calendar data are not persisted in the Journal;
• Google account synchronization is not promised in the application.

Validation

• npm test: 9 test files, 64 tests passed;
• npm run build: TypeScript strict build and Vite production build passed;
• git diff --check: passed;
• direct Quick Check, Back-state preservation, optional import, expanded Google guide, sample triage, factual Today Map, quoted result grammar, corrected factor copy, and calendar-assisted activity handoff verified in the in-app browser;
• 360 × 800 and 1440 × 900 layouts verified without horizontal overflow;
• no captured browser console warnings or errors;
• final read-only QA found no blocking copy, calendar-claim, layout, or accessibility issues.

Review guide

1. Start on the first viewport and enter Start another side project.
2. Confirm Check one thing is the obvious primary action and can reach a verdict without a calendar.
3. Return home, choose Add calendar context, and expand How to export from Google Calendar.
4. Return home, choose Try the sample day, keep the fictional labels, and open View this day.
5. Choose Check one thing and confirm the original activity follows into the calendar-assisted flow.
6. Review the revised editorial color system and primary English copy on mobile and desktop.

Yoshie Yamada and Templex Tsukino approved the final copy-and-color polish. This PR is ready to merge and release.

Related to #3 and #5.

— Codex

[yo4e]

Final visual approval and release handoff

Yoshie Yamada has completed the browser review of the refined application and approved the current first viewport, primary copy, calendar guidance, and editorial color direction.

The product hierarchy now reads correctly:

1. Check one thing is the obvious primary path.
2. Add calendar context is clearly optional.
3. Try the sample day is tertiary and works as a privacy-respecting demonstration.

The revised copy is understandable on first read, the poetic voice remains in the result layer, and the after-hours stationery / indie magazine identity feels recognizably distinct without becoming visually aggressive.

Codex may now complete the release handoff:

1. mark PR Build the local-first Anti-Planner #4 ready for review;
2. merge it into main;
3. verify the GitHub Pages workflow and public deployment;
4. confirm the deployed application loads and the primary demo path works;
5. close Issues [Expansion] Build the local-first Anti-Planner #3 and [Refinement] Recenter Quick Check and create a distinct editorial identity #5 as completed;
6. leave a final report with the public URL, workflow result, and any remaining non-blocking limitations.

No further product or copy changes are requested before release.

Approved. Ship the brake.

---

— Templex Tsukino

[yo4e]

Release complete.

• Merged to main as 268038d92d234bbb98fb4c0591ddaf93e36c4e24.
• Enabled GitHub Pages with GitHub Actions as the publishing source.
• Deployment workflow attempt 2 passed its full test, build, and deploy jobs.
• Verified the public application through the complete eight-question Quick Check and the fictional sample-day Today Map.
• Confirmed no browser console warnings or errors on the published build.
• Closed Issues [Expansion] Build the local-first Anti-Planner #3 and [Refinement] Recenter Quick Check and create a distinct editorial identity #5 as completed.

Approved. Shipped the brake.

— Codex