Reconcile Site V2 documentation authority

[proaiexpert]

Purpose

Repair the ProAI Expert website documentation authority chain before creating the final Site V2 Commercial Alignment Spec.

What changed

• made AI_CURRENT_HANDOFF.md the single current operational handoff;
• converted the old Phase A handoff into an explicit historical tombstone;
• updated the Site Evolution Roadmap to reflect completed Portfolio Master Polish work and the approved Site V2 sequence;
• aligned the roadmap with the canonical Client Acquisition Operating Plan and the three capability pillars;
• corrected the active portfolio route/evidence ownership model;
• marked the completed portfolio master plan, polish synthesis and experience blueprint as historical;
• marked the obsolete Local Repair Pro planning handoff as historical;
• selected alina-horb/CASE_PACK.md as the current Alina evidence owner and archived the duplicate production brief;
• updated Website Production Factory status to point to the reusable Premium Site Experience Standard and current Site V2 sequence.

Why

The repository contained multiple documents claiming current/canonical authority, references to branch-only files that do not exist in main, completed pre-implementation plans still presented as active, and an outdated two-path website roadmap. That made it unsafe to create a final redesign specification.

Scope

Documentation only. Ten Markdown files.

No changes to:

• production HTML, CSS or JavaScript;
• Jekyll includes/data;
• Header or Footer implementation/spec files;
• routes, metadata, sitemap or structured data;
• public copy, case evidence or assets;
• forms, analytics, integrations or deployment.

Coordination

Baseline: 7e990536c41faa21b182d1db6e5100be13c75188.

PR #95 is a separate Footer System task. This PR intentionally does not touch its files or scope.

Validation

• compared branch against baseline: 10 documentation files only;
• verified no production files are changed;
• retained original long-form historical content in Git history;
• added explicit current-authority and tombstone instructions;
• preserved locked commercial, evidence, EN/RU and quality decisions.

Next step after approval

Create a separate docs-only task for:

docs/site-evolution/PROAI_EXPERT_SITE_V2_COMMERCIAL_ALIGNMENT_SPEC.md

That task will define IA, Hero, capability/offer pages, CTA/contact routing, portfolio integration, measurement and route-level acceptance criteria without implementing the redesign.