Features across a version range
Parse <selector> [--from <version>] from "$ARGUMENTS". Scripts live in
${CLAUDE_PLUGIN_ROOT}/scripts/ and are named bare below. Read-only on the fleet: the only thing
written is the decision journal. Load the instance-upgrade and docs-research skills first —
this command carries the procedure, they carry the knowledge.
Process
- Targets and range.
fleet.py resolve "<selector>" --table, thenversions.py "<selector>" --json.--fromdefaults to the lowest installed version in the selection; the upper bound is the accepted target from the soak gate, else the highest installed version. Every version string you print must be an echo from that output or from a fetched release page — never from memory. - Fetch the notes for each release in the range (
docs-researchfetch ladder; quote the URL per entry). A release whose notes could not be fetched is listed asunreviewed, never inferred from its version number. - Keep only decidable entries — a release note earns a row only if it adds a config key or a command, subcommand or flag. Fixes, internals and performance work are not decisions and are dropped. This is the whole filter; without it the table is a changelog nobody reads.
- Free second source:
ocexec.py <inst> --json -- doctor --lintafter an upgrade usually names the deprecated form of something that has a newer one. Fold those findings in as candidates. - Classify each entry against the real config, per instance, reading it with
ocexec.py <inst> --json -- config get <path>(R0):already-on— the key exists and is setavailable-off— supported by this version, absent from the confignot-applicable— the feature addresses something this instance does not do; say whatunsupported-here— the instance is older than the release that added it; the row is an upgrade argument, not a config change
- Render the table:
FEATURE | ADDS | INSTANCE | STATE | RECOMMEND | RISK | SOURCE. Risk is a class fromgate.RISK_CLASSES, not an adjective.SOURCEis the URL. - Journal the decisions in
<state-root>/openclaw-ops/features/decisions.json(mode 0600, beside the health snapshots;policy.snapshot_dirmoves the root). Read it before step 6 — anything already declined is rendered asdeclined <date>and is not re-proposed — and append to it after the operator answers: one record per feature with id, version, decision (adopted/declined/deferred), date and a one-line reason. The next upgrade must not re-litigate what was already settled.
Rules
- Nothing is enabled here. A row recommended for adoption is handed on: a finding id goes to
/openclaw-ops:repair <inst> --issue <id>, anything else to theconfig-surgeryskill in its own turn with its own plan and its own--yes. - No live source, no recommendation. With neither the network nor the CLI reachable, report the
observed config state and stop (
docs-researchunverified-knowledge mode). - Model ids and version numbers appear only as echoes from the box or the fetched page.
- Never pass
--fix; never run anything above R0 from this command.
Example
/openclaw-ops:features managed
/openclaw-ops:features @reference --from <version-installed-before-the-last-upgrade>