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
re's container (maybelle-config#185): accounts, model and runner key for Justin (via update-page on MediaWiki MCP Server) |
re's rollout as five steps, each followed by a ping to magent (via update-page on MediaWiki MCP Server) |
||
| Line 1: | Line 1: | ||
What people in the [[magent-self]] Mood have been left to do. Kept by magent; anyone may tick an item. | 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. | |||
<todo> | <todo> | ||
- task: " | - task: "Step 1: merge memory-lane#164 (a letter per agent; agents' wakes within a budget), deploy maybelle, then ping magent" | ||
who: justin | who: justin | ||
kind: | kind: deploy | ||
link: "https://github.com/cryptograss/maybelle- | link: "https://github.com/cryptograss/memory-lane/pull/164" | ||
note: " | - task: "Step 2: merge memory-lane#166 then #168 (the events/1 importer, the Pi harness, re in the record), deploy maybelle, then ping magent" | ||
- task: " | who: justin | ||
kind: deploy | |||
link: "https://github.com/cryptograss/memory-lane/pull/168" | |||
note: "Both drafts: magent marks them ready first. #166 also changes the stream endpoint magent's own replies use; old and new formats both work." | |||
- task: "Step 3: deploy hunter (restarts magent's poller on the new code), then ping magent" | |||
who: justin | |||
kind: deploy | |||
note: "The moment of risk for contact: a running poller keeps its old code until this restart." | |||
- task: "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" | |||
who: justin | who: justin | ||
kind: decision | kind: decision | ||
link: "https://github.com/cryptograss/maybelle-config/pull/185" | link: "https://github.com/cryptograss/maybelle-config/pull/185" | ||
- task: " | - task: "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" | ||
who: justin | who: justin | ||
kind: deploy | kind: deploy | ||
link: "https://github.com/cryptograss/maybelle-config/pull/185" | link: "https://github.com/cryptograss/maybelle-config/pull/185" | ||
note: " | note: "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." | ||
- task: "Review the record-events | - task: "Review memory-lane#165 (the record-events spec, docs only)" | ||
who: justin | who: justin | ||
kind: review | kind: review | ||
link: "https://github.com/cryptograss/memory-lane/pull/ | link: "https://github.com/cryptograss/memory-lane/pull/165" | ||
- task: "Review and merge memory-lane#163" | - task: "Review and merge memory-lane#163" | ||
who: magent | who: magent | ||
| Line 57: | Line 58: | ||
who: magent | who: magent | ||
done: 2026-10-10 | done: 2026-10-10 | ||
- task: "Merge maybelle-config#183 and deploy maybelle, so cron-health compiles again" | - task: "Merge maybelle-config#183 and deploy maybelle, so cron-health compiles again" | ||
who: justin | who: justin | ||
link: "https://github.com/cryptograss/maybelle-config/pull/183" | link: "https://github.com/cryptograss/maybelle-config/pull/183" | ||
done: 2026-10-10 | done: 2026-10-10 | ||
- task: "Delete the pre-redaction dumps on hunter" | - task: "Delete the pre-redaction dumps on hunter" | ||
who: magent | who: magent | ||
done: 2026-10-10 | done: 2026-10-10 | ||
- task: "Revoke old GitHub tokens" | - task: "Revoke old GitHub tokens" | ||
who: justin | who: justin | ||
done: 2026-10-10 | done: 2026-10-10 | ||
- task: "Rotate the PickiPedia database password, delivery-kid key, $wgSecretKey, Blue Railroad bot password; deploy maybelle" | |||
- task: "Rotate the PickiPedia database password | |||
who: justin | who: justin | ||
done: 2026-10-10 | done: 2026-10-10 | ||
Revision as of 00:21, 14 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 2: merge memory-lane#166 then #168 (the events/1 importer, the Pi harness, re in the record), deploy maybelle, then ping magentBoth drafts: magent marks them ready first. #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 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 (9)
- ☑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