OrchestKit hook storage engine — why node:sqlite

CC hooks ship as esbuild bundles with no node_modules. That single constraint decides which SQLite engine the M168 session registry can use. Pick an engine × runtime and see whether the bundle loads and the registry works.

SQLite engine

Runtime

Bundle load

Registry works?

In session-registry.ts


    

  


  

    
The dependency chain

    

      #2003 bundle LOADS (lazy import) →
      #2005 registry WORKS (node:sqlite) →
      #2006 analytics: skill suggested→taken
    

    
#2006 (capture which suggested skills get used) writes to this very registry — so it was blocked until #2005 made the registry actually function in the shipped plugin. Right tool per layer: SQLite where you need locks/queries (Layer 1), JSONL for append-only event logs (Layer 3, #1948).