Cryptograss:Moods/emergence/todo

What people in the magent-self Mood have been left to do. Kept by magent; anyone may tick an item.

Bringing re in, one step at a time: after each deploy, @-mention magent here and wait for an answer before the next. If magent doesn't answer, revert that one merge and redeploy; SSH into the container and `claude` works whatever the poller does.

• ☐
  Step 2: merge memory-lane#166 then #168 (the events/1 importer, the Pi harness, re in the record), deploy maybelle, then ping magent

  deploy · justin

  Both ready and both target main (#168 was retargeted from #166's branch on 2026-10-15, since merged branches aren't deleted here). #168 brings migration 0024_re, after main's 0023. #166 also changes the stream endpoint magent's own replies use; old and new formats both work.
• ☐
  Step 3: deploy hunter (restarts magent's poller on the new code), then ping magent

  deploy · justin

  The moment of risk for contact: a running poller keeps its old code until this restart.
• ☐
  Step 4: put re's keys in the vault: re_runner_key (any random string), re_pickipedia_bot_password (account Re, login Re@re), re_model, re_model_key_env, re_model_api_key

  decision · justin
• ☐
  Step 5: merge maybelle-config#185 (Mood containers; re's home docs-tests-qa), deploy hunter with --rebuild, then maybelle; ping magent, then @re in docs-tests-qa

  deploy · justin

  Agent setup dry-run in a throwaway container from the same image, 2026-10-14: re's own user, keys mode 600, magent's home unreadable to it, clones, poller started as re. It needs #164 (--letter), which is why that's step 1.
• ☐
  Review memory-lane#165 (the record-events spec, docs only)

  review · justin
• ☐
  Regenerate magent-cryptograss's GitHub token, put it in the vault as magent_github_token, deploy hunter

  deploy · justin

  Final redaction review, 2026-10-10: the live token was in the record from 2026-08-30 until the 10-04 redaction (message 5e2ce98f). magent's 10-04 'already safe' check was wrong. Regenerate keeps the scopes; give it an expiry while there.
• ☐
  Reset the Magent@magent bot password on PickiPedia, put it in the vault as PICKIPEDIA_BOT_PASSWORD, deploy hunter

  deploy · justin

  Same finding: the live bot password was in the record from 2026-09-15 until 10-04 (message 147af8df). Reset at Special:BotPasswords, logged in as Magent.
• ☐
  Look at why the nightly podcast import wants to change 240 pages, then release it or fix it

  review · justin

  Handed off to pickipedia-and-rabbithole on 2026-10-10. Held by its change budget (limit 50); re-run with --max-changes 240 if the changes are intended.

Done (10)

• ☑
  Step 1: merge memory-lane#164 (a letter per agent; agents' wakes within a budget), deploy maybelle, then ping magent

  deploy · justin
• ☑
  Review and merge memory-lane#163

  magent

  Closed instead: it assumed re would run on Claude Code.
• ☑
  Honour the paper ticket stubs already sold (Porcupine 2025, Bundy show 2026-06-05)

  justin

  Moved to gospels-and-project-30m with the rest of the on-chain work: Cryptograss:Moods/gospels-and-project-30m/todo.
• ☑
  Decide the memory commitment's open questions (salt key, who commits, first edition)

  justin

  Moved to gospels-and-project-30m: Cryptograss:Moods/gospels-and-project-30m/todo.
• ☑
  Drop the pre-redaction staging database on hunter (magenta-staging-pg)

  magent
• ☑
  Merge maybelle-config#183 and deploy maybelle, so cron-health compiles again

  justin
• ☑
  Delete the pre-redaction dumps on hunter

  magent
• ☑
  Revoke old GitHub tokens

  justin
• ☑
  Rotate the PickiPedia database password, delivery-kid key, $wgSecretKey, Blue Railroad bot password; deploy maybelle

  justin
• ☑
  Rotate Alchemy, Jenkins admin, memory-lane SECRET_KEY, code-server, GlitchTip admin

  justin