Field-verified: multiline text input strips braces, same input's single-line mode passes probe + full plan - the probe decides, not the label

This commit is contained in:
Z User 2026-10-30 23:18:02 +00:00
parent dbb6c82e1f
commit 23d0def305
9 changed files with 4 additions and 1 deletions

View File

@ -219,7 +219,10 @@ shipped as `h3_agent_workflow_examples/brace_probe_oneline.json`:
A rendered one-shot test card means the surface is clean; `Extra data: line 1 A rendered one-shot test card means the surface is clean; `Extra data: line 1
column 8 (char 7)` (`"shots"` is 7 characters) means it eats braces — deliver column 8 (char 7)` (`"shots"` is 7 characters) means it eats braces — deliver
through the internal widget instead. through the internal widget instead. Field observation from a live session: a
multiline text-input widget stripped the braces while the same input's regular
single-line mode passed both the probe and the full 5.8 kB example plan — multiline
text widgets are the prime suspect, but the probe decides, never the label.
A leftover demo or earlier plan AHEAD of the paste also reports `Extra data`, but A leftover demo or earlier plan AHEAD of the paste also reports `Extra data`, but
only after the whole leftover object parses — its `char N` is far larger than the only after the whole leftover object parses — its `char N` is far larger than the

View File

View File

0
h3-plan-gate/h3_agent_workflow_examples/outline.json Normal file → Executable file
View File

0
h3-plan-gate/h3_agent_workflow_examples/plan.json Normal file → Executable file
View File

View File

0
h3-plan-gate/h3_agent_workflow_examples/scene_01.json Normal file → Executable file
View File

0
h3-plan-gate/h3_agent_workflow_examples/scene_02.json Normal file → Executable file
View File

0
h3-plan-gate/h3_agent_workflow_examples/scene_03.json Normal file → Executable file
View File