Sesh production indexing boundary and incremental sync
A company-wide Sesh deployment should keep Coding Sessions/TimeTracker as the canonical source, treat Sesh as a rebuildable derived FTS+vector index, and expose it through Sherlock/Cosmos as the ACL-constrained access layer. Do a one-time allowlisted backfill, then ingest increme…