Repository navigation
fix(harness): read the consumed engine catalogue in external estates - #220
Merged
rldyourmnd merged 2 commits intoOct 8, 2026
Merged
Conversation
Signed-off-by: rldyourmnd <danil@nddev.it.com>
Signed-off-by: rldyourmnd <danil@nddev.it.com>
rldyourmnd
deleted the
fix/external-estate-harness-observation-20261008
branch
October 8, 2026 00:14
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.
Harness observations in a separate estate failed because detection and adapter inspection read
harnesses/from the estate rather than its consumed engine module. Resolve catalogue, profiles and evaluation contracts with the same source-layout resolver used by validation and mutation planning; retain estate-relative evidence inputs and the explicit adapter target.The regression fixture has a malformed estate-local catalogue, a valid consumed module and synthetic version binaries for all eight identities. It covers single/all detection, matching canonical renders, inspection, doctor, model-free evaluation, device reconciliation and refusal to configure installed-only Devin, and verifies that home and target remain empty.
Validation: focused external-estate regression passes; full Go suite and quick validation are recorded on this head.