feat: add plugin-owned primitive registry and firmware-gated reqs

[yilmazbahadir]

📝 Summary

This PR implements a plugin-owned primitive registry so adding/migrating chains no longer requires broad SDK helper coupling.

It introduces primitive definitions/requirements on chain plugins, migrates current Lattice signers (evm, solana, cosmos, xrp) to runtime primitive resolution, and enforces explicit firmware gating via minFirmware (no baseline shorthand).

🔧 Context / Implementation

• Added primitive model to chain-core:
  • PrimitiveKind, PrimitiveDefinition, PrimitiveRequirement, PluginPrimitives
  • primitives?: PluginPrimitives on ChainPlugin
• Added new chain-core primitive registry with:
  • createPrimitiveRegistry, preflight, atomic register, resolve, resolveOrThrow, reverseResolve, has, list, reset (test isolation)
  • collision semantics for name/code conflicts
• Added SDK primitive lifecycle module:
  • lazy/idempotent seeding from EXTERNAL.SIGNING.{HASHES,CURVES,ENCODINGS}
  • plugin primitive preflight/register helpers
  • fail-closed requirement validation requiring explicit minFirmware
• Updated chain runtime registration flow to be transactional:
  • seed primitives -> preflight defs -> register chain -> commit defs
  • rollback chain registration if primitive commit fails
  • discovery path now uses the same registration flow
• Added runtime firmware requirement enforcement in useChain() before signer creation.
• Updated setup flow to seed primitives early (still idempotent).
• Migrated lattice signers (evm, solana, cosmos, xrp) to context.resolvePrimitive(...) for signing primitive codes.
• Added plugin primitive requirements:
  • EVM: SECP256K1, KECCAK256, EVM
  • Solana: ED25519, NONE, SOLANA
  • Cosmos: SECP256K1, SHA256, COSMOS
  • XRP: SECP256K1, SHA512HALF, XRP
• Added explicit request-time EIP-7702 firmware gate in EVM signer (min firmware: 0.18.0).
• Kept GET_ADDR_FLAGS and existing getFwVersionConst() behavior unchanged in this PR.

Concrete developer experience — what a new chain plugin author writes:

export const latticePlugin: ChainPlugin<LatticeNewChainContext> = {
  chainId: 'newchain',
  device: 'lattice',
  module: newchain,
  createSigner: (context) => createLatticeNewChainSigner(context),
  primitives: {
    // Only include definitions for primitives that are not already seeded by SDK built-ins.
    definitions: [
      { kind: 'encoding', name: 'NEWCHAIN', code: 9 },
      { kind: 'hash', name: 'BLAKE2B', code: 4 },
    ],
    // Every requirement must use explicit minFirmware (no baseline field).
    requirements: [
      { kind: 'curve', name: 'ED25519', minFirmware: [0, 14, 0] },
      { kind: 'encoding', name: 'NEWCHAIN', minFirmware: [0, 20, 0] },
      { kind: 'hash', name: 'BLAKE2B', minFirmware: [0, 20, 0] },
    ],
  },
};

// Inside the signer: resolve codes via context (throws if missing).
const curveCode = context.resolvePrimitive('curve', 'ED25519');
const encodingCode = context.resolvePrimitive('encoding', 'NEWCHAIN');
const hashCode = context.resolvePrimitive('hash', 'BLAKE2B');

🧪 Test Plan

1. Run type checks:
   • pnpm --filter @gridplus/chain-core typecheck
   • pnpm --filter gridplus-sdk typecheck
2. Run SDK unit tests:
   • pnpm --filter gridplus-sdk test-unit
3. Verify targeted behavior:
   • primitive registry collision/preflight/atomic semantics
   • lazy seeding + requirement validation (pass/fail paths)
   • transactional chain registration + no partial state on failure
   • signer primitive resolution for EVM/Solana/Cosmos/XRP
   • EVM EIP-7702 request-time firmware gating

Expected result: all commands pass, registration remains fail-safe/transactional, and signer payloads resolve primitive codes via registry with correct firmware gating behavior.

🖼️ Screenshots (if applicable)

Before	After
N/A	N/A

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/GridPlus/gridplus-sdk@728

commit: b06f89d

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d308cf86e2

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[netbonus]

should we have this generic item here? it reduces the type safety support we get when using them.

[netbonus]

i'm not sure this is the best name for this. it's a little too generic and doesn't exactly explain what it is.

[netbonus]

don't we have this somewhere else. did we move it?

[netbonus]

this is more like a "protocol" or something right?

primitive code map could be a lot of things.