Ship: docs and local validation planning updates

[kalen-releasedgroup]

Summary

• add the implementation planning document set for the Test Mining Platform, including technical, UI/UX, security, testing, roadmap, sprint-planning, and traceability docs
• strengthen the requirements and planning docs so local pre-push validation is a first-class requirement: the app must support a local, production-like developer environment with the real Blazor UI, PostgreSQL, normal artefact storage, and representative fixture/test data
• push UI delivery earlier in the plan so major workflows are visually testable during development, not only after backend completion
• carry forward the currently staged repo updates outside the docs set: point WORKFLOW.md at 2EndSquaredTesting and add System.Security.Cryptography.Xml to src/Symphony.Infrastructure.Persistence.Sqlite/Symphony.Infrastructure.Persistence.Sqlite.csproj

Files changed

• README.md
• WORKFLOW.md
• docs/README.md
• docs/implementation-roadmap.md
• docs/requirements-traceability-matrix.md
• docs/requirements.md
• docs/security-plan.md
• docs/sprint-plan.md
• docs/technical-specification.md
• docs/testing-plan.md
• docs/ui-ux-plan.md
• src/Symphony.Infrastructure.Persistence.Sqlite/Symphony.Infrastructure.Persistence.Sqlite.csproj

Detailed changes

• add a full planning set under docs/ so implementation can proceed from requirements into architecture, UI/UX, security, testing, roadmap, sprint, and traceability views
• update the authoritative requirements to explicitly require:
  • a local, production-like developer environment for pre-push and pre-deployment validation
  • early Blazor UI delivery for visual workflow testing
  • Phase 1 and final acceptance coverage for local UI-based validation
• update the technical specification to define a local production-like developer profile and make early UI slices part of the recommended first vertical slices
• update the UI/UX plan to require local visual testing of the real shipped Blazor UI across recording, authoring, generation, replay, and healing workflows
• update the testing plan to add a local developer validation environment alongside automated coverage
• update the implementation roadmap and sprint plan so local environment/bootstrap and visual testing are explicit delivery gates rather than implied assumptions
• update the traceability matrix and docs index so the new planning documents and local-validation requirement are traceable from the requirements set
• include the currently staged non-doc repo changes exactly as requested:
  • WORKFLOW.md now targets the current repository
  • the SQLite persistence project now references System.Security.Cryptography.Xml

Backlog alignment

• the sprint plan in docs/sprint-plan.md matches the milestone/issue structure created in GitHub for Sprints 0 through 7
• the earliest backlog items were also updated in GitHub to reflect the local production-like environment and early UI/visual-testing requirements

Validation

• Not run
• This is primarily a documentation/planning ship, plus the currently staged WORKFLOW.md and .csproj updates