Use structured logging for internal diagnostics

[highbyte]

Summary

• route internal CLI and web diagnostics through typed, structured logging with stable event IDs and levels
• keep command output, safety prompts, worker events, and worker NDJSON on their existing stdout/stderr protocols
• add provider fan-out, filtering, stderr-routing, safe-target, and NDJSON-isolation coverage
• document the central logging and capture contract with POSIX and PowerShell examples

Verification

• dotnet test Wrighty.slnx --configuration Release --nologo (2,304 passed)
• npm test (96 passed; coverage thresholds met)
• npm run test:coverage (96 passed; coverage thresholds met)
• package-manager manifest tests (6 passed)
• release smoke tests (2 passed)
• dotnet list Wrighty.slnx package --vulnerable --include-transitive (no vulnerable packages)
• changed-file dotnet format ... --verify-no-changes
• real wrighty web check: 404 diagnostic reached stderr only and omitted the non-allowlisted query value

Closes #136

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
94.3% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud