Twinned from https://github.com/cfsh/ninefold/issues/868 by tools/beads/import_github.py's reconcile pass.
Raised by ninefold-reviewer while reviewing #864. Updated 2026-08-13: the dev box is resolved. Aedan minted a Graphite token there as aedanpope, then rotated it — gt auth on that box now reads jcantsp-bot. The durable rule that fell out of the episode is recorded in notes/graphite.md via #870. What stays open is the sandbox box, which has no token at all.
notes/machines.md is standing: *Every machine commits and opens PRs as jcantsp-bot … so aedanpope@ can approve every PR — GitHub forbids approving your own.* A gt token is the one credential on a box that can sit outside that rule, so it is worth answering per box rather than by habit.
gt submit refuses for want of a token, so the ban is self-enforcing rather than doc-enforced (DEV_PRINCIPLES B7). Costs gt sync / gt get; the token-free gt move fallback is already documented in notes/graphite.md. This is what stands while unanswered.jcantsp-bot (recommended). Matches the dev box, so the loop in notes/graphite.md works end-to-end everywhere and no session has to check which box it is on. The gt submit ban goes back to doc-enforced — which it already is on the dev box either way.gt submit stops refusing and starts opening PRs @aedanpope cannot approve.Default ships if unanswered — nothing is blocked on this.
None.
No comments.