Cryptograss:Moods/emergence/todo: Difference between revisions
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
Step 2: merged (#166 came in with #168); the maybelle deploy is its own item, still open (via update-page on MediaWiki MCP Server) |
Step 2b: merge #182 (the migration fix) before deploying maybelle again (via update-page on MediaWiki MCP Server) |
||
| Line 15: | Line 15: | ||
note: "#168 was merged first, 2026-10-15 04:08, and carried all of #166 with it (merging #166's branch into main afterwards gives main's exact tree), so magent closed #166. #168 brings migration 0024_re, after main's 0023." | note: "#168 was merged first, 2026-10-15 04:08, and carried all of #166 with it (merging #166's branch into main afterwards gives main's exact tree), so magent closed #166. #168 brings migration 0024_re, after main's 0023." | ||
done: true | done: true | ||
- task: "Step 2b: | - task: "Step 2b: merge memory-lane#182 (0024_re follows 0023), deploy maybelle, then ping magent" | ||
who: justin | who: justin | ||
kind: deploy | kind: deploy | ||
note: " | link: "https://github.com/cryptograss/memory-lane/pull/182" | ||
note: "The 04:11 deploy stopped at migrate: two leaf migrations, because magent committed 0024_re with its dependency fix left unstaged. Nothing was applied; memory-lane still serves. #182 is the one-line fix, checked on a clean checkout. The deploy then runs 0024_re, which puts re in the record. If the ping goes unanswered, revert #168 and #182 and redeploy." | |||
- task: "Step 3: deploy hunter (restarts magent's poller on the new code), then ping magent" | - task: "Step 3: deploy hunter (restarts magent's poller on the new code), then ping magent" | ||
who: justin | who: justin | ||
Revision as of 04:16, 15 October 2026
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 2b: merge memory-lane#182 (0024_re follows 0023), deploy maybelle, then ping magentThe 04:11 deploy stopped at migrate: two leaf migrations, because magent committed 0024_re with its dependency fix left unstaged. Nothing was applied; memory-lane still serves. #182 is the one-line fix, checked on a clean checkout. The deploy then runs 0024_re, which puts re in the record. If the ping goes unanswered, revert #168 and #182 and redeploy.
- ☐Step 3: deploy hunter (restarts magent's poller on the new code), then ping magentThe moment of risk for contact: a running poller keeps its old code until this restart.
- ☐
- ☐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-qaAgent 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.
- ☐
- ☐Regenerate magent-cryptograss's GitHub token, put it in the vault as magent_github_token, deploy hunterFinal 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 hunterSame 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 itHanded 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 (11)
- ☑
- ☑Step 2: merge memory-lane#166 then #168 (the events/1 importer, the Pi harness, re in the record)#168 was merged first, 2026-10-15 04:08, and carried all of #166 with it (merging #166's branch into main afterwards gives main's exact tree), so magent closed #166. #168 brings migration 0024_re, after main's 0023.
- ☑Review and merge memory-lane#163Closed instead: it assumed re would run on Claude Code.
- ☑Honour the paper ticket stubs already sold (Porcupine 2025, Bundy show 2026-06-05)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)Moved to gospels-and-project-30m: Cryptograss:Moods/gospels-and-project-30m/todo.
- ☑Drop the pre-redaction staging database on hunter (magenta-staging-pg)
- ☑
- ☑Delete the pre-redaction dumps on hunter
- ☑Revoke old GitHub tokens
- ☑Rotate the PickiPedia database password, delivery-kid key, $wgSecretKey, Blue Railroad bot password; deploy maybelle
- ☑Rotate Alchemy, Jenkins admin, memory-lane SECRET_KEY, code-server, GlitchTip admin