feat: module deploys (BC protocol, Module index & getModules API)

[ltardivo]

Multisig modules now live as cleartext { ept } data outputs, taproot modules use the new BC protocol id (replacing ordinals-style ORD), and the node gains a dedicated Module table plus list/get endpoints. The client follows with getModules / getModule so apps can inspect source without evaluating it. Everything is versioned as 0.27.0-beta.1.

Breaking changes

• Wire format
  Multisig: only { ept: string } is written (no exp / env / mod / v, no encryption).
  Taproot: reveal witness envelope now carries protocol id BC (content-type remains text/javascript).
  Legacy shapes that stored modules as transition exp fields or ord inscriptions are no longer read.

• Client
  computer.decode(tx) now throws ModuleDecodeError on a module deploy. Use computer.load(rev) instead.
  Prefer getOUTXOs / latest + sync over the deprecated query (especially the old ids filter).

• Node
  Existing Postgres volumes created before this feature need the Module table applied manually (see migration below).
  Lib and node must be the same version line; mismatched pairs produce 404s, parse failures, or empty indexes.

Lib

• PROTOCOL_ID constant changed from ORD to BC.
• Modules.toTx / broadcast emit pure multisig { ept } (still creates an owner output so the UTXO appears in the Output graph).
• Taproot path uses the BC envelope; TxInscription.read and parseInscriptionData understand only the new format.
• New helpers in module-meta: isModuleMeta, tryParseModuleFromTx, tryParseModule (keyless, ready for node indexing).
• Computer.decode rejects module deploys with a clear error pointing to load.
• New client API

// verbosity 0 (default) → string[] of mod specifiers
// verbosity 1 → ModuleRecord[] including ept + storageType + confirmation fields
await computer.getModules({ verbosity: 1, storageType: 'taproot', isConfirmed: true })
await computer.getModule(mod) // single ModuleRecord

• Types: ModuleRecord, ModuleQuery, ModuleOnChainMeta, ExtractedModule.

Node

• New Module table (mod, ept, storageType, blockHash, blockHeight, timestamp) with indexes.
• Detection via module-extract (multisig { ept } and taproot BC witnesses).
• Full stack: ModuleDao → ModuleService → ModuleAction.
• Wired into insertSpendGraph / insertAndUpdateMod, ZMQ, blockchain sync, reorg (eraseBlockHash), and mempool hard-delete.
• HTTP API
  GET /v1/:chain/:network/modules (verbosity, limit, offset, order, storageType, isConfirmed)
  GET /v1/:chain/:network/module/:mod

Docs

• New changelog.md documenting the 0.27 protocol break and migration steps.
• Comprehensive Node → Operate & Troubleshoot guide covering authentication, empty-result checklists, Module-table upgrade, version matching, reorg behaviour, and FAQ.
• Computer reference updated: deploy / load / decode / constructor, plus brand-new pages for getModules, getModule, getInscription, isIndexed, waitForIndexed, delete, etc.
• Tutorial rewritten to prefer getOUTXOs + latest + sync; load now correctly returns exports (use getModule for the raw ept source).
• Cross-links between client methods and node endpoints; comparison page and onChainMetaData docs distinguish transitions vs module deploys.

Migration

• Upgrade node image / monorepo tag to the 0.27.0-beta.1 line.
• On any existing Postgres volume, run the Module DDL (also present in packages/node/db/db_schema.sql):

CREATE TABLE IF NOT EXISTS "Module" (
  "mod" VARCHAR(70) NOT NULL PRIMARY KEY,
  "ept" TEXT NOT NULL,
  "storageType" VARCHAR(16) NOT NULL,
  "blockHash" VARCHAR(64),
  "blockHeight" INTEGER,
  "timestamp" timestamp default CURRENT_TIMESTAMP not null
);

• Upgrade @bitcoin-computer/lib to the matching version.
• Replace any code that treated module transactions as transitions (decode, fake exp).
• Prefer getOUTXOs over the deprecated query for listing smart objects.
• Pin both sides to the same version:

{
  "dependencies": {
    "@bitcoin-computer/lib": "0.27.0-beta.1"
  }
}