Cryptograss:Moods/magenta-interface/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)
#214 rules on the wiki; verify Dials (via update-page on MediaWiki MCP Server)
Magent (talk | contribs)
magent: four items moved here from magent-self, with the work (Justin, 04:38)
Line 2: Line 2:


<todo>
<todo>
- task: "Review and merge pickipedia-mcp#30 (onto upstream v0.19.0, keeping only our bot-edit marking, which now names whoever is signed in); then pull, npm ci, build and restart the stdio server in justin-arthel"
  who: justin
  kind: review
  link: "https://github.com/cryptograss/pickipedia-mcp/pull/30"
  note: "Decided 2026-10-18 04:22 (rebase). Tested: the full suite (2417), and the wiki's own verification gate accepting the pages the built tool produces for eight kinds of edit (a control of unmarked prose refused). Supersedes #28 and #29 (closed). Running it for every agent (re, and magent's Mood containers, now on npx upstream@latest) is a maybelle-config PR after this merges."
- task: "Merge pickipedia#147 (an Agent: namespace: everyone reads it; each agent edits only its own pages, sysops any), deploy the wiki; at Special:UserRights add Magent and Re to the new agent group; at Special:BotPasswords, as each account, add the agent-edit grant; then merge pickipedia-mcp#30, which carries the Agent: exemption (see the item above)"
  who: justin
  kind: deploy
  link: "https://github.com/cryptograss/pickipedia/pull/147"
  note: "Where the notes go (Justin, 2026-10-18 03:29-03:37: on the wiki, everything public). Protected to write, not to read: an agent reads its notes as its own memory. Also where re's bot-facing docs can live, instead of protecting pages one at a time. pickipedia-mcp: https://github.com/cryptograss/pickipedia-mcp/pull/28"
- task: "Say when memory-lane merges can freeze, for merging memory-lane into magenta (under memory-lane/, history kept)"
  who: justin
  kind: decision
  note: "Agreed 2026-10-18 03:24-03:26. The freeze runs from the copy until maybelle and hunter deploy from magenta; a memory-lane merge in that window would be lost. memory-lane#201, #203 and #204 (magenta-interface) are easiest merged or held first."
- task: "Review the rules files: AGENTS.md (what every agent keeps), agents/README.md (where each layer lives), agents/SUMMONING.md (how an agent is summoned today)"
  who: justin
  kind: review
  link: "https://github.com/cryptograss/magenta/pull/49"
  note: "re is checking SUMMONING.md against the code first (handed over in docs-tests-qa, 2026-10-17); magent folds its findings in. Nothing reads AGENTS.md until the next maybelle-config PR wires it in."
- task: "Merge memory-lane#210 (who's in a picture: 👤 Who's in it? in the lightbox; whose a face looks like offered with a ?, named only when a person says ✓ or types who; names go to PickiPedia as {{Depicts}})"
- task: "Merge memory-lane#210 (who's in a picture: 👤 Who's in it? in the lightbox; whose a face looks like offered with a ?, named only when a person says ✓ or types who; names go to PickiPedia as {{Depicts}})"
   who: justin
   who: justin

Revision as of 04:40, 18 October 2026

What the people in #magenta-interface have to do. magenta shows this list beside the Mood (memory-lane services/todo.py). Edit the YAML below: - task: ..., with who, kind, link, note and done as useful. Agents add what they leave someone to do, and mark what's done. Put a task in quotes if it has ": " or " #" in it (YAML reads those as a key and a comment); `backticks` make code.

Done (135)