docs(planning): reconcile AutoAudit product docs with engineering plan + board

[anmolg1997]

What

planning/RECONCILIATION.md — maps Akhilesh's product docs (VISION/MVP/ROADMAP/JOURNEY_MAPS, on product-planning) onto the engineering plan: the GitHub Projects board (#9) and the merged WS-A data foundation + WS-B identity.

Answers Anmol's question — "how do we use these to update our plan, and where do we need to vs not" — under Akhilesh's rule: redefine the product items, keep the foundation/technical ones.

Highlights

• Reframe: BMR Compliance Intelligence → AutoAudit AI, a 10-stage QMS; our repo is the "Document Intelligence Engine" (Stages 2–5); MVP = Stages 0–5 wrapping it with net-new entities (Profile/Audit Event/Work Item/Evidence/Finding), 9 screens, 4 roles, Dashboard, notifications.
• Foundation is not wasted: WS-A/WS-B and board workstreams A–E are the substrate and stay. F and G get redefined; a large net-new product layer (WS-P) is added.
• Board change-set (ready to apply): mark A1/A2/A3/A5/B1/B2 Done; redefine F/G; add WS-P Stage 0–5 epics + reconciliation tasks.
• Reconciliations: role realignment (4 product roles + Document-Owner upload perm); naming collision (product "Audit Event" vs our AuditEventRow trail); C2 e-signatures elevated; Phase-0 shrinks (PDF + X-Actor-Id already resolved).
• Closes two MVP open questions: our foundation already answers multi-tenancy (Open Q1) and auth strategy (Open Q2).
• Open decisions for product: brand name; SaaS-vs-on-prem demo target; reviewer assignment model.

Related

• Akhilesh's audit-rule-author skill landing: feat(skills): land audit-rule-author skill (rule + agentic-audit authoring) #155
• Product docs to merge to main so they're canonical: product-planning branch