chatroom-cli 1.71.0 → 1.72.0

package/dist/index.js

@@ -77178,6 +77178,14 @@ 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:`;
+}
+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.`;
+}
+
 // ../../services/backend/prompts/cli/role-guidance/command.ts
 function roleGuidanceCommand(params = {}) {
   const prefix = params.cliEnvPrefix ?? "";
@@ -77202,7 +77210,7 @@ var init_role_guidance_disclosure = () => {};
 function getBuilderToPlannerHandoffTemplate(roleGuidanceContext) {
   return `${getHandoffRecipientVisibilityCallout("planner")}
 
-**Handoff Template (Builder → Planner)** — paste into the handoff message. Fill in EVERY section below. If a section does not apply, write \`Not Applicable\` (do not delete the section):
+${getHandoffReportTemplateIntro("Handoff Template (Builder → Planner)")}
 
 \`\`\`markdown
 ## Summary
@@ -77225,10 +77233,10 @@ ${getFileReferenceProofOfCompletionExample()}
 ${CODE_CHANGE_VERIFICATION_CONFIRMATION}
 
 ## Blockers / questions
-<anything needing planner decision, or "Not Applicable">
+<anything needing planner decision. Omit if none.>
 
 ## Notes for review
-<specific areas for planner to check, or "Not Applicable">
+<specific areas for planner to check. Omit if none.>
 \`\`\``;
 }
 var init_builder_to_planner = __esm(() => {
@@ -77241,7 +77249,7 @@ function getPlannerToBuilderHandoffTemplate(nativeIntegration = false) {
   const sessionManagement = nativeIntegration ? `\`compact\` runs in-session context compaction via the SDK runtime. \`new_session\` starts a completely new session within the same process (not compaction). \`none\` continues the prior session. Tasks continue via injection.` : `\`compact\` is NOT supported — use \`none\` or \`new_session\`. \`new_session\` requires a hard restart (daemon stops agent, cold-starts, agent rejoins via \`get-next-task\`). \`none\` resumes prior session (\`wantResume=true\`).`;
   return `${getHandoffRecipientVisibilityCallout("builder")}
 
-**Delegation Brief (Planner → Builder)** — paste into the handoff message and fill in EVERY field. No field is optional: if a section does not apply, write \`Not Applicable\` (do not delete the section).
+${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.
 
@@ -77282,7 +77290,7 @@ ${getFileReferenceGuidanceComment()}
 (Add one ### block per file. If this slice touches only one file, still use the ### header.)
 
 ## Shared contracts (planner-owned)
-Cross-file types, interfaces, or patterns that apply beyond a single file. Write \`Not Applicable\` if everything is already specified per-file above.
+Cross-file types, interfaces, or patterns that apply beyond a single file. Omit if everything is already specified per-file above.
 
 ### Interfaces & types
 \`\`\`typescript
@@ -77299,13 +77307,13 @@ Cross-file types, interfaces, or patterns that apply beyond a single file. Write
 
 ## What to avoid
 - <anti-patterns, recurring mistakes, or scope creep for this slice — be explicit>
-- <e.g. "Do not add new abstractions", "Do not refactor unrelated files", "Do not change existing public APIs", or "Not Applicable">
+- <e.g. "Do not add new abstractions", "Do not refactor unrelated files", "Do not change existing public APIs">
 
 ## Skills to activate
-- <e.g. chatroom skill activate code-review --chatroom-id=<id> --role=builder, or "Not Applicable">
+- <e.g. chatroom skill activate code-review --chatroom-id=<id> --role=builder>
 
 ## Out of scope
-- <files or areas the builder must NOT touch in this slice, or "Not Applicable">
+- <files or areas the builder must NOT touch in this slice>
 
 ## Session Augmentation
 Valid values: \`none\` | \`compact\` | \`new_session\`
@@ -77343,16 +77351,16 @@ 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. -->
-- <decision or question — options considered, recommendation if any, or "Not Applicable">
-<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. Write \`Not Applicable\` only when there are truly no open decisions.>`;
+<!-- Decisions that need user input before work can proceed. Omit this section when there are no open decisions. -->
+- <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")}
 
-**Report Template (Planner → User)** — fill in EVERY section below in your handoff message. If a section does not apply, write \`Not Applicable\` (do not delete the section):
+${getHandoffReportTemplateIntro("Report Template (Planner → User)")}
 
 \`\`\`markdown
 ## Summary
@@ -77366,7 +77374,7 @@ ${getRoleGuidanceDisclosureBlock(roleGuidanceContext)}
 <!-- 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>
-<List the planned slices/steps the planner defined (or would have defined) before delegating. Each step should name a verifiable deliverable — not vague layers like "backend work". Write \`Not Applicable\` only for trivial single-step tasks.>
+<Omit for trivial single-step tasks.>
 
 ## What changed
 <high-level view of what changed since the user's message before the detailed proofs below>
@@ -77382,24 +77390,24 @@ ${getFileReferenceProofOfCompletionExample()}
 
 ## Backlog Tasks Implemented
 - \`backlog-item-id\` — <backlog item title/summary and how this work addresses it>
-<List every backlog item this work implemented. Write \`Not Applicable\` if no backlog items were in scope.>
+<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\` because a PR has been raised for user review
-- PR URL(s): <link to PR(s), or \`Not Applicable\` if no PR was raised>
-- If no backlog items apply, write \`Not Applicable\` for the checkbox and explain in one line
+- 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, or "Not Applicable">
+- <schema design, modules, interfaces, domain entities — what you chose and why>
 
 ## Key Tradeoffs
-- <what was weighed against what, and why you chose this path, or "Not Applicable">
+- <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, or "Not Applicable">
+- <issues noticed but intentionally left out of scope of this change>
 
 ## System Design
-<include a mermaid diagram when the change has non-trivial structure; write "Not Applicable" for trivial changes>
+<include a mermaid diagram when the change has non-trivial structure; omit for trivial changes>
 
 \`\`\`mermaid
 flowchart TD
@@ -77412,7 +77420,7 @@ ${CODE_CHANGE_VERIFICATION_CONFIRMATION}
 ${getUnresolvedDecisionsSectionBlock()}
 
 ## Notes / Next steps
-<anything the user should know, follow-ups, or open questions, or "Not Applicable">
+<anything the user should know, follow-ups, or open questions>
 \`\`\``;
 }
 var init_planner_to_user = __esm(() => {
@@ -77450,7 +77458,7 @@ var init_handoff_templates = __esm(() => {
 function getSoloToUserReportTemplate(roleGuidanceContext) {
   return `${getHandoffRecipientVisibilityCallout("user")}
 
-**Report Template (Solo → User)** — fill in EVERY section below in your handoff message. If a section does not apply, write \`Not Applicable\` (do not delete the section):
+${getHandoffReportTemplateIntro("Report Template (Solo → User)")}
 
 \`\`\`markdown
 ## Summary
@@ -77464,7 +77472,7 @@ ${getRoleGuidanceDisclosureBlock(roleGuidanceContext)}
 <!-- 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>
-<List the planned steps you defined before implementing. Each step should name a verifiable deliverable — not vague layers like "backend work". Write \`Not Applicable\` only for trivial single-step tasks.>
+<Omit for trivial single-step tasks.>
 
 ## What changed
 <high-level view of what changed since the user's message before the detailed proofs below>
@@ -77480,24 +77488,24 @@ ${getFileReferenceProofOfCompletionExample()}
 
 ## Backlog Tasks Implemented
 - \`backlog-item-id\` — <backlog item title/summary and how this work addresses it>
-<List every backlog item this work implemented. Write \`Not Applicable\` if no backlog items were in scope.>
+<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\` because a PR has been raised for user review
-- PR URL(s): <link to PR(s), or \`Not Applicable\` if no PR was raised>
-- If no backlog items apply, write \`Not Applicable\` for the checkbox and explain in one line
+- 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, or "Not Applicable">
+- <schema design, modules, interfaces, domain entities — what you chose and why>
 
 ## Key Tradeoffs
-- <what was weighed against what, and why you chose this path, or "Not Applicable">
+- <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, or "Not Applicable">
+- <issues noticed but intentionally left out of scope of this change>
 
 ## System Design
-<include a mermaid diagram when the change has non-trivial structure; write "Not Applicable" for trivial changes>
+<include a mermaid diagram when the change has non-trivial structure; omit for trivial changes>
 
 \`\`\`mermaid
 flowchart TD
@@ -77510,7 +77518,7 @@ ${CODE_CHANGE_VERIFICATION_CONFIRMATION}
 ${getUnresolvedDecisionsSectionBlock()}
 
 ## Notes / Next steps
-<anything the user should know, follow-ups, or open questions, or "Not Applicable">
+<anything the user should know, follow-ups, or open questions>
 \`\`\``;
 }
 var init_solo_to_user = __esm(() => {
@@ -108848,6 +108856,21 @@ var init_harness_spawning = __esm(() => {
   init_rate_limiter();
 });
 
+// src/utils/cli-command-formatting.ts
+function formatAuthLoginCommand(convexUrl, env2 = process.env) {
+  if (isProductionConvexUrl(convexUrl)) {
+    return "chatroom auth login";
+  }
+  const webUrl = env2.CHATROOM_WEB_URL;
+  if (webUrl) {
+    return `CHATROOM_WEB_URL=${webUrl} CHATROOM_CONVEX_URL=${convexUrl} chatroom auth login`;
+  }
+  return `CHATROOM_CONVEX_URL=${convexUrl} chatroom auth login`;
+}
+var init_cli_command_formatting = __esm(() => {
+  init_env();
+});
+
 // src/commands/machine/daemon-start/handlers/daemon-startup-log.ts
 var logStartupEffect = (cachedModels) => exports_Effect.gen(function* () {
   const session2 = yield* DaemonSessionService;
@@ -109036,7 +109059,7 @@ var discoverModelsEffect = (agentServices) => exports_Effect.gen(function* () {
     }
   }
   console.error(`
-Run: chatroom auth login`);
+Run: ${formatAuthLoginCommand(convexUrl)}`);
   console.log(`
 ⏳ Waiting for authentication (timeout: 5 minutes)...`);
   return yield* waitForAuthenticationEffect(convexUrl);
@@ -109050,7 +109073,7 @@ Run: chatroom auth login`);
   }
   console.error(`❌ Session invalid: ${validation.reason}`);
   console.error(`
-Run: chatroom auth login`);
+Run: ${formatAuthLoginCommand(convexUrl)}`);
   console.log(`
 ⏳ Waiting for re-authentication (timeout: 5 minutes)...`);
   const newSessionId2 = yield* waitForAuthenticationEffect(convexUrl);
@@ -109062,6 +109085,8 @@ Run: chatroom auth login`);
   if (!revalidation.valid) {
     return yield* exports_Effect.sync(() => {
       console.error(`❌ New session is also invalid: ${revalidation.reason}`);
+      console.error(`
+Run: ${formatAuthLoginCommand(convexUrl)}`);
       releaseLock();
       process.exit(1);
     });
@@ -109179,6 +109204,7 @@ var init_init2 = __esm(() => {
   init_agent_process_manager();
   init_harness_spawning();
   init_remote_agents();
+  init_cli_command_formatting();
   init_convex_error();
   init_error_formatting();
   init_pid();
@@ -113427,4 +113453,4 @@ program2.hook("preAction", async (_thisCommand, actionCommand) => {
 });
 program2.parse();
 
-//# debugId=7CC1598E61EBEDA564756E2164756E21
+//# debugId=70E245B4BCF61FFE64756E2164756E21