Cryptograss:Moods/ramp/todo
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
- ☐Review the reworked maybelle-config#250 (githouse on maybelle, mirror on hunter; your ten points of 2 Nov folded in)Reworked 6 Nov (e37e549). Read hardest: the keys relay and pushers.json (your point 1), fetch-only for hunter's mirror key (2), the bind assertion (5), and the containers' core.sshCommand per clone.
- ☐Confirm jenkins_github_ssh_key can push to the org's repos (githouse forwards pushes to GitHub with it); then merge #250 and redeploy maybelle, then hunterAfter re's review. If the key is read-only, fetching works and forwarding fails into githouse.log; pushes then stay on maybelle until a key that can push replaces it.
- ☐Merge magenta#408 (PR cards look at GitHub hourly), then redeploy maybelleThe likely cause of the 31 Oct starvation: the cards' ten-minute look spent about 45 of the 60 unsigned calls an hour. With this, #246 (a token of memory-lane's own) is optional; watches (below) take merge asks off GitHub's API altogether.
- ☐maybelle-config#246 (read-only GitHub token for memory-lane): merge or closeOptional once #408 is in. Justin, 6 Nov: no appetite for another token. Close it unless the asks starve again.
- ☐Verify Cryptograss:Moods/ramp/Plan, the settled design in one placeJustin, 6 Nov: 'the plan page looks great'. Still a proposal until verified.
- ☐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 one6 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 copies6 Nov: squash and rebase still allowed on all six. githouse's merged-name detection needs merge commits.
- ☐Rulesets on the branches that deploy (PR required, no force-push, no deletion; admins bypass)6 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, now reading /api/branches/ from maybelle's githouse copy); merge with or after #250Reviewed 1 Nov; changed 6 Nov: the list comes from memory-lane's /api/branches/ (views_settings.api_branches), not a Caddy host on hunter.
- ☐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. 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.
- ☐Deploys clone from githouse's copy on maybelle instead of GitHub (Jenkinsfiles, deploy scripts)re's point 9: its own PR, after githouse is live and has run a few days.
- ☐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.