fix(workflows): surface unknown-key warnings where authors are, and correct the interactive hint - #2455

Merged

Wirasm merged 18 commits into

devfrom

fix/2213-surface-unknown-key-warnings

Aug 5, 2026

Commits on Aug 5, 2026

fix(workflows): warn on unknown/misplaced keys in workflow YAML (#2213)

kagura-agent
authored and
Wirasm
committed
6a0034f
fix: remove unnecessary type assertion (lint)

kagura-agent
authored and
Wirasm
committed
43ca32b
fix: address CodeRabbit review — reverse hint + warning override cleanup

kagura-agent
authored and
Wirasm
committed
5dd8c00
fix: derive key sets from schema shapes, improve interactive hint

kagura-agent
authored and
Wirasm
committed
d845ce5
fix(workflows): correct the interactive hint and detect unknown keys one level down
Wirasm
committed
dc71bd7
fix(cli,core,server,web): surface parse warnings on the surfaces authors use
Wirasm
committed
2ace0a5
docs(workflows): document unknown-key warnings and where they appear
Wirasm
committed
f5280d0
fix(workflows): attach parse warnings to the discovery entry, not a parallel map
Wirasm
committed
e2a41bf
fix(core): surface parse warnings when a run STARTS in chat or the console
Wirasm
committed
2d65371
fix(workflows): make the "cannot drift" claim true, and correct the hint again
Wirasm
committed
ab1713a
test,docs(workflows): cover the json payload path, the console mapping, and the include gap
Wirasm
committed
54426aa
fix(core,web,docs): address CodeRabbit review on #2455
Wirasm
committed
c4deb0d
test(workflows): parse the corpus directly instead of running full discovery
Wirasm
committed
b39e352
fix(workflows): fold fan_out into the derived key sets after the #2224 rebase
Wirasm
committed
22a6636
docs(workflows): say why the nested-key registry's position is load-bearing
Wirasm
committed
510f87e
docs(workflows,cli,core): stop the warning surfaces from over-claiming their own reach
Wirasm
committed
159aa60
feat(workflows): record dropped YAML keys on the run, not just in a chat message
Wirasm
committed
8af2bc9
test(workflows): say which half of the collision pair is actually load-bearing
Wirasm
committed
ca1c08c

Navigation Menu

fix(workflows): surface unknown-key warnings where authors are, and correct the interactive hint - #2455

fix(workflows): surface unknown-key warnings where authors are, and correct the interactive hint#2455
Wirasm merged 18 commits into
devfrom
fix/2213-surface-unknown-key-warnings

Commits on Aug 5, 2026

fix(workflows): warn on unknown/misplaced keys in workflow YAML (#2213)

fix: remove unnecessary type assertion (lint)

fix: address CodeRabbit review — reverse hint + warning override cleanup

fix: derive key sets from schema shapes, improve interactive hint

fix(workflows): correct the interactive hint and detect unknown keys one level down

fix(cli,core,server,web): surface parse warnings on the surfaces authors use

docs(workflows): document unknown-key warnings and where they appear

fix(workflows): attach parse warnings to the discovery entry, not a parallel map

fix(core): surface parse warnings when a run STARTS in chat or the console

fix(workflows): make the "cannot drift" claim true, and correct the hint again

test,docs(workflows): cover the json payload path, the console mapping, and the include gap

fix(core,web,docs): address CodeRabbit review on #2455

test(workflows): parse the corpus directly instead of running full discovery

fix(workflows): fold fan_out into the derived key sets after the #2224 rebase

docs(workflows): say why the nested-key registry's position is load-bearing

docs(workflows,cli,core): stop the warning surfaces from over-claiming their own reach

feat(workflows): record dropped YAML keys on the run, not just in a chat message

test(workflows): say which half of the collision pair is actually load-bearing