scip-query 0.10.3 → 0.10.5

package/skills/scip-verify/SKILL.md

@@ -1,307 +1,158 @@
 ---
 name: scip-verify
-description: Post-implementation verification using scip-query. Confirms changes are wired correctly — no broken references, no new cycles, no orphaned code, no structural regressions, no health regressions. Run after making changes and before committing.
-allowed-tools: [Bash, Write, Edit, Glob, Agent, TaskCreate, TaskUpdate, TaskGet, TaskList]
-keywords: [verify, check, validate, wire, confirm, post-implementation, review, regression, health]
+description: Post-implementation verification using scip-query's modern gate model. Use after making code, docs, config, refactor, cleanup, or setup changes; before committing; when the user asks whether a change is wired correctly, safe, verified, regression-free, or ready to ship.
 ---
 
 # Post-Implementation Verification with scip-query
 
-You are verifying that a code change was implemented correctly. Every check must use `scip-query` to confirm the change didn't break references, introduce cycles, orphan code, or widen structural risk unexpectedly. This is the "measure twice" step — run it after making changes, before committing.
-
----
-
-## When to Use This Skill
-
-- "Verify my changes"
-- "Check if everything is wired correctly"
-- "Did I break anything?"
-- "Is it safe to commit?"
-- "Run a post-implementation check"
-- After completing a `/concrete-plan` implementation
-- Before any commit of non-trivial changes
-
----
+Verify the actual diff, not your intention. A verification pass proves that the current workspace has a runnable scip-query environment, a current index, expected blast radius, no diff-gate findings, and no relevant health or config regression.
 
 ## Hard Rules
 
-1. **Reindex first.** Always run `scip-query reindex` before verification. You're checking the current code, not the old index.
-
-2. **Every check must produce evidence.** Don't say "looks good." Say "scip-query cycles returned 0 cycles, scip-query diff-impact shows 3 changed symbols affecting 12 files, and change-surface shows the blast radius stayed within expectations."
-
-3. **Fail loudly.** If any check fails, stop and report the exact failure with the scip-query command output. Do not proceed to "looks mostly fine."
-
-4. **Compare against baseline.** If a health score or finding count was recorded before the change, compare against it. A regression is a finding.
-
----
-
-## Symbol Lookup Tips
-
-`scip-query` accepts partial symbol names — you don't need the full SCIP symbol path. These all work:
-
-```bash
-scip-query code processVegaMention              # just the function name
-scip-query call-graph ChatService               # just the class name
-scip-query trace getActiveInferenceConfig       # any unique substring
-```
+1. Run environment checks before trusting graph facts.
+2. Reindex before final verification unless a just-finished command already did so and no files changed afterward.
+3. Treat `scip-query diff-gate --json` as the primary blocker for diff-specific risk. Manual checks are drill-down evidence, not a replacement.
+4. Run the postchecks that match the actual change type.
+5. Prefer fixing findings. Use `scip-query suppress <id> --reason "<specific reason>"` only for intentional design, compatibility shims, framework entry points, or accepted false positives with durable evidence.
+6. If `.scipquery.json` or suppressions changed, run `scip-query config-validate`.
 
-**Avoid parentheses** — `()` causes shell parse errors in zsh/bash:
-```bash
-# BAD — shell tries to execute a subshell
-scip-query code processVegaMention()
+## Default Verification Flow
 
-# GOOD — no parens needed, scip-query strips them internally
-scip-query code processVegaMention
+### 1. Prove the workspace can answer
 
-# ALSO GOOD — single quotes protect special characters
-scip-query code 'processVegaMention'
-```
-
-**Read source by file + line range** when the symbol name is ambiguous:
 ```bash
-scip-query code 'src/modules/chat/chat.service.ts:100-200'
+scip-query doctor
+scip-query status --capabilities
 ```
 
-**If "Symbol not found":**
-1. Try a shorter/simpler name — `login` instead of `AuthService:login`
-2. Try `scip-query outline <file>` to see what symbols exist in the file
-3. Try `scip-query trace <name>` which uses a different lookup path
-4. Use the `file:line-line` syntax for `code` if you know the location
-
----
-
-## The 7 Verification Checks
-
-Run every one of these. Each catches a different class of implementation error.
+If either command reports missing indexers, stale indexes, invalid config, or unavailable capabilities relevant to the change, resolve that first or report it as a blocker. Unavailable is not clean; it means that signal class was not proven.
 
-### Check 1: Diff Impact Assessment
+### 2. Refresh and assess the diff
 
 ```bash
 scip-query reindex
-scip-query diff-impact
+scip-query diff-impact --json
 ```
 
-**What you're checking:** Which symbols changed and how many downstream consumers are affected.
+Use `diff-impact` to check whether the changed files, changed symbols, and downstream consumers match the work you intended to do. Unexpected symbols or a much wider blast radius are findings even if `diff-gate` later passes.
 
-**Pass criteria:**
-- Every changed symbol is intentional (no accidental modifications)
-- The number of affected consumer files matches expectations
+### 3. Run routed postchecks
 
-**Fail if:** Unexpected symbols appear in the diff, or the affected file count is much larger than expected (blast radius exceeded plan).
+Run every row that applies to the work just performed.
 
-### Check 2: No New Cycles
+| Change type | Required checks |
+|---|---|
+| Extracted a helper or created an abstraction | `scip-query incomplete-migration --json --full` |
+| Added a new helper, module, component, or adapter | `scip-query similar <symbol> --json --full` and `scip-query recent-duplicates --json --full` |
+| Added parameters, options, or config flags | `scip-query unused-params --json --full` |
+| Added a forwarding or wrapper layer | `scip-query wrapper-candidates --json --full` and `scip-query passthrough-candidates --json --full` |
+| Added an interface, base class, adapter contract, or type alias | `scip-query stale-abstractions --json --full` |
+| Changed schema, config, generated artifacts, or public contracts | `scip-query co-change <file> --json --full` |
+| Changed code described by docs or changed docs that cite code | `scip-query doc-drift --json --full` |
+| Deleted code | `scip-query cleanup-plan --verify --json` |
+| Changed React components or hooks | `scip-query react-component-duplicates --json --full`, `scip-query react-hook-candidates --json --full`, and `scip-query react-large-component-pressure --json --full` |
+| Changed Vue SFCs or composables | `scip-query vue-component-duplicates --json --full`, `scip-query vue-composable-candidates --json --full`, and `scip-query vue-large-view-pressure --json --full` |
+
+Use focused probes when a finding needs explanation:
 
 ```bash
-scip-query cycles
+scip-query code <symbol-or-file>
+scip-query refs <symbol>
+scip-query fan-in <symbol>
+scip-query fan-out <symbol>
+scip-query affected <symbol> --json
+scip-query change-surface <file> --json --full
 ```
 
-**What you're checking:** The change didn't introduce a circular dependency.
-
-**Pass criteria:** Zero cycles, OR the same cycles that existed before the change.
-
-**Fail if:** New cycle(s) appear. Report the full cycle path.
-
-### Check 3: No New Dead Code
+### 4. Run the gate
 
 ```bash
-scip-query dead --min-loc 5
+scip-query diff-gate --json
 ```
 
-**What you're checking:** The change didn't orphan existing code. If you renamed a function, did you update all callers? If you moved a module, did you update all imports?
-
-**Pass criteria:** No new dead symbols compared to before the change. Existing dead code doesn't count.
-
-**Fail if:** A symbol that was alive before the change is now dead. This means something was disconnected.
-
-### Check 4: No New Isolated Symbols
+On any finding, fix it or explicitly accept it with evidence. Do not ignore a nonzero gate. If a suppression is the right outcome, record the reason and validate config:
 
 ```bash
-scip-query isolated --min-loc 3
+scip-query suppress <id> --reason "<specific reason>"
+scip-query config-validate
 ```
 
-**What you're checking:** The change didn't completely disconnect a symbol from the graph.
-
-**Pass criteria:** No new isolated symbols.
-
-**Fail if:** New isolated symbol(s) appear — something got orphaned.
+### 5. Check baseline health when present
 
-### Check 5: References Intact
-
-For each symbol that was modified (from diff-impact), verify it's still referenced by the expected consumers:
+Run this when the repository has a committed scip-query baseline:
 
 ```bash
-scip-query refs <changed-symbol>
-scip-query fan-in <changed-symbol>
+scip-query health --baseline
 ```
 
-**What you're checking:** Consumers of modified symbols still reference them. If you changed a function signature, callers should still compile and reference it.
-
-**Pass criteria:** Fan-in count for each changed symbol is the same or higher than before.
-
-**Fail if:** A changed symbol's fan-in dropped — a consumer was disconnected.
-
-### Check 6: Change Surface Risk Check
-
-For each modified file:
+If no baseline exists and the user asked for broad health verification, run:
 
 ```bash
-scip-query change-surface <modified-file>
+scip-query health --json --full
 ```
 
-**What you're checking:** High-risk symbols in modified files based on consumer count, blast radius, and structural exposure.
+Health score changes are diagnostic, not the objective. A score drop matters when it corresponds to a real new signal; a score increase does not excuse unverified behavior.
 
-**Pass criteria:** No unexpectedly high-risk surfaces, or all high-risk symbols were intentionally modified with the blast radius understood.
+### 6. Validate config and docs when touched
 
-**Fail if:** A HIGH RISK symbol was modified without acknowledging the blast radius or downstream consumers.
-
-### Check 7: Health Score
+If `.scipquery.json`, AGENTS.md, CLAUDE.md, command docs, or skill instructions changed, run the relevant check:
 
 ```bash
-scip-query health
+scip-query config-validate
+scip-query doc-drift --json --full
 ```
 
-**What you're checking:** The overall codebase health didn't regress.
-
-**Pass criteria:** Health score is the same or higher than before the change. If it dropped, every finding that increased must be explained.
-
-**Fail if:** Health score dropped by more than 5 points without explanation.
-
----
-
-## Verification Workflow
+For generated command docs, also run the repo's descriptor or docs test if one exists.
 
-### Phase 1: Reindex and Assess Impact
+If you are maintaining scip-query analyzers or command descriptors inside the scip-query repository itself, add:
 
 ```bash
-scip-query reindex
-scip-query diff-impact
+scip-query self-audit
 ```
 
-Record: changed files, changed symbols, affected consumers, and any unexpectedly large blast-radius surfaces.
+This is a maintainer check for analyzer consistency, not a general app-developer verification step.
 
-### Phase 2: Structural Checks (parallel)
+## Manual Drill-Down Checks
 
-Run checks 2-4 simultaneously — they're independent:
+Use these when `diff-impact`, routed postchecks, or `diff-gate` point to a structural risk:
 
 ```bash
 scip-query cycles
-scip-query dead --min-loc 5
-scip-query isolated --min-loc 3
-```
-
-### Phase 3: Per-Symbol Checks
-
-For each changed symbol from diff-impact:
-
-```bash
-scip-query refs <symbol>
-scip-query fan-in <symbol>
-```
-
-### Phase 4: Per-File Checks
-
-For each modified file:
-
-```bash
-scip-query change-surface <file>
-```
-
-### Phase 5: Health Comparison
-
-```bash
-scip-query health
+scip-query dead --json --full
+scip-query isolated --json --full
+scip-query coupling
+scip-query bottlenecks
 ```
 
-Compare against the pre-change score.
-
----
+These commands are not a substitute for `diff-gate`; they explain or bound the finding.
 
-## Output Format
+## Verification Report
 
-The verification report is structured as:
+End with a compact report:
 
 ```markdown
-# Verification Report
-
-**Date:** YYYY-MM-DD
-**Change:** [description]
-**Pre-change health:** N/100
-**Post-change health:** N/100
-
-## Diff Impact
-- Changed files: N
-- Changed symbols: N
-- Affected consumer files: N
-- High-risk symbols touched: N
-
-## Check Results
-
-| # | Check | Result | Evidence |
-|---|---|---|---|
-| 1 | Diff impact | PASS/FAIL | [summary] |
-| 2 | No new cycles | PASS/FAIL | [count] |
-| 3 | No new dead code | PASS/FAIL | [count] |
-| 4 | No new isolated | PASS/FAIL | [count] |
-| 5 | References intact | PASS/FAIL | [fan-in changes] |
-| 6 | Risk assessment | PASS/FAIL | [high-risk symbols] |
-| 7 | Health score | PASS/FAIL | [score delta] |
-
-## Failures
-[Detailed explanation of any failures with scip-query output]
-
-## Verdict
-PASS — safe to commit
-FAIL — [list what needs fixing before commit]
-```
-
----
-
-## Using with /concrete-plan
-
-The ideal workflow:
+Verification: PASS/FAIL
 
-1. **Before:** Run `/concrete-plan` to design the change with full scip-query evidence
-2. **During:** Implement the plan
-3. **After:** Run `/scip-verify` to confirm the implementation matches the plan
+Environment:
+- doctor: PASS/FAIL
+- status capabilities: PASS/FAIL or unavailable checks
 
-The verification report should reference the original plan's blast radius predictions and confirm they were accurate.
+Diff:
+- changed files/symbols from `scip-query diff-impact --json`
+- unexpected blast radius, if any
 
----
-
-## Subagent Briefing Template
-
-When parallelizing verification checks:
-
-```
-## Task: Run verification check [N]
+Postchecks:
+- <command>: PASS/FAIL and finding count
 
-You are verifying a code change using scip-query. First run `scip-query reindex`.
+Gate:
+- `scip-query diff-gate --json`: PASS/FAIL
 
-Run the following command:
-[specific scip-query command]
+Health/config:
+- baseline or health result
+- config validation result when applicable
 
-Report:
-1. The exact command output
-2. Whether it PASSES or FAILS the criteria: [specific criteria]
-3. If FAIL: exactly what went wrong and which symbols/files are affected
-
-Do NOT use grep, rg, or Read. Use only scip-query commands.
+Remaining risk:
+- accepted suppressions, blocked capabilities, or checks not run
 ```
 
----
-
-## scip-query Quick Reference
-
-| Check | Command |
-|---|---|
-| Reindex | `scip-query reindex` |
-| Diff impact | `scip-query diff-impact` |
-| Cycles | `scip-query cycles` |
-| Dead code | `scip-query dead --min-loc 5` |
-| Isolated | `scip-query isolated --min-loc 3` |
-| References | `scip-query refs <symbol>` |
-| Fan-in | `scip-query fan-in <symbol>` |
-| Change surface | `scip-query change-surface <file>` |
-| Health | `scip-query health` |
-| Full blast radius | `scip-query affected <symbol>` |
-| Read source | `scip-query code <symbol>` |
+Do not claim "safe to commit" unless `scip-query reindex` and `scip-query diff-gate --json` passed after the final file edit.

package/skills/scip-verify/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "SCIP Verify"
+  short_description: "Verify changes with SCIP diff gates"
+  default_prompt: "Use $scip-verify to verify this change with reindexing, routed postchecks, and diff-gate."

package/skills/scip-vue-maintainability/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: scip-vue-maintainability
 description: Vue frontend maintainability review using scip-query's Vue SFC, template-duplicate, composable-candidate, large-view, and health commands. Use when reviewing Vue or Nuxt codebases, investigating duplicated components or composables, checking frontend health score pressure, or asking whether agents are reusing Vue code correctly.
-allowed-tools: [Bash, Read, Grep, Glob]
 ---
 
 # SCIP Vue Maintainability Review
@@ -80,7 +79,7 @@ After implementing a component reuse, composable extraction, or large-view split
 Run the checks that match what changed:
 
 ```bash
-scip-query diff-impact
+scip-query diff-impact --json
 scip-query vue-component-duplicates --scope <vue-source-scope> --full --json
 scip-query vue-composable-candidates --scope <vue-source-scope> --full --json
 scip-query vue-large-view-pressure --scope <vue-source-scope> --full --json
@@ -90,7 +89,7 @@ scip-query unused-params
 scip-query wrapper-candidates --scope <vue-source-scope> --full --json
 scip-query passthrough-candidates --scope <vue-source-scope> --full --json
 scip-query stale-abstractions --scope <vue-source-scope> --include-low-confidence --full --json
-scip-query reindex && scip-query diff-gate
+scip-query reindex && scip-query diff-gate --json
 ```
 
 Use the results this way:

package/skills/scip-vue-maintainability/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "SCIP Vue Maintainability"
+  short_description: "Review Vue reuse and view pressure"
+  default_prompt: "Use $scip-vue-maintainability to review Vue components, composables, views, and frontend health pressure."

package/vendor/scip/LICENSE.scip

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/vendor/scip/README.md

@@ -0,0 +1,6 @@
+# Managed scip binaries
+
+These binaries are built from https://github.com/scip-code/scip.git at v0.8.1.
+They are included so Windows installs can run `scip-query reindex` without requiring Go or WSL.
+
+Run `npm run build:scip-windows` before publishing to refresh them.