@danypops/pi-papyrus 0.55.1 → 0.55.3

package/extension/src/service-client.ts

@@ -17,7 +17,13 @@ import {
 type ClientConnector = () => Promise<PapyrusClient>;
 
 let connector: ClientConnector = () => connectPapyrusClient();
-const client: RetryingClient<PapyrusClient> = createRetryingClient<PapyrusClient>(() => connector(), { label: "Papyrus" });
+// connectRetry:true (vehicle-client's own bounded background retry budget) covers a
+// daemon that crashed and is mid systemd-restart -- without it, the very first call
+// during that window fails immediately instead of waiting the ~2s restart out.
+const client: RetryingClient<PapyrusClient> = createRetryingClient<PapyrusClient>(() => connector(), {
+	label: "Papyrus",
+	connectRetry: true,
+});
 
 export async function papyrusClient(): Promise<PapyrusClient> {
 	return client.call(async (resolved) => resolved);

package/extension/src/tool-rendering/render-model/index.ts

@@ -1,13 +1,8 @@
 /**
  * render-model/ -- typed, bounded Vehicle-result render details, one file per result-kind
- * (already Strategy-shaped in spirit: one create-and-is-guard pair per kind), split out of the former
- * single 827-line render-model.ts as part of a SOLID-audit-driven decomposition (see Doc
- * "Modularity playbook: building-block-shaped TypeScript modules for papyrus/pi-papyrus" and the
- * "pi-papyrus render-model.ts split" child of "Epic: Modularize papyrus/pi-papyrus god-files into
- * building-block modules"). This file is the one place that assembles every kind into the
- * PapyrusToolDetails union and validates a persisted one back (parsePapyrusToolDetails) -- the
- * "wide internal, narrow public" shape: each sibling module owns one kind's own real complexity,
- * this one only ever needs to know each kind's own type + guard, never re-derive it.
+ * (Strategy-shaped: one create-and-is-guard pair per kind). This file assembles every kind into
+ * the PapyrusToolDetails union and validates a persisted one back (parsePapyrusToolDetails) --
+ * each sibling module owns one kind's own complexity, this one only needs its type + guard.
  */
 import {
 	TOOL_DETAILS_BODY_MAX_CHARACTERS,

package/extension/src/tool-rendering/render-model/shared.ts

@@ -1,10 +1,7 @@
 /**
  * Base kernel shared by every render-model/*.ts result-kind module: the schema-version marker,
  * the common completeness/bounding primitives, and the base validators nearly every kind's own
- * parse case reuses. Split out of the former single render-model.ts as part of a SOLID-audit-
- * driven decomposition (see Doc "Modularity playbook: building-block-shaped TypeScript modules
- * for papyrus/pi-papyrus" and the "pi-papyrus render-model.ts split" child of "Epic: Modularize
- * papyrus/pi-papyrus god-files into building-block modules").
+ * parse case reuses.
  */
 import {
 	type Artifact,

package/extension/src/tool-rendering/render-model.ts

@@ -1,17 +1,8 @@
 /**
  * Barrel re-exporting the typed, bounded Vehicle-result render details, one file per result-kind,
  * from ./render-model/. Kept as a real file (not relying on directory-index resolution) so every
- * existing `from "./render-model.ts"` / `from "../tool-rendering/render-model.ts"` import across
- * this package's 5 real consumers (tool-rendering/index.ts, tool-rendering/artifact-card.ts,
- * tool-rendering/artifact-list.ts, tools/vehicle-artifact-renderers.ts, index.ts) 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 ./render-model/ (one file per result-kind, already
- * Strategy-shaped in spirit) instead of one 827-line file -- see Doc "Modularity playbook:
- * building-block-shaped TypeScript modules for papyrus/pi-papyrus" and the "pi-papyrus
- * render-model.ts split" child of "Epic: Modularize papyrus/pi-papyrus god-files into
- * building-block modules".
+ * existing `from "./render-model.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.
  */
 export * from "./render-model/index.ts";

package/extension/src/tools/renderers/index.ts

@@ -11,14 +11,9 @@
  * Falls back to the generic Vehicle renderer for any other output shape
  * (progress, transitions, gate runs, errors).
  *
- * This file is the one place that assembles every result-kind's own detector/renderer into the
- * two exported Registry entry points (papyrusVehicleRenderers/papyrusVehiclePresentations) -- the
- * "wide internal, narrow public" shape: each sibling module in this directory owns one kind's own
- * real complexity, this one only ever needs to know each kind's own type + guard + renderer, never
- * re-derive it. Split out of the former single 670-line vehicle-artifact-renderers.ts as part of a
- * SOLID-audit-driven decomposition (see Doc "Modularity playbook: building-block-shaped
- * TypeScript modules for papyrus/pi-papyrus" and the "pi-papyrus vehicle-artifact-renderers.ts
- * split" child of "Epic: Modularize papyrus/pi-papyrus god-files into building-block modules").
+ * This file assembles every result-kind's own detector/renderer into the two exported Registry
+ * entry points (papyrusVehicleRenderers/papyrusVehiclePresentations) -- each sibling module owns
+ * one kind's own complexity, this one only needs its type + guard + renderer.
  */
 
 import { TOOL_DETAILS_MAX_SERIALIZED_CHARACTERS } from "@danypops/papyrus";

package/extension/src/tools/renderers/shared.ts

@@ -1,11 +1,8 @@
 /**
  * Base shape-detection kernel shared by every renderers/*.ts result-kind module: the generic
  * "looks like an Artifact" duck-typing every other detector in this directory builds on, plus the
- * Task Focus wrapper shape and small rendering primitives with no kind-specific machinery of their
- * own. Split out of the former single vehicle-artifact-renderers.ts as part of a SOLID-audit-driven
- * decomposition (see Doc "Modularity playbook: building-block-shaped TypeScript modules for
- * papyrus/pi-papyrus" and the "pi-papyrus vehicle-artifact-renderers.ts split" child of "Epic:
- * Modularize papyrus/pi-papyrus god-files into building-block modules").
+ * Task Focus wrapper shape and small rendering primitives with no kind-specific machinery of
+ * their own.
  */
 import type { Artifact } from "@danypops/papyrus";
 import type { Theme } from "@earendil-works/pi-coding-agent";

package/extension/src/tools/vehicle-artifact-renderers.ts

@@ -1,15 +1,8 @@
 /**
  * Barrel re-exporting Papyrus's own Vehicle-projected result renderers from ./renderers/. Kept as
  * a real file (not relying on directory-index resolution) so every existing
- * `from "./vehicle-artifact-renderers.ts"` / `from "../extension/src/tools/vehicle-artifact-renderers.ts"`
- * import (vehicle-notes-client.ts plus 3 test files) keeps resolving unchanged -- this codebase's
+ * `from "./vehicle-artifact-renderers.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.
- *
- * The real implementation now lives in ./renderers/ (one file per result-kind, plus index.ts as
- * the Registry assembly point) instead of one 670-line file -- see Doc "Modularity playbook:
- * building-block-shaped TypeScript modules for papyrus/pi-papyrus" and the "pi-papyrus
- * vehicle-artifact-renderers.ts split" child of "Epic: Modularize papyrus/pi-papyrus god-files
- * into building-block modules".
  */
 export { papyrusVehiclePresentations, papyrusVehicleRenderers } from "./renderers/index.ts";

package/extension/src/tools/vehicle-notes-client.ts

@@ -121,6 +121,10 @@ export function registerNotesVehicle(pi: ExtensionAPI): Promise<RegisteredPiVehi
 			// every dispatch so a long-lived Pi session never sends one sacrificial call to a
 			// cached dead port just to discover what the handle file already says.
 			resolveIdentity: () => daemonInstanceIdentity(resolveTarget().baseUrl),
+			// connectRetry:true (vehicle-client's own bounded background retry budget) covers a
+			// daemon that crashed and is mid systemd-restart -- without it, the very first call
+			// during that window fails immediately instead of waiting the ~2s restart out.
+			connectRetry: true,
 		},
 	);
 	return registerVehicleToolsWhenReady(pi, () => Promise.resolve(currentVehicleClientTarget() ? client : undefined), {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@danypops/pi-papyrus",
-  "version": "0.55.1",
+  "version": "0.55.3",
   "description": "Pi host extension for Papyrus: native tools, TUI panels, and context injection over the daemon-backed graph store",
   "type": "module",
   "keywords": ["pi-package"],
@@ -19,7 +19,7 @@
   "dependencies": {
     "@danypops/jittor": "^0.18.1",
     "@danypops/papyrus": "^0.54.2",
-    "@danypops/vehicle-client": "^0.7.0",
+    "@danypops/vehicle-client": "^0.10.0",
     "@danypops/vehicle-client-pi": "^0.40.1",
     "@danypops/vehicle-core": "^0.12.3",
     "@danypops/vehicle-server": "^0.18.1",