Phase 3: TrackerError on the port's forge issue calls #780

Merged
claude merged 5 commits from IW-513-phase-03 into IW-513 2026-10-11 00:15:44 +00:00
Member

Phase 03 implementation for IW-513.

Files

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

Phase 03 implementation for IW-513. ### Files Browse changed files: https://code.iterative.works/iterative-works/iw-cli/-/blob/IW-513-phase-03/
The 10 GitHub, GitLab and Forgejo issue methods of TrackerOps return
Either[TrackerError, A]; Issue and Feedback take .message where they print.
Harness assertions on printed failures are exact; new tests pin that an
Unreachable issue failure is not retried.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
TrackerError on the port's forge issue calls
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 12s
CI / compile (pull_request) Successful in 1m48s
CI / dashboard-build (pull_request) Successful in 1m30s
CI / test (pull_request) Successful in 20m10s
bd084d7fed
- The 10 GitHub, GitLab and Forgejo issue methods of TrackerOps return Either[TrackerError, A]
- Issue and Feedback take .message at each call; LiveTrackerOps passes client results through
- FakeTracker issue setters take TrackerError; exact stderr assertions and no-retry tests
- docs/api pages for TrackerError, HttpCallFailure, ForgeWait and the changed forge modules
claude merged commit 5ec1ee0a14 into IW-513 2026-10-11 00:15:44 +00:00
claude deleted branch IW-513-phase-03 2026-10-11 00:15:45 +00:00
Sign in to join this conversation.
No description provided.