clean-room-sensor-implementation.md

Summary

Related Issues

Type of Change

• Bug fix (fix/ branch)
• New feature (feat/ branch)
• Refactoring (refactor/ branch)
• Documentation (docs/ branch)
• Dependencies update
• Other (chore/ branch)

Clean-room provenance

Implemented from docs/specs/sensors/<doc>.md revision <N> (commit <sha>).
Implemented from docs/specs/sensors/<doc>.md revision <N> (commit <sha>).
No other external sensor documentation was used.

Implementer attestation

• This implementation references only docs/specs/sensors/** (at the revisions pinned above) and this repository.
• Every spec document pinned above carries Status: Implementation-ready (rev N) at the pinned revision and has no unresolved TODO(provenance) markers (see "Status transition" in docs/specs/sensors/README.md).
• I did not consult LibreHardwareMonitor, OpenHardwareMonitor, Linux kernel, lm-sensors, or any decompiled monitoring tool while writing this implementation (full prohibited-source list: .github/instructions/clean-room-sensors.instructions.md).
• Register access added by this PR is read-only; the only writes are those the pinned specs document as required for reads (e.g. Super I/O config keys, bank select), and the ecosystem mutex conventions are honored.

Reviewer attestation

Reviewers: copy the checklist below into your approval review comment, with both boxes checked. Do not approve without it.

- [ ] I reviewed this implementation only against
      `docs/specs/sensors/**`, this repository, and the pinned spec
      revision.
- [ ] I did not consult LibreHardwareMonitor, OpenHardwareMonitor,
      Linux kernel, lm-sensors, or decompiled monitoring tools while
      reviewing this implementation.

Screenshots / Videos

Test Plan

• Manual testing
• Unit tests

Checklist

• Self-reviewed the code
• Linting and formatting pass (npm run lint && npm run format / cargo tauri-lint && cargo tauri-fmt)
• Tests pass (npm test / cargo tauri-test)
• No new warnings or errors