Bound automatic continuation for long-running sessions - #121
Conversation
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
|
Audit update: GitHub reports this draft PR as DIRTY because its base is local Forge main at 3e7cb77, which is 145 commits behind origin/main. The original checkout remains untouched and dirty; no rebase was performed. A fresh remote-main branch is the next integration gate, requiring path-by-path conflict resolution for ui.rs, update.rs, log.rs, README, and the generated schema before merge. The bounded recursion guard itself is at MAX_AUTO_CONTINUE_ATTEMPTS = 8; full Cargo compile/test remains unclaimed. |
|
Closing as superseded. The clean replacement PR #122 ("Bound automatic continuation after interrupt limits") was merged into This draft served its purpose as a preservation snapshot of the original dirty checkout. The provenance is retained in the |
Summary\n- capture the existing six-file auto-continue and UX changes on an isolated branch\n- bound recursive non-interactive continuation to 8 chained interruptions\n- reset the continuation budget on a new top-level message or successful completion\n\n## Verification\n- cargo metadata --offline --no-deps --format-version 1 passed\n- git diff --check passed on the original dirty checkout (line-ending warnings only)\n- nightly rustfmt parsed the touched Rust files but reports pre-existing formatting diffs; full Cargo compile/test is not claimed\n\n## Scope\nThe source checkout at main remains dirty and unchanged by this publication. This draft intentionally preserves the original six-file diff for review; it has not been merged or deployed.