<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/3.x/2026-05-12-1-wp03-review-mode-contract-PROPOSED/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-05-12-1-wp03-review-mode-contract-PROPOSED/</id>
  <title>PROPOSAL: `spec-kitty review` lightweight vs post-merge mode contract (WP03)</title>
  <updated>2026-05-12T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/3.x/2026-05-12-1-wp03-review-mode-contract-PROPOSED/"/>
  <summary>Proposes an explicit signal separating lightweight working-tree review from post-integration mission review, hard-blocking when required gate artifacts are absent.</summary>
  <content type="html">&lt;ul&gt;
&lt;li&gt;rev 1 (2026-05-12 AM): initial proposal, three open sub-questions.&lt;/li&gt;
&lt;li&gt;rev 2 (2026-05-12 PM): HiC resolved Q1 (hard-block with remediation guidance) and Q3 (keep gate logic &lt;em&gt;near&lt;/em&gt; review.py but pre-emptively refactor the file for god-class risk — see new WP07 in mission spec). Q2 remains open pending the drift-impact analysis below.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Date:&lt;/strong&gt; 2026-05-12&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Deciders:&lt;/strong&gt; Architect Alphonso (proposer), HiC (final decision)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Technical Story:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Mission &lt;code dir=&quot;auto&quot;&gt;review-merge-gate-hardening-3-2-x-01KRC57C&lt;/code&gt; WP03&lt;/li&gt;
&lt;li&gt;Source bug: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/985&quot;&gt;Priivacy-ai/spec-kitty#985&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Parent epic: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/822&quot;&gt;#822&lt;/a&gt;, &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/992&quot;&gt;#992&lt;/a&gt; (WS-5)&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty review&lt;/code&gt; (implemented at &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/review.py:235&lt;/code&gt;) is documented as a four-step post-merge validation (WP lane check, dead-code scan, BLE001 audit, report writer). In practice the command &lt;strong&gt;can also be invoked before merge&lt;/strong&gt; to perform consistency checks against the working tree — and there is no explicit signal in code or surface telling the two intentions apart.&lt;/p&gt;
&lt;p&gt;The mission-review doctrine for &lt;em&gt;post-merge&lt;/em&gt; runs requires:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; (hand-authored Markdown table, conventional in 7 prior stable/release missions, no generator)&lt;/li&gt;
&lt;li&gt;Gate 1–4 records (currently inline in &lt;code dir=&quot;auto&quot;&gt;review.py:291–446&lt;/code&gt;, not surfaced as report fields)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission-exception.md&lt;/code&gt; when cross-repo E2E has an environmental xfail&lt;/li&gt;
&lt;li&gt;A non-trivial &lt;code dir=&quot;auto&quot;&gt;mission-review-report.md&lt;/code&gt; whose YAML frontmatter (&lt;code dir=&quot;auto&quot;&gt;verdict&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;reviewed_at&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;findings&lt;/code&gt;) accurately reflects the gates that ran&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The bug (#985) is that the existing command can emit &lt;code dir=&quot;auto&quot;&gt;verdict: pass / findings: 0&lt;/code&gt; from a &lt;em&gt;post-merge intent&lt;/em&gt; invocation while none of the required artifacts exist — and operators take that as authoritative release evidence.&lt;/p&gt;
&lt;p&gt;The mission spec FR-005 calls for two explicit modes. The architectural question is: &lt;strong&gt;what is the canonical signal that selects the mode, and what is the report contract per mode?&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id=&quot;decision-drivers&quot;&gt;Decision Drivers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Operator transparency.&lt;/strong&gt; A reviewer must never mistake a lightweight check for a release gate. The mode must be visible in stdout, JSON, and the persisted report.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Backward compatibility.&lt;/strong&gt; Existing operator workflows (&lt;code dir=&quot;auto&quot;&gt;spec-kitty review --mission &amp;#x3C;slug&gt;&lt;/code&gt; without a flag) should not break; behavior may change but not in a way that turns a currently-passing legitimate invocation into a stderr-only spew.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Existing signals.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;meta.json.baseline_merge_commit&lt;/code&gt; is already populated by post-083 mission merge and is the &lt;em&gt;only&lt;/em&gt; explicit post-merge signal in code today (&lt;code dir=&quot;auto&quot;&gt;review.py:284–285&lt;/code&gt;). Reusing it avoids inventing a new lifecycle concept that #992 WS-1 may want to define centrally.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;JSON stability.&lt;/strong&gt; FR-009 requires diagnostic codes to be JSON-stable for the cross-surface fixture harness (#992 Phase 0). Mode names and failure codes must be machine-parseable strings.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Lightweight mode must remain useful.&lt;/strong&gt; Pre-merge consistency checks are valuable during mission iteration; the contract must not push operators away from them.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;considered-options&quot;&gt;Considered Options&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;(A) Implicit mode via &lt;code dir=&quot;auto&quot;&gt;baseline_merge_commit&lt;/code&gt; only&lt;/strong&gt; — no CLI flag; command auto-selects.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;(B) Explicit &lt;code dir=&quot;auto&quot;&gt;--mode {lightweight|post-merge}&lt;/code&gt; flag with auto-detect default&lt;/strong&gt; — flag overrides; default is auto-detect from &lt;code dir=&quot;auto&quot;&gt;baseline_merge_commit&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;(C) Two separate subcommands&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;spec-kitty review consistency&lt;/code&gt; vs &lt;code dir=&quot;auto&quot;&gt;spec-kitty review mission&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;(D) New &lt;code dir=&quot;auto&quot;&gt;mission_state&lt;/code&gt; field in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;&lt;/strong&gt; — explicit lifecycle field (&lt;code dir=&quot;auto&quot;&gt;proposed | in_progress | merged | accepted&lt;/code&gt;); command reads it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;proposed-decision-outcome&quot;&gt;Proposed Decision Outcome&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Recommended option: (B) Explicit &lt;code dir=&quot;auto&quot;&gt;--mode {lightweight|post-merge}&lt;/code&gt; flag with auto-detect default&lt;/strong&gt;, because it (i) satisfies FR-005 with the smallest CLI surface change, (ii) preserves backward compatibility via auto-detect from the already-existing &lt;code dir=&quot;auto&quot;&gt;baseline_merge_commit&lt;/code&gt; signal, (iii) gives operators an explicit override for the legitimate edge case of running lightweight checks on an already-merged mission (e.g., from a detached verification worktree), and (iv) does not pre-empt the centralized lifecycle authority work in #992 WS-1.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Concrete contract proposal (subject to HiC adjustment):&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Mode resolution order:&lt;/strong&gt;
&lt;ol&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;--mode&lt;/code&gt; CLI flag if present.&lt;/li&gt;
&lt;li&gt;Else &lt;code dir=&quot;auto&quot;&gt;lightweight&lt;/code&gt; if &lt;code dir=&quot;auto&quot;&gt;meta.json.baseline_merge_commit&lt;/code&gt; is absent.&lt;/li&gt;
&lt;li&gt;Else &lt;code dir=&quot;auto&quot;&gt;post-merge&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Lightweight mode contract.&lt;/strong&gt; Stdout/JSON output explicitly states &lt;code dir=&quot;auto&quot;&gt;mode: lightweight (not a release gate)&lt;/code&gt;. The persisted &lt;code dir=&quot;auto&quot;&gt;mission-review-report.md&lt;/code&gt; frontmatter adds &lt;code dir=&quot;auto&quot;&gt;mode: lightweight&lt;/code&gt; and writes “Lightweight consistency check; not a release gate” as the first line of the body. Lightweight mode runs only Step 1 (WP lane consistency) and Step 4 (report writer); skips dead-code scan and BLE001 audit. Verdict can still be &lt;code dir=&quot;auto&quot;&gt;pass&lt;/code&gt; but the report’s wording makes the limitation unambiguous.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Post-merge mode contract.&lt;/strong&gt; Stdout/JSON output explicitly states &lt;code dir=&quot;auto&quot;&gt;mode: post-merge (release gate)&lt;/code&gt;. The report frontmatter adds &lt;code dir=&quot;auto&quot;&gt;mode: post-merge&lt;/code&gt; and the following keys become &lt;strong&gt;required&lt;/strong&gt; for verdict &lt;code dir=&quot;auto&quot;&gt;pass&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;pass_with_notes&lt;/code&gt;:
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;issue_matrix_present: true&lt;/code&gt; (artifact &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; exists in the mission dir, or was auto-generated this run — see point 6 below)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;gates_recorded: [gate_1, gate_2, gate_3, gate_4]&lt;/code&gt; (each with &lt;code dir=&quot;auto&quot;&gt;command&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;exit_code&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;result&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_exception_present: true | not_applicable&lt;/code&gt; (when &lt;code dir=&quot;auto&quot;&gt;mission-exception.md&lt;/code&gt; is required and validated)
Absence of any required key → exit non-zero with a diagnostic.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Diagnostic codes (JSON-stable, per FR-009).&lt;/strong&gt; Proposed namespace &lt;code dir=&quot;auto&quot;&gt;MISSION_REVIEW_*&lt;/code&gt;:
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;MISSION_REVIEW_ISSUE_MATRIX_MISSING&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;MISSION_REVIEW_GATE_RECORD_MISSING&lt;/code&gt; (with subcode &lt;code dir=&quot;auto&quot;&gt;gate_1&lt;/code&gt;…&lt;code dir=&quot;auto&quot;&gt;gate_4&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;MISSION_REVIEW_MISSION_EXCEPTION_INVALID&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;MISSION_REVIEW_MODE_MISMATCH&lt;/code&gt; (e.g., &lt;code dir=&quot;auto&quot;&gt;--mode post-merge&lt;/code&gt; invoked when &lt;code dir=&quot;auto&quot;&gt;baseline_merge_commit&lt;/code&gt; is absent — explicit operator override of the auto-detect signal; warn-or-block per HiC choice in §“Open sub-questions for HiC” below)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;mission-review-report.md&lt;/code&gt; schema becomes explicit.&lt;/strong&gt; Today the YAML fields (&lt;code dir=&quot;auto&quot;&gt;verdict&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;reviewed_at&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;findings&lt;/code&gt;) are implicit in writer code. WP03 promotes them to a documented schema in &lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt; (and validates them in tests) so review tooling, dashboards, and the cross-surface harness can rely on a stable contract.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; handling.&lt;/strong&gt; Current pattern is hand-authored. WP03 adds (i) a documented Markdown schema (header columns: &lt;code dir=&quot;auto&quot;&gt;Issue | Scope | Verdict | Evidence ref&lt;/code&gt;), (ii) a passive validator (parse the table; fail if header drifts), (iii) &lt;strong&gt;NO auto-generation in this WP&lt;/strong&gt; (deferred to a successor mission once tracked-issue ingest is decided). Post-merge mode requires the file to exist; auto-generation is an explicit non-goal here per #822 anti-scope.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;consequences-if-approved&quot;&gt;Consequences if approved&lt;/h3&gt;
&lt;h4 id=&quot;positive&quot;&gt;Positive&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Operator can never mistake a lightweight check for a release gate (mode is in stdout, JSON, and the persisted report).&lt;/li&gt;
&lt;li&gt;The auto-detect default preserves backward compatibility for the canonical happy-path invocation.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; becomes a typed artifact (schema, validator) without inflating WP03 with auto-generation work.&lt;/li&gt;
&lt;li&gt;Diagnostic codes plug directly into the #992 Phase 0 cross-surface fixture harness with stable names.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;baseline_merge_commit&lt;/code&gt; becomes a real lifecycle signal — usable by #992 WS-1 later.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;negative&quot;&gt;Negative&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;One new CLI flag (&lt;code dir=&quot;auto&quot;&gt;--mode&lt;/code&gt;) on &lt;code dir=&quot;auto&quot;&gt;spec-kitty review&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Operator may run &lt;code dir=&quot;auto&quot;&gt;--mode post-merge&lt;/code&gt; on a pre-merge mission expecting a quick sanity check and get a hard fail. Mitigation: the &lt;code dir=&quot;auto&quot;&gt;MISSION_REVIEW_MODE_MISMATCH&lt;/code&gt; diagnostic is explicit. (HiC: choose warn vs block — see open sub-question.)&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;neutral&quot;&gt;Neutral&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;The bare invocation &lt;code dir=&quot;auto&quot;&gt;spec-kitty review --mission &amp;#x3C;slug&gt;&lt;/code&gt; continues to work; mode is implicit.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;confirmation&quot;&gt;Confirmation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Regression: synthetic mission with &lt;code dir=&quot;auto&quot;&gt;baseline_merge_commit&lt;/code&gt; set, no &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; → bare &lt;code dir=&quot;auto&quot;&gt;spec-kitty review&lt;/code&gt; exits non-zero with &lt;code dir=&quot;auto&quot;&gt;MISSION_REVIEW_ISSUE_MATRIX_MISSING&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Regression: same mission, &lt;code dir=&quot;auto&quot;&gt;--mode lightweight&lt;/code&gt; override → exit 0, report has &lt;code dir=&quot;auto&quot;&gt;mode: lightweight&lt;/code&gt;, body begins with “Lightweight consistency check; not a release gate”.&lt;/li&gt;
&lt;li&gt;Eat-our-own-dogfood (NFR-003): this mission’s own final review runs in &lt;code dir=&quot;auto&quot;&gt;--mode post-merge&lt;/code&gt;, produces an &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt;, and records Gate 1–4.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;pros-and-cons-of-the-options&quot;&gt;Pros and Cons of the Options&lt;/h2&gt;
&lt;h3 id=&quot;a-implicit-mode-via-baseline_merge_commit-only&quot;&gt;(A) Implicit mode via &lt;code dir=&quot;auto&quot;&gt;baseline_merge_commit&lt;/code&gt; only&lt;/h3&gt;
&lt;p&gt;No CLI flag; command always auto-selects mode from the meta field.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Zero new CLI surface.&lt;/li&gt;
&lt;li&gt;Smallest diff.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;No operator override. Verifying a merged mission from a detached worktree with a quick lightweight check becomes impossible.&lt;/li&gt;
&lt;li&gt;“Magic” behavior: the same command does different things in different contexts with no visible switch.&lt;/li&gt;
&lt;li&gt;Pre-083 missions (no &lt;code dir=&quot;auto&quot;&gt;baseline_merge_commit&lt;/code&gt; field) always run lightweight, even when run post-merge — silently.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;b-explicit---mode-flag-with-auto-detect-default&quot;&gt;(B) Explicit &lt;code dir=&quot;auto&quot;&gt;--mode&lt;/code&gt; flag with auto-detect default&lt;/h3&gt;
&lt;p&gt;Recommended above.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt; see “Consequences if approved” above.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt; see “Consequences if approved” above. The only real cost is one new flag.&lt;/p&gt;
&lt;h3 id=&quot;c-two-separate-subcommands&quot;&gt;(C) Two separate subcommands&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty review consistency&lt;/code&gt; vs &lt;code dir=&quot;auto&quot;&gt;spec-kitty review mission&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Maximal clarity. Hard to misuse.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Breaks every existing invocation of &lt;code dir=&quot;auto&quot;&gt;spec-kitty review&lt;/code&gt;. Hidden in agents, prompts, mission templates, doctrine, docs. Out of proportion for a stabilization mission.&lt;/li&gt;
&lt;li&gt;Violates #822 anti-scope clause on “no new CLI surface beyond what a single bug fix requires.”&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;d-new-mission_state-field-in-metajson&quot;&gt;(D) New &lt;code dir=&quot;auto&quot;&gt;mission_state&lt;/code&gt; field in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Add &lt;code dir=&quot;auto&quot;&gt;mission_state: proposed | in_progress | merged | accepted&lt;/code&gt; to meta.json; command reads it.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Cleanest semantic model.&lt;/li&gt;
&lt;li&gt;Aligns with #992 WS-1 future direction.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Cross-cutting: every status-mutating command (next, agent action, move-task, merge) would need to write the field consistently. That is exactly the WorkPackageLifecycle authority work the #992 epic is meant to do. &lt;strong&gt;Doing it inside WP03 pre-empts and inflates a separate workstream.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Migration: existing missions need backfill.&lt;/li&gt;
&lt;li&gt;This is a &lt;em&gt;successor&lt;/em&gt; mission’s design, not WP03’s.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;resolved-sub-questions-hic-2026-05-12&quot;&gt;Resolved sub-questions (HiC, 2026-05-12)&lt;/h2&gt;
&lt;h3 id=&quot;q1--mode-mismatch-behavior--resolved-hard-block-with-remediation-guidance&quot;&gt;Q1 — Mode mismatch behavior → &lt;strong&gt;RESOLVED: hard-block with remediation guidance&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;HiC accepted the recommendation: when an operator runs &lt;code dir=&quot;auto&quot;&gt;--mode post-merge&lt;/code&gt; against a mission whose &lt;code dir=&quot;auto&quot;&gt;meta.json.baseline_merge_commit&lt;/code&gt; is absent, the command &lt;strong&gt;blocks&lt;/strong&gt; with &lt;code dir=&quot;auto&quot;&gt;MISSION_REVIEW_MODE_MISMATCH&lt;/code&gt;. Implementation detail added by HiC: the diagnostic must contain (i) a clear description of &lt;em&gt;what is going on&lt;/em&gt; (i.e., “this mission has not been merged; post-merge review requires a baseline commit”), and (ii) a &lt;em&gt;suggested remediation path&lt;/em&gt; the operator can follow.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Diagnostic message contract (encoded as part of WP03 acceptance):&lt;/strong&gt;&lt;/p&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;plaintext&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:#d6deeb;--1:#403f53&quot;&gt;ERROR: MISSION_REVIEW_MODE_MISMATCH&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;Mission &apos;&amp;#x3C;slug&gt;&apos; has no baseline_merge_commit recorded in meta.json.&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;Post-merge mission review requires the mission to be merged first&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;(the merge step records the baseline commit that the review compares against).&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;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;What this means:&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;    &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;--mode post-merge expects to validate a merged mission against its&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;    &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;release-gate doctrine. Running it on a pre-merge mission would either&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;    &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;inspect an arbitrary point in the working tree (false confidence) or&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;    &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;fail the dead-code scan trivially.&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;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;Remediation options:&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;    &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;1. If the mission is ready to merge: run &apos;spec-kitty merge --mission &amp;#x3C;slug&gt;&apos;&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;       &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;and re-run this command after the merge completes.&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;    &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;2. If you want a pre-merge sanity check: re-run with --mode lightweight.&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;    &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;3. If meta.json baseline_merge_commit is missing because of a pre-083&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;       &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;legacy mission: see docs/migration/mission-id-canonical-identity.md&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;       &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;and run &apos;spec-kitty migrate backfill-identity&apos; first.&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;The diagnostic is JSON-stable: machine-parseable code (&lt;code dir=&quot;auto&quot;&gt;MISSION_REVIEW_MODE_MISMATCH&lt;/code&gt;) plus human-readable body. Stdout writes the code; the body goes to stderr. JSON output includes both as structured fields.&lt;/p&gt;
&lt;h3 id=&quot;q3--gate-source-of-truth--resolved-keep-gate-logic-near-reviewpy-but-pre-emptively-split-the-file&quot;&gt;Q3 — Gate source-of-truth → &lt;strong&gt;RESOLVED: keep gate logic near review.py, but pre-emptively split the file&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;HiC accepted the “leave inline for now” recommendation &lt;strong&gt;with a structural caveat&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/review.py&lt;/code&gt; is at risk of becoming a god-module (multiple concerns, growing LOC) once WP03’s contract enforcement code lands on top of the existing gate logic. To prevent that, a &lt;strong&gt;hygiene refactor of &lt;code dir=&quot;auto&quot;&gt;review.py&lt;/code&gt;&lt;/strong&gt; must happen &lt;em&gt;before&lt;/em&gt; WP03’s contract code is added.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Important scope distinction:&lt;/strong&gt; this refactor is a &lt;strong&gt;mechanical file/method split for hygiene&lt;/strong&gt;, not a domain-context extraction. The full domain split (e.g., extracting a &lt;code dir=&quot;auto&quot;&gt;ReleaseEvidence&lt;/code&gt; aggregate) belongs to #992 WS-5 ReleaseEvidence in a successor mission. WP03’s refactor scope is strictly:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Split &lt;code dir=&quot;auto&quot;&gt;review.py&lt;/code&gt; into a small package: &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/review/__init__.py&lt;/code&gt; + sibling files for each Gate.&lt;/li&gt;
&lt;li&gt;Extract generic helpers (e.g., report writer, lane-check, dead-code scanner, BLE001 audit) into named functions in dedicated sibling files (&lt;code dir=&quot;auto&quot;&gt;_report.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_lane_gate.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_dead_code.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_ble001_audit.py&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;The public &lt;code dir=&quot;auto&quot;&gt;review_mission()&lt;/code&gt; entry stays where it is so all existing imports remain valid.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No new abstractions, no new public types, no domain modeling.&lt;/strong&gt; Anything more sophisticated than “move methods to sibling files and stop the LOC bleed” is out of scope for WP03’s refactor and belongs to the WS-5 successor mission.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This refactor is captured as &lt;strong&gt;WP07 in the mission spec&lt;/strong&gt; (prerequisite to WP03). See mission spec for FRs.&lt;/p&gt;
&lt;h2 id=&quot;open-sub-questions-for-hic&quot;&gt;Open sub-questions for HiC&lt;/h2&gt;
&lt;h3 id=&quot;q2--issue-matrixmd-validator-strictness--still-open-hic-requested-more-background&quot;&gt;Q2 — &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; validator strictness → &lt;strong&gt;still open; HiC requested more background&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;HiC: “I need more background to make an informed decision here. Explain the issue, and what the issue-matrix drift would mean in practice.”&lt;/p&gt;
&lt;h4 id=&quot;what-issue-matrixmd-is-in-concrete-terms&quot;&gt;What &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; is, in concrete terms&lt;/h4&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; is the per-mission audit ledger that records, for each GitHub issue in the mission’s scope, the resolution verdict and the evidence supporting that verdict. It is hand-authored today (no generator). The conventional shape — established by the mission &lt;code dir=&quot;auto&quot;&gt;stability-and-hygiene-hardening-2026-04-01KQ4ARB&lt;/code&gt; on 2026-04-26 — is a Markdown table.&lt;/p&gt;
&lt;h4 id=&quot;observed-drift-in-three-recent-missions-real-examples-on-originmain&quot;&gt;Observed drift in three recent missions (real examples on &lt;code dir=&quot;auto&quot;&gt;origin/main&lt;/code&gt;)&lt;/h4&gt;
&lt;p&gt;The shape today is NOT identical across missions. Examined three:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Shape A&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;stable-320-release-blocker-cleanup-01KQW4DF/issue-matrix.md&lt;/code&gt;):&lt;/p&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;markdown&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:#D6DEEB;--1:#403F53&quot;&gt;| Issue | Scope | Verdict | Evidence ref |&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:#D6DEEB;--1:#403F53&quot;&gt;|-------|-------|----------|--------------|&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:#D6DEEB;--1:#403F53&quot;&gt;| #952  | …     | fixed   | WP01; &amp;#x3C;files&gt;; &amp;#x3C;tests&gt;; CI &amp;#x3C;jobs&gt; passed on PR #981 |&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;&lt;strong&gt;Shape B&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;release-3-2-0a5-tranche-1-01KQ7YXH/issue-matrix.md&lt;/code&gt;):&lt;/p&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;markdown&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:#D6DEEB;--1:#403F53&quot;&gt;| Issue | FR | WP | Verdict | evidence_ref |&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:#D6DEEB;--1:#403F53&quot;&gt;|-------|----|----|---------|--------------|&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:#D6DEEB;--1:#403F53&quot;&gt;| #705  | FR-002 | WP01 | &lt;/span&gt;&lt;span style=&quot;--0:#C5E478;--1:#3B61B0&quot;&gt;`fixed`&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; | … |&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;&lt;strong&gt;Shape C&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;charter-golden-path-e2e-tranche-1-01KQ806X/issue-matrix.md&lt;/code&gt;):&lt;/p&gt;
&lt;p&gt;No leading table at all — narrative prose first explaining the verdict legend, then the table appears further down with column names &lt;code dir=&quot;auto&quot;&gt;Issue | Verdict | Evidence&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Three drift dimensions are already in the wild:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Column count and order.&lt;/strong&gt; Shape A has 4 columns; Shape B has 5 (&lt;code dir=&quot;auto&quot;&gt;FR&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;WP&lt;/code&gt; columns added).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Column-name capitalization and spacing.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;Evidence ref&lt;/code&gt; vs &lt;code dir=&quot;auto&quot;&gt;evidence_ref&lt;/code&gt; — same intent, different identifiers.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Document structure.&lt;/strong&gt; Shape C puts narrative ahead of the table, which a naive Markdown-table parser would either skip or fail on depending on its rules.&lt;/li&gt;
&lt;/ol&gt;
&lt;h4 id=&quot;what-drift-means-in-practice-for-the-new-contract&quot;&gt;What “drift” means in practice for the new contract&lt;/h4&gt;
&lt;p&gt;WP03 introduces tooling that depends on &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; being machine-readable:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Cross-surface fixture harness&lt;/strong&gt; (#992 Phase 0): asserts the matrix exists and can be parsed for a synthesized post-merge fixture.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dashboard rendering&lt;/strong&gt;: if/when the dashboard ever surfaces issue-matrix verdicts per mission, it needs predictable column semantics.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;gates_recorded&lt;/code&gt; report field&lt;/strong&gt; (FR-007): WP03 wants to record the per-issue verdict alongside Gate 1–4 records; the join key is the matrix’s &lt;code dir=&quot;auto&quot;&gt;Issue&lt;/code&gt; column.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If WP03 ships with a &lt;strong&gt;strict validator&lt;/strong&gt; (hard-fail on header drift):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;Positive:&lt;/em&gt; breakage is loud and immediate. The first mission that drifts can’t pass post-merge review until the matrix conforms. The schema stabilizes for downstream consumers.&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Negative:&lt;/em&gt; legitimate evolution of the matrix (e.g., a future “Severity” column) requires a coordinated schema bump. Past missions whose matrix shape predates the validator would fail when re-reviewed (though re-review is rare).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If WP03 ships with a &lt;strong&gt;loose validator&lt;/strong&gt; (warn-and-parse-what-you-can):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;Positive:&lt;/em&gt; tolerates the existing shape variation; doesn’t break re-review of past missions.&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Negative:&lt;/em&gt; downstream consumers (harness, dashboard, future tooling) get unpredictable data. The drift problem persists because “warn” is widely ignored. We end up with &lt;code dir=&quot;auto&quot;&gt;feedback://&lt;/code&gt; vs &lt;code dir=&quot;auto&quot;&gt;review-cycle://&lt;/code&gt; all over again (cf. #962 — silent pointer-scheme drift that took a dedicated bug to fix).&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;architect-alphonso-revised-recommendation&quot;&gt;Architect Alphonso revised recommendation&lt;/h4&gt;
&lt;p&gt;&lt;strong&gt;Hard-fail (strict) on the &lt;em&gt;header row only&lt;/em&gt;&lt;/strong&gt;, with a single forward-compatibility rule: columns may be &lt;strong&gt;added&lt;/strong&gt; without breaking validation, but the four canonical columns &lt;code dir=&quot;auto&quot;&gt;Issue | Scope | Verdict | Evidence ref&lt;/code&gt; must be present in that order. Renames, removals, or capitalization changes hard-fail with &lt;code dir=&quot;auto&quot;&gt;MISSION_REVIEW_ISSUE_MATRIX_SCHEMA_DRIFT&lt;/code&gt;. The body rows are parsed loosely (free-form Markdown in cells) to keep authoring practical.&lt;/p&gt;
&lt;p&gt;This (i) stabilizes the canonical contract that downstream consumers depend on, (ii) makes legitimate forward evolution (extra columns) possible without a coordinated schema bump, (iii) catches the high-cost drift modes (rename, reorder, remove) loudly. The existing missions whose shape diverges are not currently re-reviewed by tooling, so the constraint only fires forward from WP03 onward; if they ever are re-reviewed, the operator gets a clear diagnostic naming the missing canonical column.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;HiC decision needed:&lt;/strong&gt; approve “strict on header, additive-tolerant, loose on body” — or override with a different stance (looser, stricter, or different forward-compat rule).&lt;/p&gt;
&lt;h2 id=&quot;more-information&quot;&gt;More Information&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Source bug body: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/985&quot;&gt;#985&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Code reference: &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/review.py:235&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;review_mission&lt;/code&gt; entry point); &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/review.py:284–285&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;baseline_merge_commit&lt;/code&gt; check); &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/review.py:465–470&lt;/code&gt; (current YAML frontmatter writer).&lt;/li&gt;
&lt;li&gt;Mission spec FR-005 through FR-009 and NFR-001 through NFR-003 in &lt;code dir=&quot;auto&quot;&gt;kitty-specs/review-merge-gate-hardening-3-2-x-01KRC57C/spec.md&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
