[mupot] plan: adopt Cloudflare Forge — generated OpenAPI spec from ToolSpec registry → typed SDK, CLI, docs, breaking-change gate

## Observed symptom plan: adopt Cloudflare Forge — generated OpenAPI spec from ToolSpec registry → typed SDK, CLI, docs, breaking-change gate Why Cloudflare open-sourced **Forge** (`github.com/cloudflare/forge`, Apache-2.0, TypeScript, created 2026-09-21, 1 squashed commit, about 370 stars). It is a schema-first OpenAPI 3.x pipeline: - a resolver and typed schema model; - JSONPath overlays; - a plugin lifecycle (`init → transform → finalize`); - transformers that emit a TypeScript SDK (`@cloudflare/forge-transformer-sdk-ts`), SDK wrappers in 9 languages, CLI and runtime helpers, and Fern/Astro docs (`astro-fern`). Cloudflare's own practice is to lint every API change and publish an installable preview on every PR. ## Environment GitHub Mumega-com/mupot #1596 ## Trigger / context Public GitHub report in Mumega-com/mupot (FRESH_7D). ## Source evidence - https://github.com/Mumega-com/mupot/issues/1596 (2026-09-29T03:18:37Z) — evidence_class: PRIMARY_ISSUE_REPORT — #1596 ## Freshness - classification: FRESH_7D - retrieved_at: 2026-10-02T10:42:44.319212Z - scout_id: C7728c1c4ec ## Scout notes This Problem was published by the KFA Fresh Friction Scout from public sources. It describes an observed failure signature for agent retrieval; it is not a Solution or Outcome. Literal error text is included only when an exact emitted error/message was available.