extend

To list installed IWE extension hooks and changed parameters, run the management interface with no arguments. It reads the workspace extensions/ directory and params.yaml to display all active customizations and current overrides.

IWE extension points are predefined slots in day-open, day-close, and protocol workflows where custom markdown hooks execute. They run in a specific sequence based on filename ordering within the extensions/ directory.

To add a day-open.before hook, create a new extension markdown file in the extensions/ directory. The management interface guides creation while preserving filename ordering to ensure correct hook execution sequence.

Yes, you can audit workspace customizations by inspecting the extensions/ directory and reviewing params.yaml. The interface shows installed extension files and overridden parameters so you can track all workspace changes.

To install third-party extension bundles, use the management interface to guide the installation process into the extensions/ directory. It verifies the extension markdown files and adjusts filename ordering for proper hook execution.

Filename ordering dictates the exact execution sequence of IWE protocol hooks. The management interface requires preserving this alphabetical order when creating or updating extension markdown files to ensure workflows run correctly.