Surface active runtime/source/release drift for local DMC installs

[chubes4]

Problem

After merging a DMC cleanup fix, the local running plugin still used an older copied plugin directory. The primary checkout was on release-latest, behind/diverged, while the PR merged to main. It took several checks to discover which copy powered studio wp datamachine-code.

Desired behavior

Add a status/diagnostic surface that shows:

• active WordPress plugin path and version
• whether the active plugin is a git checkout, symlink, or copied deploy
• configured source checkout path/version/branch/head
• upstream release-latest or deploy source version/head
• exact command to reconcile the runtime safely

Acceptance criteria

• One command tells the operator whether the CLI runtime includes a just-merged fix.
• It identifies source/runtime drift without manual readlink, plugin header reads, and Homeboy component probing.
• It does not mutate anything unless an explicit apply/deploy command is run.