You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit df28bfb
Browse filesBrowse the repository at this point in the historyBrowse files
| Extension bundling |`src/esbuild.mjs` calls `copyPaths()` with an explicit source list. `packages/build/src/esbuild.ts` copies only those configured paths. | Root `README.md` and `CHANGELOG.md` are package inputs and remain outside the allowlist. No allowlisted documentation is copied. |
95
+
| VSIX packaging |`src/.vscodeignore` excludes everything, then includes the built extension, webview, assets, and release metadata. | Root `docs/`, `.github/`, and the four allowlisted root files are not packaged. |
96
+
| Webview and package builds |`webview-ui/vite.config.ts`, `apps/cli/tsup.config.ts`, and `packages/types/tsup.config.ts` select code entry points and assets. | No imports, raw-file loads, or asset rules select allowlisted documentation. |
97
+
| Tests and models | Vitest configurations select code tests. Searches covered `docs/`, current documentation basenames, Markdown imports, and filesystem readers. | Documentation references are comments, temporary repository files, mocked paths, or workspace examples. Tests do not read the checked-in allowlisted documents. |
98
+
| Turbo and Knip | Root and package Turbo files define package-local inputs. `knip.json` selects code entry points and projects. | No explicit input reaches the root documentation tree. Default package inputs can include package-local Markdown, which remains outside the allowlist. |
99
+
| Release validation |`.github/workflows/release-validation.yml` builds the extension and compares root `README.md` with the copied package README. | Release inputs retain full validation. The release workflow is unchanged. |
100
+
101
+
Generic runtime tools can read Markdown in a user's workspace. This does not
102
+
make repository documentation a build or test input. The audit found no reason
103
+
to narrow the current allowlist further. This is source-level evidence for the
104
+
current tree, not a guarantee about future consumers. A new documentation
105
+
reader must update the classification policy and its regression tests.
106
+
82
107
## Fail-safe behavior
83
108
84
109
| Input | Classification |
@@ -182,3 +207,20 @@ through the existing required `compile` context.
182
207
183
208
The repeated gate jobs remain explicit to keep workflow needs and check names
184
209
visible. Extracting a shared gate action is deferred to a separate refactor.
210
+
211
+
## Current verification and open work
212
+
213
+
No live docs-only PR run has confirmed the two platform check contexts yet.
214
+
Local workflow tests verify their names and wiring; this does not establish
215
+
GitHub's live check-reporting behavior.
216
+
217
+
`format-check` and all `validation-gate` jobs are not required checks in the
218
+
current ruleset. Formatting and policy-test failures block via required
219
+
`compile`. Making audit-gate failures block directly still requires a separate
220
+
ruleset update. The gate reads job results and cannot observe step-level gating
221
+
inside `compile` or `unit-test`; workflow tests pin those step conditions.
222
+
223
+
All label changes currently start all five workflows and may cancel in-flight
224
+
PR validation, including mutation testing. This runner-time cost is accepted
225
+
for now to keep override event handling simple and consistent. A shared gate
226
+
action and broader Stryker integration remain follow-ups.
0 commit comments