Repository navigation
Name the Forbidden VS Code Files Without a Path the Dead-Path Gate Reads - #3530
Conversation
"Editor and Tasks" named `.vscode/settings.json` to forbid it, and the prose gate's dead-path rule reads a path git once tracked and the tree no longer holds as a stale mention. Every carrier that ever deleted that file therefore failed the gate on a re-vendor of this verbatim section. Naming the files by basename under `.vscode/` states the same rule in a form the gate does not read as a path. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
A recorded local strict-review pass covers head |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
There was a problem hiding this comment.
🟢 Approval recommended
No unresolved review issues were identified, and the policy is preserved while avoiding false-positive dead-path findings.
No open issues 🎉
What changed in this PR
This pull request updates the canonical governance wording so forbidden VS Code files do not trigger false-positive dead-path findings in downstream repositories.
Changes:
- Names
settings.jsonandextensions.jsonby basename under.vscode/. - Preserves the existing prohibition and
.code-workspaceconfiguration policy. - Keeps the wording compatible with the existing prose gate.
| File | Description |
|---|---|
GOVERNANCE.md |
Adjusts the verbatim Editor and Tasks guidance to avoid false-positive dead-path findings. |
Review effort: Lite
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #3530 +/- ##
========================================
Coverage 81.58% 81.58%
========================================
Files 26 26
Lines 8972 8972
========================================
Hits 7320 7320
Misses 1652 1652
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
…n-Config Python (#3535) ## Summary Promotes `develop` to `main`: - #3530: `GOVERNANCE.md` "Editor and Tasks" names the forbidden VS Code files by basename under `.vscode/`. A carrier that once deleted `.vscode/settings.json` can then re-vendor the section without the prose gate's `dead-path` rule refusing it. This fixes the defect #1612 describes (that issue is closed and is referenced here, not closed by this PR). - #3532: HomeAutomation-Config's registry entry declares `python`, its eight `pythonDirectories`, and `CODECOV_TOKEN`, with a driftNote recording the maintainer's decision. The pre-commit hooks rollout tracker rows are updated to match. Closes #2255 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Summary
Answers #1612. The issue closes on the promotion pull request.
GOVERNANCE.md"Editor and Tasks" named.vscode/settings.jsonand.vscode/extensions.jsonto forbid them. The prose gate'sdead-pathrule reads a backtick span containing a/as a path. It reports that path when git once tracked it and the tree no longer holds it. So every carrier that ever deleted.vscode/settings.jsonfailed the gate as soon as a re-vendor touched the line. This section isverbatim, so the carrier cannot reword it and is held at an old revision.The sentence now names the files by basename "under
.vscode/". The rule is unchanged.path_candidatedrops a span with no/, and.vscode/has no file-shaped last segment, so neither span reaches the deletion check.Verification
A throwaway repository commits
.vscode/settings.jsonand then deletes it. In that repository,prose_lint.py --check dead-path:GOVERNANCE.md:GOVERNANCE.md:354: dead-path: path '.vscode/settings.json' is deleted from this tree, exit 1GOVERNANCE.md: no finding, exit 0The full prose gate on
GOVERNANCE.mdandspec/validate.pyboth pass.🤖 Generated with Claude Code