fix(runtime): bundle engine daemon for packed consumers

[Looted]

Problem

First-party MCP hosts that install the published-shaped packages under pnpm isolated mode (or any layout without a nested kibi-cli) fail on first engine use:

Error: The Kibi engine is not built. Run `npm run build:cli` before using the CLI engine.

Root cause: the runtime bundle inlines kibi-cli/operations code, including EngineClient and its daemonEntry() lookup. That lookup checks:

1. <runtime>/dist/engine-daemon.js — never shipped
2. <runtime>/dist/../dist/engine-daemon.js — same path
3. <runtime>/node_modules/kibi-cli/dist/engine-daemon.js — only resolves in the kibi monorepo workspace

Published consumers have none of these, so EngineClient.start() always throws.

Fix

The kibi-runtime build now also bundles packages/cli/src/engine-daemon.ts into dist/engine-daemon.js (--packages bundle --external kibi-core, same strategy as the existing index bundle). Candidate 1 then resolves in every consumer shape with no new dependencies and no lookup changes.

Verification

• Built runtime; spawned the bundled daemon against a real workspace: socket created, branch KB attached, kb_storage_status/1 query returns success.
• Packed kibi-runtime + kibi-core tarballs, installed them into a clean npm prefix, and ran EngineClient from the installed tree: daemon auto-starts and serves queries.
• Reproduced the original failure with the previous tarball to confirm the before/after.

Notes

• Includes a patch changeset for kibi-runtime.
• No changes to lookup order, CLI package, or protocol.

[Looted]

CI triage: the red Kibi strict requirement proof job is inherited from develop, not caused by this branch. The same workflow fails on develop's last three pushes (run 32443928265, 32408967719, 32379293691); the last success predates the two requirements added after the baseline ratchet in 45e4881 (proof/baseline.json expects 91 requirements / ≤70 unproven; the branch compiles 93 / 71). This branch's own commit only touches packages/runtime/package.json + a changeset, and all other checks (build-and-test, packed-e2e, publish-dry-run) pass.

Also pushed b18aa02, which gives the fix full Kibi traceability and proof:

• REQ-runtime-packed-engine-daemon → SCEN → TEST-runtime-packed-engine-daemon with both normative clauses grounded as kibi.runtime predicate facts
• New packed E2E (documentation/tests/e2e/packed/runtime-engine-daemon.test.ts) that installs the published tarballs into a clean prefix and starts EngineClient from the installed runtime — proving daemon resolution + typed query service without a nested kibi-cli
• Contract registered in proof/verification-registry.json; local contract run passes and coverage reports the requirement proven (all nine stages green)
• Repairs REQ-kibi-verification-evidence-contract ingestion (stale proposition segmentation) which was blocking kibi sync on every branch

[Looted]

Consolidation update (4fa9901c): merged develop and resolved all conflicts.

• Took develop's refined copies of the shared files (hardened packed test with KIBI_NODE_PATH/stop(false), receipt-free TEST source, registry, test-symbol entries).
• Preserved the one piece develop had dropped: SYM-runtime-packed-daemon-build (config-granularity production symbol + coordinates + implements/covered_by shards) — without it the requirement loses production-symbol coverage.
• Validated the merge locally under committed code: full sync clean, contract re-run passed, REQ-runtime-packed-engine-daemon proven with zero gaps, kb_check 0 violations.
• PR diff vs develop is now just those 3 files / 35 lines; GitHub reports MERGEABLE.

Remaining CI reds on this branch are inherited from develop tip (run 32489557724): the same TEST-kibi-consumer-local-plugin-launcher-ontology-v1 contract failure and the baseline ratchet — both belong to the consolidation work as planned.