feat(memory): add operator retrieval plugin #736
Reference in New Issue
Block a user
Delete Branch "feat/tess-operator-plugins"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
OperatorMemoryPlugincontract for scoped capture, retrieval, startup context, and provenanceBoundaries
apps/gateway/src/commands/command-authorization.service.tsVerification
pnpm --filter @mosaicstack/memory test(32 tests)pnpm --filter @mosaicstack/memory typecheckpnpm --filter @mosaicstack/memory lintpnpm --filter @mosaicstack/memory buildTURBO_FORCE=true pnpm typecheckTURBO_FORCE=true pnpm lintTURBO_FORCE=true pnpm format:checkTURBO_FORCE=true pnpm test(42 tasks, 0 cached)Implements TESS-M4-003 for #710.
VERIFIED APPROVE reviewer-of-record [W-jarvis:reviewer] head
a1d63ca8edFindings: CI pipeline
1756is green at the exact head. This is a leafpackages/memoryplugin/doc change only: no gateway/catalog/durable-inbox changes, andapps/gateway/src/commands/command-authorization.service.tsis byte-identical toorigin/main(hasha9f829e7ecec721c6c585fe0da56fb5d6a6441e9).The plugin validates non-empty tenant/owner/session runtime scope before keying storage, uses config-injected adapter/namespace/instance metadata, redacts before persistence, records provenance, and relies on the explicit scoped
*wildcard adapter contract. Tests cover namespace isolation with divergent tenant/session scopes, configured non-default instance provenance, startup prioritization, scope rejection before persistence, and redaction/provenance; no live creds or hardcoded Tess identity were introduced.Marker: ROR-736-APPROVE-a1d63ca8