Simplify conformance and example maintenance with adapterctl

[alexolivier]

Problem / Intent

Conformance actions, adapter classifications, consumer expectations, workflow coverage, and corpus counts are currently repeated across root ledgers, native harnesses, and documentation. That makes adding one action, adapter, or consumer case a repository-wide synchronization exercise and leaves several ways for declared support to drift from executed coverage.

Closes #434.

Approach

• Add a Node 22 TypeScript adapterctl control plane with meaningful Ink views, versioned TypeBox schemas, strict and discovery validation, direct adapter outcomes, native run profiles, reports, explanations, scaffolding, and generated certification docs.
• Make conformance/catalog.json, canonical check resources, demo/cases.json, and 11 adapter-local manifests the only certification inputs; migrate every native harness and example to consume them directly.
• Remove conformance/actions.json, demo/expected.json, compatibility comparison code, repeated action counts, and the migration flag. This is an intentional repository-internal breaking cutover rather than a compatibility transition.
• Derive liveness, cardinality, and focused discovery execution from the catalog and direct outcomes while keeping unscoped certification strict. Validate workflow commands, concrete matrix rows, conditions, and environment combinations as executed evidence.
• Add scoped workflow certification, consumer artifact/usage coverage, three maintainer task runbooks, and Prisma 5 coverage across SQLite, PostgreSQL, and MySQL alongside Prisma 6 and 7.

All 11 adapters are affected. Verification includes adapterctl type-checking and 41 public-interface tests, strict 199-action × 11-adapter certification with zero unassessed outcomes, schema/docs/corpus/demo validators, workflow YAML and control-plane JSON parsing, full offline TypeScript translator suites, focused discovery tests in every language, Go offline suites/examples, packed consumer builds, Ruby/Python syntax and loader checks, and Java focused/direct compilation checks. Docker-backed semantic matrices remain covered by their adapter-owned CI workflows.