Add action-tracker input type for timestamped event logging

[luanzeba]

Summary

This PR introduces a new action-tracker input type that allows scouts to record timestamped robot actions during a match. Rather than just counting events, scouts can now tap action buttons as they happen, building a timeline of what the robot did and when.

Demo with tapping: https://drive.google.com/file/d/1ZOORtvebjrV7ntk0YtEJNCypNdfhZHAD/view?usp=sharing
Demo with holding: https://drive.google.com/file/d/1mpLHSRhjhV06cgtykoCf8Ck12Y7Edtl-/view?usp=sharing

Motivation

Traditional counter inputs capture how many times something happened, but not when. For post-match analysis, knowing that a robot scored fuel at 2.3s, 8.1s, and 14.5s during auto tells a much richer story than knowing it scored 3 times. This timing data enables analysis of cycle times, action sequences, and phase-specific performance.

Design Decisions

Tap vs Hold modes (experimental). The action-tracker supports two recording modes via the mode property:

• tap: Records an instant timestamp when the button is tapped. Best for discrete events like scoring or picking up game pieces.
• hold: Records both start and end timestamps while the button is held down. Best for continuous actions like playing defense or climbing. Supports multi-touch for tracking overlapping actions.

Both modes are included temporarily for field testing during practice matches. After evaluating usability with our scouts, we'll likely standardize on a single mode in a follow-up PR.

Separate trackers for Auto and Teleop. We opted for distinct action-tracker instances per game phase rather than one combined tracker. This keeps the timer durations phase-appropriate and makes the data easier to parse—auto actions don't need to be filtered out of a 150-second teleop timeline.

Auto-start on first tap. While scouts should ideally start the timer manually when the phase begins, tapping any action button will start the timer automatically if it isn't already running. This prevents data loss when scouts forget to hit Start, and we display an "(auto-started)" indicator so they're aware.

Human-friendly column names. When copying column names, action-tracker fields expand into readable headers like "Fuel Scored in Auto (count)" and "Fuel Scored in Auto (timestamps)" rather than raw field codes. The phase name is extracted from the field title (e.g., "Auto Actions" → "Auto").

Expanded field output. Each action generates two output columns: {code}_{actionCode}_count (integer) and {code}_{actionCode}_times (comma-separated timestamps in seconds). For example, an auto tracker with code autoAct and a "fuel" action produces autoAct_fuel_count and autoAct_fuel_times. This keeps the data flat and spreadsheet-friendly.

Optional Lucide icons. Action buttons can display icons from the Lucide icon library. Icons are lazy-loaded on demand using dynamic imports, so they add zero bytes to the initial bundle regardless of how many different icons are used across configs.

Example Configuration

{
  "title": "Auto Actions",
  "type": "action-tracker",
  "code": "autoAct",
  "required": false,
  "mode": "tap",
  "actions": [
    { "label": "Fuel Scored", "code": "fuel", "icon": "circle-dot" },
    { "label": "Crossed Bump", "code": "bump", "icon": "chevrons-up" }
  ]
}

This generates column headers "Fuel Scored in Auto (count)", "Fuel Scored in Auto (timestamps)", etc., and output data like 2 0,7.8 1 4.7 (2 fuel at 0s and 7.8s, 1 bump at 4.7s).

[github-actions]

PR Preview Action v1.8.1
🚀 View preview at https://FRC2713.github.io/QRScout/pr-preview/pr-94/
Built to branch gh-pages at 2026-02-05 18:42 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[luanzeba]

These are just examples, we'll review them on Monday

[tytremblay]

This looks awesome! Can't wait to show this to the other teams! I vote we merge sooner than later and we can update with our chosen actions later.