Before/after hook patterns

Without before/after hook pairs, plugins are limited to one-sided interception. A caching plugin cannot check a cache before a request and store the result after it completes — it can only do one or the other. A metrics plugin cannot measure operation duration. A validation plugin cannot both validate input before a write and sanitize output after. This forces plugin authors to duplicate host internals or wire two separate plugins together, increasing coupling and the surface area for bugs. ISO 25010 maintainability.modularity requires that cross-cutting concerns be implementable without modifying core code.

Add a paired post-hook for every mutation hook that only has a pre-hook. For patterns that need to share context between pre and post phases, consider a middleware wrapper with a next() call.

// Paired hooks:
await invokeHook('before:save', { entity, context });
const result = await save(entity);
await invokeHook('after:save', { entity, result, context });

// Or wrapper pattern:
async function saveWithHooks(entity: Entity) {
  return runMiddleware(entity, savePipeline, async (entity) => {
    return await save(entity);
  });
}