feat(status): refresh Downshift footer at durable lifecycle points - #20
Merged
Conversation
Centralize config loading and footer updates for lifecycle-driven status refreshes. Refresh after model turns and agent settlement, and update the footer immediately after configuration saves without changing threshold decision timing.\n\nAdd adapter-level coverage for lifecycle refreshes, config-save updates, and the absence of model-switching side effects.
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
refreshStatus().turn_endandagent_settledwithout invoking threshold decisions or model transitions.Verification
npm run checkNotes
The installed Pi Coding Agent typings do not yet declare
agent_settled, so the extension uses a narrow local API type for registering that lifecycle handler while preserving the requested runtime event integration.