Development record
The status board prints the checkout's absolute path with no redaction at all: core.Status sets Dir to filepath.Abs(cwd) (internal/core/core.go:46), bare abcd renders it raw as its first line ('abcd — <dir>', internal/surface/cli/cli.go:285) and abcd --json carries it whole as dir. Under HOME it prints /Users/<account>/..., and outside HOME the full path, in the output a person pastes most often. The board should name the checkout by the display rule fsutil.DisplayPath states (home-relative under HOME, the directory's base name outside it), the sibling of iss-2609281329007423, which routed every other checkout and worktree display but not this one.
The status board prints the checkout's absolute path with no redaction at all: core.Status sets Dir to filepath.Abs(cwd) (internal/core/core.go:46), bare abcd renders it raw as its first line ('abcd — <dir>', internal/surface/cli/cli.go:285) and abcd --json carries it whole as dir. Under HOME it prints /Users/<account>/..., and outside HOME the full path, in the output a person pastes most often. The board should name the checkout by the display rule fsutil.DisplayPath states (home-relative under HOME, the directory's base name outside it), the sibling of iss-2609281329007423, which routed every other checkout and worktree display but not this one.
Grounds
- pursued: bare abcd names a checkout under HOME as ~/rel and one outside HOME by its directory name, in text, JSON and the peers notice; TestBoardNamesACheckoutUnderHomeHomeRelative, TestBoardNamesACheckoutOutsideHomeByItsDirectoryName or TestBoardPeersNoticeNamesACheckoutOutsideHomeByItsDirectoryName failing would show it wrong
Frontmatter
| id | iss-2609281613094952 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2609281613094952-the-status-board-prints-the-checkout-s.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2609281329007423A checkout, worktree or store path outside HOME is printed whole by the surfaces that redact through fsutil.RedactHome alone: RedactHome turns a path under HOME into ~/rel and leaves every other absolute path untouched, so a sibling worktree in /private/tmp or on another volume reaches abcd peers (--json path, not_read, skipped, the peer-held refusal), the implement check's contention detail, history ingest's destination and orphan cwd, and implement status's lane worktree as a full local path in output a person pastes elsewhere. The display rule that fixes it (under HOME the home-relative form, outside HOME the directory's base name) is stated inline twice, in scrubPaths and in the capture verbs' ledgerIdentityOf, and in no primitive a new surface can reach, which is why each new surface re-derives RedactHome alone.