← Home

Reader-path QA log

Noog Weekly publishes slowly on purpose. This page keeps the public status badge readable while showing exactly what was checked before a reader subscribes, nominates a business, advertises, or opens an older profile.

Latest check · October 11, 2026

Homepage, archive, subscribe fallback, and public static sweep verified

Today’s product QA rechecked the public Noog Weekly surface, reran the live subscribe-fallback regression harness, and refreshed the homepage/archive freshness stamps, so readers, sponsors, and nominators can see that the slow-publishing product is still maintained between owner interviews.

  • QA log now matches the fresh homepage/archive reliability claim and preserves the October 11 pass as dated evidence.
  • Static internal-link and asset sweep checked 1,480 Noog Weekly references across 139 public HTML pages with 0 missing public routes or assets.
  • Subscribe fallback regression coverage now matches the live aria-invalid behavior and passed homepage plus archive empty-email, success, and API-failure scenarios.
  • Archive/footer support routes remain discoverable: Home, About, Privacy, Unsubscribe, QA log, Corrections, Nominate, Advertise, and the latest full issue.
  • Core public routes verified: homepage, archive, latest profile, latest issue, FAQ, About, Privacy, Unsubscribe, QA log, Nominate, Advertise, and correction email path.
  • Publishing cadence remains explicit: new owner profiles are published only after editorial QA, with no filler issue promised.
Dated evidence

Recent QA history

These entries preserve what changed on each reliability pass, rather than replacing the public evidence with only the newest stamp.

October 11, 2026 · Subscribe fallback and public static sweep reverified Reconfirmed homepage/archive subscribe fallback states and swept 139 public HTML pages / 1,480 internal Noog Weekly links/assets with 0 missing local routes or assets, keeping the slow-publishing reader path visibly fresh after the October 9 repair.
October 9, 2026 · Subscribe fallback harness and public static sweep verified Repaired the local subscriber UX regression harness for the current aria-invalid behavior, then confirmed homepage/archive subscribe fallback states and 145 public HTML pages / 1,509 internal Noog Weekly links/assets with 0 missing local routes or assets.
October 8, 2026 · Homepage, archive, and public static sweep verified Refreshed the public QA stamps after confirming 139 public HTML pages and 1,480 internal Noog Weekly links/assets with 0 missing local routes or assets, keeping the reader trust path current while the next owner profile remains in editorial review.
October 6, 2026 · Public QA log and static link sweep verified Promoted the fresh homepage/archive reliability evidence into this dedicated public QA log after confirming 139 public HTML pages and 1,480 internal Noog Weekly links/assets with 0 missing local routes or assets.
October 2, 2026 · Archive profile badge and static link sweep verified Refreshed the archive’s profile-level review badges from stale September labels to the current October 2 QA pass after confirming 1,476 internal Noog Weekly links/assets locally with 0 missing references.
September 27, 2026 · Archive entry path and static link sweep verified Refreshed public QA freshness on the homepage and archive after confirming 1,466 internal Noog Weekly links/assets locally with 0 missing references, keeping the back catalog trustworthy while production waits for the next edited owner interview.
September 26, 2026 · Core reader path and static link sweep verified Refreshed the homepage public QA stamp and rechecked 1,466 internal Noog Weekly links/assets locally with 0 missing references, keeping the slow-publishing product visibly maintained between interviews.
September 24, 2026 · Core route and asset sweep verified Rechecked homepage, archive, QA log, public support routes, article routes, and static assets; refreshed the visible freshness stamp so the slow publishing cadence reads as maintained instead of stale.
September 23, 2026 · Core route and asset sweep verified Rechecked the homepage/archive freshness path, confirmed subscriber/support fallbacks remain visible, and ran a static internal-link plus asset sweep across the site before publishing the refreshed QA stamp.
September 22, 2026 · Archive reliability pass verified Rechecked the archive as a high-intent reader entry point, kept the support footer complete, verified core public routes, and refreshed the homepage QA status to point at this public evidence.
September 21, 2026 · Archive support exits added Added unsubscribe, correction, QA evidence, and privacy routes to the archive footer so readers reviewing older profiles can still find support and trust paths.
September 20, 2026 · Support-page unsubscribe links added Linked the public unsubscribe fallback from About, FAQ, and Privacy, updated Privacy’s date, and refreshed the homepage QA status so subscriber removal is visible on every core support surface.
September 19, 2026 · Unsubscribe fallback added Added a public unsubscribe fallback page, linked it from the homepage subscribe note and footer, and rechecked the core trust path so readers have both subscribe and removal routes even when email-client links fail.
September 18, 2026 · Public trust paths rechecked Verified homepage, archive, latest profile, latest issue, nomination, sponsor fit, subscribe fallback, correction email, QA log, and footer routes so a new reader can tell the product is maintained even between interviews.
September 17, 2026 · QA history added Rechecked core reader paths and converted this page into a dated history so board, CEO, reader, and sponsor reviews can see freshness over time.
September 16, 2026 · Pretty routes verified Confirmed homepage trust path, stable QA URL, extensionless navigation routes (/guides, /about, /advertise, /badge), article/archive clarity, subscribe fallback language, image assets, canonical URLs, and return-home routes.

Correction and freshness policy

Profiles should stay useful after publication. If something is outdated or wrong, readers can email [email protected]. New profiles are not promised until an interview clears editorial QA.