audit: media-library - Validate readiness and operational handover #292

Audit Summary

Comprehensive validation of media library implementation and handoff to operations/content team.

Additional Context

Final phase of #267. This issue covers end-to-end validation of the media library, documentation for ongoing operations, and handoff procedures.

Acceptance Criteria

• Reconcile final catalogue coverage and accepted recovery limitations.
• Verify deployed variants, browser fallbacks, visual fidelity, references and metadata.
• Record print-suitability findings and accepted gaps; track deferred print-ready book exports separately.
• Record agreed performance, credit-display, build and usage-monitoring checks.
• Exercise runbook and rollback; record training and project-owner acceptance.

Dependencies

Dependency-role clarification: #280 supplies evaluation, #281 supplies design, #289 supplies final schema approval, #290 supplies configuration evidence and #291 supplies implementation evidence. These descriptions do not create blocking relationships.

• Blocked by: design: media-library - Design the import and reference-migration workflow #281 (migration implementation complete), research: media-library - Evaluate media storage and publishing workflows #280, content-model: media-library - Define the asset catalogue and provenance model #279, bug: assets - Restore original Figma artwork #7 (all phases done)
• No blockers after this phase

Deliverables

• End-to-end validation report (asset count, format coverage, performance)
• Operations runbook (adding assets, updating, troubleshooting)
• Content team workflow documentation
• Performance baseline report (Core Web Vitals, CDN caching, build time)
• Rollback procedure documentation
• Project sign-off checklist

References

• Strategy Report § 6: .github/reports/toa-media-library/MEDIA-LIBRARY-STRATEGY-REPORT.md
• Sample Catalogue: .github/reports/toa-media-library/SAMPLE-CATALOGUE.json

Immediate next steps

Obtain authorised implementation/deployment evidence and approved recovery/catalogue inputs. Validate visual fidelity, references, variants, metadata, credits, agreed performance and rollback. Record accepted limitations separately from deferred print-ready delivery.

Evidence required

Executed results tied to the deployed version, asset-level exceptions, reviewed runbook, rollback exercise, recipient training and project-owner acceptance. Planning documents and illustrative PASS results do not establish readiness.

Current status — 19 October 2026

Backlog. Specifications and recovery-support tooling exist, but deployed migration validation, exercised rollback, training and owner acceptance are not established.

Definition of Ready (DoR)

• Final validation and handover outcome are defined.
• Deployment, catalogue, validation guide, print-assessment scope, deferred delivery gaps and participants are confirmed.

Definition of Done (DoD)

• End-to-end results and defect/exception dispositions are reviewed.
• Operational handover and owner acceptance are recorded; the epic is updated without automatic closure.

Specification references

• Specification
• Plan
• Tasks

Draft specification/planning references at revision 02aee367; not evidence of approval, completed recovery or implementation. Task correspondences below describe relevant scope, not exclusive ownership or completed work.

T032–T038 provide potential guidance inputs only. Final deployment validation, training, rollback exercise and owner acceptance are not delivered by this task set.