neuralint v0.1.0-alpha.2

neuralint v0.1.0-alpha.2

This alpha reframes neuralint as fast semantic linting for coding-agent loops and adds the first repository onboarding and rule-management workflow.

Highlights

• Add neuralint init to create .neuralint/config.yaml and one complete example rule without overwriting existing files.
• Add neuralint rules list and neuralint rules validate.
• Load the default Git base from repository configuration with a per-run --base override.
• Replace candidate-dependent screening/localization requests with bounded concurrent Jev decision-matrix packs.
• Show only definitive findings by default; add --advisories for inconclusive matches.
• Add --rule RULE_ID for focused checks.
• Add stdin/editor evaluation with --stdin, --path, and --start-line.
• Add deterministic JSON finding locations with old/new side and line ranges.
• Add optional semantic rule context, report boundaries, exceptions, remediation guidance, evidence scope, and contrastive examples.
• Document the intended fast-lint and focused-remediation product architecture.

Initial usage

npm install --global neuralint@alpha
cd /path/to/repository
neuralint init --base origin/main
neuralint rules validate
neuralint check

Evaluate one rule against an unsaved editor selection:

printf '%s\n' 'logger.info({ token })' | neuralint check \
  --stdin --path src/client.ts --start-line 42 \
  --rule EXAMPLE_NO_SECRET_LOGGING --format json

Benchmark evidence

A 30-rule × 30-file production matrix run completed in 0.98 seconds using three Jev requests, retained all 30 predeclared primary findings as definitive, and cost an estimated $0.00635. This positive-heavy result establishes feasibility, not precision.

A five-case Home Assistant pilot found that gold finding packets handed to Terra produced the same measured remediation quality as full-catalog Terra while completing 3.31× faster and costing 24.1% less. This tests remediation given correct findings; it is not an end-to-end detection claim.

Known limitations

• Git findings currently use hunk-level ranges; stdin selections preserve their explicit range.
• Enclosing-symbol and related-definition retrieval are not yet implemented.
• Focused human remediation is benchmarked but not yet exposed as a CLI command.
• rules generate, rules test, and rules doctor remain planned.
• The alpha does not redact diff content or provide local inference. Confirm that the configured endpoint is approved before sending proprietary code.
• Rule and JSON report schemas may change before 1.0.