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
Add root context7.json on the default staging branch so Context7 can verify ownership and read the reviewed prod configuration. The public verification identifier is not an API credential. Indexing stays on prod; the existing content-selection configuration is preserved.
CI repair
The first run on 22f7431 failed: the old CLI turned the root directory into an empty service name. Installation then failed on import-assertion syntax, and Sonar scanned the repository root without project settings.
Port the seven CI/loader files from reviewed prod commit 5327f93, plus its authorization Sonar project-key correction. All eight files match that commit byte-for-byte. The workflow change intentionally selects all eleven services. No application code or dependency files change. Release workflows are untouched.
Verification and merge gates
Independent review found the omitted Sonar correction; f6b39a5 includes it. All 35 dependency-free selector/differential tests pass locally. Actual service suites and Node22 loader checks still need to pass on this staging candidate, along with each Sonar analysis and quality gate. Prod results do not prove staging results.
Protected staging requires one approving GitHub review. The advisory agent review does not satisfy it. No bypass. Existing staging push workflows can build or publish, so their tag baseline and selected services must be checked before merge. The inherited mutable Sonar action reference remains a reproducibility risk, unchanged from prod.
Context7 claim and refresh remain pending. Completion also requires comparing fresh returned excerpts with current sources.
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
documentationImprovements or additions to documentation
2 participants
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.
melissa-lomray
added
the
documentation
Scope
Add root context7.json on the default staging branch so Context7 can verify ownership and read the reviewed prod configuration. The public verification identifier is not an API credential. Indexing stays on prod; the existing content-selection configuration is preserved.
CI repair
The first run on 22f7431 failed: the old CLI turned the root directory into an empty service name. Installation then failed on import-assertion syntax, and Sonar scanned the repository root without project settings.
Port the seven CI/loader files from reviewed prod commit 5327f93, plus its authorization Sonar project-key correction. All eight files match that commit byte-for-byte. The workflow change intentionally selects all eleven services. No application code or dependency files change. Release workflows are untouched.
Verification and merge gates
Independent review found the omitted Sonar correction; f6b39a5 includes it. All 35 dependency-free selector/differential tests pass locally. Actual service suites and Node22 loader checks still need to pass on this staging candidate, along with each Sonar analysis and quality gate. Prod results do not prove staging results.
Protected staging requires one approving GitHub review. The advisory agent review does not satisfy it. No bypass. Existing staging push workflows can build or publish, so their tag baseline and selected services must be checked before merge. The inherited mutable Sonar action reference remains a reproducibility risk, unchanged from prod.
Context7 claim and refresh remain pending. Completion also requires comparing fresh returned excerpts with current sources.