daisyui-blueprint 1.6.2 → 1.6.4-beta

package/README.md

@@ -46,7 +46,7 @@ these optional runtime settings:
 | --- | ---: | --- |
 | `MAX_PAGES` | `5` | Maximum Page Architect page IDs returned or accepted per call. |
 | `MAX_COMPONENT_RESPONSE_CHARS` | `24000` | Maximum serialized Component Syntax Expert response size in characters. The first requested entry is always returned even if it alone exceeds the budget. |
-| `MAX_COMPONENT_SKIPS` | `7` | Maximum Page Architect candidate components that may omit syntax retrieval. |
+| `MAX_COMPONENT_SKIPS` | `7` | Maximum components from selected Page Architect pages that may omit syntax retrieval. |
 | `QA_MAX_FILES` | `300` | Maximum files Quality Inspector may audit per call. |
 | `QA_MAX_MB` | `2` | Maximum total megabytes Quality Inspector may audit per call. |
 | `FIGMA_TIMEOUT` | `15` | Figma API request timeout in seconds. |
@@ -64,12 +64,45 @@ next entry would exceed the serialized response budget. When its next step lists
 batch advances to implementation and, for non-conversion workflows, Quality Inspector. A single
 entry is always returned so an unusually large component cannot stall the workflow.
 
+Creative Director and Page Architect are mandatory when the agent creates a new complete page or
+screen. Call Creative Director first, then Page Architect. Both tools are optional for other tasks.
+Conversion workflows skip both tools. Component Syntax Expert remains mandatory before markup.
+
+A Page Architect call with only `context` returns page options. It preserves the active page
+selection and retrieved syntax. Call Page Architect again with the chosen `PageIDs` before
+Component Syntax Expert. Only the explicitly selected pages create component requirements.
+
+Inspector checks static component use only in the supplied files. A component that is absent from
+those files can exist elsewhere in the page. These absence findings are advisory and do not require
+extra components or a wider edit scope. Missing required syntax calls remain blocking findings.
+
 For Quality Inspector, use `auditIntent: "fix_changes"` after Blueprint edits UI code; findings
 may then be fixed only within the supplied changed scope. Use `auditIntent: "report_only"` only
 when the user explicitly requests a read-only audit, and report findings without editing files.
 Every `files[].path` must be relative to the `projectRoot` stored by Setup Expert, such as
 `src/App.tsx` or `.`; never pass an absolute path.
 
+Blueprint creates one design by default. It creates variants only when the user explicitly asks for
+them. Use separate sub-agents when the client supports them and capacity is available. Otherwise,
+create the variants sequentially in the same agent. Each variant must use a distinct `workflowId`
+and start with Setup Expert. Give parallel variants separate files. Assign one coordinator to
+shared files.
+
+When Creative Director supplies guidance, record four planning decisions before implementation.
+Pass the current `concept`, `domainAnchor`, `signatureElement`, and `compositionRule` values to each
+`fix_changes` audit in `originalityEvidence`. Update the values if the design decisions change.
+Include an intentional monochromatic, tone-on-tone, or material palette in the relevant planning
+decision. Inspector uses this evidence and the original `userRequest` to check repeated anchor
+colors. Keep `userRequest` faithful to the user's request; put your own design decisions in
+`originalityEvidence`.
+Quality Inspector validates the four fields and returns a workflow finding when they are missing.
+`SKIP_CREATIVE_DIRECTOR=true` and `report_only` audits do not require these fields. When Creative
+Director supplied guidance, the fields remain required if a browser is unavailable.
+
+These caller-provided decisions are planning records, not proof of originality. Quality Inspector
+does not verify when they were written, enforce unchanged values, or confirm that the UI implements
+them. Rendered review remains a separate check.
+
 Then ask your AI agent to use daisyUI Blueprint:
 
 - "Build a product management dashboard. Use daisyUI Blueprint."
@@ -77,3 +110,14 @@ Then ask your AI agent to use daisyUI Blueprint:
 - "Convert this Bootstrap form to daisyUI."
 - "Create a daisyUI theme from this image."
 - "Check my UI with daisyUI Blueprint and fix the issues."
+
+## Development tests
+
+Run `bun test --no-env-file` for the default suite. Built-server integration uses synthetic
+credentials and a strict test-only license-response mock. It also checks that missing and rejected
+credentials stop startup. The production server still validates every license.
+
+For the live license-service check, set `LICENSE` and `EMAIL` in the process environment, then run
+`bun run --no-env-file test:integration:live`. This sets `CHECK_LIVE_MCP_INTEGRATION=true`.
+The live check fails with a clear error when the credentials are missing. Remote image checks
+remain separate and require `CHECK_REMOTE_IMAGES=true`.