fix(viz): self-DOS guards on sensor URL overrides

[WomB0ComB0]

Summary

Three security follow-up tweaks from the post-merge review of #85 / #86. URL overrides for world bounds and LiDAR scan params previously accepted any positive finite value; a typo like ?worldGrid=8192 (~2 TB voxel buffer) or ?lidarRange=1e30 (DDA walks every voxel + float-precision erosion) would lock up the GPU.

Self-DOS only — no server amplification, no cross-origin attack surface — but a sane upper bound prevents "my browser tab died" footguns when an operator typos a test URL.

Caps

Param	Range	Reason
worldGrid	≤ 1024	1024³ × 4 B = 4 GB voxel buffer ceiling
voxelScale	≤ 256	1024 × 256 = 256 km cube ceiling
lidarElev / lidarAzim	≤ 4096	LiDAR manager capacity from registry.ts
lidarRange	0.1–10 000 m	Visualization terrain is only 4 km
lidarInterval	0.001–60 s	1 minute is the practical floor for "useful sensor"

Log hygiene

Truncate raw log value to 64 chars (+ … ellipsis) in all URL warn paths, so a poisoned URL with megabytes of garbage can't bloat the console or log aggregator. Shared _truncRaw helper in both files.

The lenient _readPositiveFinite helper in effects.ts is removed — the two call sites (lidarRange, lidarInterval) now use _readNumberInRange with explicit bounds, matching the pattern already used for lidarFov.

Bundle

Main 757.7 → 757.9 KB (+0.2 KB; 92.5 % of cap).

Test plan

• npm run build passes
• tsc --noEmit clean
• npm test 17/17 green
• Browser: ?worldGrid=99999 → warn-and-fall-back
• Browser: ?lidarRange=1e30 → warn-and-fall-back
• Browser: ?worldGrid= + 100 KB of garbage → log shows truncated …

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@WomB0ComB0 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 32 minutes and 56 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: fe593a24-5f6b-4205-b73a-8c515a883cd0

📥 Commits

Reviewing files that changed from the base of the PR and between 3890d8e and 971461e.

📒 Files selected for processing (2)

• src/ResQ.Viz.Web/client/effects.ts
• src/ResQ.Viz.Web/client/webgpu/sensors.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/sensor-url-bounds

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 32 minutes and 56 seconds.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request introduces sanity upper bounds for LiDAR and world grid parameters passed via URL overrides to prevent potential Denial-of-Service (DoS) scenarios and GPU lockups. It also adds a _truncRaw utility to truncate long URL parameter values in warning logs, protecting against log bloat. I have no feedback to provide as there were no review comments to evaluate.