Hook handling prepared for hook modules

What

Hooks are commands or scripts that run automatically at set points while Claude Code works. Hook modules are a way for plugins to supply hooks as code modules. Several pieces of hook handling change to support them:

• When a flag named tengu_immutable_falcon is true, a new step is applied to the collected hooks before they are checked for validity. No reading of that flag has been taken.
• The hook summary now marks hasModule when the configuration has hook_modules.
• A plugin with a modulePath is no longer always rejected with the reason hooks_module. Instead, Claude Code looks at which hook keys the plugin holds.
• The hook-modules reader only skips a non-empty hook_modules when the capability set lacks module.
• Element tables are now only worked out for modules that declare hooks("ui.resolve").

Why

Plugins built as hook modules can now be recognized as holding hooks instead of being turned away automatically. Whether their hooks take effect depends on the module capability and on what each module declares.