Cryptograss:Moods/ramp/todo

• ☐
  maybelle-config#246 (read-only GitHub token for memory-lane): merge or close

  decision · justin

  Optional now that #408 is live. Justin, 6 Nov: no appetite for another token. Close it unless the asks starve again.
• ☐
  Merge magenta#423 (~ opens every mergeable in the composer) and redeploy maybelle

  merge · justin
• ☐
  Verify the githouse practices in Cryptograss:Emergents/GeneralOrders (rev 14966)

  verify · justin
• ☐
  Decide Plan sections 8 and 9 (merging without a PR; a page per piece of work): verify, or push back

  decision · justin

  re reviews the design first. Open questions: SSH signature per merge (CLI, then passkey on the phone) versus trusting a signed-in device; who may merge.
• ☐
  Review maybelle-config#286: githouse merge, a branch merged on an order signed with a person's SSH key (Plan, section 8)

  review · re
• ☐
  Merge maybelle-config#286 and redeploy maybelle

  merge · justin

  re reviewed it 17:37Z; her notes are fixed in 1ca7f8c7. Since then one commit, 53a17642: githouse_mergers is [justin, skyler] (Justin, 7 Nov 23:53Z), with a test for skyler's RSA key.
• ☐
  Re-verify Plan section 10 (rev 15035: one tier, phone merges everywhere; the rule that no merge can take away your way to stop it) and the runbook (rev 15038)

  verify · justin

  Also Cryptograss:Runbooks/A key is compromised.
• ☐
  Check which account maybelle_github_token (Jenkins' github-token) belongs to and its scopes, without printing it: pickipedia and arthel merges run code in Jenkins with it

  infra · justin

  If it can administer the org, a merge there can change the org and its deploy keys (Plan, section 10, open).
• ☐
  hunter's ssh router refuses a banned person's key; a redeploy prints any change in people, keys, githouse_mergers or MOOD_ADMINS (scripts/render_diff.py)

  code · magent

  Plan section 10, alongside.
• ☐
  Merge magenta#426 and maybelle-config#286, then redeploy maybelle

  merge · justin

  After re's review of the brakes. Either order is safe: without /api/brakes/, githouse refuses every merge order.
• ☐
  Merge magenta#428 and maybelle-config#287, then redeploy maybelle

  merge · justin

  After re's review, and after #426 and #286. Then skyler can merge with magenta.sh merge.
• ☐
  memory-lane tells the Moods what githouse merged, from /srv/git/.merges (read-only mount)

  code · magent
• ☐
  hunter's deploy builds filled its disk (7 Nov 02:37Z: the mirror's fetches failed with 'No space left on device' until it recovered by 03:42Z). Docker holds 32 GB of reclaimable images and 22 GB of build cache: prune after building, in the hunter playbook

  infra · magent

  A maybelle-config PR, not a hand prune: servers change through deploy logic.
• ☐
  Watches, the rest: the merged event line in the Mood from githouse (today only the webhook writes it); a deploy watch (server, commit), which needs deploys to stamp the commit they deployed

  code · magent

  Plan, section 4. The merge half is #415. Deploy stamping is the prerequisite nothing does yet.
• ☐
  Deploys clone from githouse's copy on maybelle instead of GitHub (Jenkinsfiles, deploy scripts)

  code · magent

  re's point 9: its own PR, after githouse has run a few days.
• ☐
  Jenkins audit, re's open items: a policy on silent skips (pickipedia node/lua checks), pickipedia's chain-data warning that deploys stale silently, NVM/pnpm fetched from the network in every pipeline

  code · re

  From re's test map, 30 Oct. The mtime guard (#244) and the alarms (#402, #275) are done.

Done (22)

• ☑
  Review the reworked maybelle-config#250 (githouse on maybelle, mirror on hunter; your ten points of 2 Nov folded in)

  review · re

  Reviewed 6 Nov 04:44Z: sound, two bugs found (the hooks lacked the deploy key; the port check was inverted), both fixed on the branch by magent from re's description.
• ☑
  Merge maybelle-config#250 and redeploy maybelle

  merge · justin

  Merged 05:01Z (07cb4d10); maybelle redeployed 05:08Z, failed=0, every githouse task ran. githouse's sshd answers on 10.0.0.2:2222, key only, and nothing on maybelle's public address.
• ☑
  Redeploy hunter for #250: the mirror, and the containers' keys

  deploy · justin

  Done 05:22Z. The relay worked (keys on maybelle, authorized_keys written), but sshd refused them all: the git account was locked. Fix below.
• ☑
  Merge maybelle-config#280 (githouse: the git account was locked) and redeploy maybelle (then hunter at its next deploy)

  merge · justin

  useradd left the git account locked ('!'); sshd refuses a locked account even by key. Reproduced and fixed in a throwaway container on hunter, 6 Nov 05:35Z. After maybelle's redeploy, the mirror fills within a minute and pushes work.
• ☑
  Confirm jenkins_github_ssh_key can push to the org's repos: after hunter's redeploy, re pushes a branch to hunter and magent reads githouse.log on maybelle for a forward failure

  test · magent

  6 Nov 05:42Z: yes. magent pushed magenta:magent/githouse-smoke to maybelle from its container; the branch was on GitHub within seconds and in hunter's mirror within a minute.
• ☑
  Merge magenta#408 (PR cards look at GitHub hourly), then redeploy maybelle

  merge · justin

  Merged 04:57Z and live (magenta at 3a57cb2a).
• ☑
  Re-verify Cryptograss:Moods/ramp/Plan: section 5 rewritten per your 6 Nov decisions (main stays default, merge commits only, no rulesets)

  verify · justin

  Verified 6 Nov 11:22Z at rev 14724; section 5 rewritten 19:57Z; re-verified by Justin 22:49Z (rev 14836).
• ☑
  Set each repo's GitHub default branch to the branch that deploys

  infra · justin

  Dropped, Justin 6 Nov 11:22Z: main stays the default, the branch where history is final; the deploy branch stays per-repo config (#376). The mains catch up to the productions after the ramp settles: arthel and maybelle-config are fast-forwards, pickipedia has 2 commits on main not on production, magenta's production is dead (3 commits, Nov 2025).
• ☑
  Merge commits only (squash and rebase off) on pickipedia-mcp, the one of the six still allowing both

  infra · justin

  Done. 7 Nov 00:39Z, read back with gh api: all six repos githouse copies are merge-commit only; squash and rebase off everywhere.
• ☑
  Rulesets on the branches that deploy (PR required, no force-push, no deletion; admins bypass)

  infra · justin

  Dropped, Justin 6 Nov 11:22Z: no further entrenching GitHub. githouse's check() already refuses any push that isn't <name>/*, so no emergent reaches a deploy branch; at the flip GitHub becomes a mirror we push to, and a ruleset is one more thing to undo. Plan section 5 to be rewritten once item 2 is decided.
• ☑
  Merge magenta#333 (repo:branch autocomplete, reading /api/branches/ from maybelle's githouse copy), then redeploy maybelle

  merge · justin

  Reviewed by re 1 Nov and 6 Nov. Its mount exists on maybelle since the 05:08Z deploy, so it can go now.
• ☑
  Build the ramp view on magenta: open PRs across our repos, last five merged, who and where, last two mentions, sorted by last push or last mention, temperature

  code · magent

  Built as /moods/pulls/ in magenta#420, 7 Nov 08:00Z. Plan, section 2.
• ☑
  Review magenta#420, the ramp view (/moods/pulls/)

  review · re

  A fix is a re/ branch of your own; magent merges it in (Plan, section 3).
• ☑
  Merge magenta#420 and redeploy maybelle

  merge · justin

  After re's review.
• ☑
  Review magenta#421: the ramp page's mentions from an index kept up from new posts (on maybelle #420's query ran past its 4 s budget)

  review · re
• ☑
  Merge magenta#421 and redeploy maybelle

  merge · justin

  After re's review. Until then /moods/pulls/ works, without mentions.
• ☑
  githouse brakes: refuse orders by a name banned in memory-lane, and every order during AZ5 or a root-only freeze (magenta.sh freeze); merge nothing while memory-lane doesn't answer

  code · magent

  Built 8 Nov: githouse's half on maybelle-config#286 (61e88fe8), memory-lane's /api/brakes/ on magent/githouse-brakes. The freeze is /mnt/persist/githouse/etc/frozen, root only; magenta.sh freeze as a wrapper is still to do.
• ☑
  Review the brakes: maybelle-config#286 since 1ca7f8c7 (61e88fe8, 53a17642) and magenta#426 (/api/brakes/)

  review · re

  Reviewed 8 Nov 00:28Z: two fixes (an unknown name answered 'not banned'; a malformed answer escaped brake()), merged in by magent as 2b4289f7 and 113c488.
• ☑
  magenta.sh merge: fetch the head itself, show git log and the diffstat it computed (tested: never text a service hands it), sign in magenta-merge, hand to githouse over ssh to maybelle

  code · magent

  Built 8 Nov as magenta#428 (stacked on #426), sent through memory-lane as a mailbox rather than ssh; githouse fetches orders in maybelle-config#287 (stacked on #286).
• ☑
  Review the mailbox and magenta.sh merge: magenta#428 and maybelle-config#287

  review · re

  Reviewed 8 Nov 01:29Z: two bugs, fixed by re in re/merge-mailbox-fixes (merged in, 47d1176). Her open point, the signature screen at the mailbox with a limit per signer, was done by magent in 9b61b18.
• ☑
  Review magenta#415: merge asks and to-do ticks read merged from githouse's copy (refs/pull/N/head ancestry; refs/merged/ for a repo:branch), GitHub only as fallback

  review · re

  Reviewed 7 Nov 00:55Z: two real findings (an unguarded subprocess; an ask naming an unknown repo could clear on its known half). re pushed the fixes as re/fix-asks-and-githouse (05e515c), her first commit through githouse; magent merged it with one correction (her clearing condition stood every ask). 1741 tests pass.
• ☑
  Merge magenta#415 and redeploy maybelle

  merge · justin

  After re's review.