bug(cli): high precision flag is advertised but not implemented

[kmch4n]

Summary

--high is exposed as a high precision / frame interpolation mode, but the video pipeline only logs that the feature is planned for the future. The flag currently does not change inference, frame processing, scoring, or output behavior.

Expected behavior

Either --high should enable a real high precision path, or the CLI/help text should stop advertising frame interpolation until it exists.

Actual behavior

run.py accepts --high and passes high_precision=True into process_video(). process_video() only emits a log message and then runs the same frame loop as normal mode.

Steps to reproduce

1. Run python run.py --high.
2. Compare the code path with python run.py.
3. Observe that no processing branch changes beyond the log message.

Environment

Any environment. This is visible from static code inspection.

Evidence

• run.py:35 defines the --high flag.
• run.py:36 describes it as high precision mode with frame interpolation.
• run.py:50 passes the flag to process_video().
• src/skisense/main.py:420 checks high_precision.
• src/skisense/main.py:421 logs that frame interpolation is a future implementation.
• rg high_precision only finds the CLI pass-through and this log branch.

Impact

Users can believe they are running a more accurate analysis mode when the output is actually identical to normal mode. This also makes benchmark comparisons unreliable.

Suspected cause

The CLI option was added before the processing implementation.

Priority

medium

Labels

bug

Acceptance criteria

• --high either performs a documented high precision workflow, or the flag/help text is removed.
• README and CLI help describe the same behavior.
• A small validation confirms that high precision mode has a measurable code-path difference if kept.

[kmch4n]

Decision: defer — keep as placeholder

For now, --high stays as a callable flag that only logs intent, matching the current behavior in src/skisense/main.py:442-443. No code change is being made in this iteration.

Rationale

A meaningful high-precision path (One-Euro keypoint smoothing, optical-flow keypoint propagation, multi-frame fusion, etc.) is a non-trivial design exercise that doesn't fit a single-issue fix. It also overlaps with future temporal-smoothing work tracked in the project's pose-improvement backlog. Removing the flag now would lose the entry point if/when that work lands.

Action

• Priority lowered from medium to low.
• Flag, help text, and process_video(high_precision=...) plumbing remain as today.

Follow-up

If temporal smoothing or any real high-precision path is picked up, file it as a fresh enhancement issue and decide there whether it wires into --high or supersedes it. At that point, this issue can either be closed as superseded or repurposed.