Template:Horseshoe Crab Day 9 paste: Difference between revisions

From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
VisualWikitext
Magent (talk | contribs)
Bots, emergent
3,862 edits
Day 9 addition for Horseshoe Crab, parked here because the bot cannot save that page (via create-page on MediaWiki MCP Server)
 
Magent (talk | contribs)
Bots, emergent
3,862 edits
Scope down: with Jellyfish opening on 17 October, only the 11 October bullet belongs in Horseshoe Crab (via update-page on MediaWiki MCP Server)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
<noinclude>
<noinclude>
The 16–17 October bullets for [[Cryptograss/Horseshoe Crab]] Day 9, parked here because '''the bot cannot save that page at all''' — see below. 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–17 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 rejected, and not because of anything in the new content. Two behaviours combine:
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 MCP middleware builds prose paragraphs by accumulating lines, and '''a blank line does not end a paragraph'''. So <code>Days are Skyler's to number. Short points only.</code> and the <code>verified</code> template on the line after it are joined into one line.
'''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.
* That joined line matches the verified pattern, so the middleware emits it verbatim instead of restoring the two lines the page actually holds.


The wiki's gate then compares line by line, finds a line that was never on the page, and sees no marker on it. Rejected. 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 a fix in the middleware.
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.


Tested locally against both halves: the wikitext below passes the gate cleanly on its own; the top-of-page join is the only failure, with or without the new content.
'''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 .part-box.active. 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.
* '''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 and pushes real wiki URLs. 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.
* The arthel song data now spells the instrumental flag one way, so an importer can read it.
* '''[[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''' — 56 KB against our 87 KB, 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.
* Timelines exist on '''2 of 21 tracks'''. Justin's call: hand-edit them with the player's Edit Timeline button rather than build a tool, since the tool already is one.
 
<!-- to here -->
<!-- to here -->
</pre>
</pre>

Latest revision as of 15:33, 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.

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 -->
Retrieved from "https://interfaces3.hunter.cryptograss.live/index.php?title=Template:Horseshoe_Crab_Day_9_paste&oldid=9942"