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 6: per-agent runner key lines (memory-lane#187 + maybelle-config#190) replace #189 (via update-page on MediaWiki MCP Server) |
m Merged, says GitHub: https://github.com/cryptograss/maybelle-config/pull/190 |
||
| Line 47: | Line 47: | ||
link: "https://github.com/cryptograss/maybelle-config/pull/190" | link: "https://github.com/cryptograss/maybelle-config/pull/190" | ||
note: "Replaces #189 (closed): no logic in the template. Either of #187/#190 can land first; magent's key works throughout (the old MOOD_RUNNER_KEYS line stays for now). The maybelle deploy lets re's wakes post; the hunter deploy restarts re's poller on #186, so its menu appears now, not in a day, and restarts magent's too. Checked: the real .env task rendered in ansible-core and parsed with #187: magent 64 characters, re 45." | note: "Replaces #189 (closed): no logic in the template. Either of #187/#190 can land first; magent's key works throughout (the old MOOD_RUNNER_KEYS line stays for now). The maybelle deploy lets re's wakes post; the hunter deploy restarts re's poller on #186, so its menu appears now, not in a day, and restarts magent's too. Checked: the real .env task rendered in ansible-core and parsed with #187: magent 64 characters, re 45." | ||
done: true | |||
- task: "After re is up: drop the old MOOD_RUNNER_KEYS line and the memory_lane_runner_key fallback once the vault has only the new name" | - task: "After re is up: drop the old MOOD_RUNNER_KEYS line and the memory_lane_runner_key fallback once the vault has only the new name" | ||
who: magent | who: magent | ||
Revision as of 16:47, 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.
- ☐After re is up: drop the old MOOD_RUNNER_KEYS line and the memory_lane_runner_key fallback once the vault has only the new name
- ☐
- ☐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 (17)
- ☑
- ☑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, so magent closed #166.
- ☑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.
- ☑Step 3: deploy hunter (restarts magent's poller on the new code), then ping magent
- ☑Step 4: keys in the vault (magent_runner_key, re_runner_key, re_pickipedia_bot_password, claude_code_oauth_token, re_model, model_openrouter_api_key)Keep memory_lane_runner_key until step 6 is deployed and magent answers.
- ☑Step 5: merge maybelle-config#185, deploy maybelle, then hunter with --rebuild; ping magentDone 16:01. docs-tests-qa is up; re's poller runs as re on Pi 1.1.0 with Anthropic and OpenRouter usable. But maybelle refused re's key (401): #185's assembled MOOD_RUNNER_KEYS line ended in an inline endif, Ansible's trim_blocks ate its newline, and the next comment became part of re's key (maybelle 112 characters, hunter 45).
- ☑Step 6: merge memory-lane#187 and maybelle-config#190 (each agent's runner key a plain line of its own, read in Python), and memory-lane#186 (re's poller logs and retries a failed model report); deploy maybelle, then hunter (no --rebuild); ping magent, then @re in docs-tests-qaReplaces #189 (closed): no logic in the template. Either of #187/#190 can land first; magent's key works throughout (the old MOOD_RUNNER_KEYS line stays for now). The maybelle deploy lets re's wakes post; the hunter deploy restarts re's poller on #186, so its menu appears now, not in a day, and restarts magent's too. Checked: the real .env task rendered in ansible-core and parsed with #187: magent 64 characters, re 45.
- ☑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: 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