docs: trim generated prose

packages/ui/acp/tests/stream-update.spec.ts

@@ -288,10 +288,8 @@ describe('ToolPresenter (tool-owned presentation via the tool registry)', () =>
   })
 
   it('a THROWING presentCall/presentResult is contained: generic fallback + onError, never propagates', () => {
-    // A buggy tool whose display callbacks throw must NOT fail a live turn or a
-    // session/load replay (docs/defensive-patterns.md "contain callback exceptions at the
-    // boundary"). The presenter swallows the throw, reports via onError, and
-    // falls back to the generic presentation.
+    // A buggy tool whose display callbacks throw must not fail a live turn or a session/load
+    // replay (docs/defensive-patterns.md "contain callback exceptions at the boundary").
     const boom: ToolDefinition = {
       name: 'boom',
       description: 'b',
@@ -621,12 +619,10 @@ describe('diff-card mapping', () => {
 })
 
 describe('result-time diff card (REAL fs edit tool → tool_call_update diff blocks)', () => {
-  // Drive the SHIPPING fs edit tool through the bridge: the pending tool/call
-  // installs the call-time snippet, then the tool/result carries the tool's
-  // computed applied-hunk `meta`, which presentResult narrows into a `diff`
-  // result card the bridge forwards as `{ type: 'diff' }` content blocks. Uses
-  // the REAL tool (not a stand-in) per the anti-mock convention, mirroring the
-  // call-side diff test above.
+  // Drive the SHIPPING fs edit tool through the bridge: the pending tool/call installs the
+  // call-time snippet, then the tool/result carries the tool's computed applied-hunk `meta`,
+  // which presentResult narrows into a `diff` result card the bridge forwards as `{ type:
+  // 'diff' }` content blocks.
   async function fsCtx(): Promise<Context> {
     const ctx = new Context()
     await ctx.plugin(SystemPrompt)
@@ -678,11 +674,9 @@ describe('result-time diff card (REAL fs edit tool → tool_call_update diff blo
   })
 
   it('the completed diff TITLE relativizes against the session cwd (the result title replaces the card header)', async () => {
-    // A `tool_call_update.title` replaces the card header, so the result-side
-    // diff must relativize its title exactly as the pending card did — otherwise
-    // a completed absolute-path edit flips `Edit src/b.ts` back to the raw
-    // absolute path. The diff/location paths stay absolute (the editor opens the
-    // real path). Drive the REAL fs edit tool with an absolute in-workspace path.
+    // A `tool_call_update.title` replaces the card header, so the result-side diff must
+    // relativize its title exactly as the pending card did — otherwise a completed
+    // absolute-path edit flips `Edit src/b.ts` back to the raw absolute path.
     const ctx = await fsCtx()
     const presenter = new ToolPresenter(ctx.tools)
     const args = JSON.stringify({ file_path: '/work/proj/src/b.ts', old_string: 'OLD', new_string: 'NEW' })
@@ -704,11 +698,7 @@ describe('result-time diff card (REAL fs edit tool → tool_call_update diff blo
   })
 
   it('a diff result with an EMPTY diffs array and no title omits both keys (nothing to send)', () => {
-    // A synthetic tool whose presentResult yields a `diff` card with no hunks and
-    // no title — the shipping fs tools never emit this (edit always has a hunk;
-    // write always falls back to a whole-file diff), so a stand-in is the only way
-    // to exercise the empty-content AND absent-title branches of the result-side
-    // diff arm.
+    // A synthetic empty diff covers branches shipping filesystem tools cannot emit.
     const emptyDiffTool: ToolDefinition = {
       name: 'writer',
       description: 'writes a file',
@@ -734,11 +724,8 @@ describe('result-time diff card (REAL fs edit tool → tool_call_update diff blo
 })
 
 describe('relative-path display titles (bridge relativizes the title against the session cwd)', () => {
-  // The bridge relativizes a file card's TITLE against the session workspace cwd
-  // (mirroring the reference adapter's toDisplayPath), while leaving locations/
-  // diff paths RAW. Drive it with the REAL fs tools so the title/locations come
-  // from the shipping presentCall, and pass an ABSOLUTE file path (which a real
-  // editor forwards). The presenter is pure/args-only; the cwd is known only here.
+  // The bridge relativizes a file card's TITLE against the session workspace cwd (mirroring the
+  // reference adapter's toDisplayPath), while leaving locations/ diff paths RAW.
   async function fsCtx(): Promise<Context> {
     const ctx = new Context()
     await ctx.plugin(SystemPrompt)
@@ -789,10 +776,8 @@ describe('relative-path display titles (bridge relativizes the title against the
   })
 
   it('an in-workspace file whose relative form starts with `..` chars (a sibling name) still relativizes', async () => {
-    // `/work/proj/..cache/x` is INSIDE the workspace — its relative form
-    // `..cache/x` begins with the chars `..` but is NOT a parent segment. The
-    // guard tests for a `..` SEGMENT, so this relativizes (matching the reference
-    // adapter, which accepts any target under `cwd + sep`).
+    // `/work/proj/..cache/x` is inside the workspace — its relative form `..cache/x` begins
+    // with the chars `..` but is not a parent segment.
     const ctx = await fsCtx()
     const update = callUpdate(ctx, '/work/proj', 'read', { file_path: '/work/proj/..cache/x.ts' })
     expect((update as { title: string }).title).toBe('Read ..cache/x.ts')