@danypops/papyrus 0.58.1 → 0.58.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@danypops/papyrus",
-  "version": "0.58.1",
+  "version": "0.58.2",
   "description": "Daemon-backed graph artifacts, evidence-bearing tasks, rules, skills, and native TUI workflows for Pi",
   "type": "module",
   "main": "./src/index.ts",

package/src/handlers/artifact-helpers.ts

@@ -1,9 +1,4 @@
-/**
- * Cross-domain artifact name/id resolution and workflow-run narrative building, split out of
- * handlers/shared.ts as part of a SOLID-audit-driven decomposition (see Doc "Modularity playbook:
- * building-block-shaped TypeScript modules for papyrus/pi-papyrus" and the "handlers/shared.ts
- * split" child of "Epic: Modularize papyrus/pi-papyrus god-files into building-block modules").
- */
+/** Cross-domain artifact name/id resolution and workflow-run narrative building. */
 import { type VehicleContentBlock, VehicleError } from "@danypops/vehicle-core";
 import type { Artifact } from "../artifact/artifact.ts";
 import type { ArtifactStore } from "../artifact/artifact-store.ts";

package/src/handlers/operation-schema.ts

@@ -1,10 +1,7 @@
 /**
- * Generic, domain-agnostic operation-input schema DSL, split out of handlers/shared.ts as part of
- * a SOLID-audit-driven decomposition (see Doc "Modularity playbook: building-block-shaped
- * TypeScript modules for papyrus/pi-papyrus" and the "handlers/shared.ts split" child of "Epic:
- * Modularize papyrus/pi-papyrus god-files into building-block modules"). Nothing here references
- * a specific Papyrus domain (tasks/docs/rules/...) -- a real candidate to eventually become its
- * own building block other Vehicle-backed daemons could reuse directly.
+ * Generic, domain-agnostic operation-input schema DSL. Nothing here references a specific
+ * Papyrus domain (tasks/docs/rules/...) -- a real candidate to eventually become its own building
+ * block other Vehicle-backed daemons could reuse directly.
  */
 import {
 	defineVehicleSchema,

package/src/handlers/paired-mutation.ts

@@ -1,10 +1,4 @@
-/**
- * Vehicle-operation-definer DSL (createOperationDefiner) and the paired add/remove mutation shape
- * built on top of it (definePairedMutation), split out of handlers/shared.ts as part of a
- * SOLID-audit-driven decomposition (see Doc "Modularity playbook: building-block-shaped
- * TypeScript modules for papyrus/pi-papyrus" and the "handlers/shared.ts split" child of "Epic:
- * Modularize papyrus/pi-papyrus god-files into building-block modules").
- */
+/** Vehicle-operation-definer DSL (createOperationDefiner) and the paired add/remove mutation shape built on top of it (definePairedMutation). */
 import { bindVehicleOperation, defineVehicleOperation, type VehicleLimits, type VehicleOperationContext } from "@danypops/vehicle-core";
 import type { VehicleRegistry } from "@danypops/vehicle-server";
 import { looseObjectSchema, passthroughOutput } from "./operation-schema.ts";

package/src/handlers/shared.ts

@@ -1,20 +1,11 @@
 /**
  * Barrel re-exporting the shared schema helpers and name->id resolution used by every per-domain
- * VehicleRegistry projection (notes-vehicle.ts, rules-vehicle.ts, docs-vehicle.ts,
- * artifact-trash-vehicle.ts, ...). Kept as a real file (not a `shared/index.ts` subdirectory) so
- * every existing `from "./shared.ts"` import across the 8 handler files that depend on it keeps
- * resolving unchanged -- this codebase's imports always carry an explicit `.ts` extension, which
- * does not implicitly resolve a bare specifier to a directory's own index file the way Node's
- * CJS `require()` does.
- *
- * The real implementation now lives in four focused sibling modules instead of one 435-line file
- * mixing four unrelated concerns -- see Doc "Modularity playbook: building-block-shaped
- * TypeScript modules for papyrus/pi-papyrus" and the "handlers/shared.ts split" child of "Epic:
- * Modularize papyrus/pi-papyrus god-files into building-block modules":
- *   - operation-schema.ts: generic, domain-agnostic operation-input schema DSL
- *   - paired-mutation.ts: the Vehicle-operation-definer DSL and the paired add/remove shape built on it
- *   - task-classifiers.ts: business-rule error classifiers specific to this package's own domain errors
- *   - artifact-helpers.ts: cross-domain artifact name/id resolution and workflow-run narrative building
+ * VehicleRegistry projection. Kept as a real file (not a `shared/index.ts` subdirectory) so every
+ * existing `from "./shared.ts"` import keeps resolving unchanged -- this codebase's imports
+ * always carry an explicit `.ts` extension, which does not implicitly resolve a bare specifier to
+ * a directory's own index file the way Node's CJS `require()` does. Real implementation lives in
+ * operation-schema.ts (schema DSL), paired-mutation.ts (operation-definer DSL), task-classifiers.ts
+ * (domain error classifiers), artifact-helpers.ts (name/id resolution, workflow-run narrative).
  */
 export {
 	buildWorkflowRunContent,