Repository navigation
feat(harness): observe installed Devin without configuring it - #219
Merged
Merged
Conversation
Signed-off-by: rldyourmnd <danil@nddev.it.com>
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.
GDS rejected an installed Devin CLI as an unknown identity even though the workstation bootstrap delivers it alongside the other seven harnesses. Add Devin to the canonical catalogue for bounded version observation while retaining the seven proven execution/configuration adapters.
The Devin bridge explicitly declares
not-provenruntime evidence and does not inherit the setup-systems evidence owner. Default catalogue validation includes the installed-only entry; an explicit runtime-proof request and any attempt to install unproven Devin configuration remain refused. No model calls or vendor configuration writes are performed by version detection.Validation: focused harness and CLI tests pass, including version-only observation, configuration refusal, runtime-proof refusal, active/canonical separation, and bridge evidence digest binding. Full Go tests and hash-locked Python tests run as additional evidence.