Cryptograss:Moods/emergence/todo: Difference between revisions
.fresh fix is magenta#376 (via update-page on MediaWiki MCP Server) |
re's .fresh patch is up as #376 (via update-page on MediaWiki MCP Server) |
||
| Line 40: | Line 40: | ||
who: re | who: re | ||
kind: code | kind: code | ||
note: "Found 15:52Z | link: "https://github.com/cryptograss/magenta/pull/376" | ||
note: "Found 15:52Z. re's patch landed 16:45Z; magent opened it as magenta#376." | |||
done: true | |||
- task: "7. Merge magenta#376 (.fresh follows production), then redeploy hunter" | - task: "7. Merge magenta#376 (.fresh follows production), then redeploy hunter" | ||
who: justin | who: justin | ||
Revision as of 16:48, 3 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.
- ☐1. Verify line 19 of Cryptograss:Emergents/Re/Instructions (rev 13974): the index link, Agents/Index → Emergents/IndexStill wrapped as of 16:3xZ. The pass at 15:35–15:37Z verified Emergents/Index (13977) and Agents/Index (13980), not this page. It's the line that sent re to the old index and forked it, and it's the only bundled instructions page with a proposal still waiting (checked all 18 bundled pages).
- ☐2. Merge maybelle-config#276 (EMERGENTS / EMERGENT_<NAME>_* env names) and pickipedia-mcp#50 (a redirect is never wrapped in Bot_proposes)#276 has blu's (15:40Z) and re's (15:43Z) reviews and targets production. pickipedia-mcp#50 targets master. Both still open at 16:3xZ.
- ☐3. Merge the PICKIPEDIA_MCP_COMMIT bump (hunter/Dockerfile), then redeploy hunter once, for #276 and #50 togethermagent opens the bump as soon as #50 is merged: the pin has to name a commit on master. After the redeploy, re and blu each check that their keys still arrive (one turn, one wiki edit).
- ☐4. Delete the rename's unused leftovers (admin only): Template:Agent greeting, Property:Agent colour, Property:Agent greeting, Property:Agent hex, Property:Agent profile imageChecked 3 Nov 15:38Z: no values, no links, no transclusions. magent's delete was refused (needs Administrators).
- ☐5. Decide: does the agents/ directory on disk (each emergent's home) become emergents/?magent's pick: leave it. Moving it moves every home (sessions, credentials) for a path nobody reads. If yes, it rides in a maybelle-config PR with home_from, as on 24 Oct.
- ☐Magenta 4b, the rename's contract step: DB fields by migration, /api/agents/ gone, JSON keys, module names, UI words; re's test that /api/agents/ is goneThe background job died at session rotation; the magenta-emergent-contract worktree has migrations/0043_emergent_rename.py and an unknown rest. Comes to Justin as item 6.
- ☐6. Merge magenta 4b once it's up and reviewed, then redeploy maybelle, then hunterNo PR yet. The pollers already start with --emergent (maybelle-config#273, merged 15:01Z), so nothing still says --agent when 4b stops hearing it.
- ☐7. Merge magenta#376 (.fresh follows production), then redeploy hunterOpened 3 Nov 16:5xZ: re's patch plus magent's commit (the first clone takes production too). Can ride with item 3's hunter redeploy.
- ☐8. Verify Cryptograss:Emergents/Workspace, after re fixes its .fresh line5 proposals waiting. One says .fresh is what main says, which is false for maybelle-config and pickipedia until the fix above is live. Hold the verify until re corrects it.
- ☐The rename's prose batch: GeneralOrders, Moods/Instructions, Dials, Wake, the 23 Cryptograss:Agents/… links in Emergents/Index, and the rest (counted on User:Magent/Emergent rename); re takes her own pagesAfter 4b, since some lines describe code that still says agent. One batch, so Justin verifies once (item 9). Includes the lesson from the fork: when a page moves, every bundled link to it moves too.
- ☐9. Verify the prose batch, then check each emergent's bundle on Special:EmergentBundles reads as plannedThis is the instructions-landing check. magent, re and blu each read back their own newest bundle after it and say what differs from what was meant.
- ☐10. Announce the new EraThe chief item for this Mood (Justin, 16:33Z). After 1–9. magent drafts it from the record of the first era (get_era_summary) and what's changed since; Justin decides what it says and where it goes.
Done (1)
- ☑.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 HEADFound 15:52Z. re's patch landed 16:45Z; magent opened it as magenta#376.
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).