v1.1.1 — Security patch: multi-tenant row-level isolation

Fixes the tenant-isolation issue reported in #1.

Fixed

• Security: in --auth-file multi-tenant serve mode, knowledge / experience / knowledge-graph entries stored in one tenant context could be recalled from another (#1). Every entry now carries a row-level tenant ownership tag; all read paths (recall, contextual memory, meta-memory, stats, graph traversal) filter by the effective tenant scope. Entries written by the agent itself (CLI / single-user serve) remain unowned and invisible to tenants — strict isolation by default.
• Destructive operations (prune / clear / compress / graph build·link·clear) are scoped or refused in tenant context — a tenant cannot delete or rebuild what it cannot see.
• CLI and single-user serve behavior unchanged.

Added

• Regression test suite for tenant isolation: src/tenant-isolation.test.ts
• Vitest global setup (test/setup.ts) isolating the knowledge store into a temp dir during tests

Credits

• Thanks @CaiHB2000 for the responsible disclosure.

Full Changelog: v1.1.0...v1.1.1