TD-078: render info-severity doctor issues distinctly from warnings

BackendCapabilities marks poll-mode queue_sync_unsupported and
queue_connection_missing diagnostics as severity=info, but the doctor
command routed every non-error issue through warn(), so a healthy
service/poll-mode deployment rendered an informational queue note in
the amber [WARN] band that operators treat as a real configuration
problem.

V2DoctorCommand::renderHumanSnapshot() now branches on severity and
prefixes the message with the severity level: [ERROR] issues stay on
error(), [WARN] issues stay on warn(), and [INFO] issues fall through
to line() so they do not carry warning styling.

Regression coverage in V2DoctorCommandTest proves three paths:
poll-mode sync queue → [INFO] + strict success,
poll-mode missing connection → [INFO] + strict success,
queue-mode sync queue → [ERROR] + strict failure.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: durable-workflow-ops

src/Commands/V2DoctorCommand.php

@@ -66,17 +66,19 @@ private function renderHumanSnapshot(array $snapshot): void
                 continue;
             }
 
+            $severity = (string) ($issue['severity'] ?? 'warn');
             $message = sprintf(
-                '[%s] %s',
+                '[%s] [%s] %s',
+                strtoupper($severity),
                 (string) ($issue['code'] ?? 'capability_issue'),
                 (string) ($issue['message'] ?? 'Capability issue detected.'),
             );
 
-            if (($issue['severity'] ?? null) === 'error') {
-                $this->error($message);
-            } else {
-                $this->warn($message);
-            }
+            match ($severity) {
+                'error' => $this->error($message),
+                'info' => $this->line($message),
+                default => $this->warn($message),
+            };
         }
     }
 

tests/Unit/Commands/V2DoctorCommandTest.php

@@ -29,4 +29,49 @@ public function testJsonOutputSucceedsWithoutStrictMode(): void
             '--json' => true,
         ])->assertSuccessful();
     }
+
+    public function testPollModeSyncQueueIsReportedAsInfoNotWarning(): void
+    {
+        // TD-078: in poll mode the queue-driver diagnostic is informational,
+        // not a capability failure. The doctor command must render it with an
+        // [INFO] tag rather than Laravel's amber [WARN] tag, and --strict must
+        // still succeed.
+        config()->set('queue.default', 'sync');
+        config()->set('queue.connections.sync.driver', 'sync');
+        config()->set('workflows.v2.task_dispatch_mode', 'poll');
+
+        $this->artisan('workflow:v2:doctor', ['--strict' => true])
+            ->expectsOutputToContain('[INFO] [queue_sync_unsupported]')
+            ->doesntExpectOutputToContain('[WARN] [queue_sync_unsupported]')
+            ->assertSuccessful();
+    }
+
+    public function testPollModeMissingQueueConnectionIsReportedAsInfoNotWarning(): void
+    {
+        // Mirror of the sync-driver case for a missing queue connection in
+        // poll mode. Same rule: info-severity output, not a warning, and
+        // --strict still succeeds.
+        config()->set('queue.default', 'missing-driver');
+        config()->set('queue.connections.missing-driver', []);
+        config()->set('workflows.v2.task_dispatch_mode', 'poll');
+
+        $this->artisan('workflow:v2:doctor', ['--strict' => true])
+            ->expectsOutputToContain('[INFO] [queue_connection_missing]')
+            ->doesntExpectOutputToContain('[WARN] [queue_connection_missing]')
+            ->assertSuccessful();
+    }
+
+    public function testQueueModeSyncQueueIsReportedAsErrorAndFailsStrict(): void
+    {
+        // The flip side of the poll-mode relaxation: in default queue mode
+        // a sync driver is an error-severity capability failure. The doctor
+        // command must render it with [ERROR] and --strict must fail.
+        config()->set('queue.default', 'sync');
+        config()->set('queue.connections.sync.driver', 'sync');
+        config()->set('workflows.v2.task_dispatch_mode', 'queue');
+
+        $this->artisan('workflow:v2:doctor', ['--strict' => true])
+            ->expectsOutputToContain('[ERROR] [queue_sync_unsupported]')
+            ->assertFailed();
+    }
 }