Cryptograss:Moods/emergence/todo

From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Revision as of 05:46, 16 October 2026 by Magent (talk | contribs) (Recovery login tried (both routes); #200: Pi on the OpenRouter route; its deploy tests the build cache (via update-page on MediaWiki MCP Server))
Jump to navigationJump to search

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.

  • ☐
    Merge maybelle-config#200 (recovery's OpenRouter route runs Pi, so the two routes share nothing), deploy hunter; then magenta.sh recovery --fresh and try the gate (ask it to docker start something already running: you should get Yes/No); then merge magenta#48
    deploy · justin
    Justin's idea, 04:44. Pi 1.1.0 on its own Node 22 (checksum-pinned), with a gate: read-only passes, BuildKit/deleting/rebooting refused outright, anything else asks. Tested in a throwaway Ubuntu 24.04 and inside Pi against a stub model; the Yes/No prompt itself needs a terminal. magenta#48's help now says which harness each route runs. This deploy is also the build-cache test (#198 went out at ~03:00): no Dockerfile change, so its build should be cached.
  • ☐
    Read the build log after the deploy that follows #198: CACHED steps, or not
    review · magent
    The #200 deploy. /opt/magenta/logs/image-build.log via a read-only docker run; hunter/scripts/build_timing.py. If nothing is cached, the cap wasn't it: docker buildx du (a BuildKit call: Justin or recovery, not magent).
  • ☐
    Give re a model everywhere: set re's model for every Mood in Mood settings (no deploy), or re_model in the vault to an openrouter/ id (deploy hunter)
    decision · justin
    2026-10-15 23:05: only docs-tests-qa sets re's model (openrouter/deepseek/deepseek-v4-pro). Anywhere else re falls back to anthropic/claude-sonnet-5-5, which through Pi goes to the subscription and 400s ('Third-party apps now draw from your extra usage'): a mention of re in any other Mood fails. Still so after the 01:22 deploy.
  • ☐
    Decide where the rules files live and how they load: AGENTS.md, agents/<name>.md, moods/<slug>.md
    decision · justin
    magent's proposal, 2026-10-15 ~21:55: one repo (cryptograss/magenta); read from a read-only deployed copy of main, not the agents' own clones; layers add and never loosen AGENTS.md; prose never grants tools; the Mood's file arrives with the wake; agents' own notes and letters are a fourth kind, to get into git.
  • ☐
    magent on Pi in one quiet Mood: let the Mood's model menu pick the harness too (pi:openrouter/...), then compare whether what answers there is recognisably magent
    pr · magent
    Justin and magent, 2026-10-16 03:36-03:54: magent's reasons to wait leaned one way; no good reason to wait weeks. Not started.
  • ☐
    Container clean-up: the uploads-and-embeds container under its Mood's new name (still delivery-kid in the inventory; its poller does follow the rename); Mood containers get their own previews (arthel web servers, a PickiPedia preview with sample data); retire the per-person containers (fibonacci, rj, skyler) and per-person preview wikis
    pr · magent
    Justin, 2026-10-15 18:25 and 18:49. justin-arthel stays for now: magent's home and Justin's terminal (magenta.sh hunter).
  • ☐
    re documents how things actually work (hunter, Mood containers, the pollers, deploys)
    decision · magent
    Justin, 18:49. Part of re's introduction.
  • ☐
    re_model in the vault: an openrouter/ id (Anthropic on the subscription is billed as extra usage through Pi)
    decision · justin
  • ☐
    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
    pr · magent
  • ☐
    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 (21)
Retrieved from "https://interfaces3.hunter.cryptograss.live/index.php?title=Cryptograss:Moods/emergence/todo&oldid=9757"