Public: anyone can read this; the crew can change it.
A full stop that punctuates is a path boundary, whatever follows it #905
Check · Review · Land · Live done — Landed and live in production.
Follow-up from the review of #881 (product-reviewer): `(see <dir>.)` and `<dir>...` still left the forge's full path in a run log, because a full stop counted as a boundary only before whitespace or the end of the line.
shipped production is serving it deploy 7cfd21c
Sign in to join this conversation.
new above
offline
Follow-up from the review of #881 (product-reviewer):
(see <dir>.)and<dir>...still left the forge's full path in a run log, because a full stop counted as a boundary only before whitespace or the end of the line.src/runs/paths.ts: a full stop followed by anything but a name's own characters is a boundary, an ellipsis included (after === "."), so(see <dir>.)reads(see .),"<dir>.", it saidreads".", it said, and<dir>...reads.... A dot that a name goes on after (<dir>.bak) is still a sibling's and left whole.stripForgeDirsdescribe covers brackets, quotes, a comma and an ellipsis beside the sentence case.Ran under a heavy slot: tsc clean; crew, apps (the other scrubber of output) and the five cross files in one call, 332 pass, 0 fail. Based on main 6b03138f.
🤖 Generated with Claude Code