[xiduzo]

Why

The docs described a contract no code implemented:

• figma/<name> topics on the generic MQTT node, including in both Penpot pages and two templates;
• microflow/v1/… topics with full VariableIDs;
• a /set web route and a microflow-studio:// scheme for prototypes;
• separate Host and Port fields;
• a node "renamed to MQTT (Express)";
• a README claim that a Penpot prototype can turn on an LED.

What changes

• Plugin docs, Figma and Penpot: parallel structure. Each covers what the plugin does (editor-time, not prototypes), install, the single Broker URL field and default broker, the Bridge ID and where to find it in Studio, the MHB collection/token set with the type mapping, both directions of value flow, the raw ADR-0028 topic table for other MQTT clients, and limitations (no booleans in Penpot). The pages the plugins' help buttons open are the landing pages.
• Design variable node page, updated how-tos, the "Link a sensor to Figma or Penpot" tutorial (matches the template), troubleshooting (Bridge ID, reachability, mosquitto_sub microflow/<id>/#), the glossary, the MQTT node page, and the home page string.
• README, ARCHITECTURE (packages/design-bridge, the protocol seam), SECURITY (plain-text plugin credentials, allowedDomains: ["*"], rejectUnauthorized: false, the Bridge ID as the only separation on a public broker), QA and TECH.
• docs/plans/design-tool-bridge.md: the plan, its decisions, and §6 Outcome and findings: what was built, where the build differs from the plan, the Penpot and Figma API findings, verification, and what is still open.

Verification

• bun run types:check and a full bun run build of apps/fumadocs pass.
• Every internal /docs/… link and anchor resolves.

🤖 Generated with Claude Code