chore(apm): bump apm-cli to 0.31.0 - the pin in the install commands, the CI workflows, the marketplace build and the harness kit

.claude/commands/launch-llms-benchmark.md

@@ -146,7 +146,7 @@ Steps:
    - the package, for the opencode target, **into the repository**
      (opencode's user scope takes no MCP server, so `--global` fails
      there):
-     `uvx --from 'apm-cli==0.30.0' apm install --target opencode`
+     `uvx --from 'apm-cli==0.31.0' apm install --target opencode`
      from the repository root. Record `git status --porcelain` **before**
      this command: it deploys files into the working tree — `.opencode/`,
      `.agents/skills/`, `opencode.json`, and an edit to `.gitignore` —
@@ -166,7 +166,7 @@ Steps:
    For `copilot`:
    - `copilot update`, then record `copilot --version`.
    - the package, for the copilot target, **into the repository**:
-     `uvx --from 'apm-cli==0.30.0' apm install --target copilot`
+     `uvx --from 'apm-cli==0.31.0' apm install --target copilot`
      from the repository root. Record `git status --porcelain` **before**
      it: it deploys `.github/prompts/`, `.github/agents/`,
      `.github/hooks/`, `.github/mcp.json`, `.agents/skills/` and an edit

.claude/skills/test-plugin-harnessing/SKILL.md

@@ -68,7 +68,7 @@ the path of `/odd-observe`, `/odd-verify` or `/odd-status`.
 2. **Deploy to every scope the host reads, and prove they match** —
    the scopes are the CLI's, as `launch-llms-benchmark` step 3 states
    them:
-   - `opencode`: `uvx --from 'apm-cli==0.30.0' apm install --target opencode`
+   - `opencode`: `uvx --from 'apm-cli==0.31.0' apm install --target opencode`
      in the lab clone; opencode also reads `~/.claude/skills/`, so copy
      `.apm/skills/*` there too;
    - `claude`: nothing in the clone (the claude target deploys hooks

.github/workflows/ci-apm.yml

@@ -10,7 +10,7 @@ permissions:
   contents: read
 
 env:
-  APM_CLI_VERSION: "0.30.0"
+  APM_CLI_VERSION: "0.31.0"
 
 jobs:
   reference-contract:

.github/workflows/ci-hooks.yml

@@ -16,7 +16,7 @@ permissions:
 
 env:
   RUFF_VERSION: "0.16.4"
-  APM_CLI_VERSION: "0.30.0"
+  APM_CLI_VERSION: "0.31.0"
 
 jobs:
   lint:

AGENTS.md

@@ -75,7 +75,7 @@ the paths touched (commands and pins are owned by
   (`bash scripts/build-marketplace.sh`, then revert the generated
   trees).
 - `.apm/` or `apm.yml` changed → validate the package like CI does:
-  `uvx --from apm-cli==0.30.0 apm install --target claude && uvx --from apm-cli==0.30.0 apm audit`,
+  `uvx --from apm-cli==0.31.0 apm install --target claude && uvx --from apm-cli==0.31.0 apm audit`,
   and `python3 .apm/skills/observability-cli-guides/scripts/check_stack_reference.py`
   when a stack reference changed.
   The install deploys the package into the working tree and edits

CONTRIBUTING.md

@@ -59,7 +59,7 @@ bash scripts/build-marketplace.sh
 
 # Validate the APM package like CI does (keep the apm-cli pin: it is
 # the minimum supported version, and older releases corrupt the install)
-uvx --from apm-cli==0.30.0 apm install --target claude && uvx --from apm-cli==0.30.0 apm audit
+uvx --from apm-cli==0.31.0 apm install --target claude && uvx --from apm-cli==0.31.0 apm audit
 python3 .apm/skills/observability-cli-guides/scripts/check_stack_reference.py   # every stack reference follows references/CONTRACT.md
 ```
 
@@ -138,7 +138,7 @@ name only. The full set of rules a reviewer holds a report to is in
 
 The product tests itself: install your working copy into a scratch
 consumer
-(`uvx --from apm-cli==0.30.0 apm install /path/to/your/clone --target claude`),
+(`uvx --from apm-cli==0.31.0 apm install /path/to/your/clone --target claude`),
 or run
 the ODD loop on the repo itself (`/odd-observe` on `oddyssey-mcp`) —
 the stored reports under `.odd/` show what a healthy run looks like.

README.md

@@ -15,7 +15,7 @@ https://github.com/user-attachments/assets/a8dbc6e1-115e-4f33-83d1-b488bb1d9c51
 With [APM](https://microsoft.github.io/apm/), to install the latest release, for Claude Code:
 
 ```bash
-uvx --from 'apm-cli==0.30.0' apm install --global --target claude 'using-system/oddyssey#>=1.0.0'
+uvx --from 'apm-cli==0.31.0' apm install --global --target claude 'using-system/oddyssey#>=1.0.0'
 ```
 
 Same command for every other supported CLI agent — swap the target:
@@ -26,11 +26,11 @@ only.
 To update an existing install to the latest release:
 
 ```bash
-uvx --from 'apm-cli==0.30.0' apm update --global --target claude using-system/oddyssey
+uvx --from 'apm-cli==0.31.0' apm update --global --target claude using-system/oddyssey
 ```
 
 It shows the update plan and asks for confirmation (`--yes` to skip,
-`--dry-run` to only look); `uvx --from 'apm-cli==0.30.0' apm outdated`
+`--dry-run` to only look); `uvx --from 'apm-cli==0.31.0' apm outdated`
 tells you whether an update is worth running.
 
 ### From the native marketplaces (no APM)

scripts/build-marketplace.sh

@@ -11,7 +11,7 @@
 # always carry the released version and the matching oddyssey-mcp pin.
 set -euo pipefail
 
-APM_CLI_VERSION="${APM_CLI_VERSION:-0.30.0}"
+APM_CLI_VERSION="${APM_CLI_VERSION:-0.31.0}"
 ROOT="$(cd "$(dirname "$0")/.." && pwd)"
 cd "$ROOT"