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
Magent (talk | contribs)
Steps 4-5 done; step 6: maybelle-config#189 (re's key mangled on maybelle) and memory-lane#186 (poller logs and retries), then @re (via update-page on MediaWiki MCP Server)
Magent (talk | contribs)
Step 6: per-agent runner key lines (memory-lane#187 + maybelle-config#190) replace #189 (via update-page on MediaWiki MCP Server)
Line 40: Line 40:
   kind: deploy
   kind: deploy
   link: "https://github.com/cryptograss/maybelle-config/pull/185"
   link: "https://github.com/cryptograss/maybelle-config/pull/185"
   note: "Done 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 MOOD_RUNNER_KEYS line ended in an inline endif, Ansible's trim_blocks ate its newline, and the next comment line became part of re's key (maybelle 112 characters, hunter 45). Step 6 fixes it."
   note: "Done 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)."
   done: 2026-10-15
   done: 2026-10-15
- task: "Step 6: merge maybelle-config#189 (re's key on maybelle) and memory-lane#186 (re's poller logs and retries a failed model report); deploy maybelle, then hunter (no --rebuild needed); ping magent, then @re in docs-tests-qa"
- task: "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-qa"
   who: justin
   who: justin
   kind: deploy
   kind: deploy
   link: "https://github.com/cryptograss/maybelle-config/pull/189"
   link: "https://github.com/cryptograss/maybelle-config/pull/190"
   note: "#189 alone lets re's wakes post. #186 + the hunter deploy restarts re's poller, so it reports its models (the menu) now, not in a day; it restarts magent's poller too. Checked: the real .env task rendered in ansible-core gives 112 on production, 45 with #189."
   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."
- task: "After re is up: MOOD_RUNNER_KEYS built in one loop over the agents (<agent>_runner_key), not one inline if each; drop 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
   kind: pr
   kind: pr

Revision as of 16:40, 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.

Done (16)