Docs: path segment two-mode stripWorkPrefix behavior; changelog matches shipped true

omp-docs/pi/statusline.md

@@ -65,12 +65,23 @@ values look identical. Docs' claim that contextLine is "box composer only" is
 wrong for the meter itself; the labeled inline variant (`57%×—200K←`) is the
 box/band-only part.
 
-## Path segment in worktrees
+## Path segment and `stripWorkPrefix`
 
-Inside a git worktree the `path` segment always renders
-`projectName/worktreeName` when `segmentOptions.path.stripWorkPrefix` is true
-(default), or the abbreviated cwd otherwise — base-directory-only is not
-renderable. `maxLength` clips tail-first.
+`segmentOptions.path.stripWorkPrefix` (default **true** — the code tests
+`!== false`) gates two behaviors in the `path` renderer:
+
+1. **Worktree sessions:** `true` never shows the disk path — it renders the
+   logical `projectName/worktreeName` label (bare `projectName` when the
+   current branch is named after the worktree) with the worktree glyph.
+   `false` opts out and shows the real cwd with a folder glyph, plus a
+   ` ↳ relativeRepoRoot` suffix inside a repo. Base-directory-only is not
+   renderable in either mode.
+2. **All sessions:** `true` uses the pretty display path (scratch sessions
+   get the scratch-folder icon); `false` uses the raw absolute cwd.
+
+`abbreviate` and `maxLength` (clip, default 40) apply afterwards in both
+modes. The fleet runs `true` — logical label, worktree glyph (verified live
+2026-10-18; an earlier trial of `false` for the full cwd was rejected by eye).
 
 ## Fleet configuration (2026-10-18)