fix server retry memory input override ordering
This commit is contained in:
@@ -0,0 +1,12 @@
|
||||
# Retry memory input override ordering
|
||||
|
||||
On 2026-10-18, selected-stage retry input overrides are persisted separately
|
||||
from the immutable source-stage input. Retry reconstruction now resolves the
|
||||
selected stage's memory bindings from the original prefix first, then applies
|
||||
the validated override once to that invocation. This keeps the persisted
|
||||
`run_steps.input` and downstream handoff aligned with the requested correction
|
||||
without changing the source history or unrelated later stages.
|
||||
|
||||
The shared retry documentation and packaged OpenCode skill reference should be
|
||||
folded by the manual `docs-fold` pipeline; this note records the behavior change
|
||||
without editing those shared documents.
|
||||
Reference in New Issue
Block a user