v0.4.0 – Context-aware validation & structured violations

[atellaluca]

What's new

• Environment-aware import contracts
  Added support for the environment key in .yml contracts. You can now specify:

  • variables: a list of expected runtime environment variables using the new Variable type.
  • secrets: a list of required secret names (without exposing content).
    This enables safe, declarative enforcement of runtime conditions without leaking sensitive data.

• Structured import errors
  Import failures are now context-aware. The new ViolationSystem introduces a structured error model that includes the reason, scope, and expected vs actual values—making debugging and tooling integration easier.

• SpyModel simplification
  The internal representation of SpyModel has been cleaned up and optimized for better maintainability and future extensibility.

• Documentation overhaul
  All documentation has been migrated from Sphinx to MkDocs. The new docs are faster to navigate and easier to contribute to.

Fixes and improvements

• Updated internal validation logic to support environment-based conditions.
• Added test coverage for new environment and ViolationSystem features.
• Security patches applied to all dependencies.

Breaking changes

• Environment variable schema
  Previously defined as a raw dictionary, environment variables must now be defined using the new Variable type under the environment section.

  environment:
    variables:
      - name: MY_ENV_VAR
        required: true
    secrets:
      - API_TOKEN
  

---

This discussion was created from the release v0.4.0 – Context-aware validation & structured violations.