iris-execute-mcp-v2

Review and promote configuration/code drift from a source IRIS environment to a target using the review-before-write iris_env_diff -> iris_env_promote workflow (scoped diff, plan, an explicit user-selected step allowlist, confirmed execute, re-diff verify). Never acts on onlyInTarget warnings -- never deletes a target-only item, in any action.

Resend failed Interoperability messages for a config item using the dry-run-first iris_message_resend workflow — preview the match count before executing, then verify the new headers via iris_production_messages. States the duplication hazard and that resend/resendFiltered are governance-default-disabled writes.

Audit the IRIS instance's security posture: users (default passwords, %All holders), roles, service authentication settings, SSL/TLS configs, and instance auditing status.

Run a full IRIS instance health check (iris_health_check) and interpret every non-ok finding, naming the fixing tool for each one.

Deploy an ObjectScript class or package to IRIS (iris_doc_load, glob-path form), fix compile errors, then run its unit tests (iris_execute_tests) with a total-count check.

Diagnose a slow SQL query using iris_sql_analyze (explain, indexUsage, stats) and recommend a fix — never auto-applies one.

A concise (<=300 word) pre-write checklist distilling the project's ObjectScript conventions ($$$ macros, Quit-in-try/catch, %OnNew/initvalue, no-underscore names, storage sections untouchable, deploy/test discipline).

Provision a new IRIS project environment: two databases, a namespace, a user, and a web application — verifying each step before the next, with rollback notes.

Diagnose and recover a troubled/wedged Interoperability production, following the recover-first, clean-last-resort escalation ladder. Never suggests killAppData without the user's explicit acceptance of persistent business-state loss.

Freeze the IRIS instance for an external (OS/SAN-level) snapshot backup and thaw it safely afterward — thaw ALWAYS runs, even if the snapshot step failed.

Trace a message's flow through an Interoperability production using iris_production_messages, iris_message_diagram, and iris_production_logs for any erroring items.

Plans, creates, and validates BMad modules. Use when the user requests to 'ideate module', 'plan a module', 'create module', 'build a module', or 'validate module'.