From 872b5622edcecd6e1933c017685735d19ee8b651 Mon Sep 17 00:00:00 2001
From: Teakowa <27560638+Teakowa@users.noreply.github.com>
Date: Tue, 3 Nov 2026 16:31:22 +0800
Subject: [PATCH] docs: record lint findings in check and compile (ADR-0011)

ADR-0011 still said lint findings are outside the check gate. Record the owner decision on #1032.

Refs #1032
---
 docs/adr/0011-distinct-tooling-workflows.md | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/docs/adr/0011-distinct-tooling-workflows.md b/docs/adr/0011-distinct-tooling-workflows.md
index ae4b2a7e..9fdfc269 100644
--- a/docs/adr/0011-distinct-tooling-workflows.md
+++ b/docs/adr/0011-distinct-tooling-workflows.md
@@ -36,7 +36,10 @@ inputs:
    canonical validation, their diagnostics are included as well. A complete
    compiler backend is not a prerequisite for diagnostic `check`, and an
    unavailable requested stage remains an explicit owner/provider outcome.
-   Ordinary configurable lint findings are not part of this gate by default.
+   Since Issue #1032, `check` and `compile` also report the enabled `lint`
+   findings in their diagnostics and counts, under the same rule configuration
+   and severity overrides as `lint`. A warning does not fail either command; a
+   rule raised to `error` does.
 2. **`lint`** applies configurable Wright or local rules to semantic facts and
    reports rule findings. Findings retain stable rule identity, effective
    severity, support classification, boundedness where applicable, and
@@ -67,7 +70,7 @@ framework is not required before a useful, deterministic report exists.
 
 - CLI, driver, tool, and agent consumers must preserve the workflow-specific
   result types while sharing common envelopes and semantic inputs.
-- Changes to lint policy do not silently change the correctness gate.
+- Lint policy changes alter the `check` and `compile` verdict only through an explicit rule severity of `error`.
 - New analysis facts can be introduced without creating a lint rule or
   assigning project severity.
 - The `AnalyzeResult` payload is a facts/report contract rather than a finding