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
#387 is up; Justin's order (via update-page on MediaWiki MCP Server) |
m Merged, says GitHub: https://github.com/cryptograss/magenta/pull/387 |
||
| Line 69: | Line 69: | ||
link: "https://github.com/cryptograss/magenta/pull/387" | 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." | 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." | ||
done: true | |||
- 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:25, 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.
- ☐8. Verify Cryptograss:Emergents/Workspace, after re fixes its .fresh line5 proposals waiting. One says .fresh is what main says; since #376 went live (01:08Z) it's what production says where a repo has one. re corrects that line first, then you verify.
- ☐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 pagesUnblocked: 4b is live (4 Nov 01:08Z). 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.
- ☐Delete the 27 old redirects (Cryptograss:Agents, Cryptograss:Agents/…, Template:Agent, Template:Agent task) once nothing links to themJustin, 17:32Z: crufty in autocomplete. After the prose batch rewrites the links (23 in Emergents/Index alone); magent hands over the list with Special:WhatLinksHere empty for each. Admin only.
- ☐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 (12)
- ☑1. Verify line 19 of Cryptograss:Emergents/Re/Instructions (rev 14024): the index is a map to look things up inReworded at Justin's 17:32Z question (rev 14024): re keeps the index and looks pages up in it; it isn't read whole on waking. Verified by Justin, 17:49Z.
- ☑
- ☑3. Merge maybelle-config#277 (pickipedia-mcp pinned to #50's merge, 1a7156c), then redeploy hunter once, for #276, #277 and magenta#376 together#277 merged 17:49Z; hunter redeployed by 18:16Z (all three emergent containers recreated then). re and blu each check that their keys still arrive (one turn, one wiki edit).
- ☑
- ☑5. Decide: does the agents/ directory on disk (each emergent's home) become emergents/?Keep (Justin, 17:32Z).
- ☑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 gonemagenta#382, opened 3 Nov 22:44Z: 1611 tests pass on Postgres (main: 1606).
- ☑Review magenta#382 (4b): the migration, the dropped /api/agents/ and --agent, and which tests were flippedYour ask from 2 Nov is in it: tests flipped last, in their own commit, and /api/agents/ answers 404. The diff is at /moods/emergence/382.diff (3,211 lines; most of it is the tests).
- ☑6. Merge magenta#382 (4b) and magenta#376 (.fresh follows production), then redeploy maybelle, then hunterMerged and redeployed, 4 Nov 01:08Z. Checked live by magent at 01:09Z: /api/agents/ answers 404, /api/settings/ says emergents, the three pollers run the new code, and .fresh/maybelle-config and .fresh/pickipedia sit on production.
- ☑Merge pickipedia#171 (Special:EmergentBundles asks magenta with ?emergent=), redeploy pickipediaFound by re, 4 Nov 00:31Z. After it's live, magent drops the last ?agent= from magenta's /api/bundles/.
- ☑magenta: drop the ?agent= fallback on /api/bundles/, once pickipedia#171 is livemagenta#387: ?agent= refused with a 400, never read as no filter. 1635 tests pass.
- ☑Redeploy pickipedia (for #171), then merge magenta#387 and redeploy maybelleIn that order: #387 merged first makes Special:EmergentBundles show a 400 when filtered by emergent. The rename's last old name at an edge.
- ☑.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).