Restore demand history and serve pending machine requests - #179
Merged
Conversation
AgentTanuki
changed the title
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
1 participant
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.
The public demand and utility reports lost older requests and invocations when the serving cache was trimmed, even though SQLite retained those events. The conversion report also checked obsolete outcome names and missed current delivery, acceptance and neutral-stop records.
Read these reports from a fixed, replayable durable event view, disclose incomplete history and separate actual receipt states. Preserve signed feed content and conditional caching. Persist first-party labels before appending discovery/invocation events; disclose that historical missing attribution cannot be reconstructed. Report acquisition cost as unknown because no allocated cost ledger exists.
Restoring history also exposed queued requests being crowded out by the scout's historical top ten. Eligible pending requests now go first in queue order, with the same per-run limit, qualification rules and network behaviour. Updated scout fixtures isolate each scenario's new requests from earlier tests' retained history; the canary fixture stamps its timestamp before persistence.
Validation: 14 new regression cases; 68 focused database checks; full JSON suite 2,032 passed / 17 skipped; full SQLite suite 2,033 passed / 16 skipped. Contract generation has no drift. Historical count corrections are explicitly labelled and do not establish new adoption, useful paid work or independent ownership.