[Verslabs]

Summary

Closes #30. HudOverlay.render resolved the crosshair target for dwell tracking, and renderConfidencePanel resolved it again. Both the compact panel and the hover tooltip also re-read FlagHistory (tier, score, explanation, alerted checks, flag counts), which takes locks and allocates, and rebuilt their Text lines every frame.

Changes

• The crosshair target is resolved once per frame and passed to dwell tracking and both panels.
• New PanelModel: header, explanation and FP-hint lines, built at most once per client tick (or on a target change) and shared by the compact panel and the hover tooltip. The tooltip's extra "top flagged checks" line is built lazily, only when the tooltip is shown.
• The tier comes from the tracker's per-tick TrackedPlayer.tier cache (what the nametag mixins read), falling back to FlagHistory.tierFor for untracked targets.
• The cache is cleared when there is no target.
• Display output is unchanged and at most one tick stale. All paths stay fail-open (each render call is still wrapped in try/catch).

Affected areas

• Detection/check logic
• Packet observation or inference
• Config or presets
• Commands or UI
• Rendering or HUD
• Replay, clips, camera, or input
• Persistence or local data
• Documentation/tests/tooling

Verification

Commands run (branch head 2f4536f):

python scripts/verify_contribution.py --static
./gradlew test
./gradlew build
python scripts/live_selftest.py --check pipeline-smoke

Results:

• Static verifier: PASS (only warning: no build/selftest-manifest.json before the first live run)
• Tests: PASS, BUILD SUCCESSFUL, 49 tests, 0 failures, 0 errors
• Build: PASS, BUILD SUCCESSFUL

Live client verification

• Client launch/mixin application: PASS. The real 1.21.11 client booted with this branch through runClientGameTest, and pipeline-smoke passed (1/1).
• Scenario(s): client boot plus the detection pipeline smoke test.
• Expected result: the client loads with the HUD callback registered and no errors.
• Observed result: as expected.
• Not tested: the automated suite doesn't look at HUD rendering. I haven't done a manual runClient check of the confidence panel and hover tooltip with a flagged target, and I haven't profiled the frame-time saving.

Safety and privacy review

• No telemetry, uploads, analytics, or remote reporting were added.
• No unintended outgoing gameplay packets were added.
• Fail-open behavior is preserved where appropriate.
• Local-world, camera, input, and persistence state restore after stop/error/world change where relevant.
• Logs, screenshots, clips, and test data contain no secrets or private information.

Documentation and migration

• User-facing documentation updated, or no update is needed.
• Config/clip migration reviewed, or no migration is needed.
• Generated documentation source data updated if applicable. (Not applicable.)

AI assistance

• AI tool(s) used: Claude Code (Claude Opus 5.5)
• What the tool contributed: wrote the change, and ran the static verifier, Gradle test/build and the live smoke test above.
• What I reviewed manually: the diff, with an AI-assisted review pass on 2026-10-12. Maintainer review requested.

Known limitations and follow-up work

• A flag that arrives mid-tick shows up on the HUD one tick later.
• Conflicts with i18n: add L10n pattern, lang verifier and first migrated call sites #43: both PRs edit HudOverlay.kt (i18n: add L10n pattern, lang verifier and first migrated call sites #43 moves the same panel strings to L10n). Whichever merges second needs a rebase, and the PanelModel lines should then use the L10n keys.
• Needs a manual HUD check in runClient before merge.