v5.9.0 — Brand kits on the tool surface

Contract refresh for API v5.226.0.

• upload_asset gains purpose=brand (forward spelling of theme — one path, two names, theme still accepted) for uploading a brand kit template.
• browse_catalog gains type=brands — list your kits with versions (theme_id=<slug> default, <slug>@<n> pins one).
• manage_account gains action=brand_report (per-token fidelity report) and action=feedback_list (read your filed reports back).
• README, llms-install.md, AGENTS.md and the skills now document brand kits.
• Fixed a real pricing error in the pdf-to-pptx skill (extraction has always billed $0.01/page, not free) and its stale claim about scanned PDFs.

Additive only — no tools or parameters removed or renamed. Full CHANGELOG entry: CHANGELOG.md.

v5.5.1 — Dockerfile command args

Dockerfile CMD is now ["python", "-m", "slideforge_mcp"] (command + args) so container launchers that require a non-empty argument list — e.g. Glama's deploy config ("At least one command argument is required") — accept it. Adds slideforge_mcp/__main__.py. Behaviour identical to the slideforge-mcp console script.

v5.5.0 — local stdio MCP server

Adds a local stdio MCP server alongside the hosted remote endpoint. A thin REST client over api.slideforge.dev (holds no engine logic): the 7 tool schemas are baked in locally — so tools/list works with no network and no key — and each call forwards to the REST tool-dispatch endpoint (POST /v1/tools/{name}) authenticated with SLIDEFORGE_API_KEY.

• For clients that boot MCP servers from a container/stdio, and for offline schema discovery.
• Most agents should keep using the hosted remote server (https://api.slideforge.dev/mcp/, OAuth 2.1 or API key) — no install.
• Ships pyproject.toml (console entry slideforge-mcp), the package under src/slideforge_mcp/, a prod contract snapshot, and a contract-parity test.
• Replaces the previous mcp-remote-based Dockerfile with one that builds and runs the local server.

Install: pip install slideforge-mcp · Docker: docker build -t slideforge-mcp .

v5.2.0 — safe mode, code-mode trust contract, quality profiles

Syncs the repo to the served surface (service v5.81.0). Three engineering arcs landed since 5.1.0, each validated by an external retest (5.5 → 8.2/10):

• mode=safe: validate-then-render in ONE call — renders and bills only if faithful, otherwise a $0 invalid report with the fix. The recommended default over the dry_run round-trip.
• Code-mode trust contract: intent fields (headline/context/takeaway/source_note) render as deterministic chrome around your build(prs, slide); verify tiers (lint default, lint+vlm visual second-look); helper geometry contracts reject impossible dimensions with exact numbers; code renders carry the same status/warnings[]/errors[] vocabulary and a measured layout readiness block. Code-mode slides are first-class deck children.
• Quality profiles: quality_profile (executive | technical | appendix) sets the readiness bar layout.presentation_ready is judged against — measurement only, never blocks or re-prices.
• Complex-diagram robustness: connector-routing/label solver kernel for flows, org charts, swimlanes; capacity contracts on relationship-heavy forms (over-dense content is refused honestly with a decomposition plan rather than rendered unreadable); six decomposition strategies.
• Routing controls: variant_policy (production_safe), literal candidate_margin, calibrated route.confidence with honest labels; decisive routes never read as ambiguity.
• Honest-by-default flags: allow_fabrication / allow_truncation / allow_low_confidence — the server rejects at $0 rather than guessing, unless you opt in.

Server: https://api.slideforge.dev/mcp/ (remote — OAuth 2.1 or API key, no install).
Full history: CHANGELOG.md