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 4: model vendors' keys are shared by all agents (model_<vendor>_api_key) (via update-page on MediaWiki MCP Server) |
m Merged, says GitHub: https://github.com/cryptograss/memory-lane/pull/183 |
||
| Line 31: | Line 31: | ||
link: "https://github.com/cryptograss/memory-lane/pull/183" | link: "https://github.com/cryptograss/memory-lane/pull/183" | ||
note: "Runs migration 0025_harness_models. Before step 5, so the endpoint re's poller reports its models to exists when it first starts. magent's own poller is untouched until a hunter deploy, and on Claude Code it reports nothing." | note: "Runs migration 0025_harness_models. Before step 5, so the endpoint re's poller reports its models to exists when it first starts. magent's own poller is untouched until a hunter deploy, and on Claude Code it reports nothing." | ||
done: true | |||
- task: "Step 4: put keys in the vault: re_runner_key (any random string), re_pickipedia_bot_password (account Re, login Re@re), re_model (its default, e.g. openrouter/moonshotai/kimi-k3), and model_<vendor>_api_key for each vendor you get a key for" | - task: "Step 4: put keys in the vault: re_runner_key (any random string), re_pickipedia_bot_password (account Re, login Re@re), re_model (its default, e.g. openrouter/moonshotai/kimi-k3), and model_<vendor>_api_key for each vendor you get a key for" | ||
who: justin | who: justin | ||
Revision as of 14:27, 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 4: put keys in the vault: re_runner_key (any random string), re_pickipedia_bot_password (account Re, login Re@re), re_model (its default, e.g. openrouter/moonshotai/kimi-k3), and model_<vendor>_api_key for each vendor you get a key forThe vendor keys are shared by every agent (re now, orang and blu later); re_<vendor>_api_key would give re its own, only if it ever needs a separate limit or bill. Vendors: openrouter (https://openrouter.ai/settings/keys — one key, 401 models), anthropic (https://console.anthropic.com/settings/keys), openai (https://platform.openai.com/api-keys), google (https://aistudio.google.com/apikey), moonshotai (https://platform.moonshot.ai/console/api-keys), deepseek (https://platform.deepseek.com/api_keys). Any you skip show greyed in the menu.
- ☐Step 5: merge maybelle-config#185 (Mood containers; re's home docs-tests-qa), deploy maybelle, then hunter with --rebuild; ping magent, then @re in docs-tests-qaMaybelle first, so memory-lane accepts re's runner key before re's poller starts and reports with it. Agent setup dry-run in a throwaway container, 2026-10-14; the vendor keys (f748058f) checked 10-15: agent.env mode 600, only vendors with a key, values shell-quoted; the shared-or-own lookup checked in ansible-core.
- ☐
- ☐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 (14)
- ☑
- ☑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.
- ☑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 magentDeployed 2026-10-15 04:32; magent's poller restarted 04:33 on main's code (7ce1200) and answered the 04:35 ping, streaming its turn into the record step by step.
- ☑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