Files
imccyu c62f26aaa1 fix(ui-chat): keep notice-woken Turns in the human exchange
Under "On next message" folding, a Turn woken by a notice (settled
subagent, goal round, schedule, background job) advanced the bottom Turn
and folded the finished Turn without an own-input driver, so the generic
fold room left a following reader looking at blank space.

Chat Nodes now declare a group-tree position (`groupTree`, ordered
`exchange` > `turn` > `process`). Human input claimed in Step 1 marks its
Turn as opening an exchange; notices and later steering carry no
position. `GroupTreeSegments` splits the loaded Turns at opening Turns,
and `bottomSource` covers the whole latest exchange, so notice-woken
Turns no longer fold earlier ones while the next human message folds the
exchange through the own-input path. Only `exchange` is read today; the
`turn` and `process` positions are reserved for the existing kind lists.
2026-10-12 10:35:05 +08:00

26 lines
785 B
YAML

# Bilingual-pair consistency record for glossary.md (docs/i18n/README.md): per heading
# section, a hash of its English and Chinese blocks outside code blocks and generated regions.
# After editing either side, bring the other along and re-record with:
# pnpm run verify-translation-pairing --write docs/glossary.md
/glossary:
en: 9b364904616b2266
zh: 934b9d189a4f34a2
/glossary/capability-seam:
en: 18eea8301b73be7e
zh: 50f1adf512543a7e
/glossary/agent-scope:
en: 893655aaaa6a9db4
zh: 48b699fd15fa7ba6
/glossary/goal:
en: c64d9e91d54c6315
zh: a2918c9d276af8a1
/glossary/human-command:
en: 38a55fc61b359ace
zh: 567cae201b3a1bdf
/glossary/loop-hierarchy:
en: 6bf1ad7dd53f79cc
zh: 6231e68c769fdefa
/glossary/ralph:
en: 5059f8a377980b9d
zh: 39bf11c10e5c0a84