@themoltnet/pi-extension 0.9.0 → 0.10.0

package/dist/index.d.ts

@@ -94,7 +94,14 @@ export declare interface ExecutePiTaskOptions {
     extraAllowedHosts?: string[];
     /** Sandbox overrides (env, VFS shadows, resources). */
     sandboxConfig?: SandboxConfig;
-    /** Forwarded to `buildPromptForTask` for per-type builders. */
+    /**
+     * Forwarded to `buildPromptForTask` for per-type builders. Static
+     * across tasks. Today no built-in builder needs per-task `extras` —
+     * judges fetch their own dependent data via MoltNet tools
+     * (`moltnet_get_task`, `moltnet_list_task_attempts`, etc.) at run
+     * time, which keeps this layer task-type-agnostic. Field is kept
+     * for forward compat with custom prompt builders that might want it.
+     */
     promptExtras?: Record<string, unknown>;
     /** Snapshot progress callback; defaults to stderr logging. */
     onSnapshotProgress?: (message: string) => void;
@@ -133,6 +140,26 @@ declare type MoltNetAgent = Awaited<ReturnType<typeof connect>>;
 declare function moltnetExtension(pi: ExtensionAPI): void;
 export default moltnetExtension;
 
+/**
+ * Active-task context. When present, `moltnet_create_entry` is forced to
+ * land entries in `diaryId` (the task diary), regardless of the env-derived
+ * diary, and auto-injects provenance tags (`task:<id>`, `task_type:<type>`,
+ * `task_attempt:<n>`, and `correlation:<id>` when the task carries one).
+ * See issue #979.
+ */
+declare interface MoltNetTaskContext {
+    taskId: string;
+    taskType: string;
+    attemptN: number;
+    diaryId: string;
+    /**
+     * Optional correlation id. When set, propagated as a `correlation:<id>`
+     * provenance tag so all entries from a multi-task workflow can be
+     * grouped without enumerating individual task ids.
+     */
+    correlationId: string | null;
+}
+
 declare interface MoltNetToolsConfig {
     getAgent(): MoltNetAgent | null;
     getDiaryId(): string | null;
@@ -148,6 +175,13 @@ declare interface MoltNetToolsConfig {
      * Defaults to HOST_EXEC_DEFAULT_BASE_ENV when omitted.
      */
     hostExecBaseEnv?: ReadonlySet<string>;
+    /**
+     * Active-task context, populated by the agent-daemon path. When set,
+     * `moltnet_create_entry` enforces `diaryId === taskContext.diaryId` and
+     * injects provenance tags. When absent (interactive pi-extension / TUI),
+     * entry creation behaves as before (env-derived diary, no auto-tags).
+     */
+    getTaskContext?(): MoltNetTaskContext | null;
 }
 
 declare interface PiJudgeRecipeCid {