comisai 1.0.45 → 1.0.46

package/node_modules/@comis/memory/dist/schema-trigram.js

@@ -1,6 +1,6 @@
 // SPDX-License-Identifier: Apache-2.0
 /**
- * Trigram twin DDL — FTS-01's table half (Phase 180).
+ * Trigram twin DDL — the trigram-search table half.
  *
  * Three SELF-CONTAINED FTS5 trigram twins that mirror the lossless base tables,
  * plus the base-table delete-mirror triggers and the WHEN-guarded memories
@@ -10,8 +10,8 @@
  *   - `lcd_summaries_fts_tri`  ← lcd_summaries  (conversation_id/agent_id/summary_id UNINDEXED)
  *   - `memory_fts_tri`         ← memories       (no scope columns — the rowid-JOIN lane)
  *
- * The twins are the substrate every wave-2 search/write plan targets: appends
- * write `normalizeForSearch(content)` into them (TS-side, plans 180-05/06) so a
+ * The twins are the substrate the search/write paths target: appends
+ * write `normalizeForSearch(content)` into them (TS-side) so a
  * script-routed `MATCH` can read Hebrew/Arabic/Cyrillic/CJK; the base-table
  * triggers below close the ~5 delete/update bypass sites BY CONSTRUCTION — a
  * delete needs no normalizer, and a missed TS write site can never leave
@@ -22,11 +22,11 @@
  *
  * These twins store their OWN `content` (no `content=`/`content_rowid=` option).
  * An external-content twin would expose the FTS5 `'rebuild'` command, which
- * re-reads the RAW base-table text — silently UNDOING the FTS-02 normalization
- * the twins exist to hold. The doctor backfill (plan 180-08) instead feeds
+ * re-reads the RAW base-table text — silently UNDOING the normalization
+ * the twins exist to hold. The doctor backfill instead feeds
  * normalized text explicitly. These twins are NOT content-free shadow tables —
- * storing their own content is exactly the G10 mechanism (orphaned rows stay
- * matchable until a SCOPED DELETE removes them — plan 180-05's wipe-list close).
+ * storing their own content is exactly the mechanism that keeps orphaned rows
+ * matchable until a SCOPED DELETE removes them (the scoped-wipe path).
  *
  * ## Per-block boot safety (each twin CREATE + its trigger(s) are ONE block)
  *
@@ -35,17 +35,16 @@
  * trigger(s): a base-table existence guard + the CREATE-then-triggers in a single
  * `db.exec` means a failed twin CREATE (trigram absent) skips that twin's
  * triggers — no orphan trigger can ever reference a missing twin and break a
- * base-table DELETE (T-180-02-02/04). Search probes availability at query time
- * (`isTriAvailable`, plan 180-05) and degrades to the scan floors; it never
+ * base-table DELETE. Search probes availability at query time
+ * (`isTriAvailable`) and degrades to the scan floors; it never
  * hard-fails. Forward-only: every CREATE is guarded re-run-safe, no DROP /
- * down-migration (design §9). Static SQL, no interpolated identifiers
- * (T-131-02-01).
+ * down-migration. Static SQL, no interpolated identifiers.
  *
  * @module
  */
 /** True iff a base table `name` exists — so a twin block is skipped wholesale on
  *  a partial-schema host (the table + its triggers stay paired; no orphan twin
- *  table and no orphan trigger). Static SQL, bound param (T-131-02-01). */
+ *  table and no orphan trigger). Static SQL, bound param. */
 function tableExists(db, name) {
     const row = db
         .prepare("SELECT name FROM sqlite_master WHERE type = 'table' AND name = ?")
@@ -74,7 +73,7 @@ export function ensureTrigramTwins(db) {
         CREATE VIRTUAL TABLE IF NOT EXISTS lcd_messages_fts_tri USING fts5(
           content,
           conversation_id UNINDEXED,
-          agent_id UNINDEXED,          -- R4: per-agent read isolation (WR-02); MATCH … AND agent_id = ?
+          agent_id UNINDEXED,          -- per-agent read isolation; MATCH … AND agent_id = ?
           message_id UNINDEXED,
           tokenize='trigram'
         );
@@ -98,7 +97,7 @@ export function ensureTrigramTwins(db) {
         CREATE VIRTUAL TABLE IF NOT EXISTS lcd_summaries_fts_tri USING fts5(
           content,
           conversation_id UNINDEXED,
-          agent_id UNINDEXED,          -- R4: per-agent read isolation (WR-02); MATCH … AND agent_id = ?
+          agent_id UNINDEXED,          -- per-agent read isolation; MATCH … AND agent_id = ?
           summary_id UNINDEXED,
           tokenize='trigram'
         );
@@ -117,14 +116,14 @@ export function ensureTrigramTwins(db) {
     }
     // ── Block 3: memories twin + delete-mirror trigger + WHEN-guarded update ─────
     // The memory twin carries NO scope columns — the LTM lane scopes via a
-    // rowid-JOIN to `memories` plus the existing post-fusion tenant/agent filters
-    // (plans 180-05/06). It also carries TWO triggers (delete + update); the
+    // rowid-JOIN to `memories` plus the existing post-fusion tenant/agent filters.
+    // It also carries TWO triggers (delete + update); the
     // WHEN-guarded update is mandatory: a plain `AFTER UPDATE OF content` fires on
     // the consolidation proof-only fold `content = COALESCE(NULL, content)`
-    // (probe-verified, RESEARCH correction #3), which would silently de-index a
+    // (probe-verified), which would silently de-index a
     // memory on every consolidation. The WHEN guard below de-indexes ONLY when the
     // content column value actually changed; the normalized re-insert is
-    // TS-side (plan 180-06), and its failure leaves the row de-indexed (the
+    // TS-side, and its failure leaves the row de-indexed (the
     // fail-safe direction), never stale-indexed.
     if (tableExists(db, "memories")) {
         try {

package/node_modules/@comis/memory/dist/schema-usefulness.d.ts

@@ -1,13 +1,13 @@
 /**
  * The `memory_usefulness.failure_count` per-column migration — the
- * outcome-attributed task-failure signal (FORGET-02) read by the memory
+ * outcome-attributed task-failure signal read by the memory
  * lifecycle sweep's per-(tenant, agent) JOIN. DISTINCT from `ignored_count`
  * (recalled-but-not-cited, a usage proxy): a correct-but-unused memory accrues
  * `ignored_count`, never `failure_count`.
  *
- * Relocated here (Phase 224, v2.31) OUT of `schema-tuned-alpha.ts` — that file
+ * Relocated here OUT of `schema-tuned-alpha.ts` — that file
  * is the bandit `tuned_alpha` migration and is DELETED when the bandit is cut.
- * This column is a KEEPER (the FORGET-02 source the lifecycle JOIN reads), so it
+ * This column is a KEEPER (the source the lifecycle JOIN reads), so it
  * lives in its own focused keeper schema module, mirroring the
  * `schema-outcome-events.ts` co-location precedent (a small schema file imported
  * + called by `schema.ts`, which is at the 800-line cap). `schema.ts` calls it as
@@ -18,7 +18,7 @@
  * is guarded by a `PRAGMA table_info(memory_usefulness)` presence check, then an
  * `ADD COLUMN ... NOT NULL DEFAULT 0` (O(1), constant default — never NULL for a
  * count). The `ensureMemoryColumns` per-column-add idiom; no destructive or
- * reverse DDL, no branch on an old shape (design §9, additive).
+ * reverse DDL, no branch on an old shape (additive).
  *
  * `better-sqlite3` durability is WAL + path-based chmod (never fd-based file
  * sync), so this DDL is permission-model-safe by construction — no fd-fs guard is
@@ -29,7 +29,7 @@
 import type Database from "better-sqlite3";
 /**
  * Idempotently ensure `memory_usefulness` carries the `failure_count` column —
- * the outcome-attributed task-failure signal (FORGET-02). DISTINCT from
+ * the outcome-attributed task-failure signal. DISTINCT from
  * `ignored_count` (recalled-but-not-cited, a usage proxy): a correct-but-unused
  * memory accrues `ignored_count`, never `failure_count`. The per-column
  * `ensureMemoryColumns` idiom: a `PRAGMA table_info` presence guard, then an

package/node_modules/@comis/memory/dist/schema-usefulness.js

@@ -1,14 +1,14 @@
 // SPDX-License-Identifier: Apache-2.0
 /**
  * The `memory_usefulness.failure_count` per-column migration — the
- * outcome-attributed task-failure signal (FORGET-02) read by the memory
+ * outcome-attributed task-failure signal read by the memory
  * lifecycle sweep's per-(tenant, agent) JOIN. DISTINCT from `ignored_count`
  * (recalled-but-not-cited, a usage proxy): a correct-but-unused memory accrues
  * `ignored_count`, never `failure_count`.
  *
- * Relocated here (Phase 224, v2.31) OUT of `schema-tuned-alpha.ts` — that file
+ * Relocated here OUT of `schema-tuned-alpha.ts` — that file
  * is the bandit `tuned_alpha` migration and is DELETED when the bandit is cut.
- * This column is a KEEPER (the FORGET-02 source the lifecycle JOIN reads), so it
+ * This column is a KEEPER (the source the lifecycle JOIN reads), so it
  * lives in its own focused keeper schema module, mirroring the
  * `schema-outcome-events.ts` co-location precedent (a small schema file imported
  * + called by `schema.ts`, which is at the 800-line cap). `schema.ts` calls it as
@@ -19,7 +19,7 @@
  * is guarded by a `PRAGMA table_info(memory_usefulness)` presence check, then an
  * `ADD COLUMN ... NOT NULL DEFAULT 0` (O(1), constant default — never NULL for a
  * count). The `ensureMemoryColumns` per-column-add idiom; no destructive or
- * reverse DDL, no branch on an old shape (design §9, additive).
+ * reverse DDL, no branch on an old shape (additive).
  *
  * `better-sqlite3` durability is WAL + path-based chmod (never fd-based file
  * sync), so this DDL is permission-model-safe by construction — no fd-fs guard is
@@ -29,7 +29,7 @@
  */
 /**
  * Idempotently ensure `memory_usefulness` carries the `failure_count` column —
- * the outcome-attributed task-failure signal (FORGET-02). DISTINCT from
+ * the outcome-attributed task-failure signal. DISTINCT from
  * `ignored_count` (recalled-but-not-cited, a usage proxy): a correct-but-unused
  * memory accrues `ignored_count`, never `failure_count`. The per-column
  * `ensureMemoryColumns` idiom: a `PRAGMA table_info` presence guard, then an

package/node_modules/@comis/memory/dist/schema-video-jobs.d.ts

@@ -1,19 +1,19 @@
 /**
- * The `video_jobs` table DDL — the durable async job store the Phase-189
- * background poller resumes against across a daemon restart (JOB-01/JOB-03).
- * A job row survives the agent turn AND a daemon restart because it lives on
- * disk in the shared `memory.db`, not in memory.
+ * The `video_jobs` table DDL — the durable async job store the background poller
+ * resumes against across a daemon restart. A job row survives the agent turn
+ * AND a daemon restart because it lives on disk in the shared `memory.db`, not
+ * in memory.
  *
  * Forward-only, re-run-safe: create-if-not-exists only, no destructive or
- * reverse DDL (design §9). Extracted from `schema.ts` (which is at the
+ * reverse DDL. Extracted from `schema.ts` (which is at the
  * 800-line cap) — `initSchema` CALLS this so the table exists on every boot.
  *
- * SECURITY (T-189-02): columns are the opaque provider jobId + routing + state +
+ * SECURITY: columns are the opaque provider jobId + routing + state +
  * cost + path + a `deliver_attempts` redelivery counter ONLY — no credential
  * column. Columns MUST match `VideoJobDbRowSchema` (video-job-row-schema.ts)
  * exactly — the strictObject rejects any drift.
  *
- * CR-01 (Phase-189 code review): `deliver_attempts` bounds the poller's
+ * `deliver_attempts` bounds the poller's
  * redelivery loop. A row whose channel delivery keeps failing is re-driven by
  * the sweeper every `pollIntervalMs`; without a persisted counter that re-poll +
  * re-download (up to 200 MB) repeats forever. The poller increments this column
@@ -23,7 +23,7 @@
  *
  * `better-sqlite3` durability is WAL + path-based chmod (never fd-based file
  * sync), so this DDL is permission-model-safe by construction — no fd-fs guard
- * is needed (Pitfall 2 / [[node-permission-model-disables-fsync]]).
+ * is needed ([[node-permission-model-disables-fsync]]).
  *
  * @module
  */

package/node_modules/@comis/memory/dist/schema-video-jobs.js

@@ -1,20 +1,20 @@
 // SPDX-License-Identifier: Apache-2.0
 /**
- * The `video_jobs` table DDL — the durable async job store the Phase-189
- * background poller resumes against across a daemon restart (JOB-01/JOB-03).
- * A job row survives the agent turn AND a daemon restart because it lives on
- * disk in the shared `memory.db`, not in memory.
+ * The `video_jobs` table DDL — the durable async job store the background poller
+ * resumes against across a daemon restart. A job row survives the agent turn
+ * AND a daemon restart because it lives on disk in the shared `memory.db`, not
+ * in memory.
  *
  * Forward-only, re-run-safe: create-if-not-exists only, no destructive or
- * reverse DDL (design §9). Extracted from `schema.ts` (which is at the
+ * reverse DDL. Extracted from `schema.ts` (which is at the
  * 800-line cap) — `initSchema` CALLS this so the table exists on every boot.
  *
- * SECURITY (T-189-02): columns are the opaque provider jobId + routing + state +
+ * SECURITY: columns are the opaque provider jobId + routing + state +
  * cost + path + a `deliver_attempts` redelivery counter ONLY — no credential
  * column. Columns MUST match `VideoJobDbRowSchema` (video-job-row-schema.ts)
  * exactly — the strictObject rejects any drift.
  *
- * CR-01 (Phase-189 code review): `deliver_attempts` bounds the poller's
+ * `deliver_attempts` bounds the poller's
  * redelivery loop. A row whose channel delivery keeps failing is re-driven by
  * the sweeper every `pollIntervalMs`; without a persisted counter that re-poll +
  * re-download (up to 200 MB) repeats forever. The poller increments this column
@@ -24,7 +24,7 @@
  *
  * `better-sqlite3` durability is WAL + path-based chmod (never fd-based file
  * sync), so this DDL is permission-model-safe by construction — no fd-fs guard
- * is needed (Pitfall 2 / [[node-permission-model-disables-fsync]]).
+ * is needed ([[node-permission-model-disables-fsync]]).
  *
  * @module
  */
@@ -58,9 +58,9 @@ export function ensureVideoJobTable(db) {
       updated_at_ms      INTEGER NOT NULL
     )
   `);
-    // OBS-04 (Phase 192): forward-only, re-run-safe migration for the
+    // Forward-only, re-run-safe migration for the
     // `session_key` column. `CREATE TABLE IF NOT EXISTS` is a no-op on a table that
-    // a PRIOR v2.24 build (without this column) already created, so a fresh db gets
+    // a PRIOR build (without this column) already created, so a fresh db gets
     // the column from the CREATE above while an upgraded db needs this ALTER. Guard
     // it with a `PRAGMA table_info` column-exists check so the ALTER runs at most
     // once and re-running ensureVideoJobTable never throws (a duplicate ADD COLUMN
@@ -74,8 +74,8 @@ export function ensureVideoJobTable(db) {
     if (!cols.has("session_key")) {
         db.exec(`ALTER TABLE video_jobs ADD COLUMN session_key TEXT`);
     }
-    // Partial index for the poller's listPending() boot-resume scan (JOB-03).
+    // Partial index for the poller's listPending() boot-resume scan.
     db.exec(`CREATE INDEX IF NOT EXISTS idx_video_jobs_pending ON video_jobs (state) WHERE state = 'pending'`);
-    // Index for the agent-scoped get (JOB-04 / TARGET-01).
+    // Index for the agent-scoped get.
     db.exec(`CREATE INDEX IF NOT EXISTS idx_video_jobs_agent ON video_jobs (agent_id)`);
 }

package/node_modules/@comis/memory/dist/schema.d.ts

@@ -14,8 +14,8 @@ import type Database from "better-sqlite3";
 export declare function isVecAvailable(): boolean;
 /**
  * Additively ensure the `memories` table carries every column the current code
- * expects, adding any absent. The package's forward-only, additive column-add path
- * (design §4.1): SQLite has no `ADD COLUMN IF NOT EXISTS`, so each add is guarded by a
+ * expects, adding any absent. The package's forward-only, additive column-add path:
+ * SQLite has no `ADD COLUMN IF NOT EXISTS`, so each add is guarded by a
  * `PRAGMA table_info(memories)` presence check. Safe on every boot, including a live
  * `~/.comis` DB created before a column existed — existing rows get the column NULL (a
  * nullable add is O(1); no rewrite, no backfill).
@@ -40,8 +40,8 @@ export declare function ensureMemoryColumns(db: Database.Database): void;
  *
  * ## The UNIQUE index keys on `canonical_key`, NOT a SQL lower() expression
  *
- * RESEARCH Pitfall 3: SQLite's built-in `lower()` is ASCII-only (it leaves
- * `İSTANBUL`/`CAFÉ`/`ПРИВЕТ` unchanged), so the original §4.2 spec's UNIQUE index
+ * SQLite's built-in `lower()` is ASCII-only (it leaves
+ * `İSTANBUL`/`CAFÉ`/`ПРИВЕТ` unchanged), so a UNIQUE index
  * over a SQL `lower(...)` of the display name would NOT dedup Turkish/CJK/Cyrillic
  * case-variants → duplicate entities. Instead the resolver computes a
  * locale-independent `canonical_key` in TypeScript (`normalizeEntityKey` in
@@ -55,8 +55,8 @@ export declare function ensureMemoryColumns(db: Database.Database): void;
  * ENTIRE link-maintenance story (no orphan-sweep job). It fires
  * automatically because `openSqliteDatabase` already sets `PRAGMA foreign_keys = ON`
  * (sqlite-adapter-base.ts:52). NB: the parent `memory_entities` row is intentionally
- * NOT cascaded by a memory delete (entities are per-concept and may be re-linked;
- * RESEARCH Pitfall 7), so a stale `mention_count` is by-design, not an orphan bug.
+ * NOT cascaded by a memory delete (entities are per-concept and may be re-linked),
+ * so a stale `mention_count` is by-design, not an orphan bug.
  *
  * @param db - An open better-sqlite3 Database whose `memories` table exists (the FK
  *   target). Call AFTER the base `memories` CREATE.

package/node_modules/@comis/memory/dist/schema.js

@@ -4,6 +4,7 @@ import { ensurePinnedColumn } from "./schema-pinned.js";
 import { ensureVideoJobTable } from "./schema-video-jobs.js";
 import { ensureDurableRunTable } from "./schema-durable-runs.js";
 import { ensureOutwardLedgerTable } from "./schema-outward-ledger.js";
+import { ensureMsTeamsConversationTable } from "./schema-msteams-conversation.js";
 import { ensureOutcomeEventsTable } from "./schema-outcome-events.js";
 import { ensureMentalModelsTable } from "./schema-mental-models.js";
 import { ensureUsefulnessFailureColumn } from "./schema-usefulness.js";
@@ -20,8 +21,8 @@ export function isVecAvailable() {
 }
 /**
  * Additively ensure the `memories` table carries every column the current code
- * expects, adding any absent. The package's forward-only, additive column-add path
- * (design §4.1): SQLite has no `ADD COLUMN IF NOT EXISTS`, so each add is guarded by a
+ * expects, adding any absent. The package's forward-only, additive column-add path:
+ * SQLite has no `ADD COLUMN IF NOT EXISTS`, so each add is guarded by a
  * `PRAGMA table_info(memories)` presence check. Safe on every boot, including a live
  * `~/.comis` DB created before a column existed — existing rows get the column NULL (a
  * nullable add is O(1); no rewrite, no backfill).
@@ -85,8 +86,8 @@ export function ensureMemoryColumns(db) {
  *
  * ## The UNIQUE index keys on `canonical_key`, NOT a SQL lower() expression
  *
- * RESEARCH Pitfall 3: SQLite's built-in `lower()` is ASCII-only (it leaves
- * `İSTANBUL`/`CAFÉ`/`ПРИВЕТ` unchanged), so the original §4.2 spec's UNIQUE index
+ * SQLite's built-in `lower()` is ASCII-only (it leaves
+ * `İSTANBUL`/`CAFÉ`/`ПРИВЕТ` unchanged), so a UNIQUE index
  * over a SQL `lower(...)` of the display name would NOT dedup Turkish/CJK/Cyrillic
  * case-variants → duplicate entities. Instead the resolver computes a
  * locale-independent `canonical_key` in TypeScript (`normalizeEntityKey` in
@@ -100,8 +101,8 @@ export function ensureMemoryColumns(db) {
  * ENTIRE link-maintenance story (no orphan-sweep job). It fires
  * automatically because `openSqliteDatabase` already sets `PRAGMA foreign_keys = ON`
  * (sqlite-adapter-base.ts:52). NB: the parent `memory_entities` row is intentionally
- * NOT cascaded by a memory delete (entities are per-concept and may be re-linked;
- * RESEARCH Pitfall 7), so a stale `mention_count` is by-design, not an orphan bug.
+ * NOT cascaded by a memory delete (entities are per-concept and may be re-linked),
+ * so a stale `mention_count` is by-design, not an orphan bug.
  *
  * @param db - An open better-sqlite3 Database whose `memories` table exists (the FK
  *   target). Call AFTER the base `memories` CREATE.
@@ -113,7 +114,7 @@ export function ensureEntityTables(db) {
       tenant_id TEXT NOT NULL,
       agent_id TEXT NOT NULL,
       canonical_name TEXT NOT NULL,            -- display form (first-seen casing)
-      canonical_key  TEXT NOT NULL,            -- normalized key (TS lower+NFKD+strip-marks; NOT sqlite lower(), Pitfall 3)
+      canonical_key  TEXT NOT NULL,            -- normalized key (TS lower+NFKD+strip-marks; NOT sqlite lower())
       mention_count INTEGER NOT NULL DEFAULT 1,
       first_seen INTEGER NOT NULL,
       last_seen  INTEGER NOT NULL
@@ -222,7 +223,7 @@ export function ensureUsefulnessTable(db) {
     // The `failure_count` column is part of this table's complete contract (the
     // adapter's recordFailure upsert references it eagerly at construction) — add it
     // here so EVERY caller that ensures the usefulness table gets it, not only
-    // initSchema (v2.26 WS4, FORGET-02; distinct from ignored_count).
+    // initSchema (distinct from ignored_count).
     ensureUsefulnessFailureColumn(db);
 }
 /**
@@ -335,11 +336,11 @@ export function ensureTripleTable(db) {
   `);
 }
 // (The `relationship` table — the sole storage for the directional social-modeling
-//  subsystem — was DELETED in Phase 226 SIMPLIFY-03 with the rest of that subsystem
+//  subsystem — was DELETED with the rest of that subsystem
 //  (the __SOCIAL_MODELING__ cron, the RelationshipStore port + adapter, the
 //  relationship-block prompt injection). A fresh DB no longer creates it; an existing
 //  DB's orphaned `relationship` table is inert (never read/written) — no migration, no
-//  read path. No alias, I1.)
+//  read path. No alias.)
 /**
  * Initialize the full memory schema on the given SQLite database.
  *
@@ -467,29 +468,30 @@ export function initSchema(db, embeddingDimensions) {
     CREATE INDEX IF NOT EXISTS idx_sessions_tenant ON sessions(tenant_id);
     CREATE INDEX IF NOT EXISTS idx_sessions_updated ON sessions(updated_at);
   `);
-    // NOTE: the DAG context-store tables (ctx_*) were removed in v2.12 (Phase 126,
-    // LCD reimplementation) — only the schema-create call is gone (no reverse migration; existing DBs keep harmless orphaned tables, design §9).
+    // NOTE: the DAG context-store tables (ctx_*) were removed when the LCD store
+    // replaced them — only the schema-create call is gone (no reverse migration; existing DBs keep harmless orphaned tables).
     // The calls below run in dependency order AFTER the `memories` table (the FK
     // target) exists; each is idempotent, and every `ON DELETE CASCADE` fires via
     // the `PRAGMA foreign_keys = ON` already set by `openSqliteDatabase`. Per-table contracts (schema shape, isolation scope, trust floor) live in each fn JSDoc.
-    ensureMemoryColumns(db); // additive memory columns (forward-only; design §4.1)
+    ensureMemoryColumns(db); // additive memory columns (forward-only)
     ensureEntityTables(db); // entity junction tables
-    ensureUsefulnessTable(db); // recall-utility usefulness + intent bucket + failure_count (v2.26 WS4, FORGET-02)
+    ensureUsefulnessTable(db); // recall-utility usefulness + intent bucket + failure_count
     ensureCausalTables(db); // causal-edge table
     ensureTripleTable(db); // bi-temporal KG triples
-    // (ensureRelationshipTable — the directional social-modeling table — was DELETED in
-    //  Phase 226 SIMPLIFY-03 with the rest of that subsystem; orphaned tables on existing
+    // (ensureRelationshipTable — the directional social-modeling table — was DELETED
+    //  with the rest of that subsystem; orphaned tables on existing
     //  DBs are inert, no migration.)
-    ensureLcdTables(db); // LCD lossless message + parts store (Phase 127)
-    ensurePinnedColumn(db); // pinned-memory column + partial index (forward-only; design §4.1)
-    ensureVideoJobTable(db); // durable async video-job store (Phase 189, JOB-01/JOB-03)
-    ensureDurableRunTable(db); // durable run checkpoint store (Phase 216, DUR-01)
-    ensureOutwardLedgerTable(db); // exactly-once outward send ledger (Phase 216, ONCE-01)
-    ensureOutcomeEventsTable(db); // outcome_events ledger (v2.26 WS1, OUTCOME-01) — no FK, (tenant,agent)-scoped
-    ensureMentalModelsTable(db, embeddingDimensions, localVecAvailable); // mental_models doc store + FTS/vec/trigram twins (v2.31; generalized from v2.26 WS2 SKILL-01) — trust CHECK IN ('learned'), (tenant,agent)-scoped; copies a pre-existing learned_skills table forward as kind='skill'
-    // --- Observation partial indexes (design §4.1) --- created AFTER ensureMemoryColumns (indexed columns must exist first).
+    ensureLcdTables(db); // LCD lossless message + parts store
+    ensurePinnedColumn(db); // pinned-memory column + partial index (forward-only)
+    ensureVideoJobTable(db); // durable async video-job store
+    ensureDurableRunTable(db); // durable run checkpoint store
+    ensureOutwardLedgerTable(db); // exactly-once outward send ledger
+    ensureMsTeamsConversationTable(db); // conversation-id → routing-tuple map (proactive send)
+    ensureOutcomeEventsTable(db); // outcome_events ledger — no FK, (tenant,agent)-scoped
+    ensureMentalModelsTable(db, embeddingDimensions, localVecAvailable); // mental_models doc store + FTS/vec/trigram twins (generalized from the learned_skills store) — trust CHECK IN ('learned'), (tenant,agent)-scoped; copies a pre-existing learned_skills table forward as kind='skill'
+    // --- Observation partial indexes --- created AFTER ensureMemoryColumns (indexed columns must exist first).
     // `idx_memories_unconsol` serves the candidate scan (consolidated_at IS NULL); `idx_memories_observations` serves the observation lookup (proof_count IS NOT NULL).
-    // The design's third "live" index (exact-dup-retirement) is OMITTED — deferred to a later phase.
+    // A third "live" index (exact-dup-retirement) is intentionally OMITTED for now.
     db.exec(`
     CREATE INDEX IF NOT EXISTS idx_memories_unconsol
       ON memories(agent_id, created_at) WHERE consolidated_at IS NULL;
@@ -519,8 +521,8 @@ export function initSchema(db, embeddingDimensions) {
       cost_cache_write REAL NOT NULL DEFAULT 0,
       cache_saved REAL NOT NULL DEFAULT 0,
       latency_ms INTEGER NOT NULL,
-      -- PERSIST-02 cost-correctness columns (fresh DB; ensureObsTokenColumns ALTERs an
-      -- existing DB). The dead cache_retention column is intentionally ABSENT (OQ3 DROP).
+      -- Cost-correctness columns (fresh DB; ensureObsTokenColumns ALTERs an
+      -- existing DB). The dead cache_retention column is intentionally ABSENT.
       warmup_turn INTEGER,
       cache_eligible INTEGER,
       cost_correction REAL,
@@ -532,7 +534,7 @@ export function initSchema(db, embeddingDimensions) {
     CREATE INDEX IF NOT EXISTS idx_obs_token_provider ON obs_token_usage(provider, timestamp);
     CREATE INDEX IF NOT EXISTS idx_obs_token_session ON obs_token_usage(session_key, timestamp);
   `);
-    // PERSIST-02 + AUDIT-01/02 (both in schema-obs-token.ts, 800L cap). Called HERE,
+    // Both migrations live in schema-obs-token.ts (800L cap). Called HERE,
     // after the obs_token_usage CREATE — NOT in the ensure-call sequence above (runs
     // first). ensureObsTokenColumns: forward-only EXISTING-DB upgrade (drop dead
     // cache_retention + add the 5 cols). ensureObsAuditTable: obs_audit_events + indexes.

package/node_modules/@comis/memory/dist/setup-secrets.js

@@ -19,7 +19,7 @@ import { parseMasterKey, createSecretsCrypto, safePath, } from "@comis/core";
  *          err(Error) when key is present but invalid.
  */
 export function setupSecrets(opts) {
-    // W1: treat empty/whitespace SECRETS_MASTER_KEY as absent so seedKeyHex is not
+    // Treat empty/whitespace SECRETS_MASTER_KEY as absent so seedKeyHex is not
     // silently discarded when the operator exports an empty SECRETS_MASTER_KEY.
     const envKey = opts.env.SECRETS_MASTER_KEY;
     const raw = (envKey !== undefined && envKey.trim() !== "") ? envKey : opts.seedKeyHex;

package/node_modules/@comis/memory/dist/sqlite-memory-adapter.d.ts

@@ -11,7 +11,7 @@ import type { MemoryPort, MemoryPinnedStore, MemorySearchOptions, MemorySearchRe
 import { type Result } from "@comis/shared";
 import type Database from "better-sqlite3";
 /**
- * The decided branch of a {@link SqliteMemoryAdapter.supersede} call (FORGET-04),
+ * The decided branch of a {@link SqliteMemoryAdapter.supersede} call,
  * returned to the caller and logged as metadata (never the content body). A closed
  * string-literal union (no `kind: string`): `"superseded"` = the incumbent's content
  * was updated to the new value and its prior state appended to `memories.history`;
@@ -73,11 +73,11 @@ export declare class SqliteMemoryAdapter implements MemoryPort, MemoryPinnedStor
     }, Error>>;
     delete(id: string, tenantId?: string): Promise<Result<boolean, Error>>;
     /**
-     * Phase 224 (FORGET-04): resolve a user CORRECTION of an existing fact by
+     * Resolve a user CORRECTION of an existing fact by
      * SUPERSESSION, NOT deletion. UPDATEs the scoped incumbent's `content` to
      * `newContent` and APPENDs the prior state (`{ previousContent, changedAt }`) to
      * the `memories.history` JSON array. The row is UPDATEd, never DELETEd — deletion
-     * stays reserved for the FORGET-02 corroborated-poison security path. The existing
+     * stays reserved for the corroborated-poison security path. The existing
      * row IS the latest, so recall (search/searchLanes) naturally returns the new
      * content; there is NO `mentioned_at` column and NO recall-side asOf filter (the
      * superseded content simply stops being the row's `content`, preserved in history).
@@ -90,7 +90,7 @@ export declare class SqliteMemoryAdapter implements MemoryPort, MemoryPinnedStor
      * `WHERE id = ? AND tenant_id = ? AND agent_id = ?` (+ `user_id` when supplied),
      * bound params only (V4 isolation). The incumbent is parsed via the row mapper (no
      * `as Row`). The NEW content passes the same `validateMemoryWrite` redaction
-     * firewall a write goes through (INV-5) BEFORE the txn — a CRITICAL correction is
+     * firewall a write goes through BEFORE the txn — a CRITICAL correction is
      * rejected, never persisted. The `memories_au AFTER UPDATE OF content` trigger
      * re-syncs `memory_fts`; the normalized `memory_fts_tri` trigram twin is
      * re-inserted on the content change (the `growObservation` precedent), and the
@@ -108,13 +108,13 @@ export declare class SqliteMemoryAdapter implements MemoryPort, MemoryPinnedStor
      */
     supersede(id: string, newContent: string, scope: MemorySupersedeScope, now: number): Promise<Result<MemorySupersedeOutcome, Error>>;
     /**
-     * Phase 172 (DIST-05, WR-02): Read the memory ids for a (sessionKey, tenant,
+     * Read the memory ids for a (sessionKey, tenant,
      * agent) scope WITHOUT deleting. Used by the session-reset handler to capture
      * THIS session's ids BEFORE `deleteBySessionKey`, so `--purge-derived` can be
      * session-scoped (source_ids ∩ thisSessionIds) instead of the coarse
      * "any dangling source id" sweep.
      *
-     * R4 isolation: filters on `source_session_key` AND `tenant_id` AND `agent_id`
+     * Tenant/agent isolation: filters on `source_session_key` AND `tenant_id` AND `agent_id`
      * — the SAME scope as `deleteBySessionKey`. Typed read via the row mapper (no
      * `as Foo[]` cast — untyped-sqlite gate). Returns the ids (possibly empty).
      */
@@ -123,11 +123,11 @@ export declare class SqliteMemoryAdapter implements MemoryPort, MemoryPinnedStor
         agentId: string;
     }): Promise<Result<string[], Error>>;
     /**
-     * Phase 172 (DIST-05): Delete ALL memory rows for a (sessionKey, tenant, agent)
+     * Delete ALL memory rows for a (sessionKey, tenant, agent)
      * scope. ONE query covers BOTH paired-conversation memories AND lcd-distilled
      * episodic memories — both store `source_session_key` on the `memories` row.
      *
-     * R4 isolation: the WHERE filters on `source_session_key` AND `tenant_id` AND
+     * Tenant/agent isolation: the WHERE filters on `source_session_key` AND `tenant_id` AND
      * `agent_id`, so a cross-tenant or cross-agent row is never deleted (the same
      * fail-closed scoping the consolidation paths use). The `ON DELETE CASCADE` on
      * `lcd_memory_provenance.memory_id` drops the provenance rows automatically;