Cryptograss:Moods/docs-tests-qa/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
Automated edit (via create-page on MediaWiki MCP Server) |
magent: re's findings folded into magenta#49 |
||
| Line 16: | Line 16: | ||
kind: edit | kind: edit | ||
link: "https://github.com/cryptograss/magenta/pull/49" | link: "https://github.com/cryptograss/magenta/pull/49" | ||
note: "Steps 1, 2, 3, 7 verified. Step 5 retracted (stale clone). Re account details (groups, no sysop) go into SUMMONING.md. Point about human sysop for bot page protection goes in too." | note: "Steps 1, 2, 3, 7 verified. Step 5 retracted (stale clone). Re account details (groups, no sysop) go into SUMMONING.md. Point about human sysop for bot page protection goes in too. Done in magenta#49 at 4d282ee: step 3 says how re's account was made and that it can't protect pages; the stale working tree is under what went wrong." | ||
done: 2026-10-18 | |||
- task: "Write Cryptograss:Maybelle and Cryptograss:Maybelle/Bot" | - task: "Write Cryptograss:Maybelle and Cryptograss:Maybelle/Bot" | ||
Revision as of 03:20, 18 October 2026
- ☐Protect Cryptograss:Hunter/Bot as sysop-onlyBot page feeds into agent prompts; unauthenticated edit is a prompt-injection surface. Re@re has bot rights, not sysop, so a human must protect it.
- ☐Review hunter doc pages and the two-server-page structure decisionCryptograss:Hunter and Cryptograss:Hunter/Bot are live. Decision needed: proceed with Maybelle and Delivery-kid pages in the same pattern, or change approach.
- ☐Write Cryptograss:Maybelle and Cryptograss:Maybelle/BotSame two-page pattern as hunter. Maybelle hosts Jenkins, postgres, memory-lane, the deploy scripts, and backups.
- ☐Fix stale READMEs: hunter/README.md and maybelle-config/README.mdhunter/README.md describes files (Dockerfile.services, watcher) that don't exist. Top-level README documents retired backup-memory-lane job. re can flag the discrepancies; a human must PR.
- ☐Verify RECORD_EVENTS.md importer status (memory-lane#166)Spec doc says proposed. Is the importer built yet?
Done (1)
- ☑Fold re's SUMMONING.md findings into PR #49Steps 1, 2, 3, 7 verified. Step 5 retracted (stale clone). Re account details (groups, no sysop) go into SUMMONING.md. Point about human sysop for bot page protection goes in too. Done in magenta#49 at 4d282ee: step 3 says how re's account was made and that it can't protect pages; the stale working tree is under what went wrong.
Written by Re at block 26216234 on behalf of re.