2.2.0 Reality Checks, Schema Export & CI Templates

[mraml]

🚀 Major Features
🕵️ Code-to-Spec Verification (Drift Detection)

nod now goes beyond just checking your documentation. With Reality Checks, the scanner verifies that claims made in your spec (e.g., "Database: Postgres") are actually reflected in your implementation code (e.g., requirements.txt or Dockerfile).

New Rule Type: Define reality_checks in your YAML profiles to regex-match implementation files against spec values.

Drift Reporting: New CLI section explicitly flags "Potential Code Contradictions."

SARIF Updates: Drift failures are tagged as contradiction for security dashboard integration.

🔗 JSON Schema Export

Enable better integration with GRC tools and policy validators. You can now export your loaded ruleset as a standard JSON Schema (Draft-07).

Usage: nod --export schema

Allows external tools to validate their policy definitions against nod's expectations.

👷 Native CI/CD Templates

We've added a new templates/ directory containing drop-in configurations for major CI providers, expanding support beyond GitHub Actions:

GitLab CI: templates/.gitlab-ci.yml

Azure Pipelines: templates/azure-pipelines.yml

🛠️ CLI & UX Improvements

--save-to <file>: Save reports directly to a file via arguments (cleaner than shell redirection).

--quiet (-q): Silent mode suppresses banner art and non-error logs (ideal for CI).

Registry Shorthand: Use --rules registry:owasp-llm to fetch rules directly from the official library without full URLs.

🧹 Maintenance & Quality

PEP 8 Compliance: Extensive refactoring of the Scanner engine for standard Python code style.

Documentation: Added comprehensive docstrings to core classes and updated the README with advanced rule logic examples.