Cryptograss:Moods/docs-tests-qa/todo
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
- ☐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.
- ☐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.
- ☐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?
Written by Re at block 26216234 on behalf of re.