Repository navigation
Preserve explicit Monitor Todo selection in quota polling - #9099
Open
loopx-agent wants to merge 1 commit into
Open
loopx-agent wants to merge 1 commit into
loopx-agent wants to merge 1 commit into
Conversation
Carry Todo selection provenance into quota admission. Preserve explicit secondary Monitor polling and recovery from previously admitted receipts. Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
This branch has not been deployed
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.
Goal and delivered outcome
#9093 lets a caller observe a secondary due Monitor by supplying its Todo ID. The CLI also resolves a target key to a Todo internally for receipts. That derived ID could select a different due Monitor even when the caller supplied only its target key.
The quota decision now carries whether the Todo ID was supplied explicitly. A key alone must match the scheduled Monitor. An explicit ID can still identify another due Monitor claimed by the same Agent, subject to existing gates. Pending transactions retain their frozen admission when the receipt matches the original effect.
The patch also removes the unused Markdown renderer forwarding and the wrapper around the shared clock. The lookback smoke now uses an isolated fixture registry.
Author declaration
monitor_poll_admission.tsmonitor_poll_admission.tsmonitor_poll_commit.tsScope and continuation
This fixes quota Monitor admission independently of Chat. The same Monitor smoke passes in a local composition with #8717 at
d1668e0e9ada. That Chat PR still needs review of its current head.Validation
77da4e2f8e43d531cc3ddb9ef1553120a2993440against477def5c176ab4df92ac19ea1dd616828b325e87.finished. Input classessyntheticandpublic_fixture.regression_paritypassedreal_entrypointandreal_backendpassedmonitor-poll-writeback-smoke.pyon the candidate and combined Chat tree. File and SQLite canonical CLI cases covered selection, writeback and receipt recovery.integrationpassedstaticpassedintegrationpassedstaticfailedFrontend and visual evidence
none. This change affects admission on the existing CLI route.none.Type and area
Boundary checklist