IW-629: Two-line PURPOSE headers for core harness tests #638
No reviewers
Labels
No labels
agent-ready
bug
contract
documentation
duplicate
enhancement
good first issue
help wanted
invalid
needs-human
needs-input
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
iterative-works/iw-cli!638
Loading…
Reference in a new issue
No description provided.
Delete branch "IW-629"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Gives the core harness tests the two-line
// PURPOSE:header that the project rule requires, and removes a one-time debug test.Changes
// PURPOSE:line to 17core/test/*HarnessTest.scalafiles. Comment-only change.core/test/DebugTest.scala. It only existed to debug a stdout-capture problem and nothing refers to it.Testing
rg -c '^// PURPOSE:'over every changed file (each gives 2).corecompiles with warnings as errors; the pre-push unit suite passed.Follow-ups
PhaseMergeHarnessTest.scalastill do not have exactly two PURPOSE lines.LinearClientTestcalls the live Linear API in the unit suite and failed the pre-push hook once on a slow call.Release notes
See
project-management/issues/IW-629/release-notes.md(Czech). No user-visible change.Review packet:
project-management/issues/IW-629/review-packet.md🤖 Generated with Claude Code
Closes #629
DebugTest.scala and the core *HarnessTest.scala files have only one PURPOSE line Artifacts: - analysis.md - issue.md 🤖 Generated with Claude Code Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>