Put the reviewer App key on dev boxes? nf-uplj ← Beads

Twinned from https://github.com/cfsh/ninefold/issues/582 by tools/beads/import_github.py's reconcile pass.

Surfaced by ninefold-reviewer reviewing #578, which adds ./tools/pr/review_now.py <pr> so a dev session can pull a Tier-0 verdict instead of waiting out the ~30m cron. The tool works only where the reviewer App's private key is; the key is machine-local and hand-carried, so today that is the sandbox box alone. Every other box preflights with an honest "no credential here, the cron picks it up".

This is a security-posture call, not an engineering one — the tool is identical either way, only its reach changes.

A. Key stays on the sandbox box only. Sessions elsewhere keep waiting out the cron. Smallest blast radius; the feature helps one box.

B. (recommended default) Carry the key to the boxes that host dev sessions too — today the WSL office box and the Linux gating host. Every session can pull its own review; the key spreads to three machines, each of which can post as ninefold-reviewer[bot].

C. Neither — put the key on one box and let other boxes ask it to run a review over SSH. Keeps the key in one place, adds a hop and a host to keep alive.

Default ships if unanswered — nothing is blocked on this.