probe-runlisted

# Run a dynamic-verification probe (slice 2) Drive the layer-5 dynamic-verification pipeline. Each invocation executes one (or several) declarative probe definitions against an ephemeral local docker-compose stack, captures measurements, and feeds them back into the static-layer artefacts. This skill is the maintainer-facing entry point per `adrs/drafts/dynamic-verification-layer.md` slice 2. ## Prerequisite - Local Docker daemon running and reachable as the current user (`docker ps` succeeds without sudo). - `python3` with `PyYAML` + `requests` installed. - The probe-stack docker-compose file exists at `lineage/_extractor/probe-stacks/{profile}.docker-compose.yml`. - The probe definition exists at `lineage/{repo}/probes/{probe-id}.yaml` and is well-formed (`runner.py --validate <id>` passes). - The substrate has been scanned at least once (`lineage/{repo}/manifest.yaml` exists with `last_scan_commit`). If any prerequisite fails, the skill reports the missing piece and exits. ## Argument forms | Form | Behaviour | |---|---| | `/probe-run <probe-id>` | Execute one probe; produce one probe-run artefact; merge measured values into the static layers. | | `/probe-run <id-1> <id-2> ...` | Execute multiple probes in batch mode (shared docker-compose lifecycle). All listed probes must share the same `stack_profile`. Slice-4 capability. | | `/probe-run --feature <feature-id>` | Slice-5. Resolve `feature_id` against `lineage/{repo}/probes/*.yaml`; run every matching probe in bat