Add advisory test-surface cues to simplicity guidance - #3
Merged
Merged
Conversation
Record authoring questions and junk-pattern evidence for weak verification theater without a new skill or coverage gate. Co-authored-by: Dennis Geldmacher <geldmacher.dennis@outlook.de>
geldmacher
marked this pull request as ready for review
September 24, 2026 16:42
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Scope
Guidance only. A missing authoring answer means do not add that test yet; existing tests are not removed from the pattern name alone. The cues do not authorize creating, running, or deleting tests outside an approved change, and they do not add coverage or mutation gates.
Validation
npm run check:targets,npm run validate, andnpm run check:linkspassed. The full test suite passed when Git’s local URL rewrite was not applied to fixture remotes (100 tests). A plainnpm testin this environment fails those release-script cases becausegit remote get-urlrewritesgit@github.com:to a tokenized HTTPS URL; that failure is independent of this docs change.