Skip to content

Add OpenCode verification skill - #46

Open
edmundmiller wants to merge 1 commit into
opencodefrom
codex/opencode-verification
Open

edmundmiller wants to merge 1 commit into
opencodefrom
codex/opencode-verification

Conversation

@edmundmiller

Copy link
Copy Markdown
Collaborator

OpenCode needs a repeatable way to prove native tools and recovery rather than relying on startup checks or manually written markers. Add a project verification skill with four feature recipes and an executable, isolated Docker harness.

I ran the generation self-test and maintenance pass against OpenCode 2.0.23. Browser and API Write/Read and authenticated Seqera documentation searches passed; an independent snapshot matched all 21 messages across three sessions and exact file bytes in a fresh runtime, followed by a new native Read. Owned resources were removed and evidence survived cleanup.

The changes are confined to the verification skill. Local recovery is covered here; the separate live Fusion procedure requires cloud readback and a fresh Studio without a parent checkpoint, and was not repeated in this maintenance run. This PR targets the dedicated OpenCode Studio branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant