JevGate 0.30.0: the roadmap from 0.26 to 0.30 (a measured gate, the agent loop, per-question cache, your rules, nine more languages)

.claude-plugin/marketplace.json

@@ -0,0 +1,15 @@
+{
+  "name": "jevgate",
+  "owner": {
+    "name": "Tech Byte Frontier",
+    "url": "https://github.com/Tech-Byte-Frontier"
+  },
+  "description": "JevGate, the code-review gate that asks TypeSafe Jev short, typed questions about your code",
+  "plugins": [
+    {
+      "name": "jevgate",
+      "source": "./plugin",
+      "description": "Checks each edit and the end of each turn with JevGate, and adds its MCP tools and a skill for acting on findings"
+    }
+  ]
+}

.gitattributes

@@ -0,0 +1,8 @@
+# Text the binary embeds (include_str!) or its tests compare byte for byte
+# stays LF in every checkout. With Git's Windows default (core.autocrlf), the
+# instructions `init --agent` manages were embedded with CRLF, so the block it
+# wrote never compared equal to the next run's, and the docs test found no
+# JSON example after its heading.
+src/setup/instructions.md text eol=lf
+src/setup/opencode.js text eol=lf
+site/src/*.md text eol=lf

.github/homebrew-formula.sh

@@ -48,7 +48,7 @@ class Jevgate < Formula
     generate_completions_from_executable(bin/"jevgate", "completions")
     man1.mkpath
     (man1/"jevgate.1").write Utils.safe_popen_read(bin/"jevgate", "man")
-    %w[auth check baseline rules init serve mcp completions man].each do |command|
+    %w[auth check baseline rules init serve mcp hook completions man].each do |command|
       (man1/"jevgate-#{command}.1").write Utils.safe_popen_read(bin/"jevgate", "man", command)
     end
   end

.github/workflows/ci.yml

@@ -31,6 +31,16 @@ jobs:
         run: rustup toolchain install stable --profile minimal
       - uses: Swatinem/rust-cache@6323deb102c322ba6fcbdcafc7e3dddab59af2b6 # v2.9.2
       - run: cargo +stable test --locked
+  node:
+    # The npm launcher and the OpenCode plugin, on each runner's own Node.
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest, windows-latest]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+      - run: node --test npm/test/launcher.test.js src/setup/opencode.test.mjs
   msrv:
     runs-on: ubuntu-latest
     steps:

.gitignore

@@ -1,5 +1,8 @@
 /target/
 /.jevgate/
+# What publishing the npm launcher leaves behind.
+/npm/*.tgz
+/npm/SHA256SUMS
 .env
 .env.*
 *.pem

CONTRIBUTING.md

@@ -24,6 +24,7 @@ The tests run offline and need no API key. `jevgate check --dry-run --show-reque
 ## Code conventions
 
 - Unused code is deleted, not silenced, and long parameter lists are grouped into a type. `tests/lint_policy.rs` rejects `allow` or `expect` for `dead_code`, `unused`, `too_many_arguments` and `complexity`. Any other exception uses `#[expect(lint, reason = "…")]`.
+- Tests run Git through `tests/support/git.rs`, which drops the variables that point Git at a repository (`GIT_DIR`, `GIT_INDEX_FILE` and the others Git exports to hooks and `git rebase --exec`), so `cargo test` run there leaves that repository alone. `tests/lint_policy.rs` rejects starting Git anywhere but there and `src/revision.rs`.
 - Commit subjects say what changed, in the imperative ("Report overlapping tests by groups").
 - Messages and findings are plain sentences that name the code and say what to do next.
 
@@ -40,7 +41,7 @@ JevGate asks the model small questions and decides findings in code. When you ch
 
 ## Documentation site
 
-The site at <https://tech-byte-frontier.github.io/jevgate/> is built from `site/` with [mdBook](https://rust-lang.github.io/mdBook/): `site/build.sh` generates the rules, configuration and command-line reference pages from a release build, then builds the book into `site/book`. It is published with each release, so it describes the released binary. Guide pages are in `site/src`; the reference pages are generated, so change the rule catalog, the configuration types or the `--help` text instead.
+The site at <https://tech-byte-frontier.github.io/jevgate/> is built from `site/` with [mdBook](https://rust-lang.github.io/mdBook/): `site/build.sh` generates the rules, configuration and command-line reference pages from a release build, then builds the book into `site/book`. It is published with each release, so it describes the released binary. Guide pages are in `site/src`; the reference pages are generated, so change the rule catalog, the configuration types or the `--help` text instead. Each rule has a hand-written page, `site/src/rules/<rule ID>.md`, that includes its generated facts and shows findings it got wrong; a new rule needs one, and a test checks it.
 
 ## Pull requests
 

Cargo.toml

@@ -3,14 +3,14 @@ name = "jevgate"
 version = "0.25.0"
 edition = "2024"
 rust-version = "1.90"
-description = "Code-review gate for CI and coding agents: asks TypeSafe Jev small questions about functions, files, tests and docs, and reports maintainability, test, security and documentation findings with locations and probabilities"
+description = "Code-review gate for CI and coding agents: asks TypeSafe Jev small questions about functions, files, tests and docs, and reports maintainability, test, security and documentation findings with locations and how often findings like them were right"
 repository = "https://github.com/Tech-Byte-Frontier/jevgate"
 homepage = "https://tech-byte-frontier.github.io/jevgate/"
 documentation = "https://tech-byte-frontier.github.io/jevgate/"
 readme = "README.md"
 keywords = ["code-review", "ci", "static-analysis", "maintainability", "security"]
 categories = ["command-line-utilities", "development-tools"]
-include = ["/src/**", "/tests/**", "/Cargo.toml", "/Cargo.lock", "/README.md", "/CHANGELOG.md", "/LICENSE-*", "/NOTICE"]
+include = ["/src/**", "/tests/**", "/gallery/**", "/Cargo.toml", "/Cargo.lock", "/README.md", "/CHANGELOG.md", "/LICENSE-*", "/NOTICE"]
 license = "MIT OR Apache-2.0"
 
 # `cargo binstall jevgate` downloads the archives the release workflow attaches.
@@ -33,7 +33,7 @@ keyring = { version = "=4.2.0", default-features = false, features = ["v1"] }
 rpassword = "=7.5.4"
 zeroize = "=1.9.0"
 serde = { version = "=1.0.229", features = ["derive"] }
-serde_json = { version = "=1.0.151", features = ["float_roundtrip"] }
+serde_json = { version = "=1.0.151", features = ["float_roundtrip", "raw_value"] }
 sha2 = "=0.11.0"
 toml = "=1.1.6"
 tree-sitter = "=0.27.0"
@@ -47,6 +47,16 @@ tree-sitter-ruby = "=0.23.1"
 tree-sitter-php = "=0.24.2"
 tree-sitter-java = "=0.23.5"
 tree-sitter-bend2 = "=0.1.2"
+# The generic tier (`analysis::generic`), read through tag queries only.
+tree-sitter-c = "=0.24.2"
+tree-sitter-cpp = "=0.23.4"
+tree-sitter-kotlin-ng = "=1.1.0"
+tree-sitter-swift = "=0.7.3"
+tree-sitter-bash = "=0.25.1"
+tree-sitter-dart = "=0.2.0"
+tree-sitter-scala = "=0.26.2"
+tree-sitter-elixir = "=0.3.5"
+tree-sitter-lua = "=0.5.0"
 ureq = { version = "=3.4.2", default-features = false, features = ["rustls", "json"] }
 
 # The JSON Schema of jevgate.toml is generated by a test from the configuration types.