chatroom-cli 1.129.0 → 1.130.0

package/dist/index.js

@@ -100665,6 +100665,102 @@ function getHandoffSeverityGuidanceBlock() {
 - [low] <minor cleanup — nice to have>`;
 }
 
+// ../../services/backend/prompts/teams/verifier-handoff-templates.ts
+function normalizeEntryPointRole3(entryPointRole) {
+  return entryPointRole.trim().toLowerCase() || "planner";
+}
+function getEntryPointToVerifierHandoffTemplate(entryPointRole) {
+  const entryPoint = normalizeEntryPointRole3(entryPointRole);
+  return `${getHandoffRecipientVisibilityCallout("verifier")}
+
+## Handoff Template (${entryPoint} → verifier)
+
+The verifier judges, from chatroom logs only, whether the user's last message was achieved. It ${VERIFIER_TEST_RULE}; list any user-requested tests under Requested test runs. Treat the claimed outcome as a claim, not as evidence: the verifier does not trust it and checks every requirement against the logs themselves. Request this review only when the task involved code changes, in any conversation mode. The verdict returns to \`${entryPoint}\`.
+
+## Round
+<1 or 2; for 2, cite the round-1 verdict message id>
+
+## Mode
+<chat | code | code:enhanced>
+
+## User message id
+<id of the user's last message: the origin message id of the user task, or from \`chatroom messages anchor\`>
+
+## Context id
+<id from \`chatroom context read\`, or \`none\` if no context was read for this task>
+
+## Requested test runs
+<the test commands the user explicitly asked for, one per line, or exactly \`None requested.\`>
+
+## Claimed outcome
+<requirement-by-requirement what you believe is complete>
+
+## Evidence pointers
+<builder handoff message ids, commits, PRs, and test results as quoted in those handoffs>
+
+## Known gaps
+<anything incomplete, or exactly \`None.\`>
+
+## Handoff
+Send this request to the verifier with the command below, then stop. The verdict returns to \`${entryPoint}\`.
+
+\`\`\`bash
+${handoffCommand({
+    chatroomId: "<chatroom-id>",
+    role: entryPoint,
+    nextRole: "verifier",
+    cliEnvPrefix: ""
+  })}
+\`\`\``;
+}
+function getVerifierToEntryPointHandoffTemplate(entryPointRole) {
+  const entryPoint = normalizeEntryPointRole3(entryPointRole);
+  return `${getHandoffRecipientVisibilityCallout(entryPoint)}
+
+## Handoff Template (Verifier → ${entryPoint})
+
+Return one advisory verdict for the authoritative request. This review is non-binding: it uses chatroom logs, plus the requested test runs listed in the request, if any, deciding every requirement from the evidence those logs and runs actually contain. It also checks the work against the user's expectations (\`## User Expectations\`) under the same logs-only, claim-is-not-evidence rule. It ${VERIFIER_TEST_RULE}. Never accept the claimed outcome as proof. Use the exact sections below, in this order.
+
+## Verdict
+<exactly one of ${VERIFIER_VERDICTS.join(", ")} as the value; ${ACHIEVED} only if every requirement and user expectation is met; ${NOT_ACHIEVED} if any requirement or user expectation is unmet (logs show it was not done, or contradict it); ${INCONCLUSIVE} if none is unmet but any is unverified (logs are silent)>
+
+## Objective
+<user message id, any prior user messages used, objective in 1-2 sentences>
+
+## Requirements
+<numbered \`R1 — <requirement> — met | unmet | unverified — <evidence ref>\`>
+
+## User Expectations
+<numbered \`U1 — <expectation from the user's handoff template> — met | unmet | unverified — <evidence ref>\`; exactly \`None applicable.\` in chat mode or when no expectation applies>
+
+## Evidence
+<bullets: \`<message id or handoff> — "<short quote>" — supports R#\`; for a requested test run, \`<command> — exit <result> — supports R#\`>
+
+## Missing or unmet
+<per unmet or unverified requirement or user expectation: what is missing and what evidence would resolve it; exactly \`None.\` if ${ACHIEVED}>
+
+## Scope and limits
+<state the test runs the verifier executed (command and exit result), or "No tests were run; none were requested."; log range read; whether the download was truncated; context id read and whether it matched the request>
+
+## Handoff
+Run the normal handoff command to \`${entryPoint}\` with this complete verdict, then stop.
+
+\`\`\`bash
+${handoffCommand({
+    chatroomId: "<chatroom-id>",
+    role: "verifier",
+    nextRole: entryPoint,
+    cliEnvPrefix: ""
+  })}
+\`\`\``;
+}
+var VERIFIER_VERDICTS, VERIFIER_TEST_RULE = "runs no test the user did not ask for, and never builds, lints, or edits", ACHIEVED, NOT_ACHIEVED, INCONCLUSIVE;
+var init_verifier_handoff_templates = __esm(() => {
+  init_command2();
+  VERIFIER_VERDICTS = ["ACHIEVED", "NOT_ACHIEVED", "INCONCLUSIVE"];
+  [ACHIEVED, NOT_ACHIEVED, INCONCLUSIVE] = VERIFIER_VERDICTS;
+});
+
 // ../../services/backend/prompts/utils/proof-of-verification.ts
 function messagesAnchorCommand(params = {}) {
   const prefix = params.cliEnvPrefix ?? "";
@@ -100680,6 +100776,21 @@ function messagesDownloadSinceCommand(params = {}) {
   const limit = params.limit ?? 100;
   return `${prefix}chatroom messages download --chatroom-id="${chatroomId}" --role="${role}" --since-message-id="${sinceMessageId}" --limit=${limit}`;
 }
+function verifierRequestCommand(params = {}) {
+  const prefix = params.cliEnvPrefix ?? "";
+  const chatroomId = params.chatroomId ?? "<chatroom-id>";
+  const role = params.role ?? "<role>";
+  return `${prefix}chatroom handoff --chatroom-id="${chatroomId}" --role="${role}" --next-role="verifier"`;
+}
+function getVerifierReviewDisclosureBlock(params = {}) {
+  return `**Proof of verification (verifier review):**
+${VERIFIER_REVIEW_CHECKBOX}
+- Verifier review: <${VERIFIER_REVIEW_VALUES}>
+- Verifier request command (disclose the command you sent): \`${verifierRequestCommand(params)}\`
+- Verifier request message id: <id of your verifier handoff> · Round: <1 | 2>
+- Verdict message id: <id of the verifier's verdict handoff> · Verdict user message id: <id> (must equal the current last user message)
+- Verdict gaps (only if not ACHIEVED): <each unmet item, or \`None.\`>`;
+}
 function getProofOfVerificationComment(params = {}) {
   const anchorCmd = messagesAnchorCommand(params);
   const downloadCmd = messagesDownloadSinceCommand({
@@ -100696,9 +100807,14 @@ Then: \`${anchorCmd}\` → \`${downloadCmd}\` (use the message ID from anchor ou
 }
 function getEntryPointProofOfCompletionVerificationBlock(params = {}) {
   return `${getProofOfVerificationComment(params)}
-${PROOF_OF_VERIFICATION_CHECKBOX}`;
+${PROOF_OF_VERIFICATION_CHECKBOX}
+${getVerifierReviewDisclosureBlock(params)}`;
 }
-var PROOF_OF_VERIFICATION_CHECKBOX = "- [ ] I confirm I verified the user's full request: anchored on the last user message, downloaded history since that anchor, reviewed handoffs/goals (including prior user messages when the latest was a terse follow-up), and validated every requirement below before this handoff";
+var PROOF_OF_VERIFICATION_CHECKBOX = "- [ ] I confirm I verified the user's full request: anchored on the last user message, downloaded history since that anchor, reviewed handoffs/goals (including prior user messages when the latest was a terse follow-up), and validated every requirement below before this handoff", VERIFIER_REVIEW_CHECKBOX = "- [ ] I checked the verifier verdict for this task: its user message id is the user's current last message, it is round 1 or 2 (maximum 2), and the verdict is `ACHIEVED` — or every unmet item is listed under Unresolved / action required", VERIFIER_REVIEW_VALUES;
+var init_proof_of_verification = __esm(() => {
+  init_verifier_handoff_templates();
+  VERIFIER_REVIEW_VALUES = `${VERIFIER_VERDICTS.join(" | ")} | UNAVAILABLE (<reason>) | not required (no code changes)`;
+});
 
 // ../../services/backend/prompts/utils/unresolved-decisions.ts
 function getUnresolvedDecisionsSectionBlock() {
@@ -100798,6 +100914,7 @@ ${getHandoffNotApplicableSectionComment("List manual steps outside the system")}
 var init_handoff_report_template_body = __esm(() => {
   init_context_disclosure();
   init_handoff_quality_principles();
+  init_proof_of_verification();
   init_role_guidance_disclosure();
   init_unresolved_decisions();
 });
@@ -100829,11 +100946,11 @@ function getChatToUserHandoffTemplate() {
 var init_chat_handoff_template = () => {};
 
 // ../../services/backend/prompts/teams/researcher-handoff-templates.ts
-function normalizeEntryPointRole3(entryPointRole) {
+function normalizeEntryPointRole4(entryPointRole) {
   return entryPointRole.trim().toLowerCase() || "planner";
 }
 function getEntryPointToResearcherHandoffTemplate(entryPointRole) {
-  const entryPoint = normalizeEntryPointRole3(entryPointRole);
+  const entryPoint = normalizeEntryPointRole4(entryPointRole);
   return `${getHandoffRecipientVisibilityCallout("researcher")}
 
 ## Handoff Template (${entryPoint} → researcher)
@@ -100862,7 +100979,7 @@ ${handoffCommand({
 \`\`\``;
 }
 function getResearcherToEntryPointHandoffTemplate(entryPointRole) {
-  const entryPoint = normalizeEntryPointRole3(entryPointRole);
+  const entryPoint = normalizeEntryPointRole4(entryPointRole);
   return `${getHandoffRecipientVisibilityCallout(entryPoint)}
 
 ## Handoff Template (Researcher → ${entryPoint})
@@ -100913,11 +101030,11 @@ var init_researcher_handoff_templates = __esm(() => {
 });
 
 // ../../services/backend/prompts/teams/triage-handoff-templates.ts
-function normalizeEntryPointRole4(entryPointRole) {
+function normalizeEntryPointRole5(entryPointRole) {
   return entryPointRole.trim().toLowerCase() || "planner";
 }
 function getEntryPointToTriageHandoffTemplate(entryPointRole) {
-  const entryPoint = normalizeEntryPointRole4(entryPointRole);
+  const entryPoint = normalizeEntryPointRole5(entryPointRole);
   return `${getHandoffRecipientVisibilityCallout("triage")}
 
 ## Handoff Template (${entryPoint} → triage)
@@ -100936,12 +101053,12 @@ ${handoffCommand({
 \`\`\``;
 }
 function getTriageToEntryPointHandoffTemplate(entryPointRole) {
-  const entryPoint = normalizeEntryPointRole4(entryPointRole);
+  const entryPoint = normalizeEntryPointRole5(entryPointRole);
   return `${getHandoffRecipientVisibilityCallout(entryPoint)}
 
 ## Handoff Template (Triage → ${entryPoint})
 
-Return a complete, evidence-backed investigation of the authoritative reported bug. Triage is advisory: do not edit implementation files or implement the proposed fix. Use the exact sections below. Cite concrete repository paths and symbols, observed behavior, commands, and test output. Distinguish confirmed findings from hypotheses; never claim a test proved behavior unless its failing assertion demonstrates the report.
+Return a complete, evidence-backed investigation of the authoritative reported bug. Triage is advisory: do not edit implementation files or implement the proposed fix. Begin with the \`## Summary\` section, then use the remaining sections below in order. Use \`###\` for sub-items within a section. Cite concrete repository paths and symbols, observed behavior, commands, and test output. Distinguish confirmed findings from hypotheses; never claim a test proved behavior unless its failing assertion demonstrates the report.
 
 ## Summary
 <briefly state the diagnosis and whether the root cause was confirmed or remains a hypothesis>
@@ -100980,99 +101097,6 @@ var init_triage_handoff_templates = __esm(() => {
   init_command2();
 });
 
-// ../../services/backend/prompts/teams/verifier-handoff-templates.ts
-function normalizeEntryPointRole5(entryPointRole) {
-  return entryPointRole.trim().toLowerCase() || "planner";
-}
-function getEntryPointToVerifierHandoffTemplate(entryPointRole) {
-  const entryPoint = normalizeEntryPointRole5(entryPointRole);
-  return `${getHandoffRecipientVisibilityCallout("verifier")}
-
-## Handoff Template (${entryPoint} → verifier)
-
-The verifier judges, from chatroom logs only, whether the user's last message was achieved. It ${VERIFIER_TEST_RULE}; list any user-requested tests under Requested test runs. Treat the claimed outcome as a claim, not as evidence: the verifier does not trust it and checks every requirement against the logs themselves. Request this review only when the task involved code changes, in any conversation mode. The verdict returns to \`${entryPoint}\`.
-
-## Round
-<1 or 2; for 2, cite the round-1 verdict message id>
-
-## Mode
-<chat | code | code:enhanced>
-
-## User message id
-<id of the user's last message: the origin message id of the user task, or from \`chatroom messages anchor\`>
-
-## Context id
-<id from \`chatroom context read\`, or \`none\` if no context was read for this task>
-
-## Requested test runs
-<the test commands the user explicitly asked for, one per line, or exactly \`None requested.\`>
-
-## Claimed outcome
-<requirement-by-requirement what you believe is complete>
-
-## Evidence pointers
-<builder handoff message ids, commits, PRs, and test results as quoted in those handoffs>
-
-## Known gaps
-<anything incomplete, or exactly \`None.\`>
-
-## Handoff
-Send this request to the verifier with the command below, then stop. The verdict returns to \`${entryPoint}\`.
-
-\`\`\`bash
-${handoffCommand({
-    chatroomId: "<chatroom-id>",
-    role: entryPoint,
-    nextRole: "verifier",
-    cliEnvPrefix: ""
-  })}
-\`\`\``;
-}
-function getVerifierToEntryPointHandoffTemplate(entryPointRole) {
-  const entryPoint = normalizeEntryPointRole5(entryPointRole);
-  return `${getHandoffRecipientVisibilityCallout(entryPoint)}
-
-## Handoff Template (Verifier → ${entryPoint})
-
-Return one advisory verdict for the authoritative request. This review is non-binding: it uses chatroom logs, plus the requested test runs listed in the request, if any, deciding every requirement from the evidence those logs and runs actually contain. It ${VERIFIER_TEST_RULE}. Never accept the claimed outcome as proof. Use the exact sections below, in this order.
-
-## Verdict
-<exactly one of ${VERIFIER_VERDICTS.join(", ")} as the value; ${ACHIEVED} only if every requirement is met; ${NOT_ACHIEVED} if any requirement is unmet (logs show it was not done, or contradict it); ${INCONCLUSIVE} if none is unmet but any is unverified (logs are silent)>
-
-## Objective
-<user message id, any prior user messages used, objective in 1-2 sentences>
-
-## Requirements
-<numbered \`R1 — <requirement> — met | unmet | unverified — <evidence ref>\`>
-
-## Evidence
-<bullets: \`<message id or handoff> — "<short quote>" — supports R#\`; for a requested test run, \`<command> — exit <result> — supports R#\`>
-
-## Missing or unmet
-<per unmet or unverified requirement: what is missing and what evidence would resolve it; exactly \`None.\` if ${ACHIEVED}>
-
-## Scope and limits
-<state the test runs the verifier executed (command and exit result), or "No tests were run; none were requested."; log range read; whether the download was truncated; context id read and whether it matched the request>
-
-## Handoff
-Run the normal handoff command to \`${entryPoint}\` with this complete verdict, then stop.
-
-\`\`\`bash
-${handoffCommand({
-    chatroomId: "<chatroom-id>",
-    role: "verifier",
-    nextRole: entryPoint,
-    cliEnvPrefix: ""
-  })}
-\`\`\``;
-}
-var VERIFIER_VERDICTS, VERIFIER_TEST_RULE = "runs no test the user did not ask for, and never builds, lints, or edits", ACHIEVED, NOT_ACHIEVED, INCONCLUSIVE;
-var init_verifier_handoff_templates = __esm(() => {
-  init_command2();
-  VERIFIER_VERDICTS = ["ACHIEVED", "NOT_ACHIEVED", "INCONCLUSIVE"];
-  [ACHIEVED, NOT_ACHIEVED, INCONCLUSIVE] = VERIFIER_VERDICTS;
-});
-
 // ../../services/backend/prompts/teams/duo/handoff-templates/planner.ts
 var duoPlannerHandoffContract;
 var init_planner = __esm(() => {
@@ -101871,7 +101895,9 @@ var init_glossary = __esm(() => {
 });
 
 // ../../services/backend/prompts/cli/history-retrieval/guidance.ts
-var init_guidance = () => {};
+var init_guidance = __esm(() => {
+  init_proof_of_verification();
+});
 
 // ../../services/backend/prompts/sections/general-knowledge.ts
 var init_general_knowledge = __esm(() => {
@@ -101879,6 +101905,7 @@ var init_general_knowledge = __esm(() => {
   init_glossary();
   init_guidance();
   init_utils3();
+  init_proof_of_verification();
 });
 
 // ../../services/backend/prompts/sections/commands-reference.ts
@@ -101899,7 +101926,9 @@ function getInterRoleHandoffRule() {
 // ../../services/backend/prompts/cli/sections/handoff-rules.ts
 var init_handoff_rules = () => {};
 // ../../services/backend/prompts/cli/sections/proof-of-verification.ts
-var init_proof_of_verification = () => {};
+var init_proof_of_verification2 = __esm(() => {
+  init_proof_of_verification();
+});
 
 // ../../services/backend/prompts/cli/sections/operating-model.ts
 var init_operating_model = () => {};
@@ -101908,7 +101937,7 @@ var init_operating_model = () => {};
 var init_sections = __esm(() => {
   init_core_responsibilities();
   init_handoff_rules();
-  init_proof_of_verification();
+  init_proof_of_verification2();
   init_operating_model();
 });
 
@@ -101975,6 +102004,29 @@ chatroom handoff --chatroom-id="<chatroom-id>" --role="researcher" --next-role="
 \`\`\``;
 });
 
+// ../../services/backend/prompts/cli/roles/triage.ts
+var TRIAGE_GUIDANCE;
+var init_triage3 = __esm(() => {
+  init_sections();
+  TRIAGE_GUIDANCE = `## Triage Operating Model
+
+You are the triage agent responsible for investigating a reported bug so the entry point can delegate a precise fix. You are advisory only: do not edit implementation files or implement the fix.
+
+${"{SESSION_CONTINUITY}"}
+
+${getInterRoleHandoffRule()}
+
+1. Recover the reported bug from the injected task and chatroom history: the observed behavior, the expected behavior, and any reproduction details. If the expected behavior is not explicit, state the assumption you made.
+2. Trace the relevant code paths with concrete repository paths and symbols. Label every finding \`confirmed\` or \`hypothesis\`. Never present a hypothesis as fact.
+3. Attempt a focused reproduction only when it is cheap and safe. A focused regression test may be written as evidence. Do not edit implementation files.
+4. Write the report using the sections in the injected \`<handoff-templates>\`, in the order given, beginning with the \`## Summary\` section.
+5. Hand the report to the configured entry point with the normal command, then stop:
+
+\`\`\`bash
+chatroom handoff --chatroom-id="<chatroom-id>" --role="triage" --next-role="{ENTRY_POINT_ROLE}"
+\`\`\``;
+});
+
 // ../../services/backend/prompts/cli/roles/uiux-engineer.ts
 var UIUX_ENGINEER_GUIDANCE;
 var init_uiux_engineer3 = __esm(() => {
@@ -102006,6 +102058,8 @@ The handoff must contain every required brief section, repository evidence, chos
 var ACHIEVED2, NOT_ACHIEVED2, INCONCLUSIVE2, VERIFIER_GUIDANCE;
 var init_verifier3 = __esm(() => {
   init_verifier_handoff_templates();
+  init_chat_handoff_template();
+  init_handoff_report_template_body();
   init_sections();
   [ACHIEVED2, NOT_ACHIEVED2, INCONCLUSIVE2] = VERIFIER_VERDICTS;
   VERIFIER_GUIDANCE = `## Verifier Operating Model
@@ -102021,8 +102075,9 @@ ${getInterRoleHandoffRule()}
 2a. Requested test runs: if the user's last message (or prior user messages for this objective) explicitly asks for tests to be run, run exactly those commands from the repository root, record the command and exit result, and count the output as evidence. Run no test the user did not ask for. If the request is absent, run nothing.
 3. Run \`chatroom context read --chatroom-id="<chatroom-id>" --role="verifier"\` and note any mismatch with the request's context id.
 4. Decompose the objective into numbered requirements R1..Rn. Split compound requests and ignore anything the user did not actually ask for.
+4a. User expectations: the user's handoff template (the section at the end of this prompt) defines what the user expects from the work. In a code mode, turn each applicable item that concerns the work into an expectation \`U1..Un\`: each requirement's evidence (PR, commit, or file), files changed, Code Change Verification, backlog items moved to \`pending_user_review\` after a verified end-to-end feature with a PR, and any manual steps or unresolved decisions the user must act on. Skip presentation-only items: template disclosure checkboxes, section order, collapsing, diagram format, and Proof of Planning. In \`chat\` mode the template asks only for a direct, concise answer, so add no expectations beyond the requirements.
 5. Find evidence for every requirement in the logs alone: builder handoff reports, planner delegations, quoted test output, commits, and PRs. \`met\` requires concrete evidence in the logs. The planner's claimed outcome is a claim, not evidence. Silence means \`unverified\`. A contradiction, or a log showing the requirement was not done, means \`unmet\`. Never state that tests passed unless a log reports it, or you ran the requested tests yourself.
-6. Choose the verdict by the rules in the injected verdict template: exactly one of ${VERIFIER_VERDICTS.join(", ")}. ${ACHIEVED2} only if every requirement is met; ${NOT_ACHIEVED2} if any requirement is unmet; ${INCONCLUSIVE2} if none is unmet but any is unverified.
+6. Choose the verdict by the rules in the injected verdict template: exactly one of ${VERIFIER_VERDICTS.join(", ")}. ${ACHIEVED2} only if every requirement and every U-expectation is met; ${NOT_ACHIEVED2} if any is unmet; ${INCONCLUSIVE2} if none is unmet but any is unverified.
 7. Follow the injected \`<handoff-templates>\` verdict template exactly, in its order, and put the complete verdict in the handoff. Then hand off to the configured entry point with the normal command, then stop:
 
 \`\`\`bash
@@ -102052,6 +102107,7 @@ var init_fromContext2 = __esm(() => {
   init_builder2();
   init_planner2();
   init_researcher2();
+  init_triage3();
   init_uiux_engineer3();
   init_verifier3();
   init_fromContext();
@@ -138448,4 +138504,4 @@ program2.hook("preAction", async (_thisCommand, actionCommand) => {
 });
 program2.parse();
 
-//# debugId=8506C14FCD932D1964756E2164756E21
+//# debugId=6447CA0431CEDFDC64756E2164756E21