@janvitos/pi-plan-build 0.1.47 → 0.1.48

package/README.md

@@ -26,7 +26,7 @@ Optionally keep the approved plan visible in a docked side panel while implement
 
 - New sessions start in **Build** mode.
 - Bare `Tab` cycles **Build → Plan → Build**, while active autocomplete dropdowns retain Pi's normal Tab completion.
-- The composer uses OpenCode prompt-inspired blue/orange mode colors on the rounded top-left border and left rail, complemented by Pi's border color on the right rail and rounded bottom-right border; rounded corners inherit their vertical rail colors while horizontal `╌` segments bridge the borders at both junctions, paired with a light vertical `┆` at the top right and a mode-specific bottom-left transition: thin `┆` in Plan and heavy `┇` in Build. User messages carry a heavy dashed `┇` transcript rail in the mode used to submit them—using the active Pi theme's `warning` color in Plan and `thinkingLow` color in Build—and retain that color after mode changes and session restores. It also includes a mode/model/thinking metadata row; cycling the thinking level updates this row without adding a duplicate status above the composer. The model is shown as `model-id [provider]` (for example, `gpt-5.6-luna [openai]`), with the model ID inheriting the terminal foreground like unselected entries in `/model` and the provider using the footer's dim text color. The footer keeps the remaining path and usage stats without duplicating model metadata.
+- The composer uses OpenCode prompt-inspired blue/orange mode colors on the rounded top-left border and left rail, complemented by Pi's border color on the right rail and rounded bottom-right border; rounded corners inherit their vertical rail colors while horizontal `╌` segments bridge the borders at both junctions, paired with a light vertical `┆` at the top right and a mode-specific bottom-left transition: thin `┆` in Plan and heavy `┇` in Build. The active composer and submitted user messages use a continuous solid thin `│` left rail in both modes. These rails use the active Pi theme's `warning` color in Plan and `thinkingLow` color in Build, and submitted messages retain their original mode after mode changes and session restores. It also includes a mode/model/thinking metadata row; cycling the thinking level updates this row without adding a duplicate status above the composer. The model is shown as `model-id [provider]` (for example, `gpt-5.6-luna [openai]`), with the model ID inheriting the terminal foreground like unselected entries in `/model` and the provider using the footer's dim text color. The footer keeps the remaining path and usage stats without duplicating model metadata.
 - `/plan`, `/build`, and the `--plan` startup flag.
 - Per-session plans at `~/.pi/agent/plans/<session-id>.md`.
 - In Plan mode, built-in `edit` and `write` are restricted to the exact plan file.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@janvitos/pi-plan-build",
-  "version": "0.1.47",
+  "version": "0.1.48",
   "description": "Plan safely, approve explicitly, then implement here or in a clean session.",
   "type": "module",
   "license": "MIT",

package/user-message-rail.ts

@@ -139,7 +139,7 @@ export function installUserMessageRail(
 			resolver: new TranscriptModeResolver(),
 			formatRail: options.formatRail,
 			getFallbackMode: options.getFallbackMode,
-			glyph: "┇",
+			glyph: "│",
 		};
 		globalState[PATCH_KEY] = state;
 	}
@@ -148,7 +148,7 @@ export function installUserMessageRail(
 	state.owner = owner;
 	state.formatRail = options.formatRail;
 	state.getFallbackMode = options.getFallbackMode;
-	state.glyph = "┇";
+	state.glyph = "│";
 	// Reinstall from the preserved original on every extension load. This migrates
 	// already-running processes away from stale decorator code without stacking wrappers.
 	UserMessageComponent.prototype.render = function renderWithModeRail(width: number): string[] {