SerialkompatExtension
Configures the serialkompat { … } block (design §6, §9). Policy that can't be inferred from code (direction, baseline ref, scope) stays declared here; the wire config itself is read from the real jsonInstance.
Properties
Breaks the team has explicitly sanctioned — each downgraded from failing to acknowledged. Each entry is "<serialName> <RULE> [DIRECTION]", e.g. "com.example.Order PROPERTY_REMOVED" or "com.example.Order PROPERTY_REMOVED FORWARD" (omit the direction to accept both).
The git ref the current schema is checked against (e.g. origin/main).
Direction(s) of compatibility to enforce. Defaults to FULL.
How checked types are discovered when types is empty (issue #115): EXPLICIT (default) checks only types; OPT_OUT checks every discovered @Serializable type except those carrying @SerialkompatIgnore; OPT_IN checks only types carrying @SerialkompatChecked. A non-empty types list always wins, in every mode.
Whether a breaking change fails the build. Defaults to true.
Whether a baseline that produced zero contracts (while the current schema has some) fails the build. Defaults to true: a degenerate baseline would otherwise diff as "everything added → safe" and silently mask removals. Set false for first-time adoption, where the baseline ref legitimately has no @Serializable types yet.
Published-schema history for the transitive, persisted-data check (design §5).
FQN of a Json instance whose configuration describes the wire (e.g. com.acme.WireJson.instance). If it is set but can't be loaded from the runtime classpath, extraction fails.
Machine-readable report formats written by the pairwise check (#122).