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
DrivingThatTrain (talk | contribs)
m Merged, says GitHub: https://github.com/cryptograss/pickipedia/pull/171
Magent (talk | contribs)
#387 is up; Justin's order (via update-page on MediaWiki MCP Server)
Line 61: Line 61:
   who: magent
   who: magent
   kind: code
   kind: code
  link: "https://github.com/cryptograss/magenta/pull/387"
  note: "magenta#387: ?agent= refused with a 400, never read as no filter. 1635 tests pass."
  done: true
- task: "Redeploy pickipedia (for #171), then merge magenta#387 and redeploy maybelle"
  who: justin
  kind: deploy
  link: "https://github.com/cryptograss/magenta/pull/387"
  note: "In that order: #387 merged first makes Special:EmergentBundles show a 400 when filtered by emergent. The rename's last old name at an edge."
- task: ".fresh copies of maybelle-config and pickipedia follow production, not dead main: refresh_fresh checks ls-remote (return code first), fetches production if it's there, else HEAD"
- task: ".fresh copies of maybelle-config and pickipedia follow production, not dead main: refresh_fresh checks ls-remote (return code first), fetches production if it's there, else HEAD"
   who: re
   who: re

Revision as of 01:21, 4 November 2026

What people in the emergence Mood have been left to do. Kept by magent; anyone may tick an item. Done items come off the list when they're done — the page history keeps every one of them. Justin's next steps come first, in the order to do them. The cold start drill and the rest of the least-privilege work live on Cryptograss:Moods/ops/todo; GitHub and version-control items on Cryptograss:Moods/ramp/todo.

The goal (Justin, 3 Nov 16:33Z): finish the agent → emergent refactor, check that each emergent's instructions land as planned, then announce the new Era.

Done (11)

The container plan settled 23–24 Oct (in magent-self, with Justin and re) and reshaped 1 Nov (Cryptograss:Moods as Directories): one emergent-<name> per emergent, holding its home and poller; each Mood a directory under /moods, seen by every container; workbench for people, with each Mood's previews; recovery for emergencies; no personal containers and no shared agency (retired 1 Nov, #263).