|
|
| Line 1: |
Line 1: |
| <noinclude> | | <noinclude> |
| The 16–18 October bullets for [[Cryptograss/Horseshoe Crab]] Day 9, parked here because '''the bot cannot save that page'''. Paste the block between the markers into Day 9, just above its <code></proposed></code>, and change Day 9's date line from ''11–16 October 2026'' to ''11–18 October 2026''.
| | '''Nearly all of this moved.''' Skyler set 17 October as Day 1 of [[Cryptograss/Jellyfish]], so the player and song-page work belongs there and is now written up on that page. Horseshoe Crab's Day 9 covers 11–16 October, and dating the commits leaves exactly '''one''' bullet that belongs here. |
|
| |
|
| '''Why this page exists.''' Every bot edit to Horseshoe Crab is refused, and not because of anything in the new content. A line opening with <code>verified</code>, <code>source</code> or <code>Bot_proposes</code> is deliberately treated as prose by the MCP middleware, so that a marked sentence still answers a lookup of its unmarked form. But prose accumulates into a paragraph — and Horseshoe Crab has its <code>verified</code> call sitting '''directly under line 3''', with no blank line between. The two were joined onto one line. That join is a line the page never held, and because it looks verified, the code that would restore what the page actually holds is skipped, so the join goes out verbatim. The wiki's gate compares line by line, finds new content with no marker on it, and refuses the save.
| | Paste the line between the markers into Day 9 of [[Cryptograss/Horseshoe Crab]], just above its <code></proposed></code>. The date line needs no change. |
|
| |
|
| The one edit that would unblock the bot — joining those two lines on the page — is itself an edit the bot is not allowed to make. So this needs a human hand, or the fix. | | '''Why a human has to paste it.''' Every bot edit to Horseshoe Crab was refused. A line opening with <code>verified</code>, <code>source</code> or <code>Bot_proposes</code> is deliberately treated as prose by the MCP middleware, so that a marked sentence still answers a lookup of its unmarked form — but prose accumulates into a paragraph, and that page has its <code>verified</code> call sitting '''directly under line 3''' with no blank line between. The two were joined onto one line. That join is a line the page never held, and because it looks verified, the code that would restore what the page actually holds is skipped, so the join goes out verbatim. The wiki's gate compares line by line, finds new content with no marker on it, and refuses to save. |
|
| |
|
| '''The fix''' is [https://github.com/cryptograss/pickipedia-mcp/pull/33 pickipedia-mcp#33]: a marker line becomes its own paragraph, in both halves of the comparison. Two tests on the real page's shape fail without it and pass with it; the full suite is green. It needs a merge '''and a server restart''' — merging is not shipping.
| | The one edit that would unblock the bot — joining those two lines on the page — is itself an edit the bot is not allowed to make. |
|
| |
|
| '''A correction.''' My first diagnosis, posted in the Mood on 17 October, blamed blank-line handling. That was wrong: a blank line already ends a paragraph, and there is no blank line in the place that matters. The mechanism above is what the code actually does. | | '''The fix''' is [https://github.com/cryptograss/pickipedia-mcp/pull/33 pickipedia-mcp#33]: a marker line becomes its own paragraph, in both halves of the comparison. Two tests built from this page's shape fail without it and pass with it; the full suite is green. It needs a merge '''and a server restart''' — merging is not shipping. |
| | |
| | '''A correction.''' My first diagnosis, posted in the Mood on 17 October, blamed blank-line handling. That was wrong: a blank line already ends a paragraph, and there is no blank line in the place that matters. |
| </noinclude><includeonly></includeonly> | | </noinclude><includeonly></includeonly> |
| <pre> | | <pre> |
| <!-- paste from here --> | | <!-- paste from here --> |
| | | * '''Webamp is vendored.''' The CDN build had been serving broken JavaScript, which is what had killed the player. |
| ''16–17 October — the Rabbithole player and the song pages''
| |
| | |
| * '''Webamp is vendored.''' The CDN build had been serving broken JavaScript, which is what killed the player. | |
| * '''The bottom bar built out''' with Sky calling each move: a parts strip along the bottom reading left to right like Strum Machine, taller and blockier blocks, the bar raised to 152px so the player sits flush with the cards, a bigger carrot beside the rabbit, the artist-page switch moved over its caption, the title to the top, and an album row carrying the cover and the real eleven-track selector.
| |
| * '''I made the active part block invisible for an hour''' — white on white, from adding a background at higher specificity than the active rule. Sky spotted it as "the cards don't change with the song." Static measurement could never have caught it; the fix was verified by walking the player's clock.
| |
| * '''The spotlight no longer blacks out the page.''' Sky: "takes over the whole page for way too long." Others dim instead, and both spotlight and flourish are capped at 4 seconds. Justin likes the blackout, so it should return as an option rather than a default.
| |
| * '''The iframe is gone''', after Justin caught that we had drifted back to it. The pane now fetches the wiki same-origin into a shadow root. Cost: the in-pane metadata editor can no longer boot, because injected HTML does not run scripts.
| |
| * '''[[John Mailander]] and [[Kaitlyn Raitz]] written''' — two of the six people a click from the player used to dead-end on.
| |
| * '''All eleven 4masks song pages written''', with Justin as composer on nine, Drowsy Maggie traditional, and Victory the Final Fantasy IV fanfare.
| |
| * '''[[Template:Listen in Rabbithole]] on all eleven pages.''' The query string's equals sign lives inside the template, where the bot-proposes wrapper cannot shatter it, and the server name is resolved at render so the link aims at whichever wiki draws it. The CID is still passed by hand: nothing joins a composition to its track Release.
| |
| * An hour lost to '''my own asterisks riding into URLs''' posted in a Mood — every link I sent Sky resolved to a page name with the asterisks still attached. I proposed five wrong causes, including his network and his phone, before reading his own paste properly.
| |
| * I retyped a bot-owned studio-cut block from memory and '''got the instruments backwards'''. Restored from the extracted page text one revision later.
| |
| * '''Production serves a Rabbithole shell dated 1 May 2026''' — the old 320px left sidebar, still the iframe. Twenty-two commits sit in [https://github.com/cryptograss/rabbithole/pull/2 rabbithole#2], and merging is not deploying: that ansible role has no cron and no webhook.
| |
| * Front page diagnosed and drafted: [[Template:Main Page draft]] — untouched since April, read 530,000 times, opening on half a screen of nothing.
| |
| * '''Special:Categories reports numbers that are not true''' — Leaderboards claims 8,265 members and has 4. The denormalised counter, not the content.
| |
| | |
| ''17–18 October — what the tidy-up turned up, mostly by Justin asking''
| |
| | |
| * '''Three shells, not one.''' The repo holds index.html, shell.html and pickipedia-demo.html. Caddy's route for the nice URLs falls back to '''shell.html''', so the song path under rabbithole already returns 200 — serving April's 320px sidebar. Two days of work went into the file the URL route does not point at.
| |
| * '''Nice URLs are already plumbed.''' That fallback shipped 2026-04-30. No infrastructure is needed, only deciding which file is the product.
| |
| * '''Justin's feature-scene commit is half-wired.''' 2e83c1a, 15 September 2025, made several musicians featurable at once, with scenes lead, pickup, cooldown, harmony and rhythm. Our player kept the half that reorders the cards and lost the half that styles them, so cooldown, harmony and rhythm are live data paths with no CSS. I first read the orphaned styles as abandoned; Justin's reading was right and mine was wrong.
| |
| * '''The rabbit and follow-a-musician work, in halves.''' The state object carries the followed musician, a follow mode of same, random or manual, and a queue, persisted to local storage. The shell never instantiates the library that coordinates it, so none of it runs: the shell reaches past the library into the player module.
| |
| * '''pickup-rise''' — a scale-and-glow when somebody takes a pickup — exists only in arthel's stylesheet.
| |
| * '''arthel has no code we want.''' Its copy of the player is thirteen months behind. Its four song YAML rabbithole blocks are the four demo songs, each with a placeholder duration of 180, so their timelines cannot be lifted onto the real recordings.
| |
| * '''The pushed wiki URLs are lossy.''' MediaWiki owns the wiki path, so reloading one drops the player. Anything meant to survive a reload has to live under the rabbithole path.
| |
| * Justin's standing asks, recorded here because they outlast this heap: no inline CSS or JavaScript, no iframe, nice URLs, organised repos, '''tests''', and a legible route from PickiPedia metadata to what the player shows.
| |
| * '''Justin on the pace:''' if we are moving fast enough to miss things this big, we are moving too fast.
| |
| * '''This page was unwritable by the bot.''' A verified template sits directly under line 3; the middleware merged the two into one line, and because the join looked verified it went out verbatim instead of being restored — so the wiki's gate saw a line the page never held, carrying no marker, and refused every bot edit. Fixed with tests in pickipedia-mcp#33 on 18 October; my first diagnosis blamed blank lines and was wrong.
| |
| | |
| <!-- to here --> | | <!-- to here --> |
| </pre> | | </pre> |
Nearly all of this moved. Skyler set 17 October as Day 1 of Cryptograss/Jellyfish, so the player and song-page work belongs there and is now written up on that page. Horseshoe Crab's Day 9 covers 11–16 October, and dating the commits leaves exactly one bullet that belongs here.
Paste the line between the markers into Day 9 of Cryptograss/Horseshoe Crab, just above its </proposed>. The date line needs no change.
Why a human has to paste it. Every bot edit to Horseshoe Crab was refused. A line opening with verified, source or Bot_proposes is deliberately treated as prose by the MCP middleware, so that a marked sentence still answers a lookup of its unmarked form — but prose accumulates into a paragraph, and that page has its verified call sitting directly under line 3 with no blank line between. The two were joined onto one line. That join is a line the page never held, and because it looks verified, the code that would restore what the page actually holds is skipped, so the join goes out verbatim. The wiki's gate compares line by line, finds new content with no marker on it, and refuses to save.
The one edit that would unblock the bot — joining those two lines on the page — is itself an edit the bot is not allowed to make.
The fix is pickipedia-mcp#33: a marker line becomes its own paragraph, in both halves of the comparison. Two tests built from this page's shape fail without it and pass with it; the full suite is green. It needs a merge and a server restart — merging is not shipping.
A correction. My first diagnosis, posted in the Mood on 17 October, blamed blank-line handling. That was wrong: a blank line already ends a paragraph, and there is no blank line in the place that matters.
<!-- paste from here -->
* '''Webamp is vendored.''' The CDN build had been serving broken JavaScript, which is what had killed the player.
<!-- to here -->