Add a read-only QM meeting-memory adapter

[Shravani889]

Inwise OSS pull-request notes

Suggested title: Add a read-only QM meeting-memory bridge

What changed

• Added an outbound laptop edge connector, self-hosted opaque relay, and QM sandbox CLI.
• Added X25519 key agreement, out-of-band key confirmation, and AES-256-GCM request/response encryption.
• Exposed only the ten existing read-only Inwise MCP tools.
• Added a QM-compatible tool descriptor and personal-scope meeting-memory skill.
• Added a reproducible QM Docker deployment fixture and live bridge smoke-test runner.

User impact

Users can connect local Inwise OSS meeting memory to a personal QM scope without an Inwise Cloud account. If Inwise Desktop is offline, requests fail without a cloud fallback.

Validation

• npm test: 3 tests passed.
• npm run test:deployed: passed against QM 291faf194c1df2fcb5bc38c4c974da782e201d02 and a running Inwise MCP endpoint.
• QM check: passed.
• QM conformance: passed all four reported contract clauses.
• Dependency audit: zero known vulnerabilities.

The detailed evidence is in integrations/qm/e2e/TEST_REPORT.md.

[Shravani889]

Consolidated the adapter implementation and proposal into yc-software/qm#347 so there is one review surface.