<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/operations/how-to-maintain/">
  <id>https://docs.spec-kitty.ai/operations/how-to-maintain/</id>
  <title>How to Maintain — Spec Kitty Issue Tracker</title>
  <updated>2026-06-16T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/operations/how-to-maintain/"/>
  <summary>Maintainer runbook for Spec Kitty tracker hygiene: issue-tracker structure, priority levels, issue types, and milestone/release-goal conventions grounded in live repo data.</summary>
  <content type="html">&lt;span id=&quot;how-to-maintain--spec-kitty-issue-tracker&quot;&gt;&lt;/span&gt;
&lt;blockquote&gt;
&lt;p&gt;Maintainer entry-point for tracker hygiene. Authored 2026-06-16 (planner-priti, governance op).
Grounded in &lt;strong&gt;live repo data&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;spec-kitty/spec-kitty&lt;/code&gt;) and the operator conventions in
&lt;code dir=&quot;auto&quot;&gt;work/TRACKER_DOCTRINE_NOTES.md&lt;/code&gt;. Items marked &lt;strong&gt;(inferred)&lt;/strong&gt;
are derived from observed usage, not an explicit written rule; everything else is &lt;strong&gt;confirmed&lt;/strong&gt;
from the label taxonomy, native GitHub Types, or an existing convention doc.&lt;/p&gt;
&lt;p&gt;Decision rationale for the milestone / release-goal recommendations lives in
&lt;a href=&quot;#5-recommended-additions&quot;&gt;§5 Recommended additions&lt;/a&gt; (per Directive 003 — Decision Documentation).&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;h2 id=&quot;1-issue-tracker-structure&quot;&gt;1. Issue tracker structure&lt;/h2&gt;
&lt;p&gt;Three structural roles. Keep them distinct — conflating them is the most common drift.&lt;/p&gt;

























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Role&lt;/th&gt;&lt;th&gt;What it is&lt;/th&gt;&lt;th&gt;Parenting rule&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Functional epic&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A &lt;em&gt;domain that produces code/behaviour&lt;/em&gt; — a subsystem, capability, or bug-class. Labelled &lt;code dir=&quot;auto&quot;&gt;epic&lt;/code&gt;, native Type &lt;code dir=&quot;auto&quot;&gt;Feature&lt;/code&gt;.&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Owns&lt;/strong&gt; work. Functional tickets are parented here via native sub-issues.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Functional ticket&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A single Bug / Task / enhancement that changes the product.&lt;/td&gt;&lt;td&gt;Lives under exactly one functional epic (single-parent constraint).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Meta-tracker&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A release / go-no-go / stabilization rollup (e.g. &lt;em&gt;3.2.0 release tracker&lt;/em&gt;). &lt;strong&gt;Not&lt;/strong&gt; a domain of work.&lt;/td&gt;&lt;td&gt;&lt;strong&gt;NEVER the canonical parent&lt;/strong&gt; of functional tickets. Prefix &lt;code dir=&quot;auto&quot;&gt;META-TRACKER:&lt;/code&gt;. References work via a body checklist only.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;&lt;strong&gt;The cardinal rule (confirmed — CLAUDE.md “Meta vs functional epics” + TRACKER_DOCTRINE_NOTES §1):&lt;/strong&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Functional epics own work; meta-trackers only &lt;em&gt;reference&lt;/em&gt; it. Never make a meta-tracker the parent
of a functional ticket — use a checklist in the meta-tracker body, and parent the ticket under its
functional epic.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Live example of the pattern done right: &lt;strong&gt;#1929&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;Tracking: post-#1908 adversarial-panel findings&lt;/code&gt;)
is a checklist-only meta view; each of its four findings (#1915–#1918) is canonically parented under
its &lt;em&gt;functional&lt;/em&gt; epic (#1795/#1868/#1666/#1914), and #1929 explicitly states it is &lt;strong&gt;not&lt;/strong&gt; their parent.&lt;/p&gt;
&lt;h3 id=&quot;native-sub-issues-are-the-source-of-truth&quot;&gt;Native sub-issues are the source of truth&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Parent/child is the &lt;strong&gt;native GitHub sub-issue graph&lt;/strong&gt;, &lt;em&gt;not&lt;/em&gt; body checklists (checklists are invisible
to tooling). &lt;strong&gt;Confirmed:&lt;/strong&gt; 29 of 35 open epics already use native sub-issues; e.g. &lt;strong&gt;#1619&lt;/strong&gt; carries 10
native children. Backfill native links wherever a body checklist implies a parent.&lt;/li&gt;
&lt;li&gt;REST: &lt;code dir=&quot;auto&quot;&gt;POST/DELETE /repos/{owner}/{repo}/issues/{n}/sub_issues&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;sub_issue_id&lt;/code&gt; is the integer
&lt;strong&gt;database id&lt;/strong&gt; (use &lt;code dir=&quot;auto&quot;&gt;gh api -F&lt;/code&gt;, not &lt;code dir=&quot;auto&quot;&gt;-f&lt;/code&gt;). Single-parent → &lt;code dir=&quot;auto&quot;&gt;DELETE&lt;/code&gt; from the old parent before &lt;code dir=&quot;auto&quot;&gt;POST&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;.parent&lt;/code&gt; is reliable only via &lt;strong&gt;GraphQL&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;issue.parent&lt;/code&gt;), not REST.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;hygiene-invariants-every-open-ticket&quot;&gt;Hygiene invariants (every open ticket)&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Resolves to a &lt;strong&gt;functional epic&lt;/strong&gt; — not an orphan, not meta-rooted, not under a closed/superseded epic.&lt;/li&gt;
&lt;li&gt;Has an &lt;strong&gt;issue Type&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;Task&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;Bug&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;Feature&lt;/code&gt;; epics = &lt;code dir=&quot;auto&quot;&gt;Feature&lt;/code&gt;). See &lt;a href=&quot;#3-issue-types&quot;&gt;§3&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Has a &lt;strong&gt;priority&lt;/strong&gt; label (&lt;code dir=&quot;auto&quot;&gt;priority:P0..P3&lt;/code&gt;). See &lt;a href=&quot;#2-priority-levels&quot;&gt;§2&lt;/a&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Sweep closed epics for &lt;em&gt;open&lt;/em&gt; children and rehome them — open tickets under a closed parent look
tracked but are invisible.&lt;/p&gt;
&lt;h3 id=&quot;how-a-mission-maps-to-issues&quot;&gt;How a mission maps to issues&lt;/h3&gt;
&lt;p&gt;A mission’s &lt;strong&gt;issue-matrix&lt;/strong&gt; (in the mission spec) lists every tracker issue the mission addresses.
At spec time:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Every addressed issue → a row in the issue-matrix &lt;strong&gt;and&lt;/strong&gt; a tracker comment naming the mission.&lt;/li&gt;
&lt;li&gt;The issue is &lt;strong&gt;claimed&lt;/strong&gt; (assigned to the operator) per the claim discipline below.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Claim discipline (operator rule, 2026-06-16):&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Claim before WORKING&lt;/strong&gt; a ticket — assign it to yourself/operator &lt;em&gt;before&lt;/em&gt; starting implementation,
so concurrent agents/contributors don’t collide.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Closing / cleanup is exempt.&lt;/strong&gt; You may close a provably-done ticket &lt;strong&gt;without claiming it first&lt;/strong&gt; —
attach an evidence comment (the PR/commit/test proving it’s done). No claim needed to close.&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&quot;2-priority-levels&quot;&gt;2. Priority levels&lt;/h2&gt;
&lt;p&gt;Priority is a &lt;strong&gt;tracker-state label&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;priority:P0..P3&lt;/code&gt;), distinct from the MoSCoW planning lens
(MoSCoW = a scoping discipline at mission-negotiation time; &lt;code dir=&quot;auto&quot;&gt;priority:Px&lt;/code&gt; = backlog state). Both
coexist; do not collapse one into the other.&lt;/p&gt;
&lt;p&gt;Operational meaning is &lt;strong&gt;confirmed&lt;/strong&gt; from the label descriptions and &lt;strong&gt;(inferred)&lt;/strong&gt; from observed
application across the current 3.2.x stabilization lane:&lt;/p&gt;








































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Label&lt;/th&gt;&lt;th&gt;Label description (confirmed)&lt;/th&gt;&lt;th&gt;Operational meaning (inferred from usage)&lt;/th&gt;&lt;th align=&quot;right&quot;&gt;Open count&lt;/th&gt;&lt;th&gt;Example&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;priority:P0&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;em&gt;Release blocker / must decide before final 3.2.0&lt;/em&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Release/merge blocker.&lt;/strong&gt; Must be resolved or explicitly decided before the targeted release ships.&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;7&lt;/td&gt;&lt;td&gt;#1844 (rc verify blocked), #1619 (exec-context epic)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;priority:P1&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;em&gt;High-value stabilization / bug or release confidence&lt;/em&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Important&lt;/strong&gt; — high-value stabilization or release-confidence work; not a hard ship-gate but strongly targeted for the cycle.&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;63&lt;/td&gt;&lt;td&gt;#1978 (naming split-brain), #1945 (ToolSurfaceContract epic)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;priority:P2&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;em&gt;Planned enhancement / post-blocker work&lt;/em&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Normal&lt;/strong&gt; — planned enhancements / cleanup scheduled after blockers clear.&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;83&lt;/td&gt;&lt;td&gt;#1979, #1928 (lint/strict debt epic)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;priority:P3&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;em&gt;Backlog / future / needs reconfirmation&lt;/em&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Low&lt;/strong&gt; — backlog; future or needs reconfirmation before it’s actionable.&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;55&lt;/td&gt;&lt;td&gt;#1973 (experiment), #1911&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Triage rule: assign a &lt;strong&gt;provisional priority and flag it&lt;/strong&gt; rather than silently guessing. The
&lt;code dir=&quot;auto&quot;&gt;p1-decision:*&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;triage:*&lt;/code&gt; labels (see §3) record in-flight triage decisions on top of the base level.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;3-issue-types&quot;&gt;3. Issue Types&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Confirmed:&lt;/strong&gt; the repo uses GitHub’s &lt;strong&gt;native org-level issue Types&lt;/strong&gt; (not type-via-label). Three
types are enabled: &lt;code dir=&quot;auto&quot;&gt;Task&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;Bug&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;Feature&lt;/code&gt; (GitHub’s built-in default set — note this &lt;code dir=&quot;auto&quot;&gt;Feature&lt;/code&gt; is
GitHub’s generic Type and is &lt;em&gt;unrelated to&lt;/em&gt; the prohibited domain term “feature/Mission”; do not
rename it).&lt;/p&gt;





















&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Type&lt;/th&gt;&lt;th&gt;Use for&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;Bug&lt;/code&gt;&lt;/td&gt;&lt;td&gt;An unexpected problem or incorrect behaviour to fix.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;Task&lt;/code&gt;&lt;/td&gt;&lt;td&gt;A specific, scoped piece of work (refactor, chore, doc, tech-debt item).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;Feature&lt;/code&gt;&lt;/td&gt;&lt;td&gt;A request / new capability &lt;strong&gt;and all epics&lt;/strong&gt; (epic = &lt;code dir=&quot;auto&quot;&gt;Feature&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;epic&lt;/code&gt; label).&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Set Type via GraphQL &lt;code dir=&quot;auto&quot;&gt;updateIssue(input:{id, issueTypeId})&lt;/code&gt; (type ids are per-repo). Derive Type
objectively — from the conventional-commit prefix + labels — not by guesswork.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Adoption gap (inferred — action item):&lt;/strong&gt; Type coverage is incomplete. In an 80-issue recent-open
sample, ~24% (19/80) had &lt;strong&gt;no&lt;/strong&gt; Type set (e.g. #1929, #1978 at time of audit). Backfilling Type on
untyped open issues is a standing hygiene task.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;4-labels&quot;&gt;4. Labels&lt;/h2&gt;
&lt;p&gt;The label taxonomy is documented in one place:
&lt;a href=&quot;/development/how-to/manage-issue-tracker/#label-taxonomy&quot;&gt;Managing the issue tracker → Label taxonomy&lt;/a&gt;.
It is the canonical authority for every label family (priority, classification,
&lt;code dir=&quot;auto&quot;&gt;domain:*&lt;/code&gt;, concern, &lt;code dir=&quot;auto&quot;&gt;triage:*&lt;/code&gt;, provenance &lt;code dir=&quot;auto&quot;&gt;from:*&lt;/code&gt;, PR-workflow, lifecycle,
legacy).&lt;/p&gt;
&lt;p&gt;Labels never encode kind: the &lt;code dir=&quot;auto&quot;&gt;bug&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;enhancement&lt;/code&gt; labels and the &lt;code dir=&quot;auto&quot;&gt;type:*&lt;/code&gt;
label family are retired and were deleted from the repository on 2026-10-19; the
native Type above is the sole kind carrier. There is no &lt;code dir=&quot;auto&quot;&gt;future&lt;/code&gt; label (paused
work is &lt;code dir=&quot;auto&quot;&gt;deferred&lt;/code&gt;), and release scope lives in milestones (§5), not labels. The
labels this section previously listed (&lt;code dir=&quot;auto&quot;&gt;research-mission&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;agent_profiles&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;oauth-ddd-refactor&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;launch-blocker&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mvp&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;3.2.0&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;3.3.0&lt;/code&gt; version labels and &lt;code dir=&quot;auto&quot;&gt;p1-decision:*&lt;/code&gt;) no longer exist.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;a id=&quot;5-recommended-additions&quot;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&quot;5-release-scoping-emergent-milestones--declarations-of-intent-implemented&quot;&gt;5. Release scoping: emergent milestones + declarations of intent (IMPLEMENTED)&lt;/h2&gt;
&lt;p&gt;Adopted 2026-06-16. Milestones were previously &lt;strong&gt;abandoned&lt;/strong&gt; (2 historical, no due-dates, zero open
issues; release scoping rode on version labels &lt;code dir=&quot;auto&quot;&gt;3.2.0&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;3.3.0&lt;/code&gt;). The model below is now live.&lt;/p&gt;
&lt;h3 id=&quot;5a-emergent-milestones-per-minor-cycle-not-per-patch&quot;&gt;5a. Emergent milestones (per minor cycle, not per patch)&lt;/h3&gt;
&lt;p&gt;Scope by &lt;strong&gt;minor cycle&lt;/strong&gt;: milestones are &lt;code dir=&quot;auto&quot;&gt;3.2.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;3.3.x&lt;/code&gt; (+ a retroactive point-in-time &lt;code dir=&quot;auto&quot;&gt;3.2.0&lt;/code&gt; for
what shipped). A minor cycle has &lt;strong&gt;one goal&lt;/strong&gt;; multiple &lt;strong&gt;emergent patches&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;3.2.1&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;3.2.2&lt;/code&gt;, …) each
advance that same goal, and the milestone stays &lt;strong&gt;open until the goal is structurally met&lt;/strong&gt;. This lets
us split a minor cycle into as many patches as the work needs without re-litigating scope.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Current milestones:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;3.2.0&lt;/code&gt; (#3, closed — 7 shipped issues) · &lt;code dir=&quot;auto&quot;&gt;3.2.x&lt;/code&gt; (#4, open — the active
stabilization cycle) · &lt;code dir=&quot;auto&quot;&gt;3.3.x&lt;/code&gt; (#5, open — next cycle, #1878 write-side + forward).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;What it buys:&lt;/strong&gt; a real “what’s left this cycle” burndown for free; one stable target across patches.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Gotcha (record this):&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;gh issue edit --milestone &quot;&amp;#x3C;title&gt;&quot;&lt;/code&gt; only resolves &lt;strong&gt;open&lt;/strong&gt; milestones by
title. To attach issues to a &lt;strong&gt;closed&lt;/strong&gt; (retroactive) milestone, use the API by &lt;strong&gt;number&lt;/strong&gt;:
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame is-terminal not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;span class=&quot;title&quot;&gt;&lt;/span&gt;&lt;span class=&quot;sr-only&quot;&gt;Terminal window&lt;/span&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#C5E478;--1:#3B61B0&quot;&gt;unset&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;GITHUB_TOKEN&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;gh&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;api&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;repos/spec-kitty/spec-kitty/milestones&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;-X&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;POST&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;-f&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;title=&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;3.2.x&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;-f&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;state=&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;open&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;-f&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;description=&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;&amp;#x3C;one-line goal + link to docs/changelog/3.2.x.md&gt;&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;gh&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;issue&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;edit&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;&amp;#x3C;num&gt;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--repo&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;spec-kitty/spec-kitty&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--milestone&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;3.2.x&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;        &lt;/span&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# open milestone, by title&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;gh&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;api&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;repos/spec-kitty/spec-kitty/issues/&amp;#x3C;num&gt;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;-X&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;PATCH&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;-F&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;milestone=&amp;#x3C;N&gt;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;   &lt;/span&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# any/closed milestone, by number&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;5b-declarations-of-intent-the-canonical-goal-home&quot;&gt;5b. Declarations of intent (the canonical goal home)&lt;/h3&gt;
&lt;p&gt;The &lt;strong&gt;release goal lives in a version-controlled doc&lt;/strong&gt;, not (only) the milestone description:
&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;docs/changelog/&amp;#x3C;minor&gt;.md&lt;/code&gt;&lt;/strong&gt; — the durable, PR-reviewed declaration of intent (goal · rationale
· scope · non-goals · success criteria · emergent-patch plan · links). The &lt;strong&gt;milestone description is a
short pointer&lt;/strong&gt; back to it (it is ephemeral, char-limited, unreviewable, and can’t link to research).&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Why a doc over the milestone description: a “declaration of intent” deserves git history + review and
must link to the research/missions; the milestone is the burndown surface, the doc is the intent.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Connection to mission practice:&lt;/strong&gt; a cycle goal maps to a driving mission (or small named set); the
mission’s &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; is the per-patch closure ledger that rolls up into the milestone burndown.&lt;/li&gt;
&lt;li&gt;See &lt;a href=&quot;/changelog/release-goals/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/changelog/release-goals.md&lt;/code&gt;&lt;/a&gt; for the convention and
&lt;a href=&quot;/changelog/3.2.x/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/changelog/3.2.x.md&lt;/code&gt;&lt;/a&gt; for the live example
(&lt;strong&gt;3.2.x — “Strangle the naming/identity/read-path split-brain toward a consistent SSOT.”&lt;/strong&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h3 id=&quot;quick-maintainer-checklist&quot;&gt;Quick maintainer checklist&lt;/h3&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; Every open issue: functional-epic parented (native sub-issue), Typed, prioritized.&lt;/li&gt;
&lt;li class=&quot;task-list-item&quot;&gt;&lt;input type=&quot;checkbox&quot; disabled&gt; No functional ticket parented under a &lt;code dir=&quot;auto&quot;&gt;META-TRACKER:&lt;/code&gt; issue.&lt;/li&gt;
&lt;li class=&quot;task-list-item&quot;&gt;&lt;input type=&quot;checkbox&quot; disabled&gt; Backfill native sub-issue links where a body checklist implies a parent.&lt;/li&gt;
&lt;li class=&quot;task-list-item&quot;&gt;&lt;input type=&quot;checkbox&quot; disabled&gt; Backfill issue &lt;strong&gt;Type&lt;/strong&gt; on the ~24% currently untyped.&lt;/li&gt;
&lt;li class=&quot;task-list-item&quot;&gt;&lt;input type=&quot;checkbox&quot; disabled&gt; Claim before working; close-with-evidence is claim-exempt.&lt;/li&gt;
&lt;li class=&quot;task-list-item&quot;&gt;&lt;input type=&quot;checkbox&quot; disabled&gt; (Proposal) Stand up a &lt;code dir=&quot;auto&quot;&gt;v3.2.1&lt;/code&gt; milestone + one-line release goal in its description.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
