refactor: move Matrix implementation ownership to pinned plugins #98
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refactor/matrix-gateway-ownership"
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?
Actual Matrix ownership extraction
Remove Core Matrix channel/factory/sync/native-delivery implementation, consume plugin-owned sources pinned to published d703c9c (plugins PR4 merged). CLI consumes generic baseline module catalog, no hardcoded Matrix factory/namespace. Core keeps generic GatewayManager/contract and shared progress/durability helpers. Existing Matrix tests now import generated pinned plugin source.
Materializer distinguishes locked sibling imports from Core imports, including import() type references, verifies every digest before replacing output. Regression verifies imports and failed integrity leaves prior generated files intact. Catalog resolves actual gateway factory. Docs explicitly distinguish build-time ownership from runtime overlay.
Validation/limits
Full554/554tests,typecheck/build/diffcheck PASS; 66focused Matrix/gateway plus2 extraction regressions. No actual live Matrix acceptance or runtime hot swap claimed. Existing zero/multiple gateway manager tests retained. Author inspected, no additional independent reviewer/reset; standing delivery mandate. Other policy/memory extraction and persistent overlays still open. Build/merge not deployment, defaults/environment remain unchanged. All unrelated original dirty drafts preserved.