Verify relative imports through the application lifecycle

docs/roadmap/implementation.md

@@ -344,7 +344,7 @@ limitations.
 
 ## Stage 7 — Verify inheritance, history, sensitivity, and diffs
 
-Status: planned. Scope: retained placed data and one final application lifecycle.
+Status: complete. Scope: retained placed data and one final application lifecycle.
 
 1. Resolve a sibling parent/child supplied by separate relative imports after
    all tiers. Reuse nested inheritance/cancellation tests; add no cross-collection
@@ -366,6 +366,18 @@ Validate: engine `Import|Destination|Inheritance|Secret|Sensitivity|Explain|Diff
 tests, representative facade tests, and everyday check. Done: the feature feeds
 existing inspection/completion mechanisms without reconstructing them.
 
+Evidence (2026-10-14): based on `6458dbd`, using `go1.26.8 linux/amd64`. The
+engine import/destination/inheritance/secret/sensitivity/explanation/diff suite,
+representative facade import/destination/resource tests, and
+`./scripts/check.sh` all passed. New integration coverage resolves siblings
+from separate relative imports after a higher-tier parent replacement, then
+checks inherited secret fields, one-time defaults/resolution/validation/secret
+lookup, effective-path sensitivity, derived-value history, safe explanations,
+and bilateral redacted diffs. Relative-import output also matches equivalent
+wrapped placement in values, field presence, and safe diffs. Existing nested
+inheritance and displaced-descendant tests continue to cover cancellation and
+removed descendants. No limitations.
+
 ## Stage 8 — Demonstrate ordinary and mounted collection entries
 
 Status: planned. Scope: maintained public examples and their behavior tests.