{"version":"2.1.265","anchor":"new-create-factory-form-for-the-memory-read-tool-with-a","canonical_anchor":"new-create-factory-form-for-the-memory-read-tool-with-a","heading":"New create() factory form for the memory-read tool with a signal-only call context","tier":"internal","area":"Tooling Architecture","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-create-factory-form-for-the-memory-read-tool-with-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New `create()` factory form for the memory-read tool with a signal-only call context\n\nThe memory-read tool's internal setup was rewritten to a newer factory pattern, likely with no visible change\n\n**What**\n\nThe tool that reads memory documents (likely the one behind `project_memory_read`) was restructured internally: instead of a plain method taking a store, path, and an abort controller, it now uses a `create()` factory function that returns an object whose call method takes a cancellation signal directly. This matches a newer coding pattern already used by other tools.\n\n**Why**\n\nThis is an internal refactor rather than a behavior change, and it doesn't appear to affect what the tool does when reading memory documents.\n\n- Area: Tooling Architecture\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}