@onetaskgraph/sdk 0.14.4 → 0.14.5

package/dist/generated/models.d.ts

@@ -1,4 +1,4 @@
-export declare const SCHEMA_BUNDLE_VERSION: 56;
+export declare const SCHEMA_BUNDLE_VERSION: 57;
 export declare namespace GeneratedAsset {
     /**
      * One asset a record holds, as a read reports it.
@@ -16178,6 +16178,13 @@ export declare namespace GeneratedWritePolicyConfig {
      * asks for. `replacements` is the caller's replacement layer, sent with every sanitisation
      * and above every declaration level the policy reads, a later entry winning; it is refused
      * at load without a `sanitize_command`, because nothing would apply it.
+     *
+     * `sanitize_stored_on_write` opts a store into the read-first guard: a narrow write to a task
+     * is screened with the task and every comment on it as stored, and what that rewrites is
+     * written back first. Off, a narrow write screens only what it writes and a stored term is left
+     * for `sources sanitize`. It is refused at load without a `sanitize_command` for the same
+     * reason as `replacements`; a linking caller's own policy opts in through
+     * `Engine::with_sanitize_stored_on_write`.
      */
     interface WritePolicyConfig {
         /**
@@ -16200,6 +16207,10 @@ export declare namespace GeneratedWritePolicyConfig {
          * The caller's replacement layer: `{term, with}` or `{term, reject: true}`, in order.
          */
         replacements?: Replacement[];
+        /**
+         * Whether a narrow write to a task first rewrites the terms already stored on it.
+         */
+        sanitize_stored_on_write?: boolean;
     }
 }
 export type WritePolicyConfig = GeneratedWritePolicyConfig.WritePolicyConfig;

package/dist/generated/schemas.d.ts

@@ -23081,7 +23081,7 @@ export declare const runtimeSchemas: {
     readonly WritePolicyConfig: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly title: "WritePolicyConfig";
-        readonly description: "The commands a store asks about the public boundary: `write_policy` at the document's\nroot.\n\nBoth are generic command lines rather than a named tool, so the policy behind them stays\nthe caller's. `visibility_command` is handed `{\"repository\": \"<host/owner/name>\"}` on its\nstandard input and answers `{\"visibility\": \"public\" | \"private\" | \"unknown\"}`;\n`check_command` is handed a whole [`PublicWriteInput`](crate::boundary::PublicWriteInput)\nand passes a write only by exiting 0 with `{\"verdict\": \"pass\"}`. Either may be left out:\nwithout a visibility command every repository is `unknown`, which is private, and without\na check command no write to a public destination passes.\n\n`sanitize_command` is handed a whole\n[`PublicSanitizeInput`](crate::boundary::PublicSanitizeInput) and answers the write's\nrewritable entries with every declared replacement applied, and its verdict; with it, every\nscreened write is put to it **in place of** `check_command`, and what it answers is what is\nwritten. `terms_command` answers a scope's resolved terms, which only `sources sanitize`\nasks for. `replacements` is the caller's replacement layer, sent with every sanitisation\nand above every declaration level the policy reads, a later entry winning; it is refused\nat load without a `sanitize_command`, because nothing would apply it.";
+        readonly description: "The commands a store asks about the public boundary: `write_policy` at the document's\nroot.\n\nBoth are generic command lines rather than a named tool, so the policy behind them stays\nthe caller's. `visibility_command` is handed `{\"repository\": \"<host/owner/name>\"}` on its\nstandard input and answers `{\"visibility\": \"public\" | \"private\" | \"unknown\"}`;\n`check_command` is handed a whole [`PublicWriteInput`](crate::boundary::PublicWriteInput)\nand passes a write only by exiting 0 with `{\"verdict\": \"pass\"}`. Either may be left out:\nwithout a visibility command every repository is `unknown`, which is private, and without\na check command no write to a public destination passes.\n\n`sanitize_command` is handed a whole\n[`PublicSanitizeInput`](crate::boundary::PublicSanitizeInput) and answers the write's\nrewritable entries with every declared replacement applied, and its verdict; with it, every\nscreened write is put to it **in place of** `check_command`, and what it answers is what is\nwritten. `terms_command` answers a scope's resolved terms, which only `sources sanitize`\nasks for. `replacements` is the caller's replacement layer, sent with every sanitisation\nand above every declaration level the policy reads, a later entry winning; it is refused\nat load without a `sanitize_command`, because nothing would apply it.\n\n`sanitize_stored_on_write` opts a store into the read-first guard: a narrow write to a task\nis screened with the task and every comment on it as stored, and what that rewrites is\nwritten back first. Off, a narrow write screens only what it writes and a stored term is left\nfor `sources sanitize`. It is refused at load without a `sanitize_command` for the same\nreason as `replacements`; a linking caller's own policy opts in through\n`Engine::with_sanitize_stored_on_write`.";
         readonly type: "object";
         readonly properties: {
             readonly visibility_command: {
@@ -23124,6 +23124,11 @@ export declare const runtimeSchemas: {
                 };
                 readonly default: readonly [];
             };
+            readonly sanitize_stored_on_write: {
+                readonly description: "Whether a narrow write to a task first rewrites the terms already stored on it.";
+                readonly type: "boolean";
+                readonly default: false;
+            };
         };
         readonly additionalProperties: false;
         readonly $defs: {

package/dist/index.d.ts

@@ -6,6 +6,6 @@
  * implementation of the query semantics across the CLI and both SDKs.
  */
 /** The version this package publishes. `package.json` must agree; see the tests. */
-export declare const VERSION = "0.14.4";
+export declare const VERSION = "0.14.5";
 export * from "./client.ts";
 export type * from "./generated/models.ts";

package/dist/index.js

@@ -7194,7 +7194,7 @@ var binaryCommands = [
 ];
 
 // src/generated/models.ts
-var SCHEMA_BUNDLE_VERSION = 56;
+var SCHEMA_BUNDLE_VERSION = 57;
 
 // src/generated/schemas.ts
 var runtimeSchemas = {
@@ -38928,7 +38928,7 @@ no insignificant whitespace, UTF-8.`,
   WritePolicyConfig: {
     $schema: "https://json-schema.org/draft/2020-12/schema",
     title: "WritePolicyConfig",
-    description: 'The commands a store asks about the public boundary: `write_policy` at the document\'s\nroot.\n\nBoth are generic command lines rather than a named tool, so the policy behind them stays\nthe caller\'s. `visibility_command` is handed `{"repository": "<host/owner/name>"}` on its\nstandard input and answers `{"visibility": "public" | "private" | "unknown"}`;\n`check_command` is handed a whole [`PublicWriteInput`](crate::boundary::PublicWriteInput)\nand passes a write only by exiting 0 with `{"verdict": "pass"}`. Either may be left out:\nwithout a visibility command every repository is `unknown`, which is private, and without\na check command no write to a public destination passes.\n\n`sanitize_command` is handed a whole\n[`PublicSanitizeInput`](crate::boundary::PublicSanitizeInput) and answers the write\'s\nrewritable entries with every declared replacement applied, and its verdict; with it, every\nscreened write is put to it **in place of** `check_command`, and what it answers is what is\nwritten. `terms_command` answers a scope\'s resolved terms, which only `sources sanitize`\nasks for. `replacements` is the caller\'s replacement layer, sent with every sanitisation\nand above every declaration level the policy reads, a later entry winning; it is refused\nat load without a `sanitize_command`, because nothing would apply it.',
+    description: 'The commands a store asks about the public boundary: `write_policy` at the document\'s\nroot.\n\nBoth are generic command lines rather than a named tool, so the policy behind them stays\nthe caller\'s. `visibility_command` is handed `{"repository": "<host/owner/name>"}` on its\nstandard input and answers `{"visibility": "public" | "private" | "unknown"}`;\n`check_command` is handed a whole [`PublicWriteInput`](crate::boundary::PublicWriteInput)\nand passes a write only by exiting 0 with `{"verdict": "pass"}`. Either may be left out:\nwithout a visibility command every repository is `unknown`, which is private, and without\na check command no write to a public destination passes.\n\n`sanitize_command` is handed a whole\n[`PublicSanitizeInput`](crate::boundary::PublicSanitizeInput) and answers the write\'s\nrewritable entries with every declared replacement applied, and its verdict; with it, every\nscreened write is put to it **in place of** `check_command`, and what it answers is what is\nwritten. `terms_command` answers a scope\'s resolved terms, which only `sources sanitize`\nasks for. `replacements` is the caller\'s replacement layer, sent with every sanitisation\nand above every declaration level the policy reads, a later entry winning; it is refused\nat load without a `sanitize_command`, because nothing would apply it.\n\n`sanitize_stored_on_write` opts a store into the read-first guard: a narrow write to a task\nis screened with the task and every comment on it as stored, and what that rewrites is\nwritten back first. Off, a narrow write screens only what it writes and a stored term is left\nfor `sources sanitize`. It is refused at load without a `sanitize_command` for the same\nreason as `replacements`; a linking caller\'s own policy opts in through\n`Engine::with_sanitize_stored_on_write`.',
     type: "object",
     properties: {
       visibility_command: {
@@ -38982,6 +38982,11 @@ no insignificant whitespace, UTF-8.`,
           $ref: "#/$defs/Replacement"
         },
         default: []
+      },
+      sanitize_stored_on_write: {
+        description: "Whether a narrow write to a task first rewrites the terms already stored on it.",
+        type: "boolean",
+        default: false
       }
     },
     additionalProperties: false,
@@ -40707,7 +40712,7 @@ function assertCompleteCommandSurface() {
 }
 
 // src/index.ts
-var VERSION = "0.14.4";
+var VERSION = "0.14.5";
 export {
   taskUpdateOptionFlags,
   taskUpdateFlags,

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@onetaskgraph/sdk",
   "//": "llmlint: ignore-file[projects_stay_in_one_js_workspace] This package IS the JS workspace's one member; what the rule reads as a second is the optionalDependency below, which is the published launcher an end user installs beside the SDK and resolves from the registry at their own install. `workspace:*` names nothing there, and npm/cli is not a workspace member for the reason its own manifest records. scripts/set-version.sh writes this number and `--check` refuses any other, under distribution-check. JSON has no comment to scope this to the one line.",
-  "version": "0.14.4",
+  "version": "0.14.5",
   "description": "The TypeScript SDK for onetaskgraph, generated from the binary's own JSON Schema bundle.",
   "license": "MIT",
   "type": "module",
@@ -28,7 +28,7 @@
     "generate:check": "bun scripts/generate.ts --check"
   },
   "optionalDependencies": {
-    "@onetaskgraph/cli": "0.14.4"
+    "@onetaskgraph/cli": "0.14.5"
   },
   "devDependencies": {
     "ajv": "8.17.1",