Advisory issues read as advice rather than failure

`ADVISORY_ISSUES` moves next to `ValidationIssue` in pipeline.py, and the
model derives an `advisory` flag from its own code, so the distinction the
engine already made ships to the client instead of being re-guessed there.

The dock keeps its summary in `--destructive` only when a real fault is
among the issues and paints an advisory row `--muted-foreground`; the
canvas leaves advisories off a node's dot and border entirely, since node
status has three colours and no warning tier.

biome checks the generated `openapi.json`, which nothing formats since the
SDK script dropped its format pass — ignore it like the other generated
files.
This commit is contained in:
2026-08-25 21:46:40 +02:00
parent b2466bfc44
commit cdb1bffdd4
9 changed files with 59 additions and 14 deletions
+4 -1
View File
@@ -336,7 +336,10 @@ function FlowEditorInner({
const issuesByNode = useMemo(() => {
const map = new Map<string, string[]>()
for (const issue of issues) {
if (!issue.node) continue
// A node's dot and border are its status channel, and status has no
// warning tier — an advisory is not a fault, so it says its piece in the
// dock rather than painting the node red.
if (!issue.node || issue.advisory) continue
const list = map.get(issue.node) ?? []
list.push(issue.message)
map.set(issue.node, list)