@yagni-app/code-staging 0.2.1-staging.1041.1 → 0.2.1-staging.1043.1

package/dist/cli.d.ts

@@ -14,25 +14,20 @@
  */
 /**
  * Seed `editorPaddingX` into the per-profile pi `settings.json` so the prompt
- * input is padded to match the chat/output area (`outputPad`) and the status
- * bar. Fills the key in only when absent — an explicit user choice (including
- * 0) is never overwritten. Best-effort: a missing/corrupt settings file or a
+ * input aligns with the chat/output area (`outputPad`) and the status bar.
+ * Fills the key in only when absent — an explicit user choice (including 0)
+ * is never overwritten. Best-effort: a missing/corrupt settings file or a
  * write failure must never block the launch.
  */
+export declare function seedEditorPadding(piAgentDir: string): void;
 /**
- * Seed `editorPaddingX` into the per-profile pi `settings.json` so the prompt
- * input aligns with the chat/output area (`outputPad`) and the status bar.
- *
- * This writes to a user-owned file, so it is deliberately conservative:
- *  - fills the key in ONLY when absent — an explicit user choice (including 0)
- *    is never overwritten;
- *  - backs off on a missing-dir, corrupt, non-object, or symlinked settings
- *    file rather than risk clobbering anything;
- *  - writes ATOMICALLY (temp file + rename) and preserves the existing file's
- *    permissions, so a crash mid-write can never truncate the user's settings.
- * Any failure is swallowed: seeding must never block or break a launch.
+ * Seed `collapseChangelog` into the per-profile pi `settings.json` so the
+ * "What's New" section on startup renders as a one-liner instead of a full
+ * markdown dump. Fills the key in only when absent — an explicit user choice
+ * (including false) is never overwritten. Best-effort: a missing/corrupt
+ * settings file or a write failure must never block the launch.
  */
-export declare function seedEditorPadding(piAgentDir: string): void;
+export declare function seedCollapseChangelog(piAgentDir: string): void;
 export declare const HELP_TEXT: string;
 /** Parse `use <name> [--base-url <url>]` argv into its parts. */
 export declare function parseUseArgs(args: string[]): {

package/dist/cli.js

@@ -53,19 +53,19 @@ async function confirmOnTty(question) {
  * write failure must never block the launch.
  */
 /**
- * Seed `editorPaddingX` into the per-profile pi `settings.json` so the prompt
- * input aligns with the chat/output area (`outputPad`) and the status bar.
+ * Seed a key into the per-profile pi `settings.json`. Shared guard rails for
+ * all settings seeds:
  *
  * This writes to a user-owned file, so it is deliberately conservative:
- *  - fills the key in ONLY when absent — an explicit user choice (including 0)
- *    is never overwritten;
+ *  - fills the key in ONLY when absent — an explicit user choice (including 0
+ *    or false) is never overwritten;
  *  - backs off on a missing-dir, corrupt, non-object, or symlinked settings
  *    file rather than risk clobbering anything;
  *  - writes ATOMICALLY (temp file + rename) and preserves the existing file's
  *    permissions, so a crash mid-write can never truncate the user's settings.
  * Any failure is swallowed: seeding must never block or break a launch.
  */
-export function seedEditorPadding(piAgentDir) {
+function seedSetting(piAgentDir, key, value) {
     try {
         const settingsPath = join(piAgentDir, "settings.json");
         let settings = {};
@@ -88,9 +88,9 @@ export function seedEditorPadding(piAgentDir) {
             settings = parsed;
             existingMode = lstatSync(settingsPath).mode & 0o777;
         }
-        if (settings.editorPaddingX !== undefined)
+        if (settings[key] !== undefined)
             return; // user already chose
-        settings.editorPaddingX = PAD_X;
+        settings[key] = value;
         // Atomic write: serialize to a temp file in the same directory, then
         // rename over the target. A crash leaves either the old file or the temp
         // file, never a half-written settings.json.
@@ -111,6 +111,26 @@ export function seedEditorPadding(piAgentDir) {
         // never block launch on a settings-seed failure
     }
 }
+/**
+ * Seed `editorPaddingX` into the per-profile pi `settings.json` so the prompt
+ * input aligns with the chat/output area (`outputPad`) and the status bar.
+ * Fills the key in only when absent — an explicit user choice (including 0)
+ * is never overwritten. Best-effort: a missing/corrupt settings file or a
+ * write failure must never block the launch.
+ */
+export function seedEditorPadding(piAgentDir) {
+    seedSetting(piAgentDir, "editorPaddingX", PAD_X);
+}
+/**
+ * Seed `collapseChangelog` into the per-profile pi `settings.json` so the
+ * "What's New" section on startup renders as a one-liner instead of a full
+ * markdown dump. Fills the key in only when absent — an explicit user choice
+ * (including false) is never overwritten. Best-effort: a missing/corrupt
+ * settings file or a write failure must never block the launch.
+ */
+export function seedCollapseChangelog(piAgentDir) {
+    seedSetting(piAgentDir, "collapseChangelog", true);
+}
 async function runDefault(passthroughArgs) {
     // Cache-backed update nudge (never a network wait), then a background cache
     // refresh that completes while the session runs. Both fail soft.
@@ -141,10 +161,13 @@ async function runDefault(passthroughArgs) {
     const piAgentDir = agentDir(profile.name);
     mkdirSync(piAgentDir, { recursive: true, mode: 0o700 });
     // Seed the editor's horizontal padding so the prompt input aligns with the
-    // chat/output area and the status bar. Only fills in when the user has not
-    // set it themselves — an explicit choice is never clobbered. Best-effort: a
-    // corrupt or unreadable settings.json must never block the launch.
+    // chat/output area and the status bar, and collapse the changelog so the
+    // "What's New" section on startup renders as a one-liner instead of a full
+    // markdown dump. Only fills in when the user has not set either themselves —
+    // an explicit choice is never clobbered. Best-effort: a corrupt or
+    // unreadable settings.json must never block the launch.
     seedEditorPadding(piAgentDir);
+    seedCollapseChangelog(piAgentDir);
     // Generate the shadow pi package so the terminal title/process name read
     // "YAGNI Code" instead of "pi"/"π". Best-effort: if it can't be built we
     // still launch (un-rebranded but hermetic), never blocking the agent.

package/dist/doctor.d.ts

@@ -94,7 +94,7 @@ export interface DoctorDeps {
 export declare function ghOnPathDefault(env?: NodeJS.ProcessEnv): boolean;
 /**
  * Locate the bash pi will actually use on Windows. The order and locations
- * MIRROR pi 0.83's own shell resolution (dist/utils/shell.js) exactly:
+ * MIRROR pi 0.84.1's own shell resolution (dist/utils/shell.js) exactly:
  * `%ProgramFiles%\Git\bin\bash.exe`, then `%ProgramFiles(x86)%\Git\bin\bash.exe`,
  * then `bash.exe` on PATH (`where bash.exe`). Deliberately NOTHING wider — a
  * per-user Git install in `%LOCALAPPDATA%` that is not on PATH is invisible

package/dist/doctor.js

@@ -316,7 +316,7 @@ export function ghOnPathDefault(env = process.env) {
 }
 /**
  * Locate the bash pi will actually use on Windows. The order and locations
- * MIRROR pi 0.83's own shell resolution (dist/utils/shell.js) exactly:
+ * MIRROR pi 0.84.1's own shell resolution (dist/utils/shell.js) exactly:
  * `%ProgramFiles%\Git\bin\bash.exe`, then `%ProgramFiles(x86)%\Git\bin\bash.exe`,
  * then `bash.exe` on PATH (`where bash.exe`). Deliberately NOTHING wider — a
  * per-user Git install in `%LOCALAPPDATA%` that is not on PATH is invisible

package/dist/extension/branding.js

@@ -54,7 +54,7 @@ export const DRIVER_DELEGATION_PARAGRAPH = "Delegation: fan codebase mapping, wi
  * module stays a pure string, with no env dependency of its own.
  */
 export const YAGNI_IDENTITY_DRIVER = `${YAGNI_IDENTITY}\n\n${DRIVER_DELEGATION_PARAGRAPH}`;
-// pi 0.83.0's exact identity sentence (dist/core/system-prompt.js). Exported as
+// pi 0.84.1's exact identity sentence (dist/core/system-prompt.js). Exported as
 // the identity anchor the CLI's pi-contract tripwire test reads back from pi's
 // built system prompt, so a pi bump that reworded the opener (silently defeating
 // our rebrand) fails CI loudly. Export-only: no behavior change here.

package/dist/extension/chipEditor.d.ts

@@ -17,7 +17,7 @@
  * literal text is the source of truth, so undo/cursor/history and the
  * chip→model mapping all share one string and can't desync.
  *
- * Validated against pi 0.83.0 (spike, 5/5): the subclass owns `onPasteImage`
+ * Validated against pi 0.84.1 (spike, 5/5): the subclass owns `onPasteImage`
  * because `setCustomEditorComponent` only fills it when unset, and jiti aliases
  * the extension's pi imports to the same module instance pi uses.
  */

package/dist/extension/chipEditor.js

@@ -17,7 +17,7 @@
  * literal text is the source of truth, so undo/cursor/history and the
  * chip→model mapping all share one string and can't desync.
  *
- * Validated against pi 0.83.0 (spike, 5/5): the subclass owns `onPasteImage`
+ * Validated against pi 0.84.1 (spike, 5/5): the subclass owns `onPasteImage`
  * because `setCustomEditorComponent` only fills it when unset, and jiti aliases
  * the extension's pi imports to the same module instance pi uses.
  */

package/dist/extension/rerouteNotice.d.ts

@@ -4,7 +4,7 @@
  * The backend sets `x-yagni-model-reroute: <requested>-><effective>:vision` on
  * every response it silently upgrades for image content (yagniCodeV1.ts). pi's
  * `after_provider_response` event is the only client-side seam that sees raw
- * response headers (verified against pi 0.83.0's AfterProviderResponseEvent:
+ * response headers (verified against pi 0.84.1's AfterProviderResponseEvent:
  * `{ type: "after_provider_response", status: number, headers: Record<string,
  * string> }` in dist/core/extensions/types.d.ts). Its docs (extensions.md,
  * "after_provider_response") describe `event.headers` as "normalized response

package/dist/extension/rerouteNotice.js

@@ -4,7 +4,7 @@
  * The backend sets `x-yagni-model-reroute: <requested>-><effective>:vision` on
  * every response it silently upgrades for image content (yagniCodeV1.ts). pi's
  * `after_provider_response` event is the only client-side seam that sees raw
- * response headers (verified against pi 0.83.0's AfterProviderResponseEvent:
+ * response headers (verified against pi 0.84.1's AfterProviderResponseEvent:
  * `{ type: "after_provider_response", status: number, headers: Record<string,
  * string> }` in dist/core/extensions/types.d.ts). Its docs (extensions.md,
  * "after_provider_response") describe `event.headers` as "normalized response

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yagni-app/code-staging",
-  "version": "0.2.1-staging.1041.1",
+  "version": "0.2.1-staging.1043.1",
   "description": "YAGNI Code: a terminal coding agent that already knows your company. One YAGNI login routes the model and grounds the agent in your team's context.",
   "license": "SEE LICENSE IN LICENSE.md",
   "author": "YAGNI, Inc. <jack@yagni.app> (https://yagni.app)",
@@ -34,9 +34,9 @@
   "main": "./dist/cli.js",
   "types": "./dist/cli.d.ts",
   "dependencies": {
-    "@earendil-works/pi-coding-agent": "0.83.0",
-    "@earendil-works/pi-tui": "0.83.0",
-    "typebox": "^1.1.38"
+    "@earendil-works/pi-coding-agent": "0.84.1",
+    "@earendil-works/pi-tui": "0.84.1",
+    "typebox": "^1.3.11"
   },
-  "yagniSourceSha": "c0f29e93789c8996bced9dcc24583a9ab426efc0"
+  "yagniSourceSha": "2a370c71157559a3fc64d9c3ca2fd2677f26ef4e"
 }