Make Pro Sync readiness and Analytics completion actionable

[Coding-Dev-Tools]

Scope

• Report Cloud Sync connection separately from a valid user-held encryption key and local readiness. Disable Sync now until local prerequisites pass; never expose key material.
• Support source-tagged Pro onboarding deep links, actionable 0/0 sync recovery, and explicitly confirmed sharing for owned personal Team workspaces.
• Refresh a pending Analytics job by its existing ID without uploading another snapshot or creating another job; display a completed result and distinguish stale, empty, failed, and pending states.
• Document key backup and recovery before first upload.
• Publish immutable v72 public offline evidence because two bound source files changed. Offline aggregate values are unchanged; v70 remains historical.

Verification

• 173 focused Python tests and 11 Edge browser tests passed.
• Ruff, JavaScript syntax, dashboard asset drift, commercial manifest, and diff checks passed.
• The full offline suite had one source-checksum failure against v70. Immutable v72 was generated from the final source and the evidence tests passed; the entire suite was not rerun after that fix.
• After merging the current 1.7.6 main, v72 source hashes and artifact digest were reverified.

Release boundary

Draft for review. No hosted deployment, payment, production account journey, or live Cloud Sync was performed. Hosted Pro acceptance still requires the Cloud branch, attended staging, and exact deployed revision checks.