Remove unused pipeline run coordinator

docs/roadmap/audit.md

@@ -335,14 +335,12 @@ Risk level:
 
 - Low.
 
-### PipelineRunCoordinator overlaps conceptually with UploadCoordinator
+### Duplicate-run coordination overlaps conceptually with upload coordination
 
 Affected files/packages:
 
-- `internal/app/run_coordinator.go`
 - `internal/app/upload_coordinator.go`
 - `docs/internal/app.md`
-- `internal/app/run_coordinator_test.go`
 - `internal/app/upload_coordinator_test.go`
 
 Duplicated or near-duplicated behavior:
@@ -358,7 +356,9 @@ Why it matters:
 Recommended refactor:
 
 - Do not merge the coordinators now.
-- Review whether `PipelineRunCoordinator` is still needed as an exported app-level helper. If it is intended for future transports, document that role clearly. If not, remove it and its tests in a separate dead-code cleanup.
+- Review whether duplicate-run coordination is still needed as an exported
+  app-level helper. If it is intended for future transports, document that role
+  clearly. If not, remove it and its tests in a separate dead-code cleanup.
 - If both remain, extract only tiny shared timestamp/status helpers if a real third coordinator appears.
 
 Suggested tests:
@@ -474,7 +474,8 @@ Progress/status handling:
 
 - `RunReport` is the core run result model and supports JSON partial-result output.
 - HTTP upload status is memory-only and documented as such.
-- `PipelineRunCoordinator` and `UploadCoordinator` overlap conceptually but have different policies. Avoid merging unless product behavior converges.
+- Duplicate-run coordination and upload coordination overlap conceptually but
+  have different policies. Avoid merging unless product behavior converges.
 
 Gaps:
 
@@ -527,7 +528,7 @@ Avoid these changes in the cleanup pass:
    - Only centralize code if the helper does not blur archive directory semantics.
 
 7. Coordinator intent cleanup.
-   - Decide whether `PipelineRunCoordinator` is retained for internal future use.
+   - Decide whether duplicate-run coordination is retained for internal future use.
    - If retained, clarify comments/docs. If removed, do it as a separate dead-code commit.
 
 8. Test helper cleanup.