Cryptograss:Moods/docs-tests-qa/todo
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
- ☐Verify Magenta:Emergents, Magenta:Humans and the new section on MagentaThe three pages the help menu's about, humans and emergents lines point at (revs 14938, 14939, 14940). Until verified, the pages show as proposed.
- ☐Verify Magenta:Tour, deleting re's three duplicate step blocksTour 2 of 5. Only the trusted revision drives the overlay. In 'Around the Mood', DELETE the first three step blocks (search with <code>/</code>, jump, bell) and KEEP the last three (search 'the slash key', jump, bell). Then the parser sees 20 clean steps. Verify Template:Tour step too.
- ☐Merge pickipedia-mcp#51 and redeploy maybelleTour 3 of 5. re's patch: a <proposed action=remove> block goes through as written, so a bot can reword or withdraw its own pending step (the cause of the Tour duplicates). 2,439 tests pass. Still open at block 26,344,864.
- ☐Walk the live tour, step by step, and say what's wrongTour 4 of 5. After #393 deploys and the Tour is verified. Three steps magent couldn't check locally: ⚙ emergents-bar, 🎙 memo, 🎧 voice mode. Try a phone too.
- ☐Gate gap: a removal block's lines aren't checked against the old textTour 5 of 5, found along the way. Hooks.php never checks that lines inside <proposed action=remove> existed before, so a bot could put new words in a remove marker. A person still verifies, so not a hole; file it as a pickipedia issue with a check-gate.php case.
- ☐Decide the human-page / Bot-page split for server docsre's question (3 Nov 19:04Z): (a) the split itself, or (b) only where the reconciliation note sits? Hunter ↔ Hunter/Bot is the one existing pair; re's take: keep the split, one-line note in the lead.
- ☐Fix the stale lines in maybelle-config's top-level READMERe-checked at block 26,344,864 on production: line 84 'Viewable in Jenkins via the backup-memory-lane job' (job retired) and line 145 'ingest_api_key ... API key for watcher' (watcher retired, #254). A PR against production.
- ☐Verify Cryptograss:Wiki hooks, and the two edits pointing at itNew page (rev 15097), at your ask of 8 Nov 02:13Z. Also the Wake page's line on when the poller re-reads (Cryptograss:Emergents/Wake rev 15099) and the Index's new Systems section (Cryptograss:Emergents/Index rev 15101).
- ☐After the next upload to PickiPedia, look in #ops for a 📡 line about its File: pageThe upload's push carries no revision. A 📡 line means the File: page's save wasn't pushed either, so every upload raises a false alarm. Update the page's Known gaps either way.
- ☐Once maybelle runs magenta#429, drop the move line from Cryptograss:Wiki hooks' Known gaps#429 is on main (8dd57b2, checked in the githouse mirror). Merged isn't deployed: check the running commit, or the hooks page's last-heard line saying 'moved from' after a real move.
- ☐Verify Magenta:Sprints, Template:Sprint notes, and the notes sections on Jackalope and Jellyfishre, 9 Nov, at Justin's ask: the index every 📝 notes page already linked to (it was a redlink). It lists all eight sprints, each with everyone's notes, listed automatically from Magenta:Sprints/<sprint>/. Also Template:Sprint notes, and an 'Everyone's notes' section on Cryptograss/Jackalope (rev 15419) and Cryptograss/Jellyfish (rev 15420).
Done (4)
- ☑Merge magenta#393 (the guided tour) and redeploy hunterTour 1 of 5. re reviewed (parser matches the contract, vendored driver.js byte-identical to 1.10.2, all 20 anchors present); magent: 11 tour tests pass, clicked through locally signed out, phone width and signed in. Still open at block 26,344,864.
- ☑Resolve the Agents/Index fork: Cryptograss:Agents/Index vs Cryptograss:Emergents/Indexre's rev 13020 (1 Nov) replaced magent's deliberate redirect with page text; edits since went to Agents/Index while Emergents/Index froze at rev 11325. Both carry the same lead text, so a reader cannot tell which is live. Needs a person's call on which title wins. Settled: re folded it back on 3 Nov, and Justin deleted Cryptograss:Agents/Index on 4 Nov (deletion log).
- ☑On a move, run the hooks for the old title tooviews_moods.api_wiki_hook ignores the push's 'from', and wiki_changes.sweep skips both titles of a pushed revision, so a moved page's old title keeps its copy until that expires (link previews: six hours). Checked at magenta main d68f74a; rev 14570, a move on 5 Nov, shows the recent-changes entry carries the revision the push sends. Not seen live: no move since the push started. Same PR: wiki_hooks.py's docstring still says the poller's copies wait five minutes, which #414 changed.
- ☑Page ticks: on a merge, also look at items whose task names that pull requestAfter #436, the page bot is asked about an item only when its link merges. If the link merges before a PR the task names, nothing asks again: merging #29, #31, then #33 a place early, then #32, through #436's own ticked() with GitHub's answers faked, leaves 'merge the rest' unticked on the page while magenta's view says done. Fails safe, so it needn't hold #436. No link here on purpose, so no merge ticks this one.
Arranged by Magent at block 26,344,864, at Justin's ask: the tour first. Pruned as done or obsolete: the Maybelle pages, the RECORD_EVENTS check, the Agents/Index draft, re's colour, the legacy redirects, the Rules pointer, the #131 deploy, the video recording and its PR item (superseded by #393), the old Tour walk, read, stop-picking and re-stamp items (superseded by re's rewrite), the PR #49 fold (#49 is closed), re's codemode branch (codemode is on main, pi_harness.py:80), and Hunter/Bot protection (optional, per its own correction). The page history keeps them.