chatroom-cli 1.84.3 → 1.84.4

package/dist/index.js

@@ -77269,45 +77269,113 @@ var init_builder_to_planner = __esm(() => {
   init_role_guidance_disclosure();
 });
 
+// ../../services/backend/prompts/enhancer/webapp-ux-reference.ts
+function renderWebappUxHandoffReference() {
+  return [
+    "### UX review checklist",
+    'Complete the optional **UX** section in your output when the planner proposes UI changes. Write exactly "Not Applicable." for non-UI tasks. Put code snippets in **Suggested edits** only.',
+    "",
+    "1. **Flows** — primary action ≤3 clicks? simpler path exists?",
+    "2. **Patterns** — matches existing components? recommend one if multiple. mobile vs desktop (md: variants vs separate mobile UI)?",
+    "3. **Layout** — compact title+menu row, description, trailing end-aligned CTA? unnecessary wrappers?",
+    "4. **Shortcuts** — consistent with catalog below? gaps or conflicts?",
+    "",
+    "### Flow complexity",
+    "- Primary action ≤3 clicks from entry point",
+    "- Extend existing surfaces (palette, settings tab, row action) before new navigation",
+    "- Avoid nested modal chains and unjustified multi-step wizards",
+    "- Prefer inline actions over navigate-away-and-back",
+    "",
+    "### Presentation & responsive patterns",
+    "- Reuse existing components: `CommandPalette`, industrial dialogs, `ChatroomLoader`, timeline row chrome",
+    "- Match badge/button patterns from timeline (`BADGE_BASE`, `navButtonClass` in All-tab)",
+    "- When multiple valid patterns exist, recommend one and explain tradeoff",
+    "- **md: breakpoint** (768px) splits mobile vs desktop",
+    "- **Hide/show:** `hidden md:flex` / `flex md:hidden` for alternate chrome",
+    "- **Mobile overlay:** fixed sidebar overlay with backdrop (`md:hidden`)",
+    "- **Separate mobile UI:** dedicated mobile modal/picker when desktop uses side panel",
+    "- **Shared responsive density:** same component, `md:` size variants (`h-7 md:h-9`)",
+    "- **Command dialogs:** industrial theme via `commandDialogStyles.ts`, top-anchored, max-w-[90vw]",
+    "",
+    "### Layout simplification",
+    "- Review card/section layouts for unnecessary rows, nested wrappers, or misaligned actions",
+    "- Prefer compact rows: title and overflow menu (⋮ `MoreVertical` popover) on one line via flex/grid",
+    '- Description on the next line; primary CTA (e.g. "View Details") on a trailing row aligned end',
+    "- Canonical simplified card pattern:",
+    "  ```",
+    "  <title>          <overflow-menu ⋮>",
+    "  <description>",
+    "                   <primary-cta aligned end>",
+    "  ```",
+    "- Reuse `CardHeader` + `CardAction` grid (`grid-cols-[1fr_auto]`) or equivalent flex `justify-between`",
+    "- Flag multi-row chrome that could collapse (menu on its own row, CTA left-aligned when end-aligned matches existing cards)",
+    "",
+    "### Keyboard shortcuts (reference)",
+    "| Shortcut | Action |",
+    "|----------|--------|",
+    "| ⌘K / Ctrl+K | Chatroom switcher |",
+    "| ⌘P / Ctrl+P | File selector |",
+    "| ⌘⇧P / Ctrl+Shift+P | Command palette (scripts, saved commands) |",
+    "| ⌘⇧F / Ctrl+Shift+F | Workspace search |",
+    "| ⌘I / Ctrl+I | Attach explorer snippet |",
+    "| Enter (desktop, no Shift) | Send message |",
+    "| Shift+Enter | New line in composer |",
+    "| ⌘Enter / Ctrl+Enter | Confirm/save in modals |",
+    "| ⌘S / Ctrl+S | Save in workspace file dialogs |",
+    "| Escape | Close modal/dialog |"
+  ].join(`
+`);
+}
+
 // ../../services/backend/prompts/utils/enhancer-feedback-template-body.ts
 function getEnhancerFeedbackTemplateBody() {
   return `<handoff-overview>
 ## Summary
-<one paragraph: overall assessment — strengths, main risks, and whether the approach is sound>
+<overall assessment — cite specific strengths, risks, and whether the approach is sound; reference concrete elements from the check-in>
 
 ## User intent alignment
-<does the planner's reading of the user request match what was asked? misreadings or missing constraints?>
+<specific misreadings or missing constraints — what the user asked vs what the planner proposed>
 </handoff-overview>
 
-<!-- UI collapses proofs, direction, and notes by default; overview and action required are expanded -->
+<!-- UI collapses proofs, direction, ux, and notes by default; overview and action required are expanded -->
 
 <handoff-proofs>
 ## Reasoning review
-<logical errors, weak inference, contradictions — challenge assumptions>
+<specific logical errors, weak inference, or contradictions — cite the claim and why it fails>
 </handoff-proofs>
 
 <handoff-direction>
 ## Alignment with eventual user handoff
-<will this approach produce a credible planner→user report? what's missing for user-facing completeness?>
+<specific gaps for user-facing completeness — what proof or report sections would be missing>
 </handoff-direction>
 
+<handoff-ux>
+<!-- Optional — write exactly "Not Applicable." when no UI changes are proposed -->
+<!-- When UI is proposed: specific findings tied to the planner's proposal. No code blocks (use Suggested edits). -->
+- **Flows:** <specific finding — click count, nested modals, simpler alternatives>
+- **Patterns:** <which existing pattern fits; recommend one if multiple; mobile vs desktop>
+- **Layout:** <compact rows, trailing CTAs, unnecessary wrappers>
+- **Shortcuts:** <alignment with catalog; gaps or conflicts>
+</handoff-ux>
+
 <handoff-notes>
 ## Knowledge gaps
-<facts, context, or research the planner should verify — advisory questions, not answers from codebase>
+<specific facts, files, or research to verify — name what to check and why>
 </handoff-notes>
 
 <handoff-action>
 ## Risks & failure modes
-<what could go wrong if they proceed as planned? common pitfalls for this kind of work?>
+<specific risks tied to this plan — what fails, under what conditions, and how to mitigate>
 
-## Questions for the planner
-<specific questions they should answer before delegating — not instructions disguised as questions>
+## Recommendations
+<!-- SECOND-LAST — concrete, actionable suggestions tied to the check-in. Include tradeoffs and considerations. No code blocks here (use Suggested edits for snippets). -->
 
 ## Suggested edits (remove or change only)
-When you recommend removing or changing specific content in the planner's check-in (grounding, builder-handoff sections, or proposed approach), list each change here with file-level detail and code examples. **Omit this entire section** if you have no concrete removals or changes to suggest — keep other sections abstract.
+<!-- LAST — proposed edits to grounding and builder-handoff. File paths and code snippets required when recommending changes. Omit entirely if none. -->
+When you recommend removing or changing specific content in the planner's check-in, list each change here with file-level detail and code examples.
 ${getFileReferenceGuidanceComment()}
 
-### <section or claim to remove or change — e.g. "builder-handoff > Files to implement" or "grounding: auth middleware claim">
+### <section or claim to remove or change>
 **File:** \`apps/webapp/src/path/to/file.ts\`
 **Change:** <what to remove, replace, or correct and why>
 
@@ -77326,7 +77394,11 @@ function getEnhancerToPlannerHandoffTemplate() {
 
 ${getHandoffReportTemplateIntro("Planning Feedback (Enhancer → Planner)")}
 
-The planner sent you three XML sections. Your job is **advisory adversarial review** — raise risks, challenge assumptions, and help the planner align with user intent. Keep most sections abstract; when you recommend removing or changing specific content, put file-level detail and code examples in **Suggested edits (remove or change only)** only. **Do not rewrite their full builder brief.** The planner makes the final call.
+The planner sent you three XML sections. Your job is **advisory adversarial review** — raise risks, challenge assumptions, align with user intent. Be **specific and targeted**: cite concrete claims, files, UX choices, and gaps from the check-in so the planner can improve the plan without re-synthesizing vague feedback.
+
+Give **concrete, actionable recommendations** in every section. End with **Recommendations** (second-last: summarized suggestions, tradeoffs, and considerations) then **Suggested edits** (last: proposed edits to grounding and the builder-handoff with file paths and code snippets). For UI work, complete the optional **UX** section using the reference below. **Do not rewrite their full builder brief.** The planner makes the final call.
+
+${renderWebappUxHandoffReference()}
 
 \`\`\`markdown
 ${getEnhancerFeedbackTemplateBody()}
@@ -114318,4 +114390,4 @@ program2.hook("preAction", async (_thisCommand, actionCommand) => {
 });
 program2.parse();
 
-//# debugId=F150EF2E5727967864756E2164756E21
+//# debugId=12F4187F56EA920864756E2164756E21