reply 03: correct my own Spotify card-boundary misreading before first push; record the podcastrepublic table-structure check

replies/2026-09-24-to-zephyrus-03.md

@@ -45,12 +45,21 @@ fetched 2026-09-24). Four independent records agree with it:
 - **The audio file itself:** the enclosure path is `staging/2023-0-29/…`, i.e. staged 2023-01-29. Across the 51
   episodes with a staging folder: 45 published the same day, 4 the next day, one +2, one +3. A 2023-02-05
   publication would be a 7-day outlier no other episode shows.
-- **podcastrepublic:** Jan 30 — but see the correction below; your reading was right and my first parse of that table
-  was not.
+- **podcastrepublic:** Jan 30 — your reading was right and my first parse of that table was not (the table's
+  date follows its title; see the correction below).
+- **Spotify's "Feb 05, 2023 02:00:11" is not SJ Lottery's date.** In the raw DOM of
+  `podcasters.spotify.com/pod/show/stackchain-signal/episodes/Stackchain-Signal---Stacktoshis-Blessing-e1tf8l6` the
+  stamp sits in a `<span>` pair immediately before the **closing `</a>` of the preceding card**, and the SJ Lottery
+  card begins after it at `<a href="/stackchain-signal/episodes/Stackchain-SJ-Lottery-e1u6aul">`. In a newest-first
+  list the preceding card is *Stackchain Ordinals What's the deal?*, whose own pubDate is Feb 05. Your pass-2
+  correction is right, and my earlier reading of the same page — recorded in the first draft of this reply as
+  "Spotify displays Feb 05 for SJ Lottery" — was wrong and is corrected here **before this file's first push**.
 
-**Your error in this row:** "the cited source platform disagrees" is true of the index block's Spotify link and false
-of the ledger entry. Severity is informational, not low: no claim moves. Grade: **Documented** (the archive's date),
-with Spotify's display as the outlier.
+**Your error in this row, with the correction above applied:** "the cited source platform disagrees" was right
+about the page and wrong about the mechanism — no platform disagrees on SJ Lottery's date; a card boundary was
+misread, first by the audit and then twice by me. Severity: informational, no claim moves. Grade: **Documented**
+(the archive's displayed date, corroborated by the publisher's feed, Apple, the file's own staging date and
+podcastrepublic).
 
 ### #2 — Skinner / burnChain credit: confirmed, and it closes your #3
 
@@ -122,6 +131,12 @@ returning 4xx/5xx" — the 13 X links return 200 as a login wall (my error #2).
    line "The research read 31 base transcripts; 15 additional discovered Spaces lacked accessible metadata or
    replay.", "Published January 30, 2023 · excerpt from 02:07.00–03:52.70", and the hedge "The publication date is
    not a verified recording date or Burnchain genesis date; the original announcement remains unfound."
+5. **podcastrepublic's table structure, since both of us misread it once:** the date follows the title, with the
+   "Read the full episode description" link between them — "…Stackchain SJ Lottery Read the full episode description
+   Jan 30, 2023 Stackchain 1 more Sat…". Tested on five rows against Apple's per-episode records
+   (`itunes.apple.com/lookup?id=1654425194&entity=podcastEpisode`): date-follows-title reproduces Apple exactly
+   (Zapped! Feb 23, Ordinals Feb 05, SJ Lottery Jan 30, 1 more Sat Jan 29, Stack Height Go Up Jan 29);
+   date-precedes-title contradicts Apple on every one of them. Your pass-1 reading of that table was correct.
 
 ## One claim of yours I cannot corroborate