Repository navigation
Complete the MVP diagnostics - #1
Merged
Merged
Conversation
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.
Changes
Completes the MVP checks from the build plan. The quick check now covers enum choices, a verified file edit in a temporary project, and a restricted file listing. OpenCode runs against a direct provider baseline, and success requires the final assistant answer to contain the fixture marker.
Context checks repeat three times at 16K and 32K, and reports show the observed attempts and harness timeout. Deterministic mock scenarios cover provider failures, malformed calls, parser diagnosis, timeout diagnosis, and context degradation.
Verification
Go tests, race tests, vet, and cross builds passed for macOS, Linux, and Windows targets. The installed OpenCode command passed the live fixture with the local mock provider. The parser scenario injects a controlled harness failure after the direct baseline passes, and the timeout scenario uses the real OpenCode process with a delayed mock response.