ack-sensors

What problem does it solve?

Acknowledges every sensor available for the host project (catalog mode), verifies that every sensor referenced by an Acceptance Contract has a well-formed .yoke/sensors/<id>.md file (readiness mode), or creates / updates those sensor files from the contract's ## Sensors registry block (upsert mode). Deterministic node — no agentic spawning. Output is structured YAML on stdout; diagnostics go to stderr. Sorted output is byte-identical across consecutive invocations on the same project.

Core Features & Use Cases

• Catalog mode: enumerates every sensor that could run for the host project
• Readiness mode: ensures each referenced sensor has a valid .yoke/sensors/<id>.md with required frontmatter
• Upsert mode: materializes or updates per-sensor files from the contract's ## Sensors registry block
• Per-sensor files: live at .yoke/sensors/<id>.md, acting as the source of truth for id, command, class, tier, applies_to, and run history
• Interactions: used by the Validator at startup and by humans to refresh the memory of available sensors
• Output and validation: emits machine-friendly YAML to stdout and structured diagnostics to stderr; guards against missing registry references via preflight checks

Quick Start

Run the helper from the plugin root with --mode catalog to list sensors, then --mode readiness or --mode upsert with your contract to validate or materialize sensor files.