@xfey/tutti 0.1.92 → 0.1.94

package/dist/collaboration-state/clarification-records.d.ts

@@ -1,4 +1,4 @@
-import type { ClarificationRoundRef, ClarificationThreadRef } from "@tutti/shared/ids";
+import type { ClarificationRoundRef, ClarificationThreadRef, WorkflowInvocationRef } from "@tutti/shared/ids";
 import type { ActiveClarificationProjection, ClarificationRoundProjection, ClarificationThreadProjection, GetClarificationThreadResponse } from "@tutti/shared/schemas/api";
 import type { SqliteDatabase } from "../store/index.js";
 import type { SealedClarificationRoundWithoutSuccessor } from "./types.js";
@@ -14,5 +14,6 @@ export declare function readClarificationRoundProjection(db: SqliteDatabase, rou
 export declare function readClarificationRoundsForThread(db: SqliteDatabase, threadId: ClarificationThreadRef, options?: {
     throughRoundIndex?: number;
 }): ClarificationRoundProjection[];
+export declare function readTaskCompileClarificationRoundsByWorkflowRef(db: SqliteDatabase, workflowRef: WorkflowInvocationRef): ClarificationRoundProjection[];
 export declare function readClarificationThreadResponse(db: SqliteDatabase, threadId: ClarificationThreadRef): GetClarificationThreadResponse | null;
 //# sourceMappingURL=clarification-records.d.ts.map

package/dist/collaboration-state/clarification-records.js

@@ -165,6 +165,24 @@ export function readClarificationRoundsForThread(db, threadId, options = {}) {
             .all(threadId, options.throughRoundIndex);
     return rows.map((row) => mapClarificationRoundRow(row));
 }
+export function readTaskCompileClarificationRoundsByWorkflowRef(db, workflowRef) {
+    const threads = db
+        .prepare(`
+        SELECT id
+        FROM clarification_threads
+        WHERE owner_kind = 'task_compile'
+          AND owner_workflow_ref = ?
+        ORDER BY created_at ASC, id ASC
+      `)
+        .all(workflowRef);
+    if (threads.length === 0) {
+        return [];
+    }
+    if (threads.length !== 1 || threads[0] === undefined) {
+        throw new Error("Task Compile workflow has multiple clarification threads");
+    }
+    return readClarificationRoundsForThread(db, threads[0].id);
+}
 export function readClarificationThreadResponse(db, threadId) {
     const threadRow = readClarificationThreadRow(db, threadId);
     if (threadRow === null) {

package/dist/collaboration-state/index.d.ts

@@ -4,7 +4,7 @@ export { createMainChatAgentMessage, createMainChatMessage, createMainChatSystem
 export { createEmptyScratchpadProjection, readScratchpadReceiptSourceRefs, readScratchpadProjection, upsertScratchpadProjection, } from "./scratchpad.js";
 export { markScratchpadRefreshFailed, markScratchpadRefreshStarted, markScratchpadRefreshSucceeded, markScratchpadSourceDirty, readScratchpadSourceState, } from "./scratchpad-source-state.js";
 export { captureTaskCompileContext, completeTaskCompileContext, readActiveTaskCompileContext, readCurrentScratchpadSourceRefs, rollbackTaskCompileContext, taskCompileContextSnapshot, } from "./task-compile-context.js";
-export { deleteStaleClarificationSubmitReplayHints, readActiveClarificationProjection, readClarificationRoundProjection, readClarificationRoundsForThread, readClarificationThreadResponse, readSealedClarificationRoundsWithoutSuccessor, } from "./clarification-records.js";
+export { deleteStaleClarificationSubmitReplayHints, readActiveClarificationProjection, readClarificationRoundProjection, readClarificationRoundsForThread, readClarificationThreadResponse, readTaskCompileClarificationRoundsByWorkflowRef, readSealedClarificationRoundsWithoutSuccessor, } from "./clarification-records.js";
 export { createClarificationRoundAgentMessage, createClarificationRoundMessage, readClarificationRoundMessagesWindow, } from "./clarification-messages.js";
 export { openNextTaskBoundClarificationRound, openNextTaskCompileClarificationRound, openTaskCompileClarificationRound, } from "./clarification-rounds.js";
 export { closeTaskBoundClarificationAsRetaskingRequired, materializeClarificationSuccessor, materializeTaskBoundRunSuccessor, submitClarificationRound, } from "./clarification-successors.js";

package/dist/collaboration-state/index.js

@@ -4,7 +4,7 @@ export { createMainChatAgentMessage, createMainChatMessage, createMainChatSystem
 export { createEmptyScratchpadProjection, readScratchpadReceiptSourceRefs, readScratchpadProjection, upsertScratchpadProjection, } from "./scratchpad.js";
 export { markScratchpadRefreshFailed, markScratchpadRefreshStarted, markScratchpadRefreshSucceeded, markScratchpadSourceDirty, readScratchpadSourceState, } from "./scratchpad-source-state.js";
 export { captureTaskCompileContext, completeTaskCompileContext, readActiveTaskCompileContext, readCurrentScratchpadSourceRefs, rollbackTaskCompileContext, taskCompileContextSnapshot, } from "./task-compile-context.js";
-export { deleteStaleClarificationSubmitReplayHints, readActiveClarificationProjection, readClarificationRoundProjection, readClarificationRoundsForThread, readClarificationThreadResponse, readSealedClarificationRoundsWithoutSuccessor, } from "./clarification-records.js";
+export { deleteStaleClarificationSubmitReplayHints, readActiveClarificationProjection, readClarificationRoundProjection, readClarificationRoundsForThread, readClarificationThreadResponse, readTaskCompileClarificationRoundsByWorkflowRef, readSealedClarificationRoundsWithoutSuccessor, } from "./clarification-records.js";
 export { createClarificationRoundAgentMessage, createClarificationRoundMessage, readClarificationRoundMessagesWindow, } from "./clarification-messages.js";
 export { openNextTaskBoundClarificationRound, openNextTaskCompileClarificationRound, openTaskCompileClarificationRound, } from "./clarification-rounds.js";
 export { closeTaskBoundClarificationAsRetaskingRequired, materializeClarificationSuccessor, materializeTaskBoundRunSuccessor, submitClarificationRound, } from "./clarification-successors.js";

package/dist/control-plane/run-start.js

@@ -1,4 +1,7 @@
+import { readScratchpadReceiptSourceRefs } from "../collaboration-state/index.js";
 import { materializeWorkflowRecentReferences } from "./recent-references.js";
+import { readCompletedTaskCompileClarificationRounds } from "./task-compile-clarification-context.js";
+import { materializePromptSourceMessages } from "./task-source-context.js";
 import { recordRunPipelineFailure, recordRunPipelineResult, } from "./run-result-recording.js";
 import { projectBriefShouldRefreshForUpdatedPaths, refreshProjectBriefProjection, } from "./project-brief-refresh.js";
 function runLineageFields(lineage) {
@@ -80,12 +83,19 @@ export function startControlPlaneRunForTask(input) {
             const pipelineStartedAt = input.now();
             input.logger?.info(lifecycleFields, "Run pipeline started");
             try {
+                const workflowRef = input.run.task
+                    .created_from_workflow_ref;
+                const sourceMessages = materializePromptSourceMessages(input.store.db, readScratchpadReceiptSourceRefs(input.store.db, workflowRef));
+                const clarificationRounds = readCompletedTaskCompileClarificationRounds({
+                    store: input.store,
+                    workflowRef,
+                });
                 const recentReferences = input.projectContext === undefined
                     ? []
                     : materializeWorkflowRecentReferences({
                         db: input.store.db,
                         workspaceRoot: input.projectContext.workspaceRoot,
-                        workflowRef: input.run.task.created_from_workflow_ref,
+                        workflowRef,
                         now: input.now,
                     });
                 const pipelineResult = await input.run.runner.runTask({
@@ -97,6 +107,10 @@ export function startControlPlaneRunForTask(input) {
                     ...(input.run.continuation_context === undefined
                         ? {}
                         : { continuation_context: input.run.continuation_context }),
+                    ...(sourceMessages.length === 0 ? {} : { source_messages: sourceMessages }),
+                    ...(clarificationRounds.length === 0
+                        ? {}
+                        : { clarification_rounds: clarificationRounds }),
                     ...(recentReferences.length === 0
                         ? {}
                         : { recent_references: recentReferences }),

package/dist/control-plane/task-compile-clarification-context.d.ts

@@ -6,4 +6,8 @@ export declare function readTaskCompileClarificationRounds(input: {
     workflowRef: WorkflowInvocationRef;
     throughRoundId: ClarificationRoundRef;
 }): NonNullable<TaskCompileWorkflowInput["clarification_rounds"]>;
+export declare function readCompletedTaskCompileClarificationRounds(input: {
+    store: HostProjectStore;
+    workflowRef: WorkflowInvocationRef;
+}): NonNullable<TaskCompileWorkflowInput["clarification_rounds"]>;
 //# sourceMappingURL=task-compile-clarification-context.d.ts.map

package/dist/control-plane/task-compile-clarification-context.js

@@ -1,8 +1,4 @@
-import { readActiveClarificationProjection, readClarificationRoundProjection, readClarificationRoundsForThread, readMessageProjectionById, } from "../collaboration-state/index.js";
-import { ScratchpadSourceBudgetExceededError, truncateTextMiddle } from "./scratchpad-source-messages.js";
-const MAX_CLARIFICATION_MESSAGE_CHARS = 4_000;
-const MAX_CLARIFICATION_MESSAGES_TOTAL_CHARS = 16_000;
-const MIN_CLARIFICATION_MESSAGE_CHARS = 160;
+import { readActiveClarificationProjection, readClarificationRoundProjection, readClarificationRoundsForThread, readMessageProjectionById, readTaskCompileClarificationRoundsByWorkflowRef, } from "../collaboration-state/index.js";
 function answerMessage(store, messageId, roundId) {
     const message = readMessageProjectionById(store.db, messageId);
     if (message === null ||
@@ -36,14 +32,17 @@ export function readTaskCompileClarificationRounds(input) {
     const rounds = readClarificationRoundsForThread(input.store.db, throughRound.thread_id, {
         throughRoundIndex: throughRound.round_index,
     });
-    const contextRounds = rounds.map((round) => {
+    return materializeTaskCompileClarificationRounds(input.store, rounds);
+}
+function materializeTaskCompileClarificationRounds(store, rounds) {
+    return rounds.map((round) => {
         if (round.status !== "sealed") {
             throw new Error("Task Compile clarification context cannot include a writable round");
         }
         const answerMessages = (round.submitted_message_refs ?? [])
             .filter((messageId) => messageId !== round.opening_message_id && messageId !== round.card_message_id)
             .flatMap((messageId) => {
-            const mapped = answerMessage(input.store, messageId, round.id);
+            const mapped = answerMessage(store, messageId, round.id);
             return mapped === null ? [] : [mapped];
         });
         return {
@@ -51,20 +50,8 @@ export function readTaskCompileClarificationRounds(input) {
             answer_messages: answerMessages,
         };
     });
-    const answerCount = contextRounds.reduce((count, round) => count + round.answer_messages.length, 0);
-    if (answerCount === 0) {
-        return contextRounds;
-    }
-    if (answerCount * MIN_CLARIFICATION_MESSAGE_CHARS > MAX_CLARIFICATION_MESSAGES_TOTAL_CHARS) {
-        throw new ScratchpadSourceBudgetExceededError();
-    }
-    const perMessageChars = Math.min(MAX_CLARIFICATION_MESSAGE_CHARS, Math.floor(MAX_CLARIFICATION_MESSAGES_TOTAL_CHARS / answerCount));
-    return contextRounds.map((round) => ({
-        request_payload: round.request_payload,
-        answer_messages: round.answer_messages.map((message) => ({
-            ...message,
-            text: truncateTextMiddle(message.text, perMessageChars),
-        })),
-    }));
+}
+export function readCompletedTaskCompileClarificationRounds(input) {
+    return materializeTaskCompileClarificationRounds(input.store, readTaskCompileClarificationRoundsByWorkflowRef(input.store.db, input.workflowRef));
 }
 //# sourceMappingURL=task-compile-clarification-context.js.map

package/dist/control-plane/task-compile-continuation.js

@@ -3,6 +3,7 @@ import { withHostStoreTransaction } from "../store/index.js";
 import { clarificationInvalidates } from "./invalidations.js";
 import { applyTaskCompileProcedureOutput } from "./task-compile-output.js";
 import { readTaskCompileClarificationRounds } from "./task-compile-clarification-context.js";
+import { materializePromptSourceMessages } from "./task-source-context.js";
 import { logProcedureExecutionError } from "./procedure-logging.js";
 import { materializeRecentReferences, readRecentReferenceSources, } from "./recent-references.js";
 export function startControlPlaneTaskCompileContinuation(options) {
@@ -54,6 +55,7 @@ export function startControlPlaneTaskCompileContinuation(options) {
                 const output = await runnerResolution.runner.runTaskCompile({
                     workflow_ref: workflowRef,
                     scratchpad: taskCompileContext.scratchpad_snapshot,
+                    source_messages: materializePromptSourceMessages(options.store.db, taskCompileContext.sources),
                     worklist: readWorklistProjection(options.store.db),
                     ...(recentReferences.length === 0
                         ? {}

package/dist/control-plane/task-compile-start.js

@@ -6,6 +6,7 @@ import { projectBriefShouldRefreshForUpdatedPaths, refreshProjectBriefProjection
 import { applyProjectDocsInitializationResult, buildProjectDocsInitializationContext, tryProjectContextBootstrapDocuments, } from "./project-context-bootstrap.js";
 import { readActiveScratchpadRefreshActivityRef, readControlPlaneScratchpadSourceBatch, runControlPlaneScratchpadRefreshProcedure, } from "./scratchpad-refresh-start.js";
 import { applyTaskCompileProcedureOutput } from "./task-compile-output.js";
+import { materializePromptSourceMessages } from "./task-source-context.js";
 import { materializeRecentReferences, readPendingRecentReferenceSummaryPaths, readRecentReferenceSources, } from "./recent-references.js";
 import { startReferenceSummaryRefreshProcedure } from "./reference-summary-refresh.js";
 export function startControlPlaneTaskCompile(options) {
@@ -431,6 +432,7 @@ export async function runControlPlaneTaskCompileProcedure(options) {
         const output = await options.runner.runTaskCompile({
             workflow_ref: options.workflowRef,
             scratchpad: context.scratchpad_snapshot,
+            source_messages: materializePromptSourceMessages(options.store.db, context.sources),
             worklist: readWorklistProjection(options.store.db),
             ...(recentReferences.length === 0
                 ? {}

package/dist/control-plane/task-source-context-types.d.ts

@@ -0,0 +1,11 @@
+import type { ClarificationRequestPayload } from "@tutti/shared/schemas/api";
+export type PromptSourceMessage = {
+    role: "human" | "tutti";
+    author_display_name?: string;
+    text: string;
+};
+export type TaskCompileClarificationContext = {
+    request_payload: ClarificationRequestPayload;
+    answer_messages: PromptSourceMessage[];
+};
+//# sourceMappingURL=task-source-context-types.d.ts.map

package/dist/control-plane/task-source-context-types.js

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=task-source-context-types.js.map

package/dist/control-plane/task-source-context.d.ts

@@ -0,0 +1,7 @@
+import type { SqliteDatabase } from "../store/index.js";
+import type { PromptSourceMessage } from "./task-source-context-types.js";
+export type TaskSourceMessageRef = {
+    message_id: string;
+};
+export declare function materializePromptSourceMessages(db: SqliteDatabase, sources: TaskSourceMessageRef[]): PromptSourceMessage[];
+//# sourceMappingURL=task-source-context.d.ts.map

package/dist/control-plane/task-source-context.js

@@ -0,0 +1,31 @@
+import { readMessageProjectionById } from "../collaboration-state/index.js";
+function promptSourceMessage(db, source) {
+    const message = readMessageProjectionById(db, source.message_id);
+    if (message === null) {
+        throw new Error("Task source message is unavailable");
+    }
+    if (message.scope.kind !== "main_chat") {
+        throw new Error("Task source message is outside main chat");
+    }
+    if (message.message_kind === "user_text" && message.author.kind === "human") {
+        const displayName = message.author.display_name?.trim();
+        return {
+            role: "human",
+            ...(displayName === undefined || displayName === ""
+                ? {}
+                : { author_display_name: displayName }),
+            text: message.body,
+        };
+    }
+    if (message.message_kind === "agent_text" && message.author.kind === "agent") {
+        return {
+            role: "tutti",
+            text: message.body,
+        };
+    }
+    throw new Error("Task source message has an unsupported kind or author");
+}
+export function materializePromptSourceMessages(db, sources) {
+    return sources.map((source) => promptSourceMessage(db, source));
+}
+//# sourceMappingURL=task-source-context.js.map

package/dist/control-plane/types.d.ts

@@ -5,6 +5,7 @@ import type { ActiveApprovalProjection, ClarificationRequestPayload, ExecutionRu
 import type { HostProjectStore } from "../store/index.js";
 import type { WorkspaceEventBus } from "../server-shell/http/workspace-events.js";
 import type { RecentReferenceContext } from "./reference-context-types.js";
+import type { PromptSourceMessage, TaskCompileClarificationContext } from "./task-source-context-types.js";
 import type { ProcedureWorkflowRunnerResolver } from "./workflows/index.js";
 export type Phase5ControlPlaneOptions = {
     store: HostProjectStore;
@@ -105,6 +106,8 @@ export type RunPipelineInput = {
     dispatch_context: RunDispatchContext;
     continuation_context?: RunContinuationContext;
     correction_context?: RunCorrectionContext;
+    source_messages?: PromptSourceMessage[];
+    clarification_rounds?: TaskCompileClarificationContext[];
     recent_references?: RecentReferenceContext[];
     on_stage?: (progress: RunPipelineStageProgress) => void;
 };

package/dist/control-plane/workflows/openai.js

@@ -153,6 +153,7 @@ export function buildTaskCompilePromptInput(input) {
             open_questions: input.scratchpad.open_questions,
             task_changes: input.scratchpad.task_changes,
         },
+        source_messages: input.source_messages.map((message) => ({ ...message })),
         worklist: {
             modules: input.worklist.modules.map((entry) => ({
                 id: entry.module.id,

package/dist/control-plane/workflows/types.d.ts

@@ -1,5 +1,6 @@
 import type { ExecutionRuntimeSnapshot, MessageProjection, RunResultProjection, TaskDetailProjection, WorklistProjection } from "@tutti/shared/schemas/api";
 import type { RecentReferenceContext } from "../reference-context-types.js";
+import type { PromptSourceMessage, TaskCompileClarificationContext } from "../task-source-context-types.js";
 import type { ClarificationRequestPayload, TaskContractProjection } from "@tutti/shared/schemas/api";
 import type { ProjectDocKey } from "@tutti/shared/schemas/api";
 import type { ActivityRef, ClarificationRoundRef, ClarificationThreadRef, MessageId, TaskId, TaskModuleId, WorkflowInvocationRef } from "@tutti/shared/ids";
@@ -28,11 +29,7 @@ export type ScratchpadRefreshWorklistInput = {
         }>;
     }>;
 };
-export type ScratchpadRefreshSourceMessageInput = {
-    role: "human" | "tutti";
-    author_display_name?: string;
-    text: string;
-};
+export type ScratchpadRefreshSourceMessageInput = PromptSourceMessage;
 export type ScratchpadRefreshWorkflowContext = {
     workflow_ref: WorkflowInvocationRef;
     activity_ref: ActivityRef;
@@ -80,12 +77,10 @@ export type TaskCompileProposalTask = {
 export type TaskCompileWorkflowInput = {
     workflow_ref: WorkflowInvocationRef;
     scratchpad: ScratchpadWorkflowSnapshot;
+    source_messages: PromptSourceMessage[];
     worklist: WorklistProjection;
     recent_references?: RecentReferenceContext[];
-    clarification_rounds?: Array<{
-        request_payload: ClarificationRequestPayload;
-        answer_messages: TaskCompilePromptClarificationMessage[];
-    }>;
+    clarification_rounds?: TaskCompileClarificationContext[];
 };
 export type TaskCompileWorkflowOutput = {
     decision: "ready";
@@ -102,6 +97,7 @@ export type TaskCompilePromptInput = {
         open_questions: string[];
         task_changes: string[];
     };
+    source_messages: PromptSourceMessage[];
     worklist: {
         modules: Array<{
             id: TaskModuleId;
@@ -125,11 +121,7 @@ export type TaskCompilePromptInput = {
         answer_messages: TaskCompilePromptClarificationMessage[];
     }>;
 };
-export type TaskCompilePromptClarificationMessage = {
-    role: "human" | "tutti";
-    author_display_name?: string;
-    text: string;
-};
+export type TaskCompilePromptClarificationMessage = PromptSourceMessage;
 export type TaskCompileStructuredOutput = {
     result: {
         proposal: TaskCompileStructuredProposal;

package/dist/run-pipeline/task-run-invocation.js

@@ -6,6 +6,23 @@ function taskContractRunInput(input) {
         title: input.task.title,
         goal: input.task_detail.detail.contract.goal,
         scope: input.task_detail.detail.contract.scope,
+        ...(input.source_messages === undefined || input.source_messages.length === 0
+            ? {}
+            : { source_messages: input.source_messages.map((message) => ({ ...message })) }),
+        ...(input.clarification_rounds === undefined || input.clarification_rounds.length === 0
+            ? {}
+            : {
+                clarification_rounds: input.clarification_rounds.map((round) => ({
+                    request: {
+                        ...(round.request_payload.title === undefined
+                            ? {}
+                            : { title: round.request_payload.title }),
+                        summary: round.request_payload.summary,
+                        request: round.request_payload.request,
+                    },
+                    answer_messages: round.answer_messages.map((message) => ({ ...message })),
+                })),
+            }),
         ...(input.recent_references === undefined || input.recent_references.length === 0
             ? {}
             : { recent_references: input.recent_references }),

package/dist/server-shell/local-console/server.d.ts

@@ -25,7 +25,7 @@ type LocalConsoleServerOptions = {
     startPackageUpdate?: (preparation: LocalConsolePackageUpdatePreparation) => Promise<{
         pid: number;
     }>;
-    getPackageUpdateCompletion?: () => PackageUpdateCompletionResult | undefined;
+    packageUpdateCompletion?: PackageUpdateCompletionResult;
 };
 export declare function createLocalConsoleServer(options: LocalConsoleServerOptions): FastifyInstance;
 export declare function runLocalConsoleProcess(options?: {

package/dist/server-shell/local-console/server.js

@@ -84,6 +84,7 @@ export function createLocalConsoleServer(options) {
             operations,
             ...(options.env === undefined ? {} : { env: options.env }),
         });
+    let pendingPackageUpdateCompletion = options.packageUpdateCompletion;
     const startPackageUpdate = options.startPackageUpdate ??
         (async (preparation) => {
             try {
@@ -274,7 +275,12 @@ export function createLocalConsoleServer(options) {
     });
     app.get(`${LOCAL_CONSOLE_API_BASE}/bootstrap`, (request) => {
         const session = requireSession(request);
-        const packageUpdateCompletion = options.getPackageUpdateCompletion?.();
+        const packageUpdateCompletion = session.accountReady
+            ? pendingPackageUpdateCompletion
+            : undefined;
+        if (packageUpdateCompletion !== undefined) {
+            pendingPackageUpdateCompletion = undefined;
+        }
         return {
             account_gate: session.accountReady
                 ? {
@@ -487,7 +493,7 @@ export async function runLocalConsoleProcess(options = {}) {
             lastActivityAt = now().getTime();
         },
         onShutdown: () => requestClose(),
-        getPackageUpdateCompletion: () => packageUpdateCompletion,
+        ...(packageUpdateCompletion === undefined ? {} : { packageUpdateCompletion }),
         ...(options.now === undefined ? {} : { now: options.now }),
     });
     await app.listen({ host: "127.0.0.1", port: 0 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xfey/tutti",
-  "version": "0.1.92",
+  "version": "0.1.94",
   "type": "module",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",

package/prompts/README.md

@@ -15,7 +15,7 @@ Prompt / skill 改造后的 live 实验计划与记录见 [prompt-flow-experimen
 
 - `procedures/`：`scratchpad_refresh`、`project_brief_refresh`、`task_compile`、`project_context_bootstrap`、`context_sync`、`reference_summary_refresh`、`follow_up_check` 等 Procedure / workflow prompt。
 - `artifacts/`：候选实现完成后的 transient Artifact applicability 判断；只接收 bounded task / diff / repo evidence，不写回 Task contract 或 repo。
-- `runs/`：正式 task `Run`、task-bound continuation 与 pipeline self-correction retry 等 Run pipeline prompt；task contract 可附带 receipt-derived compact `recent_references`，两类 retry 都保留它。provider transient retry 不新增 prompt，而是复用失败 attempt 的同一 prompt family。所有 Run prompt都以持久 project workspace为 cwd contract，不设计 promotion reconcile prompt。
+- `runs/`：正式 task `Run`、task-bound continuation 与 pipeline self-correction retry 等 Run pipeline prompt；task contract 可附带 receipt-derived `source_messages`、已完成 Task Compile `clarification_rounds` 与 compact `recent_references`，两类 retry 都保留它们。provider transient retry 不新增 prompt，而是复用失败 attempt 的同一 prompt family。所有 Run prompt都以持久 project workspace为 cwd contract，不设计 promotion reconcile prompt。
 - `codex/`：Codex app-server smoke 等 adapter / spike prompt。
 - `skills/`：Tutti packaged built-in Codex skills；由 server-side app-server skill selection 选择，不在 Web Skills 页面展示，也不保存 user skills。
 - `chat-assistant.md`：主群聊与 clarification round 内 `@tutti` 只读项目问答 prompt；它不是 Procedure / Run prompt。
@@ -35,3 +35,5 @@ Prompt / skill 改造后的 live 实验计划与记录见 [prompt-flow-experimen
 - prompt 文件不得保存 provider secret、credential ref、host 绝对路径、project workspace path、join token、cookie 或 provider raw event。
 - built-in skill 文件不得保存 context API token、host-local URL、provider secret、host 绝对路径或 user skill 内容。
 - workflow 语义和 prompt 选择归 `control-plane/workflows`；provider adapter 只执行渲染后的 provider request。
+- prompt 应说明本轮实际 direct input、目标和真实能力边界。对 server-side selection 未提供且 direct input 已从结构上排除的能力，不写假设性的“不得读取”指令；安全、workspace、任务契约、证据和输出 schema 等真实边界仍需明确。
+- active app-server prompt 中显式命名的 built-in skill 必须属于对应 server-side selection；该映射由 prompt contract tests 与 `providers/openai/app-server/skills.ts` 共同约束。

package/prompts/artifacts/README.md

@@ -4,4 +4,4 @@ This directory contains model-facing prompts used by the internal Artifact candi
 
 - `applicability.md` makes one read-only, non-persistent decision after a candidate diff exists and only when deterministic evidence cannot decide whether a browser-viewable Artifact is applicable.
 
-The prompt receives only the frozen task `title / goal / scope`, bounded changed paths, bounded Git diff facts, and limited repository evidence. It must not receive chat history, Scratchpad, task / activity ids, host paths, run workspace paths, credentials, provider output, or secrets. Applicability output is transient pipeline state; it is not written back to the Task contract or repository.
+The prompt receives the frozen task `title / goal / scope`, bounded changed paths, bounded Git diff facts, and limited repository evidence. Its instructions base the decision on those supplied fields without enumerating inaccessible collaboration sources. Task / activity ids, host paths, run workspace paths, credentials, provider output, and secrets remain excluded by input construction. Applicability output is transient pipeline state; it is not written back to the Task contract or repository.

package/prompts/artifacts/applicability.md

@@ -18,7 +18,7 @@ Decide whether the completed repository candidate should provide a browser-viewa
 - Return `not_applicable` only when the evidence clearly describes a library without a browser entry, a CLI, a migration or data script, an API-only service without a Web client, docs-only maintenance, or another task with no reasonable browser presentation surface.
 - Existing browser application evidence is relevant even if the changed path is a server entry, API handler, build configuration, or other behavior required by that application.
 - Ambiguity must resolve to `artifact_required`. Do not use a missing field, `unknown`, or a confidence score to avoid the decision.
-- Do not propose implementation changes. Do not infer hidden requirements from chat, Scratchpad, task ids, or machine-local context; none of those are inputs.
+- Base the decision only on the supplied task, diff, and repository evidence. Do not propose implementation changes.
 
 # Output
 

package/prompts/procedures/README.md

@@ -6,7 +6,7 @@
 
 - `scratchpad-refresh.md`：根据当前周期完整主群聊消息、Project Brief、精简 Worklist 与可选 active Task Compile Context 重建唯一 Current Scratchpad。
 - `project-brief-refresh.md`：根据四个 baseline Project Docs 的 bounded 正文和可读状态生成 host-local Project Brief 短摘要。
-- `task-compile.md`：使用 Codex app-server read-only adapter，根据直接输入的 Scratchpad / Worklist 与按需读取的项目上下文文件生成追加式 task compile proposal，或请求 workflow-bound clarification；执行面仅为 app-server read-only。
+- `task-compile.md`：使用 Codex app-server read-only adapter，根据直接输入的冻结 source messages、Scratchpad / Worklist 与按需读取的项目上下文文件生成追加式 task compile proposal，或请求 workflow-bound clarification；执行面仅为 app-server read-only。
 - `project-context-bootstrap.md`：使用 Codex app-server read-only adapter 为缺失 baseline context files 生成完整文件内容计划；实际写入和 commit 由 `workspace-ops` 受控完成。
 - `context-sync.md`：使用 Codex app-server read-only adapter 生成文档同步更新计划；实际文件写入和 commit 由 `workspace-ops` 受控完成。
 - `reference-file-summary.md`：使用 Codex app-server read-only adapter 读取单个 reference 文件并生成“包含什么”的抽象 summary；不复现原句、表格行、个人信息、标识符或 secret-like value，正文敏感本身不构成 unavailable，只有无法访问、解码或理解才返回该分支。实际 README summary 索引写入和 commit 由 `workspace-ops` 受控完成。
@@ -14,13 +14,13 @@
 
 `project_context_bootstrap` 的 provider path 只让 Codex app-server read-only adapter 生成缺失文档内容；如果该计划不可用，Control Plane 会回退到本地保守模板。
 `project_context_bootstrap` 的 read-only 输入只包含项目名、非空时的 `missing_docs` 与刷新后的 Scratchpad；prompt 会要求 app-server 只读探索仓库，并可通过 `read-project-docs` / `read-references` skill 按需读取现有文档和参考文件。输出只包含 `documents[].doc_key/content`，固定 path 由 Control Plane 后处理生成。
-`task_compile` 的 read-only 输入只包含 durable context 固定的五字段 Scratchpad、当前 Worklist、可选 compact `recent_references` 和可选完整有序 `clarification_rounds`；reference 项只含 path、最终 name 与 available/unavailable summary，不含 blob/message/workflow audit fields。每次 continuation 仍读取同一 pinned Scratchpad 与 source set，不读取并行变化的 Current Scratchpad或 boundary 后的新上传；later round 可以纠正 earlier round，明确撤回时允许空 proposal 正常结束。prompt 暴露 `read-project-docs` / `read-worklist` / `read-references` skills 供 app-server 必要时读取项目上下文文件、既有任务 contract / latest result 或相关 reference 正文；拟议工作实质依赖 reference 时必须在冻结 contract 前读取 source，不以 summary 替代原文。只有现有上下文支持一个 coherent formal contract 时才 proposal；重大歧义或冲突若必须替用户选择意图，则请求最少 clarification，低影响、可逆或已有 convention 覆盖的细节继续写成有界假设。Scratchpad 和 Worklist 紧凑视图仍以直接输入为准，不通过 skill 重读 Scratchpad。provider raw output 使用 `{ result: ... }` 互斥分支；proposal 分支用 `module_ref` 指向新模块或既有模块，task 只输出 `title / goal / scope`，runner adapter 再映射为 Control Plane 内部 proposal：`goal` 同时作为内部 task summary 和 contract goal，`scope` 作为内部 contract scope。
+`task_compile` 的 read-only 输入包含 durable context 固定的完整有序 `source_messages`、五字段 Scratchpad、当前 Worklist、可选 compact `recent_references` 和可选完整有序 `clarification_rounds`。消息与 answers 统一使用 `role / optional author_display_name / text`，不含 message/workflow ids、时间戳或完整 projection；reference 项只含 path、最终 name 与 available/unavailable summary。每次 continuation 由 Host 物化同一 pinned refs 并追加 sealed rounds，因此 boundary 后的新聊天或上传不会进入旧 workflow，无需 `read-main-chat` / `read-scratchpad` skill 或假设性禁止文本。精确正文由 source fields 承接，task `title / goal / scope` 保持简洁正式。prompt 暴露 `read-project-docs` / `read-worklist` / `read-references` skills 供 app-server 必要时读取项目上下文文件、既有任务 contract / latest result 或相关 reference 正文；拟议工作实质依赖 reference 时必须在冻结 contract 前读取 source，不以 summary 替代原文。只有现有上下文支持一个 coherent formal contract 时才 proposal；重大歧义或冲突若必须替用户选择意图，则请求最少 clarification，低影响、可逆或已有 convention 覆盖的细节继续写成有界假设。later round 可以纠正 earlier round，明确撤回时允许空 proposal 正常结束。provider raw output 使用 `{ result: ... }` 互斥分支；proposal 分支用 `module_ref` 指向新模块或既有模块，task 只输出 `title / goal / scope`，runner adapter 再映射为 Control Plane 内部 proposal：`goal` 同时作为内部 task summary 和 contract goal，`scope` 作为内部 contract scope。
 `context_sync` 没有 provider-facing direct input；workflow ref、activity ref、触发原因、安全元数据、checked paths、skipped paths 和 open questions 都不进入 prompt，只用于运行时追踪、调度或审计。prompt 说明通用文档同步目标、目标项目文档落点和 canonical docs 职责，由 app-server 主动探索 repo，并通过 `read-project-docs` / `read-worklist` / `read-references` skill 按需读取现有文档、正式任务上下文和参考文件。Worklist / task result 只作为阶段性完成背景和稳定结果线索，不写成长文档里的逐任务流水。
 `context_sync` prompt 只返回 `summary` 与 `updates[].path/content`；空 `updates` 表示无需同步，非空 `updates` 由 Control Plane 调用 `workspace-ops` 做 path policy、mainline clean 检查、文件写入和 Git commit。
 `project_brief_refresh` 只走 OpenAI SDK structured output，不使用 Codex app-server，不读取 repo 或 skills。它接收四个 baseline Project Docs 的 bounded source 内容与状态，输出 `product_summary / tech_summary / structure_summary / principles_summary`，由 Control Plane 写入 host-local `project_brief` projection；Project Docs 创建、同步、被成功 Run promotion 修改，或 provider setup 后需要 backfill 时可以触发。provider 不可用、source 不可用、brief 已经 fresh 或刷新失败都不影响 Project Docs 写入结果。
 `reference_summary_refresh` 不接收 provider-facing workflow input。Control Plane 内部保留 workflow / activity trace anchors 与单个 reference file metadata 用于定位、审计和写回；runner 会把目标文件复制到一个临时目录，并以该目录作为 app-server `cwd`，prompt 只说明读取当前目录中的唯一目标文件、禁用写入和网络，并返回 bounded structured summary 输出。
 Phase 6.5 的 reference upload message 可以作为普通聊天事实进入 `scratchpad_refresh`，但 prompt 明确禁止模型在未读取文件的情况下推断文件正文。
-`scratchpad_refresh` 与 `task_compile` 在压缩上下文时应保留任务执行和验收必需的用户提供细节。`scratchpad_refresh` 读取当前周期完整、有序的主群聊 `messages`，并按 `messages > active_task_compile > worklist > project_brief` 理解上下文；只有 `messages` 可以产生新的 `task_changes`。每条超长消息先做保留头尾的中间截断，再合并连续作者；不得静默删除较早消息。需要排除的是 secret、provider 细节、raw log 和 Tutti runtime / internal path。
+`scratchpad_refresh` 在压缩上下文时应保留任务执行和验收必需的用户提供细节。它读取当前周期完整、有序的主群聊 `messages`，并按 `messages > active_task_compile > worklist > project_brief` 理解上下文；只有 `messages` 可以产生新的 `task_changes`。每条超长消息先做保留头尾的中间截断，再合并连续作者；不得静默删除较早消息。`task_compile` 则从 durable refs 直接物化原消息正文和完整 clarification answers，不把大段原文复制进 task contract。需要排除的是 secret、provider 细节、raw log 和 Tutti runtime / internal path。
 `follow_up_check` 的 provider-facing 输入只包含展平后的 `title / goal / scope`、上一 `Run.needs_human` 的 `summary`、原 `clarification_request_payload` 和压缩后的 `answers[]`；workflow ref、task id/status、activity ref、result kind、Run lineage、message id、作者 identity 和时间戳不进入 prompt。它只判断原 human decision 是否在同一 frozen contract 内解决：已解决为 `resume`，同一决策仍可在 contract 内补充为 `needs_more_input`，采纳回答会改变 goal / scope 为 `requires_retasking`；不得请求 Run 自己负责的实现选择。provider raw output 使用 `{ result: ... }` 互斥分支，runner adapter 再映射为 Control Plane 内部 outcome。控制面负责把三个结果分别物化为 continuation、下一轮 round 或 retasking-required closure。`Run.failed` / `Task.failed` 当前不再通过 follow-up retry 复活。
 
 ## 输入变量

package/prompts/procedures/follow-up-check.md

@@ -32,7 +32,7 @@ Fields:
 
 # Decision Rules
 
-- Use only `workflow_input_json`; do not inspect files, repository state, Worklist, Scratchpad, references, Project Docs, or external context.
+- `workflow_input_json` is the complete context for this decision.
 - Treat `goal` and `scope` as the frozen task contract, `previous_run.summary` and `previous_run.clarification_request_payload` as the identified human decision, and `answers` as the submitted human reply.
 - Evaluate only whether the answers resolve that decision within the same frozen task contract.
 - Return `resume` when the blocker is resolved without changing the contract.

package/prompts/procedures/reference-file-summary.md

@@ -12,7 +12,7 @@ You summarize one human-uploaded Tutti reference file.
 
 - The current working directory is an isolated temporary directory created for this turn.
 - It contains exactly one copied target reference file.
-- No project repository context, chat history, Worklist state, Project Docs, skills, agent context API, network, or web search is available.
+- The copied file is the only evidence for this summary.
 - The original reference path, file metadata, workflow refs, and activity refs are intentionally not part of the prompt.
 
 # Task

package/prompts/procedures/task-compile.md

@@ -18,18 +18,18 @@ You compile Tutti's Scratchpad into an append-only Worklist proposal for post-ba
 
 # Context Sources
 
-- `scratchpad` is the immutable five-field snapshot pinned when this task_compile workflow was submitted. It has already removed message ids, timestamps, activity refs, and refresh state.
+- `source_messages` contains the frozen discussion submitted for this workflow. Messages remain in chronological order and preserve their original boundaries.
+- `scratchpad` is the immutable five-field summary pinned for the same submission. It has already removed message ids, timestamps, activity refs, and refresh state.
 - `worklist.modules[]` is the current formal Worklist. Module `id` values are the only valid existing module keys. Module names and task titles are historical anchors for resolving short references in the current Scratchpad.
 - `recent_references`, when present, identifies human-uploaded files from the same pinned Scratchpad cycle and provides a terminal summary status for each source.
 - `clarification_rounds`, when present, contains every sealed workflow-bound clarification round for this same pinned Scratchpad, ordered from earliest to latest. Each round keeps its request separate from its ordered submitted answer messages.
-- Later clarification rounds may add to or correct earlier rounds. Interpret them chronologically without discarding the earlier context.
-- Concurrent main-chat discussion and the mutable Current Scratchpad are intentionally absent. Never assume that a short clarification answer applies to a newer chat direction, and never use skills to find concurrent chat to complete this workflow.
-- Treat the provided Scratchpad and Worklist as authoritative. Do not use skills to reread them.
+- Use source messages and clarification answers when exact wording, values, lists, or decisions matter. Later explicit clarification takes precedence over earlier material.
+- Use the direct Worklist projection for current topology.
 - Use `read-worklist` only when an existing task's contract or latest result would clarify the current task's subject, boundary, or delivery relationship. Do not duplicate tasks already covered by the Worklist.
 - Use `read-project-docs` or `read-references` only when task scope, acceptance, product intent, technical stack, repo structure, agent working rules, or reference contents matter and are not clear from direct input.
 - When proposed work materially depends on a recent reference, read the relevant source before freezing the task contract; do not rely on its summary alone.
 - Preserve user-provided non-secret details when they are needed to execute or accept the task. Do not generalize them into vague labels.
-- Do not use web search, credentials, provider internals, raw logs, or Tutti runtime/internal paths.
+- Exclude credentials, provider internals, raw logs, and Tutti runtime/internal paths.
 
 # Delivery Surface Context
 
@@ -49,7 +49,7 @@ Return a `proposal` only when the available context supports one coherent formal
 Return `clarification_request_payload` only when all are true:
 
 - Resolving the issue would materially change goal, scope, user-visible behavior, visual or interaction direction, technical shape, data or asset source, acceptance criteria, safety boundary, or external side effect.
-- Scratchpad, Worklist, Project Docs, repo facts, and relevant references do not answer it.
+- Source messages, clarification rounds, Scratchpad, Worklist, Project Docs, repo facts, and relevant references do not answer it.
 - Guessing would likely cause rework, risk, or user surprise.
 - A concise human answer can unblock task creation.
 
@@ -80,7 +80,7 @@ Never create tasks for Tutti internal procedures or control-plane steps, includi
 - `goal`: exact task outcome in one concise sentence. Tutti uses this as the internal task summary and task contract goal.
 - `scope`: 3-7 short items that together cover implementation surfaces, important constraints / non-goals / assumptions, and observable acceptance signals.
 
-Avoid repeating the same idea across `title`, `goal`, and `scope`. Do not copy long PRD passages, chat excerpts, Scratchpad prose, or Project Docs into task details. Even though task fields should stay concise, `scope` must carry user-provided details the Run will need and cannot reliably infer later.
+Avoid repeating the same idea across `title`, `goal`, and `scope`. Keep the task contract concise. When execution depends on exact supplied material, describe how it should be used without copying the full material into the task.
 
 # Output
 

package/prompts/prompt-flow-map.md

@@ -22,12 +22,12 @@ Provider validation 也使用 OpenAI Responses API，但它只是启动前 crede
 - `scratchpad_refresh`：保持 OpenAI SDK structured output；已收敛为纯主群聊周期的轻量观察者，输入为完整 current-cycle messages、精简 Worklist、可选 ready Project Brief 和可选 active Task Compile Context，不再递归使用 previous Scratchpad 或读取 clarification。
 - `project_brief_refresh`：使用 OpenAI SDK structured output；从四个 canonical Project Docs 的 bounded source 派生 host-local Project Brief，不使用 Codex app-server、不写目标 repo。
 - `project_context_bootstrap`：已对齐为 Codex app-server read-only + `read-project-docs` / `read-references` skills；只生成缺失 baseline context files 计划，写入仍归 `workspace-ops`。
-- `task_compile`：已对齐为 Codex app-server read-only + `read-project-docs` / `read-worklist` / `read-references` skills；Scratchpad 始终来自 workflow-owned durable Task Compile Context，Worklist 使用最新紧凑视图，continuation 追加完整有序 clarification rounds，不读取 Current Scratchpad；任务化 readiness 内聚在该 workflow 中，不新增独立 gate。
+- `task_compile`：已对齐为 Codex app-server read-only + `read-project-docs` / `read-worklist` / `read-references` skills；Host 从 workflow-owned durable Task Compile Context 物化完整有序 `source_messages` 与五字段 Scratchpad，Worklist 使用最新紧凑视图，continuation 复用同一来源并追加完整有序 clarification rounds；任务化 readiness 内聚在该 workflow 中，不新增独立 gate。
 - `context_sync`：已对齐为 Codex app-server read-only + `read-project-docs` / `read-worklist` / `read-references` skills；provider-facing direct input 为空，让 app-server 只读探索 repo，并输出 `summary` 与 `updates[].path/content`。
-- `workspace_write_run`：已对齐为 workspace-write + 精简 task contract 输入 + Project Docs / Worklist skills + user skills；存在 user skills 时通过 `skills/list.perCwdExtraUserRoots` 预热当前项目 `<TUTTI_HOME>/projects/<project_id>/skills`；Reference Files 不再通过 built-in skill 暴露，若任务或项目文档指向 `docs/reference/` 中资料，Codex 可直接读取相关 repo 文件。
-- `follow_up_run`：已对齐为 workspace-write + 精简 task contract 输入 + continuation block + Project Docs / Worklist skills + user skills；存在 user skills 时同样预热当前项目 `<TUTTI_HOME>/projects/<project_id>/skills` extra root；Reference Files 不再通过 built-in skill 暴露，若任务、项目文档或 clarification answer 指向 `docs/reference/` 中资料，Codex 可直接读取相关 repo 文件。
+- `workspace_write_run`：已对齐为 workspace-write + 精简 task contract + receipt-derived `source_messages` / completed Task Compile `clarification_rounds` / `recent_references` + Project Docs / Worklist skills + user skills；存在 user skills 时通过 `skills/list.perCwdExtraUserRoots` 预热当前项目 `<TUTTI_HOME>/projects/<project_id>/skills`；Reference Files 不再通过 built-in skill 暴露，若任务或项目文档指向 `docs/reference/` 中资料，Codex 可直接读取相关 repo 文件。
+- `follow_up_run`：已对齐为 workspace-write + 同一 compile-time source context + continuation block + Project Docs / Worklist skills + user skills；存在 user skills 时同样预热当前项目 `<TUTTI_HOME>/projects/<project_id>/skills` extra root；Reference Files 不再通过 built-in skill 暴露，若任务、项目文档或 clarification answer 指向 `docs/reference/` 中资料，Codex 可直接读取相关 repo 文件。
 - `artifact_applicability`：候选缺少 manifest 且 deterministic evidence 无法明确判定时，使用 `artifacts/applicability.md` 做 transient read-only structured-output 判断；判断不写入 Task contract，失败时 fail closed。
-- `pipeline_self_correction`：已对齐为 workspace-write + 精简 task contract 输入 + 必填 correction diagnostic；使用 `runs/task-retry.md` 和 `workspace_write_run` selection，在同一 active Run 记录终态前处理 Artifact gate、checks 前后无 candidate diff、checks 失败或 accepted-checkpoint failure 等可自纠 feedback，并在同一持久 project workspace 中保留前一 attempt 的 source 与 repo-local runtime state。
+- `pipeline_self_correction`：已对齐为 workspace-write + 同一 compile-time source context + 必填 correction diagnostic；使用 `runs/task-retry.md` 和 `workspace_write_run` selection，在同一 active Run 记录终态前处理 Artifact gate、checks 前后无 candidate diff、checks 失败或 accepted-checkpoint failure 等可自纠 feedback，并在同一持久 project workspace 中保留前一 attempt 的 source 与 repo-local runtime state。
 - `follow_up_check`：保持 OpenAI SDK structured output；已收敛为只判断上游 `Run.needs_human` 的 task-bound answer，不接入 skill，不重查代码或协作上下文；provider-facing input 只保留精简 task contract、previous Run pause reason、原 clarification request 和 answers，provider raw output 使用 `{ result: ... }` 互斥分支，failed-task retry 从 active path 移除。
 - `reference_summary_refresh`：已对齐为 Codex app-server read-only + 单文件临时 `cwd`；workflow / activity refs、原始 path、blob、media type 和 file metadata 只留在 Control Plane 内部，不进入 prompt；provider raw output 使用 `{ result: ... }` 互斥分支，只输出 `summarized.summary` 或 `unavailable.reason`。
 
@@ -54,6 +54,7 @@ Provider validation 也使用 OpenAI Responses API，但它只是启动前 crede
 - 2026-08-01：Run pipeline 完成持久 project workspace cutover；本条取代上述历史记录中的 attempt workspace cleanup、fresh run workspace、result commit / fast-forward promotion 与 reconcile candidate 语义。initial、continuation、provider transient retry 和 self-correction 现在复用同一项目目录；candidate Artifact、checks 与正式 preview 共享目录身份，通过 gate 后创建 accepted commit + immutable activity tag。
 - 2026-08-10：Scratchpad / task compile 上下文边界完成重构。Scratchpad 只从当前主群聊周期完整重建，输入收敛为 `project_brief? / worklist / active_task_compile? / messages`；Submit 固定 durable Task Compile Context，bootstrap / compile / continuation 复用 pinned snapshot，continuation 使用完整 `clarification_rounds`，receipt / sources 从 context 生成，clarification 不再回写 Scratchpad。
 - 2026-08-12：Submit 在 Task Compile 前等待 pinned-cycle references 对当前 blob 形成 summary terminal；Task Compile 与对应 Run 接收 compact `recent_references`，initial / continuation / provider retry / self-correction 保留同一 source set。
+- 2026-08-18：Task Compile 与 descendant Run source context 完成贯通。Host 从 pinned / receipt refs 物化相同的有序 `source_messages`，从 workflow-owned closed clarification chain 恢复完整 Task Compile rounds；initial Run、task-bound continuation、provider transient retry 和 pipeline self-correction 均保留这些字段。Task Compile / Run 不新增 `read-main-chat` 或 `read-scratchpad` skill；active prompt 已按实际 direct input 与 server-side selection 审计，移除描述不存在读取能力的禁止文本。
 
 后续逐项讨论时，默认从尚未在本节标为已完成的环节继续推进，避免重复分析已经收口的 prompt。
 
@@ -274,14 +275,15 @@ Submit gate 在缺失 baseline context files 且当前主群聊周期存在尚
 
 当前输入：
 
+- `workflow_input_json.source_messages`：Task Compile Context 固定的完整、有序主群聊 source；每条只包含 `role / optional author_display_name / text`，保留正文与消息边界，不含 message id、cursor、timestamp 或 workflow ref。初次 compile 和所有 continuation 都由 Host 从同一组 pinned refs 物化。
 - `workflow_input_json.scratchpad`：当前 workflow-owned Task Compile Context 固定的五个业务字段：`topic / background_summary / current_consensus / open_questions / task_changes`。初次 compile 和所有 continuation 都读取同一 snapshot。
 - `workflow_input_json.worklist.modules[]`：当前正式 Worklist 的紧凑模块视图，仅包含模块 `id / name / optional summary / archived` 与任务 `title / summary / status`；模块名和任务标题作为短指代解析的历史锚点。
 - `workflow_input_json.recent_references`：可选当前 pinned Scratchpad cycle human uploads，按 source message 顺序稳定生成；每项只含 repo-relative `path`、最终 `name` 与对应 source blob 的 `available.text` 或 `unavailable.reason`，不含 blob oid、message id 或 workflow audit fields。
 - `workflow_input_json.clarification_rounds`：可选 workflow-bound continuation 上下文，按 round index 包含截至当前 sealed round 的全部 `request` 和 submitted answer messages；answer message 只包含 `role / optional author_display_name / text`。opening/card refs 被排除，later round 可修正 earlier round，但不得丢失较早轮次。
 - 可通过 `read-project-docs` / `read-worklist` / `read-references` skills 按需读取当前项目上下文文件正文、既有任务 contract / latest result 或相关 reference 正文，用于理解产品目标、技术栈、结构、agent 工作规则、阶段性任务背景或用户提供的参考资料。
-- 不通过 skill 重读 Scratchpad；Worklist 紧凑视图以直接输入为准，task detail 只在需要理解既有任务细节时读取。
+- Worklist 紧凑视图以直接输入为准，task detail 只在需要理解既有任务细节时读取；main chat 与 Scratchpad read skills 不属于该 selection，因为冻结消息和摘要已经是 direct input。
 
-不进入 prompt 的字段：`context_entry_json`、workflow ref、activity ref、Task Compile Context source window / refs / submitted time、Scratchpad `id/state/updated_*`、Worklist module/task order、时间戳、latest run result、created-from workflow ref、clarification message id / refs / created_at 等审计或调度字段。continuation 也不读取 Current Scratchpad 或 boundary 后的主群聊。
+不进入 prompt 的字段：`context_entry_json`、workflow ref、activity ref、Task Compile Context source window / refs / submitted time、Scratchpad `id/state/updated_*`、Worklist module/task order、时间戳、latest run result、created-from workflow ref、clarification message id / refs / created_at 等审计或调度字段。Host 只展开 pinned refs，因此 Current Scratchpad 与 boundary 后消息不会混入旧 workflow。
 
 Provider raw 输出：根对象只包含 `result`；`result` 内二选一输出 `proposal` 或 `clarification_request_payload`，不输出 `decision`。proposal 只包含新模块和新任务；新模块字段为 `temp_key`、`name`，任务使用 `module_ref: { kind: "new" | "existing", key }` 指向本次新模块或现有 Worklist module。任务字段只包含 `title / goal / scope`；`goal` 是一句话任务目标，`scope` 同时承接实施范围、关键约束 / 非目标 / 假设和可观察验收信号。
 
@@ -293,9 +295,9 @@ Provider raw 输出：根对象只包含 `result`；`result` 内二选一输出
 
 - `task_compile` selection 开放 `read-project-docs` / `read-worklist` / `read-references`，但 prompt 不预设读取顺序或人工拼装上下文；只说明在必要时可以读取。
 - 任务化 readiness 内聚在 `task_compile`：能冻结没有重大隐藏假设的正式 task contract 才生成 proposal；无法从现有上下文可靠推断的高影响缺失决策走现有 workflow-bound clarification，不新增 workflow / gate / schema。
-- task `scope` 是 Run 后续执行会收到的关键边界，应保留实施和验收必需的用户提供细节，而不是要求 Run 从聊天或 Scratchpad 重新推断。
+- task `goal / scope` 保持正式、简洁并决定执行边界；执行依赖的精确原文、列表或数值由同一 source context 传给 Run，不复制成长任务描述。
 - clarification 明确撤回 pinned submission 时，provider 可以返回 empty proposal 并正常结束当前 workflow；不得把 concurrent Current Scratchpad 中的新方向借给旧 chain。
-- clarification answers 按每条原始消息做头尾保留的中间截断，不跨 round 合并，也不只保留最后一轮；最小完整 chain 超预算时 continuation 明确失败。
+- clarification answers 保持原消息边界与完整正文，不跨 round 合并，也不只保留最后一轮；later explicit round 可以修正 earlier material。
 - Project Docs 缺失通常不会进入本环节，因为 Submit gate 会先通过 `project_context_bootstrap` 与 `workspace-ops.initializeProjectDocs` 补齐缺失 baseline paths。gate 检查的是固定路径存在性，不保证内容质量。
 - Project Docs unreadable / unavailable 应是少见状态，通常来自编码或二进制异常、path policy、repo snapshot / viewer、IO 或 scope 配置问题。模型应在 Scratchpad / Worklist 与其他允许证据足够时继续任务化；只有无法定义目标、范围、约束或验收时才请求 workflow-bound clarification。
 - Project Docs 中的 `To be confirmed.` 等占位是开放上下文，不是阻塞项，也不能当作已确认事实。
@@ -367,11 +369,13 @@ Provider raw 输出：根对象只包含 `result`；`result` 内二选一输出
 - `run_input_json.title`：短任务标题，用于快速定位任务意图。
 - `run_input_json.goal`：正式任务目标。
 - `run_input_json.scope`：正式任务边界，同时承接关键约束、非目标、假设和可观察验收信号。
+- `run_input_json.source_messages?`：通过 `Task.created_from_workflow_ref -> receipt sources` 恢复的原提交讨论，只含有序 `role / optional author_display_name / text`。
+- `run_input_json.clarification_rounds?`：该 Task 创建前已经完成的 Task Compile clarification questions / answers，按 round 顺序保留。
 - `run_input_json.recent_references?`：由 task 的 Task Compile receipt sources 恢复的本轮 human uploads；每项只含 path、最终 name 与 available/unavailable summary，必要时 Run 仍按 path 核对原文件。
 - 不传入 `context_entry_json`、task id、task summary、workflow / activity refs、Run lineage、dispatch context 或 project workspace 绝对路径。
 - 通过 `workspace_write_run` selection 可读取 Project Docs 与 Worklist，并可加载所有 enabled user skills；存在 user skills 时，app-server `skills/list` 会先收到当前项目 `<TUTTI_HOME>/projects/<project_id>/skills` extra user root。
 - Reference Files 不通过 built-in skill 暴露；若任务契约或 Project Docs 指向 `docs/reference/` 中资料，Codex 可直接读取相关 repo 文件正文。
-- 不直接读取主群聊或 Scratchpad；这些不作为 hidden scope。
+- `goal / scope` 决定本次执行边界；`source_messages` 与 compile `clarification_rounds` 只提供该边界引用的精确材料，不自动扩展任务目标。
 
 输出：根对象只包含 `result`；`result` 内四选一输出 `completed.{summary,user_note_candidate}`、`completed_no_repo_changes.{summary,user_note_candidate}`、`needs_human.{title,summary,request}` 或 `failed.summary`。`user_note_candidate` 是可选最终反馈候选，字段必填但可为 `null`；生成给用户直接查看的文件应写入 `docs/reference/tutti/`。`completed_no_repo_changes` 只用于任务契约不要求 repository file changes 的情况。`needs_human` payload 必须能直接作为 task-bound clarification request 使用：解释为什么 frozen contract 下无法安全继续，并提出一个具体、可回答、非 secret 的问题。
 
@@ -397,6 +401,7 @@ provider transient retry：如果本环节的 Codex app-server workspace-write t
 当前输入：
 
 - `run_input_json.title` / `goal` / `scope`：同初次 Task Run，是 frozen task contract 的完整 provider-facing 表达。
+- `run_input_json.source_messages?` / `clarification_rounds?`：与 initial Run 相同的 Task Compile source context。
 - `run_input_json.recent_references?`：与 initial Run 相同的 receipt-derived source set；task-bound continuation 不读取后续上传。
 - `run_input_json.continuation.previous_run`：上一 Run 的 needs-human summary 与原 clarification request payload，说明为什么暂停。
 - `run_input_json.continuation.clarification.resolved_rounds[]`：截至当前 round 的已提交 task-bound clarification rounds；每轮包含 request payload 和人类回答消息原文。
@@ -404,7 +409,7 @@ provider transient retry：如果本环节的 Codex app-server workspace-write t
 - 不传入 `context_entry_json`、task id、task summary、workflow / activity refs、Run lineage、dispatch context 或 project workspace 绝对路径。
 - 通过 `follow_up_run` selection 可读取 Project Docs 与 Worklist，并可加载所有 enabled user skills；存在 user skills 时，app-server `skills/list` 会先收到当前项目 `<TUTTI_HOME>/projects/<project_id>/skills` extra user root。
 - Reference Files 不通过 built-in skill 暴露；若任务契约、Project Docs 或 clarification answer 指向 `docs/reference/` 中资料，Codex 可直接读取相关 repo 文件正文。
-- 不直接读取主群聊或 Scratchpad；这些不作为 hidden scope。
+- compile-time source context 继续只作为 frozen contract 引用的材料；task-bound `continuation` 负责当前 Run 暂停后的补充。
 
 输出：同初次 Task Run 的 `{ result: ... }` 互斥分支 schema。continuation 不再自报 `docs` 或 `changed_paths`。
 
@@ -431,6 +436,7 @@ provider transient retry：continuation 的 retryable app-server failure 只在
 当前输入：
 
 - `run_input_json.title` / `goal` / `scope`：同一 frozen task contract。
+- `run_input_json.source_messages?` / `clarification_rounds?`：与原 attempt 相同的 Task Compile source context；pipeline self-correction 与其 provider transient retry 均保留。
 - `run_input_json.recent_references?`：与原 attempt 相同的 receipt-derived source set；pipeline self-correction 与其 provider transient retry 均保留。
 - `run_input_json.correction.summary`：上一 attempt 的 bounded failure summary。
 - `run_input_json.correction.reason_code`：Run pipeline 生成的 feedback 短码，来源包括 Artifact gate、checks 前后无 candidate diff、checks 失败或 accepted-checkpoint failure。

package/prompts/runs/README.md

@@ -8,7 +8,7 @@ These templates are used by task `Run` execution.
   Templates in this directory may describe task contracts, repo evidence, check expectations, artifact declaration rules, and documentation update responsibilities. They must never include provider credentials or host-local secret material.
 
 `task-run.md` keeps implementation judgment inside the frozen contract with Codex. Human clarification is reserved for interpreting contract intent, choosing among incompatible requirements or source facts, supplying required non-secret context, relaxing an explicit constraint, or accepting a material risk or external effect. Technical difficulty, tooling failure, and validation failure stay with the Run when they can be handled; otherwise the result is `failed`, not a question for the user. If the task contract does not require repository file changes, the output can use `completed_no_repo_changes`; otherwise a completed implementation is expected to produce a candidate diff. If the candidate is complete but Codex self-validation commands are unavailable or blocked, the task-run output should still be `completed`; Tutti checks are the authoritative validation gate.
-Initial `task-run.md`, active `task-continuation.md`, and active pipeline `task-retry.md` receive the compact task contract fields `title / goal / scope` plus optional receipt-derived `recent_references`; each reference includes only path, final name and available/unavailable summary. Continuation adds the required `continuation` block, and pipeline self-correction retry adds the required `correction` block with the previous failure summary, machine-generated reason code, correction guidance, a required redacted / bounded diagnostic, and `promotion_failure` as either a complete object or explicit `null`. Provider transient retry and self-correction both preserve the same reference context. Provider-facing prompts do not receive task ids, task summaries, Run lineage, workflow anchors, blob ids, message ids, changed paths, docs status, checks status, or the safety audit context entry.
+Initial `task-run.md`, active `task-continuation.md`, and active pipeline `task-retry.md` receive the compact task contract fields `title / goal / scope` plus optional receipt-derived `source_messages`, completed Task Compile `clarification_rounds`, and `recent_references`. Source messages and clarification answers preserve the exact submitted material in ordered `role / optional author_display_name / text` entries; each reference includes only path, final name and available/unavailable summary. The contract defines execution scope, while these fields supply exact content referenced by it. Continuation adds the required task-bound `continuation` block, and pipeline self-correction retry adds the required `correction` block with the previous failure summary, machine-generated reason code, correction guidance, a required redacted / bounded diagnostic, and `promotion_failure` as either a complete object or explicit `null`. Provider transient retry and self-correction both preserve all compile-time source context. Provider-facing prompts do not receive task ids, task summaries, Run lineage, workflow anchors, blob ids, message ids, changed paths, docs status, checks status, or the safety audit context entry.
 All three Run templates use a slim mutually exclusive structured output schema under `result`: exactly one of `completed.{summary,user_note_candidate}`, `completed_no_repo_changes.{summary,user_note_candidate}`, `needs_human.{title,summary,request}`, or `failed.summary`. The `summary` is a concise, human-readable result note for project members who may not inspect the code. Completed branches also require `user_note_candidate`, which is either a short user-facing final-card sentence or `null`; it must not repeat `summary` or include file paths. Checks, docs, promotion, changed paths, and other Tutti status stay in structured fields derived by the Run pipeline. They do not ask Codex to self-report docs status or changed paths; both come from Run pipeline Git diff and derived projection.
 Run templates describe `docs/reference/` as a user-visible file exchange area. Human uploads remain under `docs/reference/files/` and `docs/reference/images/`; `docs/reference/tutti/**` is for Tutti-generated files intended for direct member review in References, not temporary output, internal notes, logs, or canonical project documentation. Generated user-visible files must be written under `docs/reference/tutti/`, with `docs/reference/tutti/<meaningful-folder>/...` used when the folder name should be shown as a References UI group. Generated files under `docs/reference/tutti/` are discovered from promoted changed paths, rendered by References automatically, and may be listed in completed task result cards.
 Initial `task-run.md`, active `task-continuation.md`, and active pipeline `task-retry.md` also instruct Codex to write or update the single active `tutti.artifact.json` manifest only when the task creates or updates a member-viewable visual artifact. Each template includes the complete strict static and server JSON shapes: every behavior field is required, `network` is always an explicit boolean, and server `script / ready_path / port` fields are forbidden. A server package instead declares the fixed `artifact:preview` npm script in its own `package.json` and listens on the injected `HOST / PORT`. The manifest remains repo truth and is not reported through the structured output schema.

package/prompts/runs/task-continuation.md

@@ -23,6 +23,8 @@ Fields:
 - `title`: short task title for orientation.
 - `goal`: formal task outcome to implement.
 - `scope`: formal task boundary. Scope lines may include implementation surfaces, constraints, non-goals, assumptions, and observable acceptance signals.
+- `source_messages`, when present: the frozen submission discussion associated with this task.
+- `clarification_rounds`, when present: questions and answers completed before the task contract was created.
 - `recent_references`, when present: human-uploaded files from the Task Compile source cycle, with a terminal summary status for each source.
 - `continuation`: previous Run pause reason, submitted clarification answers, and the `follow_up_check.resume` summary.
 
@@ -39,10 +41,10 @@ Human clarification answers may clarify or confirm work inside the frozen task c
 
 # Execution Boundary
 
-- Treat `goal` and `scope` as the full executable contract.
+- `goal` and `scope` define the execution boundary.
 - Use `title` only for orientation; it does not expand the contract.
 - Use clarification answers only within the frozen contract.
-- Do not use main chat or Scratchpad as hidden scope.
+- `source_messages` and `clarification_rounds`, when present, provide the submitted material referenced by that boundary. Use them for exact content without treating them as additional objectives.
 - Work only inside the provided project workspace.
 - This workspace is the persistent development state. It may retain unaccepted source changes and project-local dependency or runtime state from the paused or failed work; inspect and continue from that state within the frozen task contract.
 - Do not reset, checkout, stash, clean, or otherwise discard existing workspace state. Do not remove changes merely because they were created before this continuation.

package/prompts/runs/task-retry.md

@@ -23,6 +23,8 @@ Fields:
 - `title`: short task title for orientation.
 - `goal`: formal task outcome to implement.
 - `scope`: formal task boundary. Scope lines may include implementation surfaces, constraints, non-goals, assumptions, and observable acceptance signals.
+- `source_messages`, when present: the frozen submission discussion associated with this task.
+- `clarification_rounds`, when present: questions and answers completed before the task contract was created.
 - `recent_references`, when present: human-uploaded files from the Task Compile source cycle, with a terminal summary status for each source.
 - `correction`: bounded pipeline feedback from the previous attempt and the immediate retry guidance.
 
@@ -47,11 +49,11 @@ Correct the existing candidate in place, using `correction.summary`, `correction
 
 # Execution Boundary
 
-- Treat `goal` and `scope` as the full executable contract.
+- `goal` and `scope` define the execution boundary.
 - Use `title` only for orientation; it does not expand the contract.
 - Use `correction` only to fix the pipeline feedback; it does not change the frozen contract.
 - Do not repeat the previous candidate blindly.
-- Do not use main chat or Scratchpad as hidden scope.
+- `source_messages` and `clarification_rounds`, when present, provide the submitted material referenced by that boundary. Use them for exact content without treating them as additional objectives.
 - Work only inside the provided project workspace.
 - Do not reset, checkout, stash, clean, or otherwise discard the previous attempt's source, dependency, or runtime state. Remove or replace existing changes only when that is directly required to correct the candidate within the frozen task contract.
 - Before returning, inspect the final Git status. Maintain the repository's own `.gitignore` for project-local state that should not be versioned, following existing project conventions; keep files Git-visible when they are intentional versioned source. Do not assume fixed runtime path names.

package/prompts/runs/task-run.md

@@ -23,13 +23,15 @@ Fields:
 - `title`: short task title for orientation.
 - `goal`: formal task outcome to implement.
 - `scope`: formal task boundary. Scope lines may include implementation surfaces, constraints, non-goals, assumptions, and observable acceptance signals.
+- `source_messages`, when present: the frozen submission discussion associated with this task.
+- `clarification_rounds`, when present: questions and answers completed before the task contract was created.
 - `recent_references`, when present: human-uploaded files from the Task Compile source cycle, with a terminal summary status for each source.
 
 # Execution Boundary
 
-- Treat `goal` and `scope` as the full executable contract.
+- `goal` and `scope` define the execution boundary.
 - Use `title` only for orientation; it does not expand the contract.
-- Do not use main chat or Scratchpad as hidden scope.
+- `source_messages` and `clarification_rounds`, when present, provide the submitted material referenced by that boundary. Use them for exact content without treating them as additional objectives.
 - Work only inside the provided project workspace.
 - This workspace is the persistent development state. It may already contain unaccepted source changes or project-local dependency and runtime state left by an earlier failed Run; inspect and continue from that state when it is relevant to the frozen task contract.
 - Do not reset, checkout, stash, clean, or otherwise discard existing workspace state. Do not remove changes merely because they predate this Run or are not part of the immediate fix.