Generated/runtime plugins should use the boring-ui primitive/design-system APIs instead of ad-hoc UI or importing broad workspace internals.\n\nKey requirement:\n- The agent runtime must have the relevant boring-ui package(s) installed/provisioned locally, so scaffolded plugins can import primitives reliably from inside the runtime workspace.\n\nAcceptance criteria:\n-
scaffold-plugin
workspace /home/ubuntu/projects/boring-ui-v2-plugin-agent-layer/scaffold-plugin
mode local-sandbox
port 5200
host 0.0.0.0 templates import documented boring-ui primitives where appropriate.\n-
verify-plugin
workspace /home/ubuntu/projects/boring-ui-v2-plugin-agent-layer/verify-plugin
mode local-sandbox
port 5200
host 0.0.0.0 can detect/warn on unsupported broad host imports and missing runtime packages.\n- Workspace/agent runtime provisioning installs the required boring-ui package(s) for local plugin authoring.\n- Prompt/skill docs instruct agents to use boring-ui primitives for generated plugin UI.\n- Hosted runtime plan accounts for the same imports via sandbox dependency/provisioning or iframe bundle build inputs.\n\nNotes:\n- Keep generated plugins route-free.\n- Do not force app/internal plugins through this restriction; they may use richer app-owned UI APIs.\n- This ties into the later runtime-plugin plan: generated plugins should consume a stable primitive surface, while core/workspace owns shell/layout/bridge.
Generated/runtime plugins should use the boring-ui primitive/design-system APIs instead of ad-hoc UI or importing broad workspace internals.\n\nKey requirement:\n- The agent runtime must have the relevant boring-ui package(s) installed/provisioned locally, so scaffolded plugins can import primitives reliably from inside the runtime workspace.\n\nAcceptance criteria:\n-
scaffold-plugin
workspace /home/ubuntu/projects/boring-ui-v2-plugin-agent-layer/scaffold-plugin
mode local-sandbox
port 5200
host 0.0.0.0 templates import documented boring-ui primitives where appropriate.\n-
verify-plugin
workspace /home/ubuntu/projects/boring-ui-v2-plugin-agent-layer/verify-plugin
mode local-sandbox
port 5200
host 0.0.0.0 can detect/warn on unsupported broad host imports and missing runtime packages.\n- Workspace/agent runtime provisioning installs the required boring-ui package(s) for local plugin authoring.\n- Prompt/skill docs instruct agents to use boring-ui primitives for generated plugin UI.\n- Hosted runtime plan accounts for the same imports via sandbox dependency/provisioning or iframe bundle build inputs.\n\nNotes:\n- Keep generated plugins route-free.\n- Do not force app/internal plugins through this restriction; they may use richer app-owned UI APIs.\n- This ties into the later runtime-plugin plan: generated plugins should consume a stable primitive surface, while core/workspace owns shell/layout/bridge.