@spec from_compiler(
  StatifierBlocks.Compiler.Finding.t(),
  keyword()
) :: {:ok, t()} | {:error, from_compiler_error()}

Adapts one StatifierBlocks.Compiler.Finding (ADR-0004 decision 10) into this module's presentation shape (ADR-0005 decision 11).

The presentation layer may depend on the compiler layer, never the reverse - a host that only compiles must not drag presentation concerns in - so this adapter lives here, in StatifierBlocks.Finding, and not in StatifierBlocks.Compiler.Finding. Compiler.Finding is one more differently-shaped source this module's moduledoc already promises to normalize.

Anchor (mechanical)

• block_id and config_key both present -> {:config, block_id, config_key}
• block_id present, config_key nil -> {:block, block_id}
• block_id nil (any config_key) -> refused, {:unanchorable, finding}

{:slot, id, name} is never produced: Compiler.Finding carries no slot name, so there is nothing to build one from. This is a known gap: sb-da9's slot-shaped structural findings (:undeclared_slot, slot arity) will need either a slot-bearing compiler finding or this seam widened (the :source override below is the closest existing hook) - that is future work, not built here.

Source (by rule, never by code)

New codes arrive continuously (sb-da9 adds :undeclared_slot and slot-arity codes; other emitters land in this campaign), so the mapping must never switch on code - an unknown code has to map correctly by construction. In order:

1. opts[:source], when given, wins outright. See "the :source override" below.
2. Severity that is not :error -> :lint. Decision 11 says every source but :lint produces :error, so a finding that is not an error cannot honestly be any other source. This is also what makes an :info severity representable end to end under the 2026-08-29 amendment's 11b (accepted; only :lint may produce one): a pass-through severity composed with this rule gets there for free.
3. Otherwise by stage: :config -> :config, :resolve -> :resolution, :structure -> :assignability.
4. Any other stage (:document, :emit, :chart at :error) -> :compile, under ADR-0005 amendment 11h. Rule 4 used to refuse instead: a compile error against generated SCXML or against the document envelope had no bucket in decision 11's enum, so the adapter refused rather than lie about where the rule lived. :compile is that bucket, and it is why an error the compiler raises at a stage this mapping does not name can now render in the editor at all - which is the half of 11h that makes the document-level panel's promise ("no finding can hide") true for compile errors too.

Because rule 4 no longer refuses, the anchor is the only thing that can: a block-less finding is {:unanchorable, _} even when its stage or severity would otherwise have mapped to a source, because there is nowhere to route it regardless of what it is about.

Severity (pass-through, not a two-clause case)

severity passes through unchanged. An :error/:warning case would go stale the moment Compiler.Finding's severity set widens to admit :info for advisory findings - decision 11's 2026-08-29 amendment accepted that severity, and 11b reserves it to :lint. Identity composed with source rule 2 above already gives the right answer for that day with no edit here, which is why the mapping does not enumerate the severities it knows about today.

Lossy on purpose

stage, fault, code and reason have no field in decision 11's four-field shape and are dropped by this adaptation. A caller that needs the fault split keeps the Compiler.Finding alongside the adapted one.

config_value_span is dropped for the same reason and is the one drop that costs a consumer something visible: it is decision 9's sub-expression span, and an editor rendering only the adapted finding underlines the whole field rather than the offending sub-expression. The anchor has nowhere to put it - {:config, id, key} names a field, not a range inside one - so widening decision 11's shape is what it would take, and that is an ADR-0005 change rather than an adapter change. Until then the same rule applies as for the fault split: keep the Compiler.Finding alongside.

The :source override

opts[:source] lets a caller that knows better than the default rule say so explicitly - the seam sb-da9's slot-shaped findings may eventually need. It is used exactly as given: it is already typed source() at the call site, so there is nothing left to validate.

@spec from_compiler_all(
  [StatifierBlocks.Compiler.Finding.t()],
  keyword()
) :: {[t()], [{StatifierBlocks.Compiler.Finding.t(), from_compiler_error()}]}

Adapts every finding in findings, partitioning into adapted findings (in input order) and every refusal paired with the Compiler.Finding that produced it (also in input order). Never silently drops a finding - length(ok) + length(refused) == length(findings) always holds - which is the same invariant StatifierBlocks.ViewModel's routing table protects ("No route drops a finding").

Wiring

The real path this exists for: compile with known_invoke_types:, take the invoke-type lint off Compiled.warnings, adapt it, and hand the result to ViewModel.build/3 as caller-supplied findings.

{:ok, compiled} =
  StatifierBlocks.Compiler.compile(document, palette, known_invoke_types: known)

{lint_findings, _refused} = StatifierBlocks.Finding.from_compiler_all(compiled.warnings)

view_model = StatifierBlocks.ViewModel.build(document, palette, lint_findings)

opts is applied to every finding in findings; see from_compiler/2.

@spec new(anchor(), source(), String.t(), keyword()) :: t()

Builds a finding, in the shape StatifierBlocks.Compiler.Finding.new/4 already uses: the fixed positional arguments first, message last among them, and everything else in opts.

opts carries :severity, defaulting to :error - the default every source but :lint uses (ADR-0005 decision 11).

@spec severity_class(t()) :: String.t()

The modifier class a finding's severity renders under (ADR-0005 decision 11, amended 2026-08-29 for :info).

It lives here rather than in each of the five components that render a finding, because it was five copies of the same two clauses and the amendment would have made it five copies of three. Decision 14's sb- prefix is a contract, so the one place that spells these names is worth having; and this module is outside StatifierBlocks.Editor.*, so a class name here costs a headless host nothing and is asserted with LiveView absent.

:info renders in a neutral advisory chrome, distinct from the warning family and never in the error family (amendment 11c).

iex> StatifierBlocks.Finding.severity_class(%StatifierBlocks.Finding{
...>   anchor: {:block, "blk_1"}, source: :lint, message: "x", severity: :info})
"sb-finding--info"