Versioning

This RFC doesn’t introduce an explicit protocol version field. Compatibility is governed by the Courier job definition version. Interpreters SHOULD be forward‑compatible: they should ignore unknown fields unless strict validation is enabled. Backwards compatibility is maintained by not removing or changing the meaning of existing fields without bumping the job definition version. Future RFCs may introduce explicit version negotiation if needed.