chatroom-cli 1.122.2 → 1.123.0

package/dist/index.js

@@ -107954,6 +107954,7 @@ function getUiuxEngineerRequirements() {
 - Define component hierarchy and ownership, props/state/events, data boundaries, and interaction behavior.
 - Choose concrete existing ShadCN components with the Base UI backend and lucide-react/react-icons conventions; do not write "use an appropriate component."
 - Specify Tailwind utility classes or semantic theme-token classes for layout, spacing, sizing, typography, states, responsive behavior, and dark mode.
+- Provide the target HTML markup with exact class attributes and any required CSS/styles in the handoff.
 - Specify responsive breakpoints/layout behavior, visual feedback, destructive-action safeguards, exact files/components, and the UI/integration test plan.
 - Do not propose or require web accessibility implementation work unless the user explicitly requests it.`;
 }
@@ -108017,8 +108018,8 @@ ${getFileReferenceGuidanceComment()}
 **Change:** <precise add/modify/remove responsibility and why>
 
 \`\`\`text
-// Component hierarchy, props/state/events, test structure, or exact
-// Tailwind/theme-token classes. Enough detail that implementation requires no invention.
+// Target HTML markup, exact class attributes, and required CSS/styles.
+// Include component hierarchy and props/state/events needed for implementation.
 \`\`\`
 
 <add one block per file; do not collapse multiple files into a directory or vague layer>
@@ -108242,7 +108243,7 @@ function getPlannerToBuilderHandoffTemplate() {
 
 ${getDelegationBriefIntro()}
 
-**Division of labor:** You (planner) own architecture and API shape. The builder implements exactly what you specify and does not redesign or invent alternatives unless blocked.
+**Division of labor:** You (planner) own architecture and API shape. The UI/UX engineer owns UI/UX design. Include its target markup, classes, and styles in UI implementation briefs; the builder implements the components.
 
 **Detail bar:** Specify down to **every file** the builder will create or modify (full repo paths). Include code snippets — types, signatures, stubs, or target implementations — until a competent builder **cannot misinterpret** what to write. Vague layers ("update the backend", "fix the component") are not acceptable.
 
@@ -109384,7 +109385,7 @@ var init_uiux_engineer3 = __esm(() => {
   init_sections();
   UIUX_ENGINEER_GUIDANCE = `## UI/UX Engineer Operating Model
 
-You are the UI/UX engineer responsible for producing one complete interface and experience design for the request. You are advisory only: do not implement code, edit files, or act as the builder.
+You are the UI/UX engineer responsible for UI/UX decisions and for producing one complete interface and experience design for the request. Provide the target markup, classes, and styles in your handoff. Do not implement code, edit files, or act as the builder.
 
 ${"{SESSION_CONTINUITY}"}
 
@@ -137080,4 +137081,4 @@ program2.hook("preAction", async (_thisCommand, actionCommand) => {
 });
 program2.parse();
 
-//# debugId=1F68354F72E2582064756E2164756E21
+//# debugId=23917805A998950464756E2164756E21