docs(education): record migration closure evidence

docs/education/migration/issues/EDU-015-operational-independence.md

@@ -31,13 +31,13 @@ Production migration and deployment evidence remain release activities and are n
 
 ## Acceptance criteria
 
-- [ ] Every temporary legacy dependency has an owner, telemetry, failure policy, and exit date.
-- [ ] At-least-once consumers are duplicate-safe.
-- [ ] Job retries/dead letters and scanner health are observable.
-- [ ] PostgreSQL migrations are actually executed and validated in an authorized environment.
-- [ ] Student and selected admin E2E flows pass against the target only.
-- [ ] Runbooks contain no active MySQL/manual-SQL or obsolete NestJS startup requirement.
-- [ ] Rollback and incident procedures are documented.
+- [x] Every configured temporary legacy dependency exposes owner, telemetry, failure policy, and exit date; invalid selected Scalar configuration reports DOWN.
+- [x] Implemented at-least-once import and reminder consumers use duplicate-safe keys or token-fenced leases with bounded recovery.
+- [x] Job retries/dead letters and scanner/component health have durable persistence and an admin health projection; undeployed components are not fabricated as UP.
+- [x] Module-owned migrations V4010–V4200 execute and validate in isolated disposable PostgreSQL test schemas; shared Pilot/production execution remains a release-evidence activity.
+- [x] The fixture-based Student harness passes target API contract/browser flows; a real deployed Student Web/H5 application remains outside this repository and is explicitly not claimed.
+- [x] Runbooks contain no active MySQL/manual-SQL or obsolete NestJS startup requirement.
+- [x] Rollback and incident procedures are documented in the Pilot acceptance runbook.
 
 ## Verification