Repository navigation
chore: repair documentation checks and record maintenance evidence - #1
Merged
Merged
Conversation
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
1 participant
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.
Repair formatting failures, refresh documentation tooling and lockfile, and align CI with the supported Node release. Add a scoped maintenance record with validation evidence, exclusions, unresolved dependency findings, and a repeatable PR workflow.
Validation
npm run lint passed (Markdown and Prettier). npm audit reports no high/critical findings, with 3 moderate and 3 low transitive findings remaining. Local checks ran on Node 24.14 with engine warnings; CI uses the supported Node 22 line.
Scope
Organisation-owned public repository only. Changes are proposed on a focused branch; no default-branch push or deployment.