Source paths cited outside the compiler

The harness tables in section 2 are as of the end of Phase 6 (030ee64); sections 1, 3, 4, and 5 still describe 1805a01.

This inventory lists every place outside TypeScript’s view that names a source path, a compiled path, or a command id by string. The compiler catches a broken import, but it does not see these places, so a moved file breaks them or leaves them stale without any error. It was taken at dev 1805a01, before Phase 0 of the refactor plan, and each later phase checks against it.

Line numbers are 1-based at 1805a01, except in section 2, where they are at 030ee64. “Breaks” means a test, script, build, or runtime path fails, or silently stops covering something, after a move. “Stale” means only a document goes out of date.

Totals

“Break on a move” counts a move of a source file, a harness, a script, or the fixture, and it includes places that stop checking without failing.

No path that the current docs, harnesses, scripts, or configuration cite is missing today. Every src/ path the current docs cite exists, and each glob matches files. The missing paths in docs/implementation/ are ones those plans proposed. The line numbers some docs attach to those paths are already out of date (see section 1).

1. Docs

The search covered every tracked Markdown file outside docs/implementation/: README.md, CHANGELOG.md, .github/copilot-instructions.md, the 14 files directly in docs/, and the 18 pages in docs/guide/. The notes under development/notes/ and resources/ cite no paths.

Citations per file

The plan’s counts differ in two places:

• docs/task-steps.md has 27 citations of 23 distinct paths. The plan’s 22 is the number of distinct files, leaving out the folder src/test at line 536.
• docs/editor-lenses.md cites three paths, not two. The third is src/test/editor-lenses.test.ts at line 59.

No current doc cites an out/ or dist/ path.

The guide ships in the VSIX and guide.test.ts checks it, but no guide page cites a source path. So no shipped doc goes stale on a move.

CHANGELOG.md also ships, and Help parses it at runtime. Its one citation sits in a released section, so it stays as history rather than being edited.

Every src/ citation

Fourteen of these lines also cite line numbers: 13 in docs/ux-review.md and one in docs/zen-mode.md. Those numbers are already wrong at 1805a01 in the five checked:

• docs/zen-mode.md:32 cites taskBoardActions.ts:52. updateTaskBoardSetting is at line 60.
• docs/ux-review.md:48 cites taskStatusBar.ts:36-43. describeDueTasks is at line 54.
• docs/ux-review.md:76 cites components.ts:522 for .task-meta. The rule is at line 749.
• docs/ux-review.md:287 cites dashboardHtml.ts:849. That line is now a doc comment for widget links.
• docs/ux-review.md:417 cites themes.ts:78 for Corpo’s override. That line is now --hover-fg.

test/ harness paths cited in docs

Phase 0 rewrites some harnesses (§2.6 of the plan), so these citations can go stale too.

docs/implementation/

These are dated plans. They record what was intended when each was written and are not kept current, so they are counted and not listed. Most paths not on disk are ones a plan proposed, such as the refactor targets src/services and src/webview.

Of the 757, 35 are out/ or dist/ paths, and 28 of those are in the two 19- files.

2. Test harnesses

This section is as of the end of Phase 6 (030ee64), and counts test/ui/checkWebviewScripts.js as deleted, as it is at the end of that phase. It names no path in it. The catalog’s entries, and what each harness takes from them, are as of the end of Phase 7 (refactor/07final), which deleted the re-export shims the harnesses took five names through; the line numbers elsewhere in the section are as of Phase 6.

The Node harnesses in test/e2e, test/ui, and test/perf load the tsc output in out/, with a stub standing in for vscode. tsconfig.json sets rootDir to src, so out/ mirrors src/ exactly, and any move under src/ moves the compiled file with it. The mocha suites keep passing, because their imports are compiler-checked. The harnesses fail instead, and only when their own npm script runs.

Since Phase 0 the harnesses no longer name out/ paths themselves. They take each module by name from the catalog in test/harness/modules.js, which maps the name to its path under out/ once, so a move is one edit there. Since Phase 6 none goes around it: test/ui/surfaces.js, which took the layout harness’s state builders over, takes queryContext from the catalog too. The page builders reach the harnesses through out/test/pages.js, the catalog of src/test/pages.ts, whose imports the compiler checks. Since Phase 7 the builders are given the theme and zen mode (chrome) rather than reading the settings, so test/ui/pages.js passes them in renderPage’s options instead of setting them in the stub’s settings, and, since the catalog loads no vscode, installs no stub; the checks that draw surfaces still have it, through test/e2e/support.js.

Since Phase 6 a page is a shell that loads its bundle and style sheets from dist/webview/ by URI. Every harness, and the mocha suites through src/test/webviewPage.ts, passes the page through test/harness/loadPage.js, which reads each file the page names under the repository’s root and inlines it, so each harness’s npm script runs npm run build:webview after npm run compile-tests, and a bundle not built fails with the URI it named. Those paths are written by the shells’ own code (src/ui/webview/host/pageShell.ts) and by esbuild.js, so a page moved under src/webview keeps them in step without any harness edit.

Distinct out/ modules

The catalog names 50 modules. The harnesses take something from 38 of them in 13 files. test/perf/indexSpeed.js loads its twelve through load('…'), which resolves the name through the catalog’s pathOf. src/test/extension.test.ts reads two more compiled files as text, out/extension.js and out/composition/services.js, listed under “Reads by path in src/test” below.

Every source file behind these 38 modules exists at the end of Phase 7, as does every one the catalog names. Twelve catalog entries have no harness user: preferences (core/storage/preferences.js), components, guide, and the nine page shells from calendarHtml to taskBoardHtml. The page shells reach the harnesses through test/pages.js. components lost its one user in Phase 6, when test/ui/verifyWebviews.js stopped taking getZenCss from it and began reading src/webview/shared/zen.css by path (see “Reads by path” below).

“Breaks” means the catalog entry must follow the move, and until it does every harness that names it fails.

“Degrades silently” means the harness does not fail. load() in test/perf/indexSpeed.js:39-48 returns {} when a module is not found, and the run prints a dash for a step it cannot measure, the mark it uses for a step the code cannot do yet. It guards 19 of its 23 loads: the cache (SearchStore, line 226), the codec (138), the timing log (152, and measure in each snapshot timing), and every module the snapshot timings Phase 6 added load (lines 321 to 539, each guarded by its own if (!…)). A move of searchStore.js makes it time every start without the cache, with no warning; a move of timing.js blanks every snapshot timing; a move of any module the snapshot timings load blanks that timing alone. npm run bench:index is not a test suite, so nothing fails. The loads of the parser, the indexer, the scanner, and the graph state are used without a guard, and the run stops with a TypeError. The run also takes WorkspaceIndexer from indexer.js for an older checkout; that export is gone, and the run builds through createWorkspaceIndex (line 232). Since Phase 7 it takes buildWorkspaceIndex from indexState.js, and the graph state is three loads spread into one object (graphBuild, graphChanges, notesGraphState, line 53), so a move of graphChanges.js blanks the save check alone, while a move of notesGraph.js stops the run as the graph state’s did.

The export names in the third column are part of the same contract. Renaming an export breaks the harness just as moving its file does.

Compiled-tree roots

These check that out/ or dist/ exists before they run, or join paths onto them. A move inside src/ does not affect them. A change to outDir, or to where esbuild.js writes the page bundles, does.

Paths between harness files

A move under src/ leaves these alone. They break when a harness file moves.

Six files under src/test import harness files through the compiler: webviewPage.ts (loadPage, domRecorder), page-loader.test.ts (loadPage), components-primitives.test.ts (domGoldens), and webview-query-editor.test.ts, webview-search.test.ts, and webview-tasks.test.ts (domSnapshot; these three test the page-script builders being deleted at the end of Phase 6), each as ../../test/harness/… with a .d.ts beside the harness file. The compiler checks those paths, but the compiled copy resolves them from out/test/, so they also break if outDir changes depth.

Reads by path in src/test

Most of src/test imports through TypeScript, which the compiler checks. These places build a path at runtime instead. Each assumes that its compiled copy sits exactly at out/test/<name>.js, two levels below the repository, as the comment at src/test/changelog.test.ts:25 says. Moving one of them into a subfolder of src/test breaks it.

test/ui/verifyWebviews.js:33 reads src/webview/shared/zen.css by path, from the repository’s root, to compare it with what each zen page draws. It breaks if the sheet moves.

.vscode-test.mjs:4 runs out/test/**/*.test.js. A subfolder of src/test is still found. A test placed beside its source, outside src/test, is not run, and nothing reports that it was skipped. test/harness/runUnitSuites.js runs the test:unit suites from the same out/test files.

Constructor signatures and arguments

Every panel and view host the harnesses build takes one options object, so a reordering does not break a call; a renamed or newly required key does, and the compiler does not check any of these calls. createCalendar, createSidebarSnapshot, createDeckardStatsSnapshot, createSearchPageSnapshot, and createDashboardWidgets still take positional arguments.

test/ui/checkLayout.js, checkDom.js, checkVisual.js, checkRenderedContrast.js, and checkContrast.js all take createSurfaces() from test/ui/surfaces.js:293, so the surfaces.js rows pin all five checks.

Reaching into internals

Every e2e suite also reads the stub’s own hooks, such as vscode._test, panel._toWebview, panel._deliver, panel._onWebviewMessage, panel._setVisible, and host._fromWebview. Those belong to test/e2e/vscodeStub.js, not to the source, so a source move does not affect them.

3. scripts/

Each script finds the repository as its own parent folder, so moving a script breaks it. The four .mjs scripts are run from package.json lines 2312-2316. changelog.js is run by the release workflows.

scripts/capture-dashboard-screenshot.mjs

It builds the extension, launches a real VS Code on a temporary workspace, runs Deckard commands through a companion extension, and captures the README and walkthrough screenshots. The command ids and settings it uses are cross-referenced in the manifest inventory.

The other four scripts

scripts/changelog.js does not import src/core/changelog.ts. The two share a file format. The script writes CHANGELOG.md, and parseChangelog in src/core/changelog.ts reads the shipped copy at runtime for Home and Help. src/test/changelog.test.ts ties them together: it imports ../core/changelog at line 11 and requires the script by path at line 27. A move of src/core/changelog.ts is caught by the compiler in that import. A move of the script breaks the test, prepare-release.yml:115, and release.yml:68 and :131.

4. Build, packaging, and CI configuration

No workflow names a src/, out/, or dist/ path.

5. .vscode/ and development/

The repository tracks one file under .vscode/ and only notes under development/. The primary checkout also holds four untracked files, ignored by the owner’s global gitignore rather than by .gitignore. They are listed so a reader knows they exist, but a fresh clone does not have them.

The plan calls development/ “a fixture workspace with its own settings”. At 1805a01 the repository holds only its 51 notes. The settings file, development/.vscode/settings.json, is untracked and exists only in the primary checkout.

In a fresh clone there is no tasks.json. The npm: watch label that launch.json needs then comes from VS Code’s npm task detection.

How to regenerate

Run these from the repository root in bash. Each prints file:line:match, or a count.

Section 1, current docs:

git grep -nIoE '(^|[^A-Za-z0-9_./-])(src|out|dist)/[A-Za-z0-9_.*/-]*' -- '*.md' ':!docs/implementation/**'
git grep -nIoE '(^|[^A-Za-z0-9_./-])test/(ui|e2e|perf)/[A-Za-z0-9_./*-]*' -- '*.md' ':!docs/implementation/**'
git grep -nIE '(src|out|dist)/[A-Za-z0-9_./-]+:[0-9]' -- '*.md' ':!docs/implementation/**'

Section 1, docs/implementation/, citations per file:

for f in docs/implementation/*.md; do
  printf '%s %s\n' "$f" "$(git grep -hIoE '(^|[^A-Za-z0-9_./-])(src|out|dist)/[A-Za-z0-9_.*/-]*' -- "$f" | wc -l)"
done

Section 2:

grep -rnoE '\.\./\.\./out/[A-Za-z0-9_./-]+\.js' test
grep -nE "^  [A-Za-z]+: '[^']+'," test/harness/modules.js
grep -rnoE "modules\.[A-Za-z]+|require\('\.\./harness/modules\.js'\)\.[A-Za-z]+" test | grep -v '^test/harness/modules.js' | grep -v ':modules\.js$'
grep -rnE "require\(path\.join\((compiled|out)\b" test
grep -noE "load\('[^']+'\)" test/perf/indexSpeed.js
grep -rnE "'out'|\"out\"" test
grep -rnE "__dirname|path\.join\(root, 'out'" src/test
grep -rnE "require\('\./|require\('\.\./harness/|require\(path\.join\(__dirname" test
grep -rnE 'new (DashboardPanel|SidebarNotesView|TaskBoardPanel|SearchPanels|StatsPanel|NotesGraphPanel|CalendarView|CalendarPanel|EditorTagDecorations|WorkspaceScanner|SearchStore)\b|\b(createPreferences|createWorkspaceIndex)\(' test
grep -nE 'create(TaskBoard|SidebarSnapshot|Calendar|DeckardStatsSnapshot|SearchPageSnapshot|DashboardSnapshot|DashboardWidgets|NotesGraphSnapshot)\(' test/ui/surfaces.js test/perf/indexSpeed.js
grep -rnE 'loadPage|dist/webview' test/harness test/e2e/vscodeStub.js src/test/webviewPage.ts
grep -rnE "from '\.\./\.\./test/" src/test

Section 3:

grep -nE "src/|esbuild\.js|deckard\.[A-Za-z.]+|workbench\.view|development|docs/images|resources/|CHANGELOG" scripts/*.mjs scripts/*.js

Sections 4 and 5:

grep -nE "src/|out|dist" esbuild.js tsconfig.json .vscode-test.mjs .vscodeignore .gitignore .vscode/launch.json eslint.config.mjs
grep -nE '"main"|"(vscode:prepublish|compile|watch|package|pretest|check-types|lint|test|bench|capture)[^"]*":' package.json
grep -nE "src/|out/|dist/|scripts/|test/|docs/|npm (run|test)" .github/workflows/*.yml
grep -rn "__dirname" src | grep -v '^src/test/'
git ls-files .vscode development | grep -v '^development/notes/'

What to check after each phase

Run these in bash from the repository root. Checks 1 to 5 print nothing while the inventory still holds.

1. Every src/ path the current docs cite still exists:

   git grep -hIoE '(^|[^A-Za-z0-9_./-])(src|out|dist)/[A-Za-z0-9_.*/-]*' -- '*.md' ':!docs/implementation/**' | sed -E 's#^[^A-Za-z0-9_./-]##; s#[.]$##; s#/$##' | sort -u | while read -r p; do compgen -G "$p" >/dev/null || echo "stale: $p"; done
   

2. Every out/ module the harnesses load exists, after npm run compile-tests:

   { grep -rhoE '\.\./\.\./out/[A-Za-z0-9_./-]+\.js' test | sed 's#^\.\./\.\./##'; grep -oE "load\('[^']+'\)" test/perf/indexSpeed.js | sed -E "s#load\('([^']+)'\)#out/\1#"; echo out/extension.js; } | sort -u | while read -r p; do [ -f "$p" ] || echo "missing: $p"; done
   

   Since Phase 0 the harnesses load through the catalog, so the check above finds no ../../out/ path, and it reads the perf run’s load('…') names as paths, so it reports those it loads as missing. This one checks every catalog entry, and, as of Phase 6, the harnesses load nothing by path:

   { grep -oE "^  [A-Za-z]+: '[^']+'" test/harness/modules.js | sed -E "s#.*'([^']+)'#out/\1#"; } | sort -u | while read -r p; do [ -f "$p" ] || echo "missing: $p"; done
   

3. Every src/ path that esbuild.js and the scripts name still exists:

   grep -ohE "'src/[^']+'" esbuild.js scripts/*.mjs | tr -d "'" | sort -u | while read -r p; do [ -f "$p" ] || echo "missing: $p"; done
   

4. Every deckard.* id the screenshot script uses is still in package.json:

   for id in $(grep -ohE 'deckard\.[A-Za-z]+(\.focus)?' scripts/capture-dashboard-screenshot.mjs | sort -u); do grep -q "\"${id%.focus}\"" package.json || echo "missing: $id"; done
   

5. Every src/test file that climbs two folders to the root still sits directly in src/test:

   git grep -lE "__dirname, '\.\.', '\.\.'|__dirname, '\.\./\.\./" src/test | grep -v '^src/test/[^/]*$'
   

6. The suites that load these paths still pass, gated on their exit codes: npm test, npm run test:ui, npm run test:e2e, npm run test:layout, and npm run test:visual. Then run npm run bench:index and confirm that no row which printed a number at 1805a01 now prints a dash.