markdowntown-workbench

What problem does it solve?

Coordinating Workbench UI, normalized state (UAM v1), and the export/compile pipeline is complex and error-prone, causing mismatched adapter outputs, missing targets, and confusing compile warnings that block exports and integrations.

Core Features & Use Cases

• Workbench UI & state guidance: Where to find key components and the single source of truth in useWorkbenchStore for selection, scopes, blocks, and scan handoff.
• Export and compile pipeline: How the Export panel, /api/compile endpoint, compile aggregation, and adapter registry interact and where to change behavior.
• Adapter management: Registering adapters, resolving target/version metadata, and updating adapter output or options with docs alignment.
• Tests & validation: Recommended checks to run and where to update unit and integration tests when export behavior changes.
• Use Case: When an adapter produces file collisions or incorrect formatting, reproduce the compile result in the Export panel, update the adapter or compile logic, and validate warnings surface correctly.

Quick Start

Reproduce the failing compile via the Workbench Export panel, inspect the compile output and adapter mapping, then update the compile or adapter code and rerun tests to verify warnings are resolved.