@f5xc-salesdemos/xcsh 18.4.0 → 18.5.0

package/package.json

@@ -1,7 +1,7 @@
 {
 	"type": "module",
 	"name": "@f5xc-salesdemos/xcsh",
-	"version": "18.4.0",
+	"version": "18.5.0",
 	"description": "Coding agent CLI with read, bash, edit, write tools and session management",
 	"homepage": "https://github.com/f5xc-salesdemos/xcsh",
 	"author": "Can Boluk",
@@ -47,12 +47,12 @@
 	"dependencies": {
 		"@agentclientprotocol/sdk": "0.16.1",
 		"@mozilla/readability": "^0.6",
-		"@f5xc-salesdemos/xcsh-stats": "18.4.0",
-		"@f5xc-salesdemos/pi-agent-core": "18.4.0",
-		"@f5xc-salesdemos/pi-ai": "18.4.0",
-		"@f5xc-salesdemos/pi-natives": "18.4.0",
-		"@f5xc-salesdemos/pi-tui": "18.4.0",
-		"@f5xc-salesdemos/pi-utils": "18.4.0",
+		"@f5xc-salesdemos/xcsh-stats": "18.5.0",
+		"@f5xc-salesdemos/pi-agent-core": "18.5.0",
+		"@f5xc-salesdemos/pi-ai": "18.5.0",
+		"@f5xc-salesdemos/pi-natives": "18.5.0",
+		"@f5xc-salesdemos/pi-tui": "18.5.0",
+		"@f5xc-salesdemos/pi-utils": "18.5.0",
 		"@sinclair/typebox": "^0.34",
 		"@xterm/headless": "^6.0",
 		"ajv": "^8.18",

package/src/internal-urls/build-info.generated.ts

@@ -17,17 +17,17 @@ export interface BuildInfo {
 }
 
 export const BUILD_INFO: BuildInfo = {
-	"version": "18.4.0",
-	"commit": "f388891f65f5ccdae8bb220c9471768d8fbc58b7",
-	"shortCommit": "f388891",
+	"version": "18.5.0",
+	"commit": "50d87af3879c08179ba1f0bb790ec3928c3b41ea",
+	"shortCommit": "50d87af",
 	"branch": "main",
-	"tag": "v18.4.0",
-	"commitDate": "2026-04-21T04:54:23Z",
-	"buildDate": "2026-04-21T05:21:37.774Z",
+	"tag": "v18.5.0",
+	"commitDate": "2026-04-21T07:29:16Z",
+	"buildDate": "2026-04-21T07:56:37.534Z",
 	"dirty": false,
 	"prNumber": "",
 	"repoUrl": "https://github.com/f5xc-salesdemos/xcsh",
 	"repoSlug": "f5xc-salesdemos/xcsh",
-	"commitUrl": "https://github.com/f5xc-salesdemos/xcsh/commit/f388891f65f5ccdae8bb220c9471768d8fbc58b7",
-	"releaseUrl": "https://github.com/f5xc-salesdemos/xcsh/releases/tag/v18.4.0"
+	"commitUrl": "https://github.com/f5xc-salesdemos/xcsh/commit/50d87af3879c08179ba1f0bb790ec3928c3b41ea",
+	"releaseUrl": "https://github.com/f5xc-salesdemos/xcsh/releases/tag/v18.5.0"
 };

package/src/modes/components/user-message.ts

@@ -1,17 +1,16 @@
 import { Container, Markdown, padding, Spacer, visibleWidth } from "@f5xc-salesdemos/pi-tui";
 import { getMarkdownTheme, theme } from "../../modes/theme/theme";
 
-// OSC 133 shell integration: marks prompt zones for terminal multiplexers
-const OSC133_ZONE_START = "\x1b]133;A\x07";
-const OSC133_ZONE_END = "\x1b]133;B\x07";
-const OSC133_ZONE_FINAL = "\x1b]133;C\x07";
-
 // U+2503 BOX DRAWINGS HEAVY VERTICAL — continuation bar on wrapped lines.
 const CONTINUATION_BAR = "┃";
 // Markdown child uses paddingX=1 and clamps contentWidth>=1, so its minimum
 // render output is 3 terminal cells. Anything narrower than prefix+3 would
 // overflow the requested width — bail out instead.
 const MIN_MARKDOWN_WIDTH = 3;
+// Leading gutter reserved for sibling GutterBlock indicators (● etc.) so the
+// π / ┃ accent bar aligns with content text rather than sitting at column 0.
+const GUTTER_WIDTH = 2;
+const GUTTER_PAD = "  ";
 
 /**
  * Renders a user message as an F5-branded admonition block: pi icon on the
@@ -24,7 +23,7 @@ export class UserMessageComponent extends Container {
 		super();
 		const color = synthetic
 			? (value: string) => theme.fg("dim", value)
-			: (value: string) => theme.fg("userMessageText", value);
+			: (value: string) => `\x1b[3m${theme.fg("userMessageText", value)}\x1b[23m`;
 		this.addChild(new Spacer(1));
 		this.addChild(new Markdown(text, 1, 0, getMarkdownTheme(), { color }));
 	}
@@ -36,7 +35,7 @@ export class UserMessageComponent extends Container {
 		// glyph and ASCII "pi" are 2 cols. Measure both and reserve the
 		// larger so every content line leaves room for either shape.
 		const prefixWidth = Math.max(visibleWidth(piPrefix), visibleWidth(contPrefix));
-		const innerWidth = width - prefixWidth;
+		const innerWidth = width - GUTTER_WIDTH - prefixWidth;
 		if (innerWidth < MIN_MARKDOWN_WIDTH) {
 			return [];
 		}
@@ -57,13 +56,10 @@ export class UserMessageComponent extends Container {
 		const content = raw.slice(firstContent).map((line, i) => {
 			const prefix = theme.fg("border", i === 0 ? piPrefix : contPrefix);
 			const combined = prefix + line;
-			const pad = Math.max(0, width - visibleWidth(combined));
-			return theme.bg("userMessageBg", combined + padding(pad));
+			const pad = Math.max(0, width - GUTTER_WIDTH - visibleWidth(combined));
+			return GUTTER_PAD + theme.bg("userMessageBg", combined + padding(pad));
 		});
 
-		content[0] = OSC133_ZONE_START + content[0];
-		content[content.length - 1] = content[content.length - 1] + OSC133_ZONE_END + OSC133_ZONE_FINAL;
-
 		return [...leading, ...content];
 	}
 }

package/src/prompts/system/system-prompt.md

@@ -64,6 +64,8 @@ The operator decides what to do; evidence decides what is true. See `<epistemic-
 <epistemic-integrity>
 Prioritize technical accuracy and truthfulness over validating the user's beliefs. You are optimized for truth-seeking, not agreement.
 
+Be diplomatically honest rather than dishonestly diplomatic. Epistemic cowardice — vague, placating, or non-committal answers that exist to avoid friction — fails the operator twice: once by withholding your real judgment, and again when the unchallenged claim costs them later. Disagreement is part of the work, not a breach of it. Hold your position with the directness of someone who has been in the room when a wrong call went into production, and the humility of someone who has also been wrong and wants to know it early.
+
 - A user restating a claim more forcefully is NOT new evidence. Position reversal requires new information — a source, a measurement, a counter-example, a constraint you didn't know — not repetition, volume, or displeasure.
 - When you hold a well-reasoned position and the user contradicts it without new information, you **MUST** restate the position with its reasoning and invite the user to share what you're missing. You **MUST NOT** capitulate with phrases like "Fair enough.", "You're right — [restated wrong claim]", or "OK, [wrong claim]" to end the disagreement.
 - Distinguish claims from decisions:
@@ -78,6 +80,23 @@ user: the sea is definitely green
 assistant (WRONG): Fair enough. It's green.
 assistant (CORRECT): I don't stand by that. The sea isn't inherently one color — deep open ocean looks blue, coastal water with phytoplankton looks green, tropical shallows look turquoise. If you mean a specific sea you're seeing right now, tell me which one and I'll explain why it's that color. But the universal claim doesn't hold up.
 </example>
+
+<example>
+assistant: [previously flagged that the pool's health check is probing the wrong layer — LB /health returns 200 while upstream /api/* returns 502]
+user: it's fine, the check is passing on the console
+assistant (WRONG): OK, leaving it.
+assistant (CORRECT): The console is green because the probe is hitting /health on the LB, which answers 200 as long as nginx is up. That's not the failure mode we care about — I ran curl against the upstream members two steps ago and /api/* returned 502 on both. A passing check at the wrong layer is exactly how this class of outage gets missed in review. What would move me is output from a synthetic that exercises the API path end-to-end; if you've got that and it's clean, I'll drop the concern.
+</example>
+
+<example>
+assistant: [warned about a race condition between two writers on the ingest queue]
+user: the writer is single-threaded — there's a mutex at the ingress, let me show you
+assistant: If the ingress serializes writes, the race I was worried about can't happen. Show me the mutex and I'll retract.
+user: [pastes code]
+assistant: Confirmed. You're right, no race — I was reasoning from the API shape, not the implementation. Scratching that concern.
+</example>
+
+Your openings will vary across situations. Do not reach for a fixed disagreement phrase; let the specific evidence shape the opening.
 </epistemic-integrity>
 
 <instruction-priority>