@danypops/papyrus 0.47.0 → 0.47.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@danypops/papyrus",
-  "version": "0.47.0",
+  "version": "0.47.1",
   "description": "Daemon-backed graph artifacts, evidence-bearing tasks, rules, skills, and native TUI workflows for Pi",
   "type": "module",
   "keywords": ["pi-package"],

package/src/handlers/shared.ts

@@ -29,6 +29,8 @@ interface OperationSchemaNode {
 	readonly properties?: Readonly<Record<string, OperationSchemaNode>>;
 	readonly required?: readonly string[];
 	readonly additionalProperties?: boolean | OperationSchemaNode;
+	/** A key not in `properties` is validated against the first pattern here whose RegExp matches it, instead of falling through to `additionalProperties` -- e.g. a free-form string-keyed map (tasks.create's checklist) uses `{"^.*$": entrySchema}` so a client-side JSON-Schema validator that reports `additionalProperties`-as-schema violations only as a generic top-level "must not have additional properties" (TypeBox's own real, confirmed behavior -- see vehicle-shell.ts's formatSchemaChildren for the matching tools_man rendering) instead descends into the real nested violation, matching an array's `items` precision. */
+	readonly patternProperties?: Readonly<Record<string, OperationSchemaNode>>;
 	readonly items?: OperationSchemaNode;
 	readonly minLength?: number;
 	readonly maxLength?: number;
@@ -80,6 +82,12 @@ function validateSchemaValue(value: unknown, schema: OperationSchemaNode, path:
 		}
 		for (const key of Object.keys(record)) {
 			if (key in (schema.properties ?? {})) continue;
+			const patternMatch = Object.entries(schema.patternProperties ?? {}).find(([pattern]) => new RegExp(pattern).test(key));
+			if (patternMatch) {
+				const issues = validateSchemaValue(record[key], patternMatch[1], [...path, key]);
+				if (issues.length > 0) return issues;
+				continue;
+			}
 			if (schema.additionalProperties === false) return schemaIssue([...path, key], `${key} is not allowed`);
 			if (typeof schema.additionalProperties === "object") {
 				const issues = validateSchemaValue(record[key], schema.additionalProperties, [...path, key]);

package/src/handlers/tasks.ts

@@ -114,31 +114,47 @@ const gateProp = {
 	],
 } as const;
 
+/**
+ * `patternProperties: {"^.*$": entrySchema}` rather than `additionalProperties: entrySchema`,
+ * despite both meaning "every key maps to entrySchema" for a free-form string-keyed map:
+ * confirmed live (2026-08-09) that TypeBox's own Value.Errors -- the schema validator Pi's tool-
+ * calling harness runs client-side, before a call ever reaches this daemon -- reports an
+ * additionalProperties-as-schema violation only as a generic top-level "must not have additional
+ * properties", with zero descent into which nested field actually broke, while the structurally
+ * identical items-as-schema case (gates, proof arrays below) descends and reports the exact
+ * broken field. patternProperties does not have that limitation and gives the same precision as
+ * items. See handlers/shared.ts's OperationSchemaNode.patternProperties for the matching
+ * server-side runtime check, and vehicle-shell.ts's formatSchemaChildren for the matching
+ * tools_man rendering.
+ */
 const checklistProp = {
 	type: "object",
 	description: "Map from completion criterion text to one or more typed proof references. An empty map clears the checklist.",
-	additionalProperties: {
-		type: "object",
-		properties: {
-			proof: {
-				type: "array",
-				minItems: 1,
-				items: {
-					type: "object",
-					description: "Accepted proof shape: {type, target, expect?}.",
-					properties: {
-						type: { type: "string", enum: PROOF_TYPES },
-						target: { type: "string", minLength: 1 },
-						expect: { type: "string" },
+	patternProperties: {
+		"^.*$": {
+			type: "object",
+			properties: {
+				proof: {
+					type: "array",
+					minItems: 1,
+					items: {
+						type: "object",
+						description: "Accepted proof shape: {type, target, expect?}.",
+						properties: {
+							type: { type: "string", enum: PROOF_TYPES },
+							target: { type: "string", minLength: 1 },
+							expect: { type: "string" },
+						},
+						required: ["type", "target"],
+						additionalProperties: false,
 					},
-					required: ["type", "target"],
-					additionalProperties: false,
 				},
 			},
+			required: ["proof"],
+			additionalProperties: false,
 		},
-		required: ["proof"],
-		additionalProperties: false,
 	},
+	additionalProperties: false,
 	examples: [
 		{
 			"tests pass": { proof: [{ type: "test", target: "bun test", expect: "0 failures" }] },