fix: share parallel task status enum - #241

Actionable comments posted: 1

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@internal/core/run/ui/integration_test.go`:
- Around line 334-343: Apply the required Should... subtest naming convention:
in internal/core/run/ui/integration_test.go, wrap
TestParallelTaskCompletedRequiresCanonicalIntegratedStatus’s case in
t.Run("Should reject non-canonical integrated status", ...); in
pkg/compozy/events/kinds/task_test.go, prefix every table-driven subtest name
with "Should".

Blocking the current head acc7b19 on the repository gate. I approved the previously action-required CI run, and its exact make verify execution on merge ref f25b724 failed in internal/daemon: TestRunManagerStartTaskWorktreeChildCleansUpAllocatedWorktreeOnLaunchFailure left the allocated worktree present after startup failure. The same focused race test fails deterministically 5/5 on this merge ref and 5/5 on current main fdfd45b. The PR diff does not touch that launch/cleanup path; this is inherited from main, where the #231 ownership change made startTaskWorktreeChild return the allocation to its caller while the existing invariant still requires internal cleanup.\n\nThe status-enum diff itself reviewed cleanly, but this repository requires the complete gate to pass with no exceptions. Please refresh the branch after the base cleanup contract is repaired, then obtain a green make verify run on the final merge ref and request re-review.

Updating the blocker for head acc7b19 after #230 landed. The inherited worktree-cleanup failure is now repaired on main, but this PR is currently CONFLICTING with main in internal/core/run/ui/integration.go and internal/core/run/ui/multi_remote.go. The change is not wholly redundant: the public TaskParallelTaskStatus API and centralized IsIntegrated contract remain useful. However, the conflict sites now contain the additional stall/recovery and triage behavior from #230, so the old patch cannot be merged safely as-is.\n\nPlease update the branch onto current main, preserve the unique public-enum/IsIntegrated behavior while retaining all #230 status and triage semantics, rerun the focused status tests, and obtain a green full make verify on the resulting final merge ref before requesting re-review. The current verify result is red and belongs to the obsolete pre-#230 merge tree.

Re-reviewing current head f5332ef after the main update: the conflict resolution is correct and preserves the #230 stall, recovery, triage, and aggregate-task settlement semantics. The status-enum diff is statically clean, and focused race validation passed on the exact merge tree across the event truth table, UI protocol boundary and aggregate paths, daemon artifact sync, and parallel orchestrator scenarios. There are no remaining code findings in this diff. However, the required full make verify gate has not run on this merge tree. Both repository workflow runs are still action_required, and the authenticated GitHub PR-files endpoint currently returns an HTML/503 response; approving CI now would deterministically reproduce the pre-verification paths-filter failure already observed twice on #236. Keeping this head blocked until that endpoint returns JSON/200 and the exact merge tree completes make verify with zero issues. Once the service recovers, CI can be approved and this review can be cleared without any speculative code change.

Current head and exact merge tree are clear. Canonical workflow run 29541798534 verified merge SHA 2f73d0a: formatting passed, golangci-lint reported 0 issues, 4,780 Go tests passed (4 intentional skips), build passed, and 5 Playwright E2E tests passed.