@av-pi-studio/server 0.0.69 → 0.0.70

package/dist/agent/file-link-instructions.d.ts

@@ -5,7 +5,7 @@
  * `file_link_markdown` capability). A session that resumes after a client disconnect will
  * retain it; one created from the CLI and later opened in a capable client will not have it,
  * because the CLI client does not advertise the capability at spawn. This asymmetry is accepted
- * (see clean-room-scope/features/file-link-rendering.md § Known Limitations).
+ * (see swe/features/file-link-rendering.md § Known Limitations).
  */
 export declare const FILE_LINK_INSTRUCTIONS: string;
 //# sourceMappingURL=file-link-instructions.d.ts.map

package/dist/agent/file-link-instructions.js

@@ -5,7 +5,7 @@
  * `file_link_markdown` capability). A session that resumes after a client disconnect will
  * retain it; one created from the CLI and later opened in a capable client will not have it,
  * because the CLI client does not advertise the capability at spawn. This asymmetry is accepted
- * (see clean-room-scope/features/file-link-rendering.md § Known Limitations).
+ * (see swe/features/file-link-rendering.md § Known Limitations).
  */
 export const FILE_LINK_INSTRUCTIONS = `
 You can embed file links in your output using Markdown link syntax: \`[label](path)\`.

package/dist/agent/inline-image-instructions.d.ts

@@ -5,7 +5,7 @@
  * `inline_image_markdown` capability). A session that resumes after a client disconnect will
  * retain it; one created from the CLI and later opened in a capable client will not have it,
  * because the CLI client does not advertise the capability at spawn. This asymmetry is accepted
- * (see clean-room-scope/features/inline-image-rendering.md § Known Limitations).
+ * (see swe/features/inline-image-rendering.md § Known Limitations).
  */
 export declare const INLINE_IMAGE_INSTRUCTIONS: string;
 //# sourceMappingURL=inline-image-instructions.d.ts.map

package/dist/agent/inline-image-instructions.js

@@ -5,7 +5,7 @@
  * `inline_image_markdown` capability). A session that resumes after a client disconnect will
  * retain it; one created from the CLI and later opened in a capable client will not have it,
  * because the CLI client does not advertise the capability at spawn. This asymmetry is accepted
- * (see clean-room-scope/features/inline-image-rendering.md § Known Limitations).
+ * (see swe/features/inline-image-rendering.md § Known Limitations).
  */
 export const INLINE_IMAGE_INSTRUCTIONS = `
 You can embed images in your output using Markdown image syntax: \`![alt](path)\`.

package/dist/agent/slash-command-operations.d.ts

@@ -16,7 +16,7 @@ import type { AgentClient } from "./provider-contract.js";
  *
  * Pi's own RPC contract is explicit that TUI-only built-ins (/settings, /hotkeys, etc.) have no
  * RPC equivalent and would not execute if sent via `prompt` — those are intentionally NOT
- * represented here or on the wire (see clean-room-scope/sprints/sprint-037-agent-slash-commands).
+ * represented here or on the wire (see swe/sprints/sprint-037-agent-slash-commands).
  */
 export interface SlashCommandOpsDeps {
     manager: AgentManager;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@av-pi-studio/server",
-  "version": "0.0.69",
+  "version": "0.0.70",
   "type": "module",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
@@ -22,9 +22,9 @@
     "clean": "rm -rf dist *.tsbuildinfo"
   },
   "dependencies": {
-    "@av-pi-studio/highlight": "^0.0.69",
-    "@av-pi-studio/protocol": "^0.0.69",
-    "@av-pi-studio/relay": "^0.0.69",
+    "@av-pi-studio/highlight": "^0.0.70",
+    "@av-pi-studio/protocol": "^0.0.70",
+    "@av-pi-studio/relay": "^0.0.70",
     "@earendil-works/pi-coding-agent": "^0.83.0",
     "@xterm/headless": "^6.0.0",
     "bcryptjs": "^3.0.3",