Cryptograss:Moods/ramp/todo

• ☐
  Register VersionControl namespace in pickipedia LocalSettings.php (NS 3016/3017, VC alias, subpages, SMW semantic links) and open PR to production

  pr · magent

  3000-3015 are taken. Needs $smwgNamespacesWithSemanticLinks[NS_VERSIONCONTROL] = true or every #ask proof query returns nothing. Redeploy maybelle after merge.
• ☐
  Review magent's two diffs (pickipedia-mcp#43 rework and LocalSettings.php namespace PR) before they open

  review · re
• ☐
  Bump PICKIPEDIA_MCP_COMMIT in maybelle-config (hunter/Dockerfile) and redeploy hunter

  pr · magent

  Waits on merge of the reworked pickipedia-mcp#43. Bumps Dockerfile pin and opens PR to production.
• ☐
  Verify GeneralOrders rev 11789 (or amend with three-key foot block: Deploy, Worked on by, Moods)

  decision · justin

  To make PR details mechanically parseable into SMW properties, footer keys must be discrete lines.
• ☐
  Create SMW properties (Property:Worked on by, Property:Mood, Property:Deploy, Property:Repository, Property:PR number, etc.) and Template:PR

  wiki · magent
• ☐
  Build and run PR sync script (sync_prs.py) to generate VersionControl:PRs/<repo>/<number> cards from GitHub

  code · magent
• ☐
  Run proof #ask queries for PRs worked on by user/emergent and in mood

  test · magent
• ☐
  Review maybelle-config#250 (githouse: canonical clones on hunter, ramp Phase 1)

  review · re
• ☐
  Before deploying #250: a git key per agent who pushes (public in inventory as git_key, private in vault as <name>_git_private_key); optionally githouse_deploy_key; DNS for git.hunter.cryptograss.live if the wildcard doesn't cover it

  decision · justin
• ☐
  Set merge commits as the only merge strategy, merge queue off, on every repo githouse mirrors

  decision · justin

  githouse's merged-name detection relies on merge commits (re and magent, #ramp 31 Oct).
• ☐
  Review magenta#333 (composer autocomplete for repo:branch mergeables), then merge after #250 is live

  review · re
• ☐
  Rulesets on the branches that deploy or are shared, in every repo magent's token can push to (PR required, no force-push, no deletion; admins bypass)

  infra · justin

  Moved from #emergence, 2 Nov (least privilege, step 2). Checked 04:28Z via gh api: magent's token pushes to 16 cryptograss repos; none has a ruleset. Unprotected production: magenta, maybelle-config, pickipedia, blue-railroad-import, arthel (arthel's and Revealer's main are protected). Unprotected default: pickipedia-mcp (master), rabbithole, RambutanMode, blox-office, .github, chartifacts. Private repos (cryptograss-private, happenings, security-and-other-private-things) can't take rulesets on the free plan. memory-lane is archived. magent tests with a push that must fail, once they're on.
• ☐
  Decide how emergents do git: keep the patch route, or give blu and re their own GitHub accounts

  decision · justin

  Moved from #ops, 2 Nov. magent's proposal is in #ops, block 26,288,099. Rulesets first (above). Since maybelle-config#265 deployed (2 Nov), re and blu have no GitHub login at all; blu's code went as patches through magent anyway, and re only read PRs.

Done (1)

• ☑
  Rework pickipedia-mcp#43: VersionControl namespace instead of Cryptograss:PRs carve-out

  pr · magent

  Supersedes the original carve-out (Justin approved VersionControl, 30 Oct 21:25Z). Revert Category/Property from EXEMPT_NAMESPACES, drop the Cryptograss:PRs regex, add 'VersionControl' to EXEMPT_NAMESPACES. re reviews before it opens.