[efraespada]

RepoWise now runs only when a maintainer dispatches it, reducing routine CI runner demand while keeping on-demand analysis and its reports available. CI and merge queue checks no longer depend on RepoWise.

What changed

• Restricted RepoWise to manual dispatch with GitHub’s native branch selection and per-ref cancellation.
• Preserved bounded scans, cleanup, and report publication; the summary and artifact identify the analyzed commit and scan status.
• Updated workflow contract checks, operator documentation, the merge-queue SDD, and catalog evidence for the manual workflow.
• Recorded live protection evidence showing CI Check remains required on master and develop, with no RepoWise requirement to remove.

Validation

• Final head 3ede9d17ec5a92b9196f0d947f91d17b29e13ecc: CI Check and the full Ubuntu, Windows and macOS coverage/package/contract matrix passed.
• Manual RepoWise run passed; its job took 20m 37s. Verified the exact head SHA in both the rendered Job Summary and revision.txt, and inspected the uploaded Markdown/JSON health reports and index log in the report artifact.
• The existing advisory boundaries remained effective: dead-code reached its 90-second timeout (exit 124); full-history security reported MemoryError under the 2 GiB limit (exit 1). Both are explicitly recorded as incomplete in the summary, warnings and advisory-status.txt; completed health reports were retained. This run does not establish a complete historical security audit.
• 274 workflow-contract cases, typecheck, lint, workflow/documentation/specification validators, npm package validation/smoke and Graphify update passed locally. The full local suite passed 11,128 cases; all 39 loopback cases blocked by the local network sandbox passed when rerun with loopback access.
• Live effective rules for master and develop, plus develop classic protection, require only CI Check; master has no classic protection. No rules were changed. The final-head run inventory contains only the explicitly dispatched RepoWise run and no automatic RepoWise PR/push run; merge-group support remains enforced for the actual automatic check producers.

Closes #639

[docs-page]

To preview the documentation for this pull request, visit the following URL:

docs.page/vypdev/copilot~641

Documentation is deployed and generated using docs.page

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.10%. Comparing base (274db40) to head (3ede9d1).
⚠️ Report is 1557 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop     #641      +/-   ##
===========================================
+ Coverage    90.94%   94.10%   +3.16%     
===========================================
  Files          135      950     +815     
  Lines         6251    30548   +24297     
  Branches      1338     8965    +7627     
===========================================
+ Hits          5685    28748   +23063     
- Misses         172      704     +532     
- Partials       394     1096     +702     

see 1017 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[vypbot]

Bugbot: review complete

Current status: No active findings on eb97eee.

Pull request · Verified commit · Workflow run

[vypbot]

Copilot approval · Human review needed

Status: A protected workflow, policy, or trust-boundary file changed.
Completed: 1/1 observed checks succeeded; Bugbot unverified.
Action required: Ask a human reviewer to decide.
Impact: No new approval is confirmed for this revision.
See checks

Technical evidence

Revision: 3ede9d17ec5a; base: 6ecf1f418b01; reason: protected-path.