P11.5 + B2.1/B2.2: per-command units + description (where applicable)

Adds  to scalar setters whose payloads are
plain numbers OR {value, unit}. Skipped where payload is compound or
mode-dependent (control-%, {F, C: [...]}, etc.) — documented inline.
Every command gains a description field for wikiGen consumption.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
znetsixe
2026-05-11 17:41:19 +02:00
parent 497f05d92c
commit 15b7414d41

View File

@@ -14,27 +14,32 @@ module.exports = [
// Toggle — payload is ignored. `any` keeps the registry validator happy
// for legacy callers that ship trigger payloads of various shapes.
payloadSchema: { type: 'any' },
description: 'Toggle the built-in simulator on / off.',
handler: handlers.setSimulator,
},
{
topic: 'set.outlier-detection',
aliases: ['outlierDetection'],
payloadSchema: { type: 'any' },
description: 'Toggle / configure outlier detection on the measurement pipeline.',
handler: handlers.setOutlierDetection,
},
{
topic: 'cmd.calibrate',
aliases: ['calibrate'],
payloadSchema: { type: 'any' },
description: 'Trigger a one-shot calibration of the measurement.',
handler: handlers.calibrate,
},
{
topic: 'data.measurement',
aliases: ['measurement'],
// Mode-dispatched: digital expects object, analog expects number/numeric
// string. The handler validates per-mode (the registry-level typeof
// check would reject one of the two valid shapes).
// Mode-dispatched: digital expects object (per-channel), analog expects
// number/numeric string in the configured Channel scaling units. Units
// are mode-dependent and resolved inside the handler — no registry-level
// `units` field.
payloadSchema: { type: 'any' },
description: 'Push a raw measurement (analog: number; digital: per-channel object).',
handler: handlers.dataMeasurement,
},
];