Skip to content

Shared plugin conformance suite (gatewaystack-connect#1344 step 1) - #49

Open
davidcrowe wants to merge 1 commit into
mainfrom
test/plugin-conformance
Open

davidcrowe wants to merge 1 commit into
mainfrom
test/plugin-conformance

Conversation

@davidcrowe

Copy link
Copy Markdown
Collaborator

What this changes

This adds the shared L1 plugin conformance adapter and the vendored corpus test/fixtures/plugin-corpus.json (hash aa186d3fb3e7d18c) for gatewaystack-connect#1344 step 1. The adapter runs the canonical notice and post-tool cases against this plugin's real entry point, using a fake gateway. EXPECTED_DIVERGENCES lists anything that still fails, and a test checks the list is exact, so a new failure or a silent fix both turn CI red.

The branch is rebased onto the current origin/main. Only tests are added; plugin code is not changed.

Tests

Local run on this branch: node --test: 290/290 pass.

No new workflow. The existing CI already runs node --test, so the adapter runs there.

Ships under ship-when-confident; Fable reviews after (queue +G/+I).

Refs davidcrowe/gatewaystack-connect#1344

Vendors the shared plugin-corpus.json (gatewaystack-connect#1344) and adds
test/conformance.test.mjs, which drives bin/govern.mjs's real PostToolUse
hook against a fake gateway and asserts the notice reaches stdout
systemMessage and the outgoing /govern/tool-output body carries
tool_name/tool_input/tool_output/session_id. node --test already
auto-discovers ./test, so no workflow change is needed to run it in CI.

No divergences recorded for this plugin: both capabilities pass as-is.
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