Cryptograss:Moods/ramp/todo
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
- ☐Merge maybelle-config#246 (read-only GitHub token for memory-lane), then redeploy maybelleStill open, mergeable (5 Nov). The webhook keeps PR cards fresh without it (magenta/402's card updated within minutes of its merge), but the ten-minute poll, to-do ticks, merge asks and status share 60 unsigned calls an hour and ran out on 31 Oct.
- ☐Verify Cryptograss:Moods/ramp/Plan, the settled design in one placeWritten by magent 5 Nov from the record. Read it as the plan; say what's wrong.
- ☐Say go on githouse-on-maybelle, then magent reworks #250 (re's points 2, 4 and 5 as requirements)#250 as opened puts it on hunter, and since 5 Nov it conflicts with production in three files (the Mood containers folding into /moods). Don't merge it; the rework supersedes it. Plan, section 3.
- ☐Set each repo's GitHub default branch to the branch that deploys: production for maybelle-config, pickipedia, arthel; main for magenta. blue-railroad-import: pick one5 Nov: all six still default to main (pickipedia-mcp master). Then delete magenta's production branch (a634f16, Nov 2025) and #376's per-repo check can go. Plan, section 5.
- ☐Merge commits only (squash and rebase off), merge queue off, on every repo githouse copies5 Nov: squash and rebase still allowed on maybelle-config, pickipedia, arthel, magenta, blue-railroad-import, pickipedia-mcp. githouse's merged-name detection needs merge commits.
- ☐Rulesets on the branches that deploy (PR required, no force-push, no deletion; admins bypass)5 Nov: none on any of the six. magent then tries a push to production that must fail, and reports. Private repos can't take rulesets on the free plan; githouse's hook covers those.
- ☐Review magenta#333 (repo:branch autocomplete); merge after githouse is liveReviewed by re 1 Nov, mergeable. Its branches.json URL moves with githouse to maybelle (re's point 7); magent updates it in the rework.
- ☐Build the ramp view on magenta: open PRs across our repos, last five merged, who and where, last two mentions, sorted by last push or last mention, temperatureJustin's memo, 30 Oct; the records half (cards) is live. After #246, so the view isn't starved of GitHub calls. Plan, section 2.
- ☐Watches: merge and deploy asks resolved by commit ancestry against githouse's copy; deploys stamp the commit they deployedAfter githouse is live. Plan, section 4. Deploy stamping is the prerequisite nothing does yet.
- ☐Decide how emergents do git: the patch route, own GitHub accounts, or githousegithouse (above) is magent's and re's answer; this closes when it's live and re pushes a branch.
- ☐Jenkins audit, re's open items: a policy on silent skips (pickipedia node/lua checks), pickipedia's chain-data warning that deploys stale silently, NVM/pnpm fetched from the network in every pipelineFrom re's test map, 30 Oct. The mtime guard (#244) and the alarms (#402, #275) are done.