docs: simplify the README and record the pad layout
validate / validate (pull_request) Successful in 58m44s
validate / test (pull_request) Successful in 58m45s
validate / markdownlint (pull_request) Successful in 58m40s

The README carried a lot of rationale that AGENTS.md already holds; what is
left is the tables a consumer wires against. It gains the swept axis and
button indices, and says plainly that the axes check themselves at runtime
and the buttons cannot.
This commit is contained in:
2026-09-16 18:06:12 -03:00
parent eede2e5774
commit e3fc538e5d
3 changed files with 231 additions and 331 deletions
+6
View File
@@ -53,6 +53,12 @@ inputs:
pad node is indistinguishable from an unplugged pad as far as the arm is
concerned.
Each pad is measured the first time it is seen sitting still, so a stick
that no longer centres has its tilt subtracted rather than deadzoned away.
A pad whose resting axes do not fit the layout this node compiles in — a
trigger where a stick should be, say — reads the same as no pad at all
and is named in the log, rather than being guessed at against a real arm.
Leave it unwired for a browser-only console. The node says so and starts.
response:
required: false