Skip to content

Latest commit

 

History

History
10 lines (8 loc) · 634 Bytes

File metadata and controls

10 lines (8 loc) · 634 Bytes

Contributing

  1. Open an issue describing the user-visible defect or bounded capability.
  2. Add or update a regression test before changing signal-bearing behavior.
  3. Keep inputs, outputs, failure modes, and evidence boundaries explicit.
  4. Run the repository's documented validation command from a clean checkout.
  5. Do not add provider credentials, generated runtime state, fabricated metrics, or unsupported production claims.
  6. Update integration and deployment documentation when a public contract changes.

Pull requests should contain: problem, reproduction, change, verification, compatibility impact, and remaining risk.