@xfey/tutti 0.1.17 → 0.1.19

package/prompts/runs/task-continuation.md

@@ -57,6 +57,8 @@ Use attached skills only when they help the current task:
 
 Human-uploaded reference material is kept in the repository under `docs/reference/`. If the task contract, project docs, or clarification answer makes a reference file relevant, read the actual repo file before relying on it. Do not infer reference contents from names, upload messages, media types, or paths.
 
+`docs/reference/` is a user-visible file exchange area. Human uploads live under `docs/reference/files/` and `docs/reference/images/`. When this task produces files that project members should inspect directly, write them under `docs/reference/tutti/`. Use `docs/reference/tutti/<meaningful-folder>/...` when a folder name helps explain the output group; that folder name is shown directly in the References UI. Do not create ad hoc folders at the `docs/reference/` root. Files under `docs/reference/tutti/` are displayed automatically, so `user_note_candidate` may mention generated file names but should not include paths.
+
 # Documentation
 
 If this change affects stable project facts, usage, public behavior, interfaces, setup, project organization, maintenance context, or project working rules, update the relevant project documentation in the same worktree.
@@ -88,6 +90,8 @@ If the task creates or updates a user-viewable web page, static page, single-pag
 
 Write `summary` as a concise, human-readable result note for project members who may not inspect the code: what changed, what was found, or why the Run cannot continue. Do not narrate process, repeat structured Tutti status such as checks / docs / promotion / changed paths, or include secrets, host paths, raw logs, provider output, or long excerpts.
 
+For `completed` and `completed_no_repo_changes`, also return `user_note_candidate`. Use a short user-facing sentence only when the final completion card should tell project members a conclusion, result, or generated file name directly. Use `null` when there is no distinct user-facing note. Do not repeat `summary`, and do not include file paths.
+
 # Output
 
 Return JSON matching the structured output schema. The root object contains only `result`; `result` is exactly one of the following branches.
@@ -98,7 +102,8 @@ Completed:
 {
   "result": {
     "completed": {
-      "summary": "The clarified implementation is now complete and the relevant project notes reflect the result."
+      "summary": "The clarified implementation is now complete and the relevant project notes reflect the result.",
+      "user_note_candidate": "The generated comparison file is ready to review."
     }
   }
 }
@@ -110,7 +115,8 @@ Completed with no repository changes:
 {
   "result": {
     "completed_no_repo_changes": {
-      "summary": "The clarified task is complete and did not require repository changes."
+      "summary": "The clarified task is complete and did not require repository changes.",
+      "user_note_candidate": null
     }
   }
 }

package/prompts/runs/task-retry.md

@@ -62,6 +62,8 @@ Use attached skills only when they help the current task:
 
 Human-uploaded reference material is kept in the repository under `docs/reference/`. If the task contract, project docs, or correction context makes a reference file relevant, read the actual repo file before relying on it. Do not infer reference contents from names, upload messages, media types, or paths.
 
+`docs/reference/` is a user-visible file exchange area. Human uploads live under `docs/reference/files/` and `docs/reference/images/`. When this task produces files that project members should inspect directly, write them under `docs/reference/tutti/`. Use `docs/reference/tutti/<meaningful-folder>/...` when a folder name helps explain the output group; that folder name is shown directly in the References UI. Do not create ad hoc folders at the `docs/reference/` root. Files under `docs/reference/tutti/` are displayed automatically, so `user_note_candidate` may mention generated file names but should not include paths.
+
 # Documentation
 
 If this change affects stable project facts, usage, public behavior, interfaces, setup, project organization, maintenance context, or project working rules, update the relevant project documentation in the same worktree.
@@ -93,6 +95,8 @@ If the task creates or updates a user-viewable web page, static page, single-pag
 
 Write `summary` as a concise, human-readable result note for project members who may not inspect the code: what changed, what was found, or why the Run cannot continue. Do not narrate process, repeat structured Tutti status such as checks / docs / promotion / changed paths, or include secrets, host paths, raw logs, provider output, or long excerpts.
 
+For `completed` and `completed_no_repo_changes`, also return `user_note_candidate`. Use a short user-facing sentence only when the final completion card should tell project members a conclusion, result, or generated file name directly. Use `null` when there is no distinct user-facing note. Do not repeat `summary`, and do not include file paths.
+
 # Output
 
 Return JSON matching the structured output schema. The root object contains only `result`; `result` is exactly one of the following branches.
@@ -103,7 +107,8 @@ Completed:
 {
   "result": {
     "completed": {
-      "summary": "The task result is now complete within the frozen scope after correcting the previous candidate."
+      "summary": "The task result is now complete within the frozen scope after correcting the previous candidate.",
+      "user_note_candidate": "The corrected export file is ready to review."
     }
   }
 }
@@ -115,7 +120,8 @@ Completed with no repository changes:
 {
   "result": {
     "completed_no_repo_changes": {
-      "summary": "The requested retry is complete and did not require repository changes."
+      "summary": "The requested retry is complete and did not require repository changes.",
+      "user_note_candidate": null
     }
   }
 }

package/prompts/runs/task-run.md

@@ -44,6 +44,8 @@ Use attached skills only when they help the current task:
 
 Human-uploaded reference material is kept in the repository under `docs/reference/`. If the task contract or project docs make a reference file relevant, read the actual repo file before relying on it. Do not infer reference contents from names, upload messages, media types, or paths.
 
+`docs/reference/` is a user-visible file exchange area. Human uploads live under `docs/reference/files/` and `docs/reference/images/`. When this task produces files that project members should inspect directly, write them under `docs/reference/tutti/`. Use `docs/reference/tutti/<meaningful-folder>/...` when a folder name helps explain the output group; that folder name is shown directly in the References UI. Do not create ad hoc folders at the `docs/reference/` root. Files under `docs/reference/tutti/` are displayed automatically, so `user_note_candidate` may mention generated file names but should not include paths.
+
 # Documentation
 
 If this change affects stable project facts, usage, public behavior, interfaces, setup, project organization, maintenance context, or project working rules, update the relevant project documentation in the same worktree.
@@ -75,6 +77,8 @@ If the task creates or updates a user-viewable web page, static page, single-pag
 
 Write `summary` as a concise, human-readable result note for project members who may not inspect the code: what changed, what was found, or why the Run cannot continue. Do not narrate process, repeat structured Tutti status such as checks / docs / promotion / changed paths, or include secrets, host paths, raw logs, provider output, or long excerpts.
 
+For `completed` and `completed_no_repo_changes`, also return `user_note_candidate`. Use a short user-facing sentence only when the final completion card should tell project members a conclusion, result, or generated file name directly. Use `null` when there is no distinct user-facing note. Do not repeat `summary`, and do not include file paths.
+
 # Output
 
 Return JSON matching the structured output schema. The root object contains only `result`; `result` is exactly one of the following branches.
@@ -85,7 +89,8 @@ Completed:
 {
   "result": {
     "completed": {
-      "summary": "The requested UI state is now available, with the related usage notes updated."
+      "summary": "The requested UI state is now available, with the related usage notes updated.",
+      "user_note_candidate": "The updated usage notes file is ready to review."
     }
   }
 }
@@ -97,7 +102,8 @@ Completed with no repository changes:
 {
   "result": {
     "completed_no_repo_changes": {
-      "summary": "The requested review is complete and did not require repository changes."
+      "summary": "The requested review is complete and did not require repository changes.",
+      "user_note_candidate": null
     }
   }
 }