Fix mobile swipe-down input triggering unintended jump

[Copilot]

Mobile touch input was firing jump() at gesture start, so a downward swipe intended to duck could trigger a jump first. This change separates tap vs swipe intent before applying jump logic.

• Input routing on mobile

  • Pointer handlers now ignore touch pointers (event.pointerType === "touch"), so touch is handled in one path only.
  • This prevents duplicate/early mobile actions from overlapping pointer + touch streams.

• Tap-vs-swipe gesture handling

  • Removed jump trigger from touchstart.
  • touchend now triggers jump only for tap-like gestures (deltaY <= 40).
  • Downward swipe behavior continues to activate ducking while preserving game-over tap restart.

• Representative change

  // before: jump on touchstart
  // now: jump only after confirming tap on touchend
  if (state.gameOver && deltaY <= 40) {
    resetGame();
    startGame();
  } else if (deltaY <= 40 && (!state.started || state.running)) {
    jump();
  } else {
    releaseJump();
  }

• Fixes Mobile version: when scroll down to duck, player will jump first #1

[Copilot]

Pull request overview

This PR adjusts mobile input handling to prevent a downward swipe (duck) from triggering an unintended jump by separating tap intent from swipe intent and avoiding duplicate touch routing through pointer events.

Changes:

• Pointer event handlers now ignore touch pointers to avoid overlapping pointer + touch input streams.
• touchstart no longer triggers jump(), and touchend triggers jump() only for tap-like gestures (deltaY <= 40).
• Swipe-down duck behavior is preserved while maintaining tap-to-restart on game over.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.