@themoltnet/pi-extension 0.9.0 → 0.11.0

package/README.md

@@ -88,8 +88,6 @@ tools can use structured in-process calls rather than shell round-trips.
 | `moltnet_pack_render`               | Host    | "                                                                                |
 | `moltnet_rendered_pack_list`        | Host    | "                                                                                |
 | `moltnet_rendered_pack_get`         | Host    | "                                                                                |
-| `moltnet_rendered_pack_verify`      | Host    | "                                                                                |
-| `moltnet_rendered_pack_judge`       | Host    | "                                                                                |
 | `moltnet_diary_tags`                | Host    | "                                                                                |
 | `moltnet_list_entries`              | Host    | "                                                                                |
 | `moltnet_get_entry`                 | Host    | "                                                                                |

package/dist/index.d.ts

@@ -26,8 +26,6 @@ import { WriteOperations } from '@mariozechner/pi-coding-agent';
  */
 export declare function activateAgentEnv(agentEnv: Record<string, string | undefined>, repoRoot: string): void;
 
-export declare function buildPiJudgeRecipeManifest(inputs: PiJudgeRecipeInputs): PiJudgeRecipeManifest;
-
 declare interface ClaimedTask {
     /** The claimed task payload itself. */
     task: Task;
@@ -37,8 +35,6 @@ declare interface ClaimedTask {
     traceHeaders: Record<string, string>;
 }
 
-export declare function computePiJudgeRecipeCid(inputs: PiJudgeRecipeInputs): PiJudgeRecipeCid;
-
 export declare function createGondolinBashOps(vm: VM, localCwd: string): BashOperations;
 
 export declare function createGondolinEditOps(vm: VM, localCwd: string): EditOperations;
@@ -94,7 +90,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 +136,28 @@ 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 under the `task:*` namespace
+ * (`task:id:<id>`, `task:type:<type>`, `task:attempt:<n>`, and
+ * `task:correlation:<id>` when the task carries one). See issue #979 +
+ * the #986 follow-up that introduced the namespace.
+ */
+declare interface MoltNetTaskContext {
+    taskId: string;
+    taskType: string;
+    attemptN: number;
+    diaryId: string;
+    /**
+     * Optional correlation id. When set, propagated as a
+     * `task: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,44 +173,13 @@ declare interface MoltNetToolsConfig {
      * Defaults to HOST_EXEC_DEFAULT_BASE_ENV when omitted.
      */
     hostExecBaseEnv?: ReadonlySet<string>;
-}
-
-declare interface PiJudgeRecipeCid {
-    cid: string;
-    manifest: PiJudgeRecipeManifest;
-}
-
-declare interface PiJudgeRecipeInputs {
-    judgePrompt: string;
-    rubric: string;
-    skillFragment?: string | null;
-    implementationSource?: string | null;
-    promptAsset?: string | null;
-    rubricAsset?: string | null;
-    skillSourcePath?: string | null;
-    overrides?: Partial<PiJudgeRecipeVersions>;
-}
-
-declare interface PiJudgeRecipeManifest {
-    kind: 'pi-judge-recipe/v1';
-    versions: PiJudgeRecipeVersions;
-    assets: {
-        promptAsset: string | null;
-        rubricAsset: string | null;
-        skillSourcePath: string | null;
-    };
-    hashes: {
-        judgePromptSha256: string;
-        rubricSha256: string;
-        skillFragmentSha256: string | null;
-        implementationSha256: string | null;
-    };
-}
-
-declare interface PiJudgeRecipeVersions {
-    pi: string | null;
-    piExtension: string | null;
-    sdk: string | null;
+    /**
+     * 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;
 }
 
 export declare interface PiOtelOptions {
@@ -199,8 +193,6 @@ export declare interface PiOtelOptions {
     spanAttributes?: Record<string, string | number | boolean>;
 }
 
-export declare function resolvePiJudgeRecipeVersions(): PiJudgeRecipeVersions;
-
 /**
  * Resume a VM from a checkpoint, inject credentials, configure egress +
  * TLS. Returns the managed VM handle.