Clarify scheduled provenance and history ordering

docs/roadmap/remediation.md

@@ -1,6 +1,6 @@
 # Import Integration Correctness Audit
 
-Status: in progress; finding 1 complete, findings 2 and 3 remain.
+Status: in progress; findings 1 and 2 complete, finding 3 remains.
 
 Reviewed tree: `91db99b` (including the six completed fixes through `5747ec4`).
 Scope: import discovery/defaults and shared dependency-ready scheduling, including
@@ -63,7 +63,7 @@ glob, symlink, and cycle tests passed, as did `./scripts/check.sh`,
 `go test -race -count=1 ./...`, and `git diff --check`. The original public
 reproduction now succeeds for all selectors.
 
-## 2. [ ] P2 — Describe scheduled provenance and history order consistently
+## 2. [x] P2 — Describe scheduled provenance and history order consistently
 
 Owner: [configuration contract](../config.md), especially layered metadata
 around lines 431–439, historical explanation around lines 501–504, and strict
@@ -96,6 +96,13 @@ DFS behavior or introduce an independent provenance ordering rule. Existing
 scheduled-placement and import-order tests already cover the main mechanics;
 check the revised wording against the public cases above.
 
+Completed: composite-origin, explanation-history, and conflict-location wording
+now links to scoped assembly order and distinguishes it from source acquisition.
+The descriptions retain precedence-tier order and item-local scope boundaries.
+No scheduler or provenance implementation changed. Verified the public composite
+origin/history and conflict reproductions, existing scheduled-placement and main/
+underlay ordering tests, local documentation links, and `git diff --check`.
+
 ## 3. [ ] P3 — Qualify the empty-path inspection exception by requiredness
 
 Owner: [import inspection contract](../config.md#explicit-imports), around lines