Phase 1: CaskServer writes expected diagnostics to stderr, and tests cannot capture them #792

Merged
claude merged 2 commits from IW-681-phase-01 into IW-681 2026-10-11 06:05:08 +00:00
Member

Phase 01 implementation for IW-681.

Files

Browse changed files: https://code.iterative.works/iterative-works/iw-cli/-/blob/IW-681-phase-01/

Phase 01 implementation for IW-681. ### Files Browse changed files: https://code.iterative.works/iterative-works/iw-cli/-/blob/IW-681-phase-01/
Tests for the devMode warning and the Forgejo search/recent degradation now capture and assert the lines.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CaskServer diagnostics go through an injected sink
All checks were successful
CI / changes (pull_request) Successful in 5s
CI / contract (pull_request) Has been skipped
CI / format (pull_request) Successful in 11s
CI / lint (pull_request) Successful in 14s
CI / compile (pull_request) Successful in 1m51s
CI / dashboard-build (pull_request) Successful in 1m31s
CI / test (pull_request) Successful in 20m12s
567508bfb5
- diagnosticsLog sink on the CaskServer constructor and CaskServer.start; all 18 System.err.println calls use it
- devMode, Forgejo recent and Forgejo search tests capture and assert their diagnostic line
- Code review: 0 critical, 3 warnings recorded in FOLLOW-UPS.md
claude merged commit 237dc48e9f into IW-681 2026-10-11 06:05:08 +00:00
claude deleted branch IW-681-phase-01 2026-10-11 06:05:08 +00:00
Sign in to join this conversation.
No description provided.