feat(mcp): add list_recent_decisions tool (#1982)

[saurabhjain1592]

Summary

V1.1 (axonflow-enterprise#1982) — adds axonflow_list_recent_decisions to OpenClaw's agent-callable tool surface. Companion to the existing axonflow_explain_decision tool: explain answers "why was this blocked?" for a single decision; list_recent_decisions answers "what's been blocked recently?" with a 5-field summary per row.

What changed

File	Why
src/upgrade-prompt.ts	Added decision_list_size to V1_LIMIT_TYPES. Required for handleEnvelope to recognize the new V1.1 limit type — without this, the throttle gate would silently drop the upgrade wording.
src/axonflow-client.ts	New listRecentDecisionsStrict method. Returns { kind: "ok", decisions } on 200 / { kind: "envelope", envelope } on 429 / throws on other non-2xx. The 429 path runs through the existing handleEnvelope helper so the throttle file is stamped + the upgrade wording is logged once-per-day.
src/agent-tools.ts	New buildListRecentDecisionsTool. Maps the JSON-Schema args → client method. On envelope hit, returns a structured tool result with upgrade_required: true so the host LLM/UI can render the upgrade prompt.
src/index.ts	Re-exports buildListRecentDecisionsTool.
Tests	4 new agent-tools.test.ts cases (forwarding, decision-enum, envelope passthrough, transport error). Updated registration count 10→11. Updated V1_LIMIT_TYPES lock test.
runtime-e2e/list-recent-decisions/	New wire-level runtime-e2e gate: tools/list advertisement check + happy-path + cap-hit envelope passthrough.
tests/e2e/runtime-tools-smoke.mjs	Added 6th scenario for the new tool. Pre-existing bug fix: expectedNames was stale at 5 (V1 Pro added 5 more, never updated) — extended to the full 11-tool surface.
runtime-e2e/_lib/openclaw-runtime.sh	Pre-existing bug fix: hardcoded Registered 5 agent-callable tools regex was stale since V1 Plugin Pro. Replaced with Registered [0-9]+ so the gate doesn't break on every tool addition.

Three-rule definition of done

Rule 0 — Runtime proof

Captured at runtime-e2e/list-recent-decisions/EVIDENCE.txt:

PASS: MCP session initialized (axonflow-e8d8a91a00596c14522b7912)
PASS: MCP server advertises list_recent_decisions
PASS: tools/call list_recent_decisions returned a recognized shape
PASS: cap-hit returned wrapped V1 envelope (upgrade_required + decision_list_size + buy_url)

PASS: list_recent_decisions runtime — MCP server advertises tool, happy path returns decisions, cap-hit preserves V1 upgrade envelope

Also verified via tests/e2e/runtime-tools-smoke.mjs against the live stack:

Registered 11 tools: axonflow_audit_search, axonflow_explain_decision, axonflow_list_recent_decisions, ...
--- 6/6 axonflow_list_recent_decisions ---
PASS: list_recent_decisions returned 0 decisions
PASS: runtime-tools-smoke — all 6 tools registered and dispatch correctly

Rule 1 — Self-review

Hunk-by-hunk per the 5-question protocol from feedback_self_review_is_mandatory_every_pr.md:

• ✅ The tool's execute() does NOT collapse 429 into isError: true. The kind === "envelope" branch returns the upgrade message + structured details so the host renders it as success-with-upgrade-prompt, not as a tool failure. This is the exact gap from feedback_429_no_upgrade_hint_is_conversion_gap.md.
• ✅ decision_list_size was added to V1_LIMIT_TYPES. Without this, handleEnvelope would short-circuit at line 309-314 (if (!V1_LIMIT_TYPES.includes(envelope.limit_type))) and silently drop the wording.
• ✅ The new SQL-bound input fields are validated client-side (decision enum check before the HTTP call) so a malformed arg becomes a structured isError instead of a wasted round-trip.
• ✅ listRecentDecisionsStrict distinguishes 429 (envelope) from other non-2xx (throws AxonFlowHttpError) — same defense-in-depth shape as the existing searchAuditEventsStrict / listOverridesStrict methods.

Rule 2 — No deferred bugs

Two stale checks fixed in this same PR rather than handed off to "another session":

• runtime-tools-smoke.mjs expectedNames (was frozen at 5; bumped to 11).
• openclaw-runtime.sh Registered 5 regex (replaced with Registered [0-9]+).

Both were latent since the V1 Plugin Pro tools landed; the broken state was simply masked because nobody ran the e2e since then.

Test plan

• npx jest --no-coverage — 450/450 pass
• npx tsc --noEmit — clean
• bash runtime-e2e/list-recent-decisions/test.sh against docker-compose at localhost:8080 — PASS
• node tests/e2e/runtime-tools-smoke.mjs against docker-compose at localhost:8080 — PASS

Do NOT merge

Per feedback_v1_1_no_merge_during_release_window.md: V1.1 release-window PRs stay open until user explicitly authorizes the V1.1 release. This PR consumes the platform endpoint at getaxonflow/axonflow-enterprise#1985 (also held open). Both land together when V1.1 ships.

[saurabhjain1592]

🚫 Release-window hold

Per feedback_v1_1_no_merge_during_release_window.md: V1.1 PRs stay open until the user explicitly authorizes the V1.1 release.

This PR depends on the platform-side endpoint + MCP tool registration in getaxonflow/axonflow-enterprise#1985, which is also held open. The two land together when V1.1 ships.

Runtime testing + verification on this branch only — do not merge to main.