<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/changelog/4.0.0/">
  <id>https://docs.spec-kitty.ai/changelog/4.0.0/</id>
  <title>4.0.0 — Hosted collaboration &amp; the open-core structural finish</title>
  <updated>2026-10-19T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/changelog/4.0.0/"/>
  <summary>Declaration of intent for the 4.0.0 cycle, re-anchored 2026-10-06: local CLI integrity gates GA, hosted collaboration is frozen, structural work continues on 4.x.</summary>
  <content type="html">&lt;span id=&quot;400--hosted-collaboration--the-open-core-structural-finish&quot;&gt;&lt;/span&gt;
&lt;p&gt;&lt;strong&gt;Milestone:&lt;/strong&gt; &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/11&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;4.0.0 release scope&lt;/code&gt;&lt;/a&gt; (open; the GA gate) ·
&lt;strong&gt;Status:&lt;/strong&gt; active (release-candidate stage; &lt;code dir=&quot;auto&quot;&gt;4.0.0rc5&lt;/code&gt; published 2026-10-02, &lt;code dir=&quot;auto&quot;&gt;4.0.0rc6&lt;/code&gt; open on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;) · &lt;strong&gt;Declared:&lt;/strong&gt; 2026-09-04 · &lt;strong&gt;Re-anchored:&lt;/strong&gt; 2026-10-06 ·
&lt;strong&gt;Supersedes&lt;/strong&gt; the retired &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/5&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;3.3.x&lt;/code&gt;&lt;/a&gt;
declaration for the hosted/experience work · &lt;strong&gt;Originally advanced&lt;/strong&gt; (see &lt;a href=&quot;#where-the-goals-stand-2026-10-06&quot;&gt;Where the goals stand&lt;/a&gt; for today’s state): epics #1800 (SaaS sync &amp;#x26;
event-envelope hardening), #1091 (Team Kitty launch gate), #3322 (CLI auth &amp;#x26; token-lifecycle
reliability), #2173 (infra-to-logic ports), #2519 (charter authoring &amp;#x26; lifecycle), #3549
(event-log integrity).&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Direction amendment (2026-10-01).&lt;/strong&gt; Team Kitty / SaaS work is frozen while the
commercial vision is reviewed, so &lt;strong&gt;G1 (hosted collaboration) is off the critical path&lt;/strong&gt;:
nothing hosted gates 4.0.0 GA, which is the
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/11&quot;&gt;4.0.0 release scope&lt;/a&gt; milestone alone.
External interaction flows through the CLI’s adapter module (the status fan-out, the seam
for a publish/subscribe system); producing events and draining them are separate concerns
with separate toggles; and the charter may ship as its own package once &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt;
reaches it only through a stable API (#645). The G1 text below is kept as the record of
the original intent. The operator detail is in the
&lt;a href=&quot;/plans/4-0-0-milestone-roadmap/#direction-update-2026-10-01-hosted-collaboration-is-off-the-critical-path&quot;&gt;4.0.0 Milestone Roadmap&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;where-the-goals-stand-2026-10-06&quot;&gt;Where the goals stand (2026-10-06)&lt;/h2&gt;
&lt;p&gt;The goals below are the record of what was declared on 2026-09-04. What 4.0.0 GA now means:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;GA is local CLI integrity.&lt;/strong&gt; The CLI never reports success while it loses, overwrites or
strands local work. The &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/11&quot;&gt;4.0.0 release scope&lt;/a&gt;
milestone (14 open, 210 closed, due 2026-10-16) is the whole gate; 119 of its 201 closed
issues were P0.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;G1 (hosted collaboration) is frozen.&lt;/strong&gt; Every G1 epic and P0 is closed or closed as not
planned; the client-side successor epics #3892 and #3893 wait on 4.x Work. Since
2026-10-06 Team Kitty is no longer actively supported, and its CLI entries are hidden
from listings (ADR &lt;code dir=&quot;auto&quot;&gt;2026-10-06-1&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;G2 is split.&lt;/strong&gt; #2173 (infrastructure ports) closed on 2026-09-27; #2519 (charter
authoring) continues on CLI 4.x stable.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;G3 (structural strangler) continues after GA&lt;/strong&gt; on the 4.x line: #645 (stable application
API, with the Mission Status Read API as its read facet), #1619 (one execution context) and
the pack-ecosystem epics. None of it gates GA.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Where the goals stand (2026-10-12).&lt;/strong&gt; GA now ships done-when-done: there is no date gate,
release candidates keep shipping, and each one still needs green CI before it is released.
The GA gate has three legs: local integrity, charter modular extraction (#645, ADR
&lt;code dir=&quot;auto&quot;&gt;2026-10-12-2&lt;/code&gt;), and the mission-status API backend. (2026-10-19: the charter leg is now a frozen
&lt;code dir=&quot;auto&quot;&gt;charter.offering.api&lt;/code&gt; seam and a green conformance corpus, not an extraction; ADR &lt;code dir=&quot;auto&quot;&gt;2026-10-12-2&lt;/code&gt;
is superseded by &lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter&lt;/code&gt; ADR-0008 and ADR-0010.)&lt;/p&gt;
&lt;p&gt;The operator detail, including the open GA issues and the decisions still owed, is in the
&lt;a href=&quot;/plans/4-0-0-milestone-roadmap/#release-posture&quot;&gt;4.0.0 Milestone Roadmap&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;why-now&quot;&gt;Why now&lt;/h2&gt;
&lt;p&gt;A &lt;strong&gt;release-queue reconciliation on 2026-08-23&lt;/strong&gt; retired the &lt;code dir=&quot;auto&quot;&gt;3.3.x&lt;/code&gt; milestone (its open work
re-triaged into 4.0.0 or Product backlog), repurposed the former &lt;code dir=&quot;auto&quot;&gt;3.2.x&lt;/code&gt; milestone (#4) into
&lt;strong&gt;Product backlog&lt;/strong&gt;, and split the near-term work into discrete &lt;strong&gt;3.2.6&lt;/strong&gt; (stabilization,
code-complete), &lt;strong&gt;3.2.7&lt;/strong&gt; (post-reconciliation follow-ups — doctrine-term renames,
profile-load consolidation, perf CI, dedups), and &lt;strong&gt;4.0.0&lt;/strong&gt; (this cycle) milestones. 4.0.0
is the largest open milestone (80 open issues) and had &lt;strong&gt;no declaration-of-intent&lt;/strong&gt;, breaking
the project’s own &lt;a href=&quot;/changelog/release-goals/&quot;&gt;release-goals convention&lt;/a&gt; (one durable declaration per
milestone). This document is that declaration. The taxonomy re-anchor that surfaced the gap
is recorded in the milestone roadmap’s
&lt;a href=&quot;/plans/3-2-x-milestone-roadmap/#addendum-2026-09-04--milestone-taxonomy-re-anchor-the-delayed-action-r&quot;&gt;2026-09-04 addendum&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;theme&quot;&gt;Theme&lt;/h2&gt;
&lt;p&gt;With 3.2.x’s &lt;strong&gt;core-domain single-sources-of-truth&lt;/strong&gt; substantially in place and 3.2.6 shipped
clean, 4.0.0 turns to &lt;strong&gt;hosted collaboration and next-generation product capabilities&lt;/strong&gt; — the
hosted Team Kitty surface (sync, consent/identity, auth, launch) and the charter/runtime depth
that builds on the stabilized core. It is also the intended landing zone for the &lt;strong&gt;open-core
structural strangler&lt;/strong&gt; that 3.2.x exists to finish — committed to this cycle by operator
decision (2026-09-04). Same discipline as the prior cycles: &lt;strong&gt;no new shadow paths&lt;/strong&gt; — route or extract onto
an existing authority, never build a parallel one.&lt;/p&gt;
&lt;h2 id=&quot;goals&quot;&gt;Goals&lt;/h2&gt;
&lt;h3 id=&quot;g1--hosted-collaboration-team-kitty&quot;&gt;G1 — Hosted collaboration (Team Kitty)&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;Off the critical path since 2026-10-01 (see the direction amendment above).&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Make the hosted surface a coherent, trustworthy product rather than a set of bolt-ons. The
durable invariants and sub-areas were held by the SaaS &amp;#x26; Hosted Sync domain plan
(retired 2026-09-06, Convergence #3881 — the surface re-homed to the authoritative
upstream repos); this cycle ships their release-scoped work:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Sync &amp;#x26; event-envelope integrity&lt;/strong&gt; — sync never reports success while authored state is
stranded; every synced event carries a contract-valid envelope. Epic &lt;strong&gt;#1800&lt;/strong&gt;; load-bearing
P0 &lt;strong&gt;#3278&lt;/strong&gt; (sync false success while &lt;code dir=&quot;auto&quot;&gt;MissionCreated&lt;/code&gt; stranded).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Consent &amp;#x26; identity boundary&lt;/strong&gt; — only explicitly consenting projects transmit, under one
unambiguous project→identity resolution. Load-bearing P0 &lt;strong&gt;#3178&lt;/strong&gt; (wrong-authority egress);
P1s &lt;strong&gt;#3197 / #3196 / #3198&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Auth &amp;#x26; token lifecycle&lt;/strong&gt; — a logged-in CLI stays authenticated, human auth is
browser-mediated, machine/CI auth has a supported path, refresh failures are named. Epic
&lt;strong&gt;#3322&lt;/strong&gt; (owns #3279 / #3277 / #3233).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Hosted rollout &amp;#x26; launch gate&lt;/strong&gt; — fail-closed-by-default rollout, named readiness failures,
launch defaults. Epic &lt;strong&gt;#1091&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Event-log integrity&lt;/strong&gt; — one canonical event store, honestly reported, delivered without
silent loss. Epic &lt;strong&gt;#3549&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;g2--next-generation-product-capabilities&quot;&gt;G2 — Next-generation product capabilities&lt;/h3&gt;
&lt;p&gt;Deepen the governance and runtime surfaces the stabilized core now supports:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Charter authoring &amp;#x26; lifecycle robustness&lt;/strong&gt; — the author/observe/reproduce paths, charter
domain events, deterministic intake. Epic &lt;strong&gt;#2519&lt;/strong&gt; (moved 3.2.x → 4.0.0 in the
reconciliation; see the
&lt;a href=&quot;/plans/domains/doctrine-charter-domain-plan/&quot;&gt;Doctrine &amp;#x26; Charter Domain Plan&lt;/a&gt; §3.1).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Infrastructure-to-logic separation&lt;/strong&gt; — inject ports for FS, Clock, GitOps, SaaSQueue,
Renderer; keep the core pure and stub-testable. Epic &lt;strong&gt;#2173&lt;/strong&gt; (moved 3.2.x → 4.0.0).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;g3--finish-the-open-core-structural-strangler&quot;&gt;G3 — Finish the open-core structural strangler&lt;/h3&gt;
&lt;p&gt;The G1/G2 strangler spine the 3.2.x cycle exists to finish — see
&lt;a href=&quot;#structural-strangler-spine--committed-to-400-2026-09-04&quot;&gt;Structural strangler spine — committed to 4.0.0&lt;/a&gt;
— is the structural foundation for 4.0.0’s hosted and next-gen work. &lt;strong&gt;Committed to 4.0.0 by
operator decision (2026-09-04):&lt;/strong&gt; the spine epics now carry milestone 4.0.0 on the live tracker.&lt;/p&gt;
&lt;h2 id=&quot;committed-scope-verified-milestone-400-2026-09-04&quot;&gt;Committed scope (verified milestone &lt;code dir=&quot;auto&quot;&gt;4.0.0&lt;/code&gt;, 2026-09-04)&lt;/h2&gt;
&lt;p&gt;These epics and P0s carry milestone 4.0.0 on the live tracker:&lt;/p&gt;



























































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Item&lt;/th&gt;&lt;th&gt;Role&lt;/th&gt;&lt;th&gt;Goal&lt;/th&gt;&lt;th&gt;State (2026-10-06)&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#1800&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Epic: SaaS sync &amp;#x26; event-envelope hardening&lt;/td&gt;&lt;td&gt;G1&lt;/td&gt;&lt;td&gt;Closed&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#1091&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Epic: Team Kitty launch gate&lt;/td&gt;&lt;td&gt;G1&lt;/td&gt;&lt;td&gt;Closed&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#3322&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Epic: CLI auth &amp;#x26; token-lifecycle reliability&lt;/td&gt;&lt;td&gt;G1&lt;/td&gt;&lt;td&gt;Closed; successor #3892 frozen on 4.x Work&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#3549&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Epic: event-log integrity&lt;/td&gt;&lt;td&gt;G1&lt;/td&gt;&lt;td&gt;Closed; successor #3893 on 4.x Work&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#3278&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;P0: sync reports success while &lt;code dir=&quot;auto&quot;&gt;MissionCreated&lt;/code&gt; stranded&lt;/td&gt;&lt;td&gt;G1&lt;/td&gt;&lt;td&gt;Closed as not planned&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#3178&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;P0: wrong-authority egress (FR-007 not discharged by FR-002)&lt;/td&gt;&lt;td&gt;G1&lt;/td&gt;&lt;td&gt;Closed&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#2519&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Epic: charter authoring &amp;#x26; lifecycle robustness&lt;/td&gt;&lt;td&gt;G2&lt;/td&gt;&lt;td&gt;Open, CLI 4.x stable&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#2173&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Epic: infrastructure-to-logic separation (ports)&lt;/td&gt;&lt;td&gt;G2&lt;/td&gt;&lt;td&gt;Closed&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;&lt;em&gt;Verify live state via &lt;code dir=&quot;auto&quot;&gt;gh issue view &amp;#x3C;n&gt; --repo spec-kitty/spec-kitty&lt;/code&gt; before acting; the
milestone description carries the one-line pointer back here.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&quot;structural-strangler-spine--committed-to-400-2026-09-04&quot;&gt;Structural strangler spine — committed to 4.0.0 (2026-09-04)&lt;/h2&gt;
&lt;p&gt;The open-core structural strangler spine — the G1/G2 structural work the 3.2.x cycle exists to
finish — is &lt;strong&gt;committed to 4.0.0 by operator decision (2026-09-04)&lt;/strong&gt;. It had sat in Product
backlog (validated, but on no committed release — exit criterion 8’s anti-drift guard fired in
a blind spot, and the work rode into Product backlog silently instead of onto a release). The
epics below now carry milestone 4.0.0 on the live tracker:&lt;/p&gt;

































































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Epic&lt;/th&gt;&lt;th&gt;Role&lt;/th&gt;&lt;th&gt;Milestone (2026-09-04)&lt;/th&gt;&lt;th&gt;State (2026-10-06)&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#1619&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;mission-execution-context root (P0)&lt;/td&gt;&lt;td&gt;4.0.0&lt;/td&gt;&lt;td&gt;Open, CLI 4.x stable&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#1797&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;degod / unshim delivery&lt;/td&gt;&lt;td&gt;4.0.0&lt;/td&gt;&lt;td&gt;Closed as not planned&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#1868&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;seam-binding enabler (WS4 / WS6)&lt;/td&gt;&lt;td&gt;4.0.0&lt;/td&gt;&lt;td&gt;Open, CLI 4.x stable&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#1746&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Mission Clarity Layer (P1)&lt;/td&gt;&lt;td&gt;4.0.0&lt;/td&gt;&lt;td&gt;Open, CLI 4.x stable&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#2160&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;coord-artifact authority (P0)&lt;/td&gt;&lt;td&gt;4.0.0&lt;/td&gt;&lt;td&gt;Closed on 4.0.0 release scope&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#1676&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;deterministic structured authoring (P0)&lt;/td&gt;&lt;td&gt;4.0.0&lt;/td&gt;&lt;td&gt;Open, CLI 4.x stable&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#2466 / #2467 / #2468&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;pack ecosystem + extensibility kinds&lt;/td&gt;&lt;td&gt;4.0.0&lt;/td&gt;&lt;td&gt;Open, 4.x Work&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#2539&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;pack trust / verified distribution&lt;/td&gt;&lt;td&gt;4.0.0&lt;/td&gt;&lt;td&gt;Open, 4.x Work&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#645 / #3179&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;stable public API surface for doctrine &amp;#x26; charter&lt;/td&gt;&lt;td&gt;4.0.0&lt;/td&gt;&lt;td&gt;#645 open on 4.x Work; #3179 closed&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;&lt;strong&gt;Security-debt coupling.&lt;/strong&gt; The 21 SonarCloud security findings (the sole failing quality
gate — 17 &lt;code dir=&quot;auto&quot;&gt;S6350&lt;/code&gt; subprocess + 3 &lt;code dir=&quot;auto&quot;&gt;S2083&lt;/code&gt; path-traversal, all pre-dating any current release
candidate) map almost 1:1 onto the degod slices above, so the security backlog rides with this
structural remediation — now both scheduled in 4.0.0. The 3 &lt;code dir=&quot;auto&quot;&gt;S2083&lt;/code&gt; blockers remain a
called-out ~90-min targeted fix that can land independent of any wave. (2026-10-06: the
security findings are tracked by #4304, #4305 and #2970 on 4.x Work, outside the GA gate.)&lt;/p&gt;
&lt;h2 id=&quot;non-goals&quot;&gt;Non-goals&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Re-opening the 3.2.x core-domain SSOTs&lt;/strong&gt; — they are the stabilized foundation 4.0.0 builds
on, not scope to re-litigate.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The 3.2.7 stabilization tail&lt;/strong&gt; — doctrine-term renames, profile-load consolidation,
perf CI, and dedups shipped under milestone &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/9&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;3.2.7&lt;/code&gt;&lt;/a&gt; (released 2026-09-10),
not here.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;success-criteria&quot;&gt;Success criteria&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Rewritten 2026-10-06; the 2026-09-04 placeholder criteria are listed below as the record.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;For 4.0.0 GA:&lt;/p&gt;
&lt;ul class=&quot;contains-task-list&quot;&gt;
&lt;li class=&quot;task-list-item&quot;&gt;&lt;input type=&quot;checkbox&quot; disabled&gt; The &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/11&quot;&gt;4.0.0 release scope&lt;/a&gt; milestone
is closed, or each open issue is re-milestoned with a rationale.&lt;/li&gt;
&lt;li class=&quot;task-list-item&quot;&gt;&lt;input type=&quot;checkbox&quot; disabled&gt; The nightly is green on the release commit; any &lt;code dir=&quot;auto&quot;&gt;skip_nightly&lt;/code&gt; waiver is an explicit,
recorded operator decision.&lt;/li&gt;
&lt;li class=&quot;task-list-item&quot;&gt;&lt;input type=&quot;checkbox&quot; disabled&gt; No command reports success while it loses, overwrites or strands local work (the
consolidation, status and workflow P0s), with an explicit decision on #5780 and #5758.&lt;/li&gt;
&lt;li class=&quot;task-list-item&quot;&gt;&lt;input type=&quot;checkbox&quot; disabled&gt; No new shadow path: no re-introduced sync transport, and only the adapter seam talks to
an external system.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For the 4.x line after GA:&lt;/p&gt;
&lt;ul class=&quot;contains-task-list&quot;&gt;
&lt;li class=&quot;task-list-item&quot;&gt;&lt;input type=&quot;checkbox&quot; disabled&gt; The structural strangler spine lands or is explicitly re-dispositioned; no epic is left
implicitly “cycle work” while off a release.&lt;/li&gt;
&lt;li class=&quot;task-list-item&quot;&gt;&lt;input type=&quot;checkbox&quot; disabled&gt; #645 gives CLI, UI, MCP and SDK consumers one versioned surface, and &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt;
reaches the charter only through it.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Deferred with G1 (frozen 2026-10-01): hosted no-false-success and no-loss under load; the
consent/identity boundary; CLI auth across device-flow and machine paths (#3892); the Team
Kitty launch gate (closed as #1091).&lt;/p&gt;
&lt;h2 id=&quot;emergent-patches&quot;&gt;Emergent patches&lt;/h2&gt;
&lt;p&gt;Declared when the cycle activates (3.2.7 stabilization tail lands first). Following the
&lt;a href=&quot;/changelog/release-goals/&quot;&gt;emergent-milestone model&lt;/a&gt;: each patch advances one of the goals above; the
milestone stays open until the goals are structurally met.&lt;/p&gt;
&lt;h2 id=&quot;links&quot;&gt;Links&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Milestone: &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/11&quot;&gt;https://github.com/spec-kitty/spec-kitty/milestone/11&lt;/a&gt; (4.0.0 release scope; the original 4.0.0 milestone 8 is now “4.x Work”) · Convention:
&lt;a href=&quot;/changelog/release-goals/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;release-goals.md&lt;/code&gt;&lt;/a&gt; · Prior cycle: &lt;a href=&quot;/changelog/3.2.x/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;3.2.x.md&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Retired predecessor declaration: &lt;a href=&quot;/changelog/3.3.x/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;3.3.x.md&lt;/code&gt;&lt;/a&gt; (milestone
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/5&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;3.3.x&lt;/code&gt;&lt;/a&gt; closed 2026-08-23)&lt;/li&gt;
&lt;li&gt;Durable domain plans: SaaS &amp;#x26; Hosted Sync (retired 2026-09-06, Convergence #3881) ·
&lt;a href=&quot;/plans/domains/doctrine-charter-domain-plan/&quot;&gt;Doctrine &amp;#x26; Charter&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Operator execution roadmap + taxonomy re-anchor:
&lt;a href=&quot;/plans/3-2-x-milestone-roadmap/#addendum-2026-09-04--milestone-taxonomy-re-anchor-the-delayed-action-r&quot;&gt;3.2.x Milestone Roadmap&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
