feat(build): report which commit this process was actually loaded from

[MGrin]

MX-141. Eighth plugin on the pattern proved in MX-139 (bb-plugin-accounts).

bb bundles a path: plugin from source at reload, so a revision read at module load is by construction the code now executing. Nothing else can say: bb plugin list prints running and the source path but no revision, bb plugin source has none to record for a path: source, and dist/ is not the loaded artifact — its mtime was measured lying by 15 minutes.

Answered first in run(), ahead of provision (creates tunnel, DNS and Access) and share (exposes a local port to the internet). "What is running" must stay answerable when the thing running is broken, and must never have a side effect of its own.

dirty rides along because a bundle built from an edited tree matches no commit; a missing git dir yields rev: null rather than a guess.

Verified

committed 8aff94e4f, NO reload:
  fell through to the default status output — the verb did not exist
after reload:
  8aff94e4f  dirty=False   (matches the checkout exactly)

npm test — 77 passing, 0 failing. node --check clean.

One pre-existing thing worth flagging, not caused by this change

npm run typecheck runs tsc --noEmit, but this repo has no tsconfig.json, so tsc just prints its help text and exits 0. The script has therefore never typechecked anything, and its exit code makes it look like it did. Not fixing it here — that is a separate call — but it should not keep passing silently.

🤖 Generated with Claude Code