c3e35cbe95
Review follow-up: the consumer-facing contract still described the removed suppression. TurnErrorNode's JSDoc, the client-runtime retry-projection README section, and the ui-conversation chat-flow section (both languages) now state that a terminal turn/end error always projects the node, beside the settled retry chain when retries exhausted, and that only intermediate failures that scheduled another retry stay retry-notice-only. The recovery note sheds its remaining cross-turn wording (closed-step boundary, retry turns, closed failed step/turn) for the same-turn reality.
6 lines
547 B
YAML
6 lines
547 B
YAML
# Bilingual-pair consistency record (docs/i18n/README.md): the git blob hash of each
|
|
# side as of the last confirmed-consistent state. Both languages carry equal authority;
|
|
# after editing either side, bring the other along and re-record with:
|
|
# pnpm run verify-translation-pairing --write .agents/notes/implemented/architecture/2026-06-21-bounded-llm-request-recovery.md
|
|
2026-06-21-bounded-llm-request-recovery.md: e725a025f2d8b0d5e8eaf4137f07d8eab4448bf4
|
|
2026-06-21-bounded-llm-request-recovery.zh.md: 9e2263b05888797eaaaeb82859730d1c4a728cea
|