investigation-mode

Application triage systematically checks runtime logs, workflow status, browser verification, and deployment environments to identify root causes in production or development. Structured reporting at every step maintains visibility and recovery plans.

Coordinating debugging workflows requires applying deterministic step sequencing across runtime logs, workflow status, browser verification, and deployment environments. This structured triage surfaces root causes quickly rather than investigating issues in isolation.

Automated triage supports debugging stalled deployments across both production and development environments. It orchestrates checks across runtime logs, workflow status, browser state, and environment configurations to identify the root cause.

Diagnostic triage triggers on frustration signals like stuck, hung, broken, or waiting, then systematically checks runtime logs, workflow status, browser state, and deployment environments to resolve the issue. It implements configurable prompt signals for recovery.

Structured triage limitations depend on the configurable prompt signals and deterministic step sequencing defined in its reporting contract. It requires clear frustration triggers to initiate the log, workflow, browser, and deployment investigation sequence effectively.