feat(dsh): capture effective route from durable request evidence - #50
Merged
Merged
Conversation
11 tasks
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.
Why
#46 now has a host-agnostic requested/resolved/effective contract, but
effectivemust be populated from runtime evidence rather than inferred from policy or UI state. DSHelm already has an authoritative keyless execution contract built around the durable DSHrequest/header; this increment turns that evidence into a production observation helper.Change
observeEffectiveRouteFromSession()in@dshelm/dsh;request/header;EffectiveRouteObservation;undefinedwhen no valid runtime header exists;GenerateOptionsand the durable request header;Evidence boundary
This proves capture from the DSH session request record used by the real AgentLoop fixture. It does not yet persist observations into the parent control-plane projection, render them in the Web UI, infer dollar cost, or emit escalation warnings.
Refs #46 #31 #32.