Repository navigation
feat(harness): v2 host smoke test and config schema validation in CI (issue #27) - #35
Merged
Merged
Conversation
4 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.
C4 of spec #23.
What
tests/v2-host.test.ts,tests/fixture-config-schema.test.ts+ support classes) that loads the built package entry the way the v2 host does — pinned@opencode/plugin@2.0.23module loading and Effect activation — and audits registrations against the real@opencode/schema: all ten agents decode againstAgent.Info, exactly one permissionevaluatehook, hook rewrites bundledexternal_directoryasks end to end. Negative controls prove the audit fails on registration loss.Config.Info; v1-shaped configs rejected.V2 verification harnessCI job.Key finding (facts record §14.6, settled negative)
Under Bun,
Host.resolve's root-index fallback is unreachable:Bun.resolveSyncthrowsResolveMessage, which is not aninstanceof Error, so the candidate-miss filter never catches and the core loader disables the plugin at the entry stage. The package had noexportsmap — consumers were silently registering nothing.exports["./server"]added; generated-package templates flagged in the record (§13 row 9) for the guidance tickets.Facts write-back
docs/reference/opencode-v2-facts.md: §14.6 settled negative with mechanism; items 1,2,3,4,7,8 recorded as not reachable from a plugin-package harness; item 5 partially confirmed (pinned shapes); §7 amended — every plugin package must declare
exports["./server"].Ref #27