chatroom-cli 1.77.4 → 1.77.5

package/dist/index.js

@@ -77263,14 +77263,21 @@ function getFileReferenceProofOfCompletionExample() {
 }
 
 // ../../services/backend/prompts/utils/handoff-quality-principles.ts
-function getHandoffQualityPrinciplesCommentBlock() {
-  const bullets = HANDOFF_QUALITY_PRINCIPLES.map((p) => `- ${p.name}: ${p.description}`).join(`
-`);
-  return `<!-- Demonstrate adherence to:
-${bullets}
--->`;
+function getHandoffQualityPrinciplesTemplateBlock() {
+  const lines = HANDOFF_QUALITY_PRINCIPLES.flatMap((p) => [
+    `- **${p.name}:** <how this work demonstrates ${p.name.toLowerCase()}, or Not Applicable>`,
+    `<!-- ${p.name}: ${p.description} -->`,
+    ""
+  ]);
+  return lines.join(`
+`).trimEnd();
 }
-var HANDOFF_QUALITY_PRINCIPLES, PROOF_OF_PRINCIPLES_HEADING_H2 = "## Proof of Principles", PROOF_OF_PRINCIPLES_HEADING_H3 = "### Proof of Principles";
+function getHandoffQualityPrinciplesSectionBlock() {
+  return `${PROOF_OF_PRINCIPLES_HEADING_H2}
+${PROOF_OF_PRINCIPLES_MANDATORY_COMMENT}
+${getHandoffQualityPrinciplesTemplateBlock()}`;
+}
+var HANDOFF_QUALITY_PRINCIPLES, PROOF_OF_PRINCIPLES_HEADING_H2 = "## Proof of Principles", PROOF_OF_PRINCIPLES_MANDATORY_COMMENT = '<!-- REQUIRED: Complete every principle below. Write an explanation or "Not Applicable" for each — do not omit this section or skip any principle bullet. -->';
 var init_handoff_quality_principles = __esm(() => {
   HANDOFF_QUALITY_PRINCIPLES = [
     {
@@ -77302,7 +77309,7 @@ var init_handoff_quality_principles = __esm(() => {
 
 // ../../services/backend/prompts/utils/handoff-section-guidance.ts
 function getHandoffReportTemplateIntro(templateLabel) {
-  return `**${templateLabel}** — include every section that applies to this handoff. **Omit sections that do not apply** — do not write \`Not Applicable\` as filler:`;
+  return `**${templateLabel}** — complete every section below. Do not omit sections, principles, or XML wrappers:`;
 }
 function getDelegationBriefIntro() {
   return `**Delegation Brief (Planner → Builder)** — paste into the handoff message. Include every field that applies. **Omit fields that do not apply** — do not write \`Not Applicable\` as filler.`;
@@ -77342,9 +77349,7 @@ ${getHandoffReportTemplateIntro("Handoff Template (Builder → Planner)")}
 - [ ] I confirm that I have seen this template at the start of this task, before implementing or modifying any code
 ${getRoleGuidanceDisclosureBlock(roleGuidanceContext)}
 
-${PROOF_OF_PRINCIPLES_HEADING_H2}
-${getHandoffQualityPrinciplesCommentBlock()}
-<how this work follows the principles above — localized changes, readable structure, correctness provable from source then tests>
+${getHandoffQualityPrinciplesSectionBlock()}
 
 ## Proof of Completion
 ${getDelegationBriefDisclosureBlock()}
@@ -77355,10 +77360,12 @@ ${getFileReferenceProofOfCompletionExample()}
 ${CODE_CHANGE_VERIFICATION_CONFIRMATION}
 
 ## Blockers / questions
-<anything needing planner decision. Omit if none.>
+<!-- REQUIRED. List blockers, or write "Not Applicable". Do not omit this section. -->
+<anything needing planner decision>
 
 ## Notes for review
-<specific areas for planner to check. Omit if none.>
+<!-- REQUIRED. List review notes, or write "Not Applicable". Do not omit this section. -->
+<specific areas for planner to check>
 \`\`\``;
 }
 var init_builder_to_planner = __esm(() => {
@@ -77372,26 +77379,29 @@ function getEnhancerToPlannerHandoffTemplate() {
 
 ${getHandoffReportTemplateIntro("Planning Feedback (Enhancer → Planner)")}
 
-The planner sent you three XML sections: \`<user-message>\`, \`<grounding>\`, and a draft \`<builder-handoff>\`. Your job is **critical review** of all three — tighten their thinking toward a high-quality eventual handoff to the user. Do not explore the codebase or invent new scope.
+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. **Do not prescribe file-level changes or rewrite their builder brief.** The planner makes the final call.
 
 \`\`\`markdown
 ## Summary
-<one paragraph: overall assessment of the planner's check-in — strengths and the main gaps to address>
+<one paragraph: overall assessment — strengths, main risks, and whether the approach is sound>
+
+## User intent alignment
+<does the planner's reading of the user request match what was asked? misreadings or missing constraints?>
 
-## User intent assessment
-<mistakes or misreadings in what the user may want; clarify the correct interpretation>
+## Risks &amp; failure modes
+<what could go wrong if they proceed as planned? common pitfalls for this kind of work?>
 
 ## Knowledge gaps
-<facts, context, or research the planner is missing or has not surfaced>
+<facts, context, or research the planner should verify — advisory questions, not answers from codebase>
 
-## Reasoning & logic
-<logical errors, weak inference chains, contradictions, or unsupported conclusions>
+## Reasoning review
+<logical errors, weak inference, contradictions — challenge assumptions>
 
-## Alignment with user handoff
-<how to tighten the research and conclusions so the eventual planner→user report will be accurate, complete, and well-justified>
+## Questions for the planner
+<specific questions they should answer before delegating — not instructions disguised as questions>
 
-## Recommended next steps
-<concrete actions for the planner: what to research, revise, validate, or decide before proceeding>
+## Alignment with eventual user handoff
+<will this approach produce a credible planner→user report? what's missing for user-facing completeness?>
 \`\`\`
 
 Return only the feedback markdown — no preamble. Follow this structure; omit sections that truly do not apply.`;
@@ -77510,11 +77520,11 @@ ${getFileReferenceGuidanceComment()}
 <builder-handoff>
 <your complete, filled-in Delegation Brief for builder review — every section with real content, not placeholders>
 
-Follow the **Handoff to \`builder\`** template structure (Summary, Goal, Files to implement, Requirements, etc.). The enhancer critiques this draft before you delegate.
+Follow the **Handoff to \`builder\`** template structure (Summary, Goal, approach, Requirements, etc.). The enhancer reviews **approach and scope** — not line-by-line file edits. Keep file references for context, but expect advisory feedback on risks and gaps, not a rewritten brief.
 </builder-handoff>
 \`\`\`
 
-After the enhancer returns feedback, you will receive it as a new planner task. Revise grounding and the builder handoff as needed, then proceed to \`builder\` or \`user\` as appropriate.`;
+After the enhancer returns **advisory** feedback, you make the **final call** — incorporate valid critiques, ignore what doesn't apply, then proceed to \`builder\` or \`user\`. Do not re-check with the enhancer for this slice; one round only.`;
 }
 var init_planner_to_enhancer = () => {};
 
@@ -77541,84 +77551,113 @@ var init_context_disclosure = () => {};
 // ../../services/backend/prompts/utils/unresolved-decisions.ts
 function getUnresolvedDecisionsSectionBlock() {
   return `## Unresolved Decisions
-<!-- Decisions that need user input before work can proceed. Omit this section when there are no open decisions. -->
+<!-- REQUIRED. List open decisions needing user input, or write "Not Applicable" if none. Do not omit this section. -->
 - <decision or question — options considered, recommendation if any>
 <Carry forward decisions still open from earlier handoffs in this chatroom. Remove items the user has resolved. Do not decide on the user's behalf unless they explicitly asked you to.>`;
 }
 
-// ../../services/backend/prompts/teams/duo/handoff-templates/planner-to-user.ts
-function getPlannerToUserReportTemplate(roleGuidanceContext) {
-  return `${getHandoffRecipientVisibilityCallout("user")}
-
-${getHandoffReportTemplateIntro("Report Template (Planner → User)")}
-
-\`\`\`markdown
+// ../../services/backend/prompts/utils/handoff-report-template-body.ts
+function getHandoffReportTemplateBody(roleGuidanceContext) {
+  return `<handoff-overview>
 ## Summary
 <what was accomplished, in plain terms — no references to prior messages>
 
+## What changed
+<high-level view of what changed since the user's message>
+</handoff-overview>
+
+<!-- UI collapses proofs, direction, and notes by default; overview and action required are expanded -->
+
+<handoff-proofs>
 ## Template Disclosure Confirmation
 - [ ] I confirm that I have seen this template at the start of any planning, before working on or delegating any task to the team
 ${getRoleGuidanceDisclosureBlock(roleGuidanceContext)}
 
 ## Proof of Planning
-<!-- Demonstrate the goal was decomposed into actionable steps with clear outcomes before implementation. -->
+<!-- REQUIRED. List planning steps, or write "Not Applicable" for trivial single-step tasks. Do not omit this section. -->
 - <step 1: concrete artifact or outcome>
 - <step 2: concrete artifact or outcome>
-<Omit for trivial single-step tasks.>
 
-## What changed
-<high-level view of what changed since the user's message before the detailed proofs below>
-
-${PROOF_OF_PRINCIPLES_HEADING_H3}
-${getHandoffQualityPrinciplesCommentBlock()}
-<how this work follows the principles above — localized changes, readable structure, correctness provable from source then tests>
+${getHandoffQualityPrinciplesSectionBlock()}
 
-### Proof of Completion
+## Proof of Completion
 ${getContextReadDisclosureBlock(roleGuidanceContext)}
 ${getFileReferenceProofOfCompletionExample()}
 <evidence the goal was met — list every file you (or the builder) modified>
 
 ## Backlog Tasks Implemented
+<!-- REQUIRED. List backlog items addressed, or write "Not Applicable" if none were in scope. Do not omit this section. -->
 - \`backlog-item-id\` — <backlog item title/summary and how this work addresses it>
-<Omit if no backlog items were in scope.>
 
 ## Backlog Pending User Review Confirmation
+<!-- REQUIRED. Complete the attestation, or write "Not Applicable" if no backlog items apply. Do not omit this section. -->
 - [ ] I confirm that every backlog item implemented in this work has been moved to \`pending_user_review\` via \`chatroom backlog mark-for-review\` after the feature was verified end-to-end and a PR was raised for user review
 - PR URL(s): <link to PR(s)>
-<Omit this section if no backlog items apply.>
+
+## Code Change Verification
+${CODE_CHANGE_VERIFICATION_CONFIRMATION}
+</handoff-proofs>
+
+<handoff-direction>
+## What exists today
+<!-- REQUIRED. Describe current state after this work, or write "Not Applicable". Do not omit this section. -->
+<current state after this work — what the user can now do, what is in place, how the system behaves>
 
 ## Key Technical Decisions
+<!-- REQUIRED. List decisions, or write "Not Applicable". Do not omit this section. -->
 - <schema design, modules, interfaces, domain entities — what you chose and why>
 
 ## Key Tradeoffs
+<!-- REQUIRED. List tradeoffs, or write "Not Applicable". Do not omit this section. -->
 - <what was weighed against what, and why you chose this path>
 
-## Tech Debt Observed
-- <issues noticed but intentionally left out of scope of this change>
-
 ## System Design
-<include a mermaid diagram when the change has non-trivial structure; omit for trivial changes>
+<!-- REQUIRED. Include a mermaid diagram when the change has non-trivial structure, or write "Not Applicable". Do not omit this section. -->
 
 \`\`\`mermaid
 flowchart TD
     A[Component] --> B[Component]
 \`\`\`
+</handoff-direction>
 
-## Code Change Verification
-${CODE_CHANGE_VERIFICATION_CONFIRMATION}
+<handoff-notes>
+## Notes
+<!-- REQUIRED. Write notes, or "Not Applicable" if none. Do not omit this section. -->
+<anything the user should know — context, caveats, or observations not covered above>
+</handoff-notes>
+
+<handoff-action>
+## Tech Debt Observed
+<!-- REQUIRED. List tech debt, or write "Not Applicable". Do not omit this section. -->
+- <issues noticed but intentionally left out of scope of this change>
 
 ${getUnresolvedDecisionsSectionBlock()}
 
-## Notes
-<anything the user should know — context, caveats, or observations not covered above. Omit if none.>
-\`\`\``;
+## Manual steps
+<!-- REQUIRED. List manual steps outside the system, or write "Not Applicable". Do not omit this section. -->
+<steps the user must take outside the system — deploy, configure credentials, run commands, verify in production, etc.>
+</handoff-action>`;
 }
-var init_planner_to_user = __esm(() => {
+var init_handoff_report_template_body = __esm(() => {
   init_context_disclosure();
   init_handoff_quality_principles();
   init_role_guidance_disclosure();
 });
 
+// ../../services/backend/prompts/teams/duo/handoff-templates/planner-to-user.ts
+function getPlannerToUserReportTemplate(roleGuidanceContext) {
+  return `${getHandoffRecipientVisibilityCallout("user")}
+
+${getHandoffReportTemplateIntro("Report Template (Planner → User)")}
+
+\`\`\`markdown
+${getHandoffReportTemplateBody(roleGuidanceContext)}
+\`\`\``;
+}
+var init_planner_to_user = __esm(() => {
+  init_handoff_report_template_body();
+});
+
 // ../../services/backend/prompts/teams/duo/handoff-templates/index.ts
 function getDuoHandoffTemplate(query) {
   const getter = DUO_HANDOFF_TEMPLATES[`${query.fromRole.toLowerCase()}:${query.toRole.toLowerCase()}`];
@@ -77655,70 +77694,11 @@ function getSoloToUserReportTemplate(roleGuidanceContext) {
 ${getHandoffReportTemplateIntro("Report Template (Solo → User)")}
 
 \`\`\`markdown
-## Summary
-<what was accomplished, in plain terms — no references to prior messages>
-
-## Template Disclosure Confirmation
-- [ ] I confirm that I have seen this template at the start of any planning, before implementing any code for this task
-${getRoleGuidanceDisclosureBlock(roleGuidanceContext)}
-
-## Proof of Planning
-<!-- Demonstrate the goal was decomposed into actionable steps with clear outcomes before implementation. -->
-- <step 1: concrete artifact or outcome>
-- <step 2: concrete artifact or outcome>
-<Omit for trivial single-step tasks.>
-
-## What changed
-<high-level view of what changed since the user's message before the detailed proofs below>
-
-${PROOF_OF_PRINCIPLES_HEADING_H3}
-${getHandoffQualityPrinciplesCommentBlock()}
-<how this work follows the principles above — localized changes, readable structure, correctness provable from source then tests>
-
-### Proof of Completion
-${getContextReadDisclosureBlock(roleGuidanceContext)}
-${getFileReferenceProofOfCompletionExample()}
-<evidence the goal was met — list every file you modified>
-
-## Backlog Tasks Implemented
-- \`backlog-item-id\` — <backlog item title/summary and how this work addresses it>
-<Omit if no backlog items were in scope.>
-
-## Backlog Pending User Review Confirmation
-- [ ] I confirm that every backlog item implemented in this work has been moved to \`pending_user_review\` via \`chatroom backlog mark-for-review\` after the feature was verified end-to-end and a PR was raised for user review
-- PR URL(s): <link to PR(s)>
-<Omit this section if no backlog items apply.>
-
-## Key Technical Decisions
-- <schema design, modules, interfaces, domain entities — what you chose and why>
-
-## Key Tradeoffs
-- <what was weighed against what, and why you chose this path>
-
-## Tech Debt Observed
-- <issues noticed but intentionally left out of scope of this change>
-
-## System Design
-<include a mermaid diagram when the change has non-trivial structure; omit for trivial changes>
-
-\`\`\`mermaid
-flowchart TD
-    A[Component] --> B[Component]
-\`\`\`
-
-## Code Change Verification
-${CODE_CHANGE_VERIFICATION_CONFIRMATION}
-
-${getUnresolvedDecisionsSectionBlock()}
-
-## Notes
-<anything the user should know — context, caveats, or observations not covered above. Omit if none.>
+${getHandoffReportTemplateBody(roleGuidanceContext)}
 \`\`\``;
 }
 var init_solo_to_user = __esm(() => {
-  init_context_disclosure();
-  init_handoff_quality_principles();
-  init_role_guidance_disclosure();
+  init_handoff_report_template_body();
 });
 
 // ../../services/backend/prompts/teams/solo/handoff-templates/index.ts
@@ -116379,4 +116359,4 @@ program2.hook("preAction", async (_thisCommand, actionCommand) => {
 });
 program2.parse();
 
-//# debugId=550B12123AE171BD64756E2164756E21
+//# debugId=139534CD91C868F464756E2164756E21