Add TODO notes for ARM register access

[Copilot]

• Re-run baseline build/configure checks to confirm current status
• Apply clang-format to register comment updates
• Re-run targeted build/configure checks
• Reply to PR comment with commit reference

[Ko496-glitch]

@copilot so for shared api for read/write maybe something like HAL would make sense ?

[Copilot]

@copilot so for shared api for read/write maybe something like HAL would make sense ?

Yes — a HAL-style boundary makes sense. The public read/write API can stay shared while a per-arch (and per-regset) backend handles the actual ptrace/regset mechanics and sub-register masking.

[Ko496-glitch]

@copilot you can just add inlibe comments in the include/libkdb/registers.hpp and registers.cpp and mark it as ready for review
dont write too much just mention as a TODO section of ARM implementation

[Copilot]

@copilot you can just add inlibe comments in the include/libkdb/registers.hpp and registers.cpp and mark it as ready for review
dont write too much just mention as a TODO section of ARM implement...

Added concise ARM TODO notes in registers.hpp and new registers.cpp. Commit: e50e0c5. No UI changes.

[Ko496-glitch]

@copilot make sure we have to clang-format on the comments

[Copilot]

@copilot make sure we have to clang-format on the comments

Ran clang-format on the comment block; update is in commit de64734. No UI changes.