<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/2.x/2026-02-17-3-events-contract-parity-and-vendor-deprecation/">
  <id>https://docs.spec-kitty.ai/adr/2.x/2026-02-17-3-events-contract-parity-and-vendor-deprecation/</id>
  <title>Events Contract Parity and Vendored Module Deprecation</title>
  <updated>2026-02-17T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/2.x/2026-02-17-3-events-contract-parity-and-vendor-deprecation/"/>
  <summary>Names the published events package the only contract authority, schedules the vendored copy for removal, and requires CI parity checks across consuming repos.</summary>
  <content type="html">&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;Spec Kitty currently contains a vendored events module while also depending on external &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt;. This creates risk of contract drift and ambiguous authority for envelope/reducer semantics.&lt;/p&gt;
&lt;p&gt;Additionally, consumer version pins are currently inconsistent across repositories.&lt;/p&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; is the sole contract authority.&lt;/li&gt;
&lt;li&gt;CLI and SaaS MUST pin the same exact &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; version.&lt;/li&gt;
&lt;li&gt;Vendored event module in CLI is deprecated and scheduled for removal after migration gates pass.&lt;/li&gt;
&lt;li&gt;CI parity checks are required to prevent version drift.&lt;/li&gt;
&lt;li&gt;Runtime mission-next implementation is gated on mission-next contracts being published in &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Consumers MUST NOT emit local-only mission-next event names outside published contracts.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;decision-drivers&quot;&gt;Decision Drivers&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Deterministic cross-repo replay.&lt;/li&gt;
&lt;li&gt;Single source of truth for event contracts.&lt;/li&gt;
&lt;li&gt;Reduced semantic ambiguity during incident/debug workflows.&lt;/li&gt;
&lt;li&gt;Better release discipline across repositories.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;consequences&quot;&gt;Consequences&lt;/h2&gt;
&lt;h3 id=&quot;positive&quot;&gt;Positive&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Replay/projection parity becomes enforceable.&lt;/li&gt;
&lt;li&gt;Event contract evolution is explicit and auditable.&lt;/li&gt;
&lt;li&gt;Lower chance of hidden drift bugs.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;negative&quot;&gt;Negative&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Requires coordinated release cadence and contract-bump workflow.&lt;/li&gt;
&lt;li&gt;Migration work to remove vendored compatibility layer.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;neutral&quot;&gt;Neutral&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Temporary compatibility shims may be needed during transition.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;enforcement&quot;&gt;Enforcement&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Add CI checks for exact version parity in consumers.&lt;/li&gt;
&lt;li&gt;Add CI checks rejecting vendored-only contract extensions.&lt;/li&gt;
&lt;li&gt;Document contract-bump process in release notes.&lt;/li&gt;
&lt;li&gt;Add CI checks ensuring runtime mission-next event types map to published &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; constants/payloads.&lt;/li&gt;
&lt;/ol&gt;</content>
</entry>
