probelisted

# The probe report This skill ships with ShipIt's test plugin (docs/262). If you can read this text through your skill listing, skills materialization (req 22) works: the file was copied from the plugin checkout into your backend's discovery root under a `plugins--<alias>--probe` namespace. Run `probe` in the project workspace. It prints one JSON report and mutates nothing. Flags: `--bump` increments the shared counter before reporting; `--host-check` also tests HTTPS egress to the declared host (example.com), which the manifest declares **optional** (reqs 23, 24) — the probe reports whether it got through and exits 0 either way, so the Plugins card offers that host rather than counting it as an unmet need. `PROBE_TOKEN` stays required, so the fixture carries one of each. | Field | Verifies | |---|---| | `cwd` | CLI runs with cwd = the project workspace (req 21) | | `mode` / `env.SHIPIT_PLUGIN_COMMIT` | the self/consumer discriminator: a consumer generation carries its exact commit; `repo: self` runs the live tree, no commit (reqs 15, 27) | | `credential.set` | `PROBE_TOKEN` injected for this command only (req 23) | | `settings.greeting` | the validated settings file (req 26), and **which side wrote it**: the consuming project's `overrides.settings` is `hello from the consuming project`, the manifest's default is `hello from the probe`. Reading the default under this repo's own `shipit.yaml`, which sets the override, means the consumer half was ignored (nikzlabs/shipit#229