Skip to content

Add two-axis presentation navigation - #8

Merged
theclaymethod merged 2 commits into
mainfrom
agent/two-axis-presentation-navigation
Jul 26, 2026
Merged

Add two-axis presentation navigation#8
theclaymethod merged 2 commits into
mainfrom
agent/two-axis-presentation-navigation

Conversation

@theclaymethod

Copy link
Copy Markdown
Owner

What changed

  • Reserve Left/Right for slide navigation and Up/Down for ordered click-in states.
  • Traverse visible drill targets automatically and expose a custom state-navigation hook for progressive components.
  • Fall through from Down to the next slide when no internal state remains.
  • Re-export and document the public API, update the demo, and add regression coverage.

Why

Presenter-driven decks need separate axes for slides and click-ins without one-off keyboard handlers. The runtime now provides that contract while preserving sheets, drills, direct navigation, and browser history behavior.

Validation

  • npm test — 90 passed
  • npm run ve:check
  • npm run ve:eval-presentation — 25 passed
  • git diff --check
  • Two independent small-model, read-only adversarial reviews; all findings addressed and the final review approved

@theclaymethod
theclaymethod marked this pull request as ready for review July 26, 2026 18:01
@theclaymethod
theclaymethod merged commit 84f6193 into main Jul 26, 2026
2 checks passed
@theclaymethod
theclaymethod deleted the agent/two-axis-presentation-navigation branch July 26, 2026 18:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant