Documentation
README
Happier Compatibility
Preserve real released and prospective predecessor behavior at system seams without preserving undeployed internal architecture or creating speculative compatibility debt.
Read docs/compatibility.md before acting. Also read the owning package instructions and the domain document for the affected protocol, feature, encryption, provider, installer, or persistence surface.
1. Classify the surface
Name the observable contract and classify it as wire, semantic, persistence, operational/installer, or internal-only.
If the change is internal-only and leaves external readers, writers, artifacts, and rollout behavior unchanged, stop the compatibility workflow. Do not create a matrix, shim, migration, or compatibility test merely because code moved.
This is the opening of the README. Read the full README on GitHub.