SDK v2 reference agents die at launch

Found by the Task 7281 acceptance run on dev. I registered the SDK v2 reference agents from the private mirror (https://github.com/jaah-ai/agent-sdk, ref develop @ fe6889ae5e, subpaths examples/python → "Echo (Python)" and examples/typescript → "Echo (TypeScript)"). Their snapshot bundles are 670 and 981 bytes, so they carry neither `jaah_agent` nor `node_modules`. Each manifest says the bundle must carry them (examples/python/jaah-agent.toml:2, examples/typescript/jaah-agent.toml:2). Every dispatch on ts2-node6 (dev tasks 5092, 5093) ended "Runner terminated — reported it could not finish", detail `broken session: unknown — connection closed`, with 0 ACP events ingested. Make a manifest 2 agent registered from a repo run. Either the snapshot vendors the SDK library the manifest names, or the node provides the pinned SDK to v2 agents. Then the reference agents echo and settle. Out of scope: v1 connectors; registry agents (Task 7429). Done means: - On dev, a task bound to "Echo (Python)" and one bound to "Echo (TypeScript)" each reach `done`, with ACP events in the task's Agent activity. - jaahd/API tests cover the bundle or library resolution. Required checks: ./dc check full

Duplicate: PR #6027 (16c0da77c) already makes the reference agents carry their SDK. Both develop agents echo and end the turn with no node SDK. Node-side alternative not PR'd (contradicts ADR-0159). Dev done-run blocked by a MicroVM-node fault; filed draft 7520.