feat: strengthen chatloop continuation flow#179
Merged
Conversation
Contributor
|
Preview available at: https://chattool.wzhecnu.cn/dev/ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
chatloopinto a PRD-aware continuation loop: bootstrap always injects the PRD contract, continuation reuses an auto-loop style state machine, and completion now requires structured progress plus a validatedSTATUS: COMPLETE/<complete>DONE</complete>pair.opencode/chatloop.events.log, stronger status/debug output, toast feedback for activation / continuation / rejected completion / max-iterations / pause, and cleanup of the legacy file-plugin config entrychatloop-from-auto-loopdesign write-up, update setup/workspace docs, bump ChatTool to6.6.2, and extendsetup workspaceto generatereference/,docs/themes/, and aworkspace-maintenanceskill for periodic workspace cleanupTesting
pytest tests/code-tests/test_setup_nodejs.py tests/mock-cli-tests/opencode/test_chattool_setup_opencode_basic.py tests/mock-cli-tests/setup/test_chattool_setup_workspace_mock_basic.py tests/cli-tests/setup/test_chattool_setup_workspace_real_basic.pypytest tests/mock-cli-tests/opencode/test_chattool_setup_opencode_basic.py tests/mock-cli-tests/opencode/test_chattool_setup_opencode_install_only.py tests/mock-cli-tests/setup/test_chattool_setup_workspace_mock_basic.py tests/cli-tests/setup/test_chattool_setup_workspace_real_basic.py tests/code-tests/test_setup_nodejs.pyNotes
opencode runis still not a reliable environment for validating multi-iteration continuation or max-iteration behavior because the instance disposes immediately after the first idle; TUI or attach-style sessions remain the correct validation path for those behaviorsprojects/, cross-project reusablereference/, and long-lived conventions underdocs/themes/so periodic cleanup can happen without overloading active project directories