clone

a browser grid puzzle game where you push words around to rewrite the rules of each level

main
miau-is-true / openspec / changes / archive / 2026-09-24-add-world-index-presentation / tasks.md
tasks.md 2.1K source

1. World header and strip

  • [x] 1.1 Render the accepted desktop/mobile INDEX header hierarchy from the D20 world view model, including fallback tagline and per-world completion.
  • [x] 1.2 Render the desktop [Q] ◀ dots ▶ [E] strip with accent-aware current dot and visible control geometry.
  • [x] 1.3 Add mobile 44px arrow targets, omit mobile keycaps, and keep strip hit geometry aligned with the drawn controls.
  • [x] 1.4 Synchronize the 110ms back-ease dot slide with the D20 280ms world sheet transition and settle both immediately for reduced motion.

2. World card

  • [x] 2.1 Apply the revised centered card composition: 96px glyph, WORLD NN, 32px name, 15px tagline, proof/progress/optional-author meta line, 16px rhythm, accent stroke, and desktop/touch actions.
  • [x] 2.2 Preserve the D20 index and workshop origins and dismiss the card to the settled INDEX sheet without entering a proof or changing simulation.
  • [x] 2.3 Fit and wrap revised card copy for desktop/mobile canvases, expose the full-width 48px coarse-pointer action, and settle under reduced motion.
  • [x] 2.4 Add focused renderer, input, and accessibility tests for first entry, Workshop PLAY, confirmation, pointer/touch parity, and one-per-session card behavior, including Core identity and missing-author copy.

3. Mobile controls and narration

  • [x] 3.1 Replace mobile INDEX keycap hints with tap the cat to play and the ☰ menu thumb affordance, keeping Workshop behind that menu.
  • [x] 3.2 Keep INDEX and open-card accessible labels synchronized with visible world identity, progress, controls, and ENTER dismissal.
  • [x] 3.3 Verify desktop and 390x844 screenshots for hierarchy, overlap, transitions, card fitting, and footer placement, including reduced motion.

4. Verification and handoff

  • [x] 4.1 Run focused presentation and browser tests without changing D20 navigation or engine solver behavior.
  • [x] 4.2 Run the full Node suite and production build.
  • [x] 4.3 Post the desktop/mobile header, strip, card, and footer evidence to docs/design-inbox.md for designer review before release.