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
ci: validate service checks and document package boundaries - #214
Document the eleven service-package boundaries and Context7 retrieval scope. Repair the CI failure exposed by a root-only documentation change: the old selector generated an empty-named service and its dispatcher could not load on the runner.
The dependency-free selector validates the event base/head and immutable merge SHA, inventories that same merge tree, and supplies its SHA to both service and Sonar jobs. Root docs yield an explicit empty list; shared tooling selects all services. Direct per-service npm commands preserve the previous install/lint/types/test commands. No service source, dependency locks, release workflows or Sonar credentials changed.
Independent review found a head-versus-merge coverage mismatch and an inventory-root symlink gap; both are repaired with regression tests. Local Node20: 17 selector tests, docs checker, syntax and YAML checks pass. This CI-changing PR must run all eleven services. Real Node22 service checks and Sonar remain CI gates, not claims made by the local fixtures. No external-index refresh or recommendation uplift is established. Protected prod approval remains required.
The first real eleven-service matrix exposed a blog test-bootstrap error in rewiremock through Mocha's native-import path. This candidate keeps Node22 and the existing service tests, scopes --no-experimental-strip-types to test steps, and adds real-loader positive/negative controls. Independent local review found no blocking code defect, but did not establish Node22 causality or service-suite success.
The blog job now runs a strict enabled/disabled Node22.23.2 differential with exact child/error/count checks; unexpected failures fail the experiment. Each service logs installed loader resolution paths. Code-matrix fail-fast is disabled so a failing service does not cancel the others; every required test remains required. Local Node20 evidence: loader controls 3/3, selector 17/17, differential-validator controls 18/18, docs and whitespace checks pass. These are not Node22 or application integration results. The ESM failure control characterizes the currently locked dependency stack and needs reassessment with future runtime/dependency upgrades.
No application source, manifests, lockfiles, Sonar configuration or branch protection changed. Sonar's JRE-metadata/token error is unresolved; the repository secret exists, but its validity is unknown. Required human review and successful real service/Sonar checks remain merge gates. This is an authorized CI experiment, not a verified fix or a release.
Run 35725306701 tested merge 087af88b3511724ac53955cf7bc402a22203f8c0 on measured Node 22.23.2. The selector, PR title and all eleven code-check jobs passed. Full code-job logs confirm install, lint, types, loader controls and each real service suite. Blog also passed the exact enabled/disabled Node22 loader differential and its separate 16-test service suite.
The earlier enabled-mode TAP-count diagnostic defect in 883c2c8 was repaired in 09d182a; the full differential now ran in actual CI, not merely synthetic tests. This does not establish production integration.
Overall CI remains failed: Sonar fails during JRE provisioning with a sonar.token/SONAR_TOKEN diagnostic, before analysis. Repository secret SONAR_CLOUD_TOKEN exists, but its validity and project permissions are not established. No Sonar gate was removed. Required human approval also remains outstanding.
melissa-lomray
changed the title
docs: clarify verified usage and retrieval scope
ci: validate service checks and document package boundaries
Sep 22, 2026
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
bugSomething isn't workingdocumentationImprovements 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
Document the eleven service-package boundaries and Context7 retrieval scope. Repair the CI failure exposed by a root-only documentation change: the old selector generated an empty-named service and its dispatcher could not load on the runner.
The dependency-free selector validates the event base/head and immutable merge SHA, inventories that same merge tree, and supplies its SHA to both service and Sonar jobs. Root docs yield an explicit empty list; shared tooling selects all services. Direct per-service npm commands preserve the previous install/lint/types/test commands. No service source, dependency locks, release workflows or Sonar credentials changed.
Independent review found a head-versus-merge coverage mismatch and an inventory-root symlink gap; both are repaired with regression tests. Local Node20: 17 selector tests, docs checker, syntax and YAML checks pass. This CI-changing PR must run all eleven services. Real Node22 service checks and Sonar remain CI gates, not claims made by the local fixtures. No external-index refresh or recommendation uplift is established. Protected prod approval remains required.
Node22 test-loader candidate (883c2c8)
The first real eleven-service matrix exposed a blog test-bootstrap error in rewiremock through Mocha's native-import path. This candidate keeps Node22 and the existing service tests, scopes
--no-experimental-strip-typesto test steps, and adds real-loader positive/negative controls. Independent local review found no blocking code defect, but did not establish Node22 causality or service-suite success.The blog job now runs a strict enabled/disabled Node22.23.2 differential with exact child/error/count checks; unexpected failures fail the experiment. Each service logs installed loader resolution paths. Code-matrix fail-fast is disabled so a failing service does not cancel the others; every required test remains required. Local Node20 evidence: loader controls 3/3, selector 17/17, differential-validator controls 18/18, docs and whitespace checks pass. These are not Node22 or application integration results. The ESM failure control characterizes the currently locked dependency stack and needs reassessment with future runtime/dependency upgrades.
No application source, manifests, lockfiles, Sonar configuration or branch protection changed. Sonar's JRE-metadata/token error is unresolved; the repository secret exists, but its validity is unknown. Required human review and successful real service/Sonar checks remain merge gates. This is an authorized CI experiment, not a verified fix or a release.
Verified CI follow-up on 09d182a
Run 35725306701 tested merge
087af88b3511724ac53955cf7bc402a22203f8c0on measured Node 22.23.2. The selector, PR title and all eleven code-check jobs passed. Full code-job logs confirm install, lint, types, loader controls and each real service suite. Blog also passed the exact enabled/disabled Node22 loader differential and its separate 16-test service suite.The earlier enabled-mode TAP-count diagnostic defect in 883c2c8 was repaired in 09d182a; the full differential now ran in actual CI, not merely synthetic tests. This does not establish production integration.
Overall CI remains failed: Sonar fails during JRE provisioning with a sonar.token/SONAR_TOKEN diagnostic, before analysis. Repository secret SONAR_CLOUD_TOKEN exists, but its validity and project permissions are not established. No Sonar gate was removed. Required human approval also remains outstanding.