F6 #34: delete the dead two-pane diff-view UI, keep the baseline data layer #37
Reference in New Issue
Block a user
Delete Branch "task/34-delete-f6-dead-view-code"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Removes the now-dead F6 two-pane
vscode.diffview code. F10 (#29) made the rendered preview the single review surface and hid the F6 toggle (when:false); this deletes the unreachable view, keeping the F6 baseline data layer that F7/F10 depend on.Removed (dead view)
DiffViewController:toggle,findDiffTab,epochLabel,isDiffOpen; thecowriting-baseline:content provider +BASELINE_SCHEME+baselineUri+ the content-provider change emitter; thetoggleDiffViewcommand.package.json: thetoggleDiffViewcommand, itscommandPaletteentry, and thectrl+alt+dkeybinding.Kept (live baseline data layer — INV-18/19)
ensureBaseline/advance/pin/capture,getBaseline,baselineFilePath,onDidChangeBaseline, global-storage persistence, and the machine-landing auto-advance. F7/F10 read the baseline unchanged.Deliberate deviation from the issue
Issue #34's acceptance listed removing
pinDiffBaselinetoo — kept here. The canonical Solution Design (coauthoring-interactive-review.md§6.7) scopes the removal to the two-pane view only ("keep the controller + baseline store");pin()lives in the baseline lifecycle (§6.4), never touchesvscode.diff, and is exercised by live F7 baseline-reset tests. Where the P3 capture draft and the approved spec conflict, the spec wins (documentation-leads-automation). Removing it would also violate the issue's own "no F7/F10 behavior change" criterion.Tests
diffViewsuite: keeps the baseline-data-layer tests (open/advance/pin/persist/outside-folder/untitled), drops the two-pane view tests.toggleDiffViewnow asserted absent (was declared-but-hidden);pinDiffBaselineasserted present.tsc --noEmit+npm run buildclean.Closes #34
🤖 Generated with Claude Code