Skip to content

fix/kernel parity 1333 1335 - #44

Open
davidcrowe wants to merge 2 commits into
mainfrom
fix/kernel-parity-1333-1335
Open

davidcrowe wants to merge 2 commits into
mainfrom
fix/kernel-parity-1333-1335

Conversation

@davidcrowe

Copy link
Copy Markdown
Contributor
  • Add shared kernel-parity corpus, run it against decide.mjs
  • Kernel parity with the gateway (#1333, #1335)

The August drift was not a bad algorithm — the gateway fixed the
classifier/floor class in July and the local copies stayed broken for weeks
because nothing compared them. This adds the comparison: one JSON case table,
consumed by every copy of the kernel, asserting classification key and
hardline verdict.

Two divergences recorded on this surface rather than silently tolerated:
force-with-lease trips the local hardline floor while the gateway allows it,
and `$(` classifies as Bash.$ instead of Bash.unknown. Both are scoped to the
assertion that actually diverges, so the half that works stays asserted. The
count guard fails if a new one appears AND if one is fixed without updating it.

Destructive binaries live in the fixture as fragment arrays: a governed write
of the bare literal is subject to response filtering, which would corrupt the
fixture silently.

Also scopes `npm test` to test/ — node --test with no path walks gitignored
demo/.home and dies on a stray app bundle, so the suite could not be run
locally at all.

Refs davidcrowe/gatewaystack-connect#1316, #1333, #1335, #36
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