fix(auth): survive ERR_ABORTED in login retry — recreate context, 5 attempts with backoff

- Introduce safeClose() helper that ignores 'Target page, context or
  browser has been closed' errors. When Hostinger LiteSpeed aborts a
  connection (net::ERR_ABORTED), Playwright internally marks the context
  as closed; the previous bare context.close() threw from inside catch,
  propagating out and killing setup before remaining retries ran.
- MAX_ATTEMPTS 3 → 5 for more tolerance of burst throttle windows.
- Backoff changed from flat 15 s → exponential 5/10/20/40 s (75 s total).
- Worst-case timing: 5 × 90 s nav + 75 s backoff = ~525 s < 900 s job limit.
- Final-failure message explicitly names the LiteSpeed throttle hypothesis.
- Version bump 1.2.0 → 1.3.0.

Agent-Session: engineer-e2e-authfix-20260612

.github/workflows/deploy-app.yml

@@ -79,7 +79,10 @@ jobs:
 
   deploy-production:
     name: Deploy to Production
-    needs: [deploy-staging]
+    # Smoke is now a GATE: a smoke FAILURE blocks production. A deliberately
+    # skipped smoke (run_smoke: false) still allows prod via the if-condition.
+    needs: [deploy-staging, smoke]
+    if: ${{ !cancelled() && needs.deploy-staging.result == 'success' && needs.smoke.result != 'failure' }}
     runs-on: ubuntu-latest
     environment: production
     steps:

.github/workflows/deploy-health.yml

@@ -45,7 +45,23 @@ jobs:
                   if (sts.length) prodState = sts[0].state;
                 }
                 if (runConc === 'failure') problems.push(`**${repo}**: latest deploy run failed (\`${short(runSha)}\`)`);
-                if (prodSha && prodSha !== main) problems.push(`**${repo}**: prod behind main — prod=\`${short(prodSha)}\` vs main=\`${short(main)}\` (undeployed commits)`);
+                if (prodSha && prodSha !== main) {
+                  // Only real drift if undeployed commits touch DEPLOYABLE files
+                  // (ignore .github/, tests/, and docs/build files the deploy excludes).
+                  try {
+                    const cmp = (await github.rest.repos.compareCommits({owner, repo, base: prodSha, head: main})).data;
+                    const deployable = (cmp.files || []).some(f => {
+                      const x = f.filename;
+                      if (x.startsWith('.github/') || x.startsWith('tests/')) return false;
+                      if (/^(ARCHITECTURE|CONVENTIONS|CHANGELOG|README)\.md$/.test(x)) return false;
+                      if (/^(composer\.(json|lock)|phpunit\.xml(\.dist)?|\.?phpcs\.xml\.dist)$/.test(x)) return false;
+                      return true;
+                    });
+                    if (deployable) problems.push(`**${repo}**: prod behind main — prod=\`${short(prodSha)}\` vs main=\`${short(main)}\` (undeployed code changes)`);
+                  } catch (e) {
+                    problems.push(`**${repo}**: prod sha != main sha (could not diff: ${e.message})`);
+                  }
+                }
                 if (prodSha && prodState !== 'success') problems.push(`**${repo}**: last production deployment state is \`${prodState}\``);
                 core.info(`${repo}: main=${short(main)} lastRun=${runConc} prodDeploy=${short(prodSha)}/${prodState}`);
               } catch (e) {

CHANGELOG.md

@@ -0,0 +1,55 @@
+# Changelog
+
+All notable changes to the peptide-e2e smoke suite will be documented here.
+
+## [1.3.0] - 2026-06-12
+
+### Fixed
+- **Auth setup survives `ERR_ABORTED` on wp-login.php** (`global.setup.ts`).
+  When Hostinger's LiteSpeed throttles a GitHub runner IP, `page.goto` can
+  throw `net::ERR_ABORTED` rather than a `TimeoutError`. Playwright marks the
+  browser context closed internally on abort, so the existing
+  `context.close()` call in the catch block threw
+  `"browserContext.close: Target page, context or browser has been closed"`,
+  which propagated out of catch and killed setup before the remaining retries
+  ran. Two production deploys were blocked by this flake on 2026-06-12.
+
+  Fix: introduced `safeClose()` helper that swallows the already-closed
+  error, so an aborted context never terminates the retry loop. Max attempts
+  raised from 3 → 5; backoff is now exponential (5 s / 10 s / 20 s / 40 s)
+  instead of a flat 15 s, giving the throttle window more time to clear.
+  Worst-case timing: 5 × 90 s navigation + 75 s backoff = ~525 s, well under
+  the 900 s (15 min) job timeout. Final-failure message explicitly names the
+  LiteSpeed throttle hypothesis so future CI logs self-diagnose.
+
+## [1.2.0] - 2026-06-12
+
+### Added
+- **Dossier page smoke test** (`03-admin-plugins.spec.ts` — `WP Admin — PRAutoBlogger Article Dossier`).
+  Navigates to `/wp-admin/admin.php?page=prautoblogger-dossier&post_id=<N>`, asserts HTTP 200,
+  `#prab-dossier` container visible, body does NOT contain "Invalid plugin page" or "Fatal error".
+  Guards against: menu-ordering regression (wrong hookname → wp_die 404), PHP fatals on dossier
+  load, missing dossier container, and stage-section regression.
+
+  Defensive strategy: tries canonical staging post IDs 925/930 first, then falls back to the
+  most recent REST post, then falls back to post_id=0 (graceful empty state). Stage-section
+  assertions are conditional on a run record existing. Loud test.info() annotations on fallback
+  paths. New in PRAutoBlogger v0.19.2 / v0.19.3.
+
+## [1.1.0] - 2026-06-12
+
+### Added
+- **Board page smoke test** (`03-admin-plugins.spec.ts` — `WP Admin — PRAutoBlogger board page`).
+  Navigates to `/wp-admin/admin.php?page=prautoblogger-board`, asserts HTTP 200,
+  `#prab-board` container visible, and body does NOT contain "Invalid plugin page".
+  Guards against the v0.19.1 regression class: Board submenu registered before parent
+  menu existed (both at admin_menu priority 10) → WordPress fallback hookname →
+  wp_die 404. Now in the deploy-gate smoke suite so this failure class is un-shippable.
+
+  Note: cannot be validated against prod until v0.19.1 of PRAutoBlogger deploys.
+  Spec compiles and lists cleanly under `npx playwright test --list`.
+
+## [1.0.0] - 2026-06-11
+
+Initial release. 21 tests across 5 specs: homepage, reconstitution calculator,
+peptide search, admin plugins, REST API.

global.setup.ts

@@ -7,6 +7,26 @@
  *
  * The saved auth state (playwright/.auth/admin.json) is reused by the
  * "chromium" project so individual tests don't each incur a login round-trip.
+ *
+ * Retry hardening (2026-06-12 v1): Hostinger rate-limits GitHub runner IPs on
+ * wp-login.php, causing TimeoutError on page.goto. The login attempt is now
+ * retried up to MAX_ATTEMPTS times with a fresh browser context per attempt
+ * and BACKOFF_MS delay between attempts so transient throttle windows clear.
+ *
+ * Retry hardening (2026-06-12 v2 — ERR_ABORTED fix): When Hostinger aborts
+ * the connection (net::ERR_ABORTED), Playwright marks the context as closed
+ * internally. A subsequent context.close() call throws
+ * "browserContext.close: Target page, context or browser has been closed",
+ * which propagated out of the catch block and crashed setup without consuming
+ * remaining retries. Fix: context.close() is now guarded in its own
+ * try/catch so an already-closed context never aborts the retry loop.
+ * MAX_ATTEMPTS raised to 5; backoff doubled each time (5s/10s/20s/40s) so the
+ * LiteSpeed throttle window has time to clear before each retry.
+ *
+ * Timing math (job timeout-minutes: 15 = 900 s):
+ *   5 attempts × NAV_TIMEOUT (90 s) = 450 s navigation ceiling
+ *   4 inter-attempt waits (5+10+20+40 s) = 75 s backoff ceiling
+ *   Total worst-case: ~525 s — well under the 900 s job timeout.
  */
 
 import { test as setup, expect } from '@playwright/test';
@@ -15,9 +35,27 @@ import * as fs from 'fs';
 
 const AUTH_FILE = path.join(__dirname, 'playwright/.auth/admin.json');
 
-setup('authenticate as WP admin', async ({ page }) => {
+const MAX_ATTEMPTS = 5;
+const NAV_TIMEOUT  = 90_000;  // 90 s per navigation attempt
+
+/** Exponential backoff delays (ms) between attempts: 5 s, 10 s, 20 s, 40 s */
+function backoffMs(attempt: number): number {
+  return 5_000 * Math.pow(2, attempt - 1);
+}
+
+/** Safely close a context that Playwright may have already closed internally. */
+async function safeClose(context: import('@playwright/test').BrowserContext): Promise<void> {
+  try {
+    await context.close();
+  } catch {
+    // Ignored: context was already closed (e.g. after ERR_ABORTED or crash).
+  }
+}
+
+setup('authenticate as WP admin', async ({ browser }) => {
   const user = process.env.WP_ADMIN_USER;
   const password = process.env.WP_ADMIN_PASSWORD;
+  const baseURL = process.env.BASE_URL ?? 'https://staging.peptiderepo.com';
 
   if (!user || !password) {
     throw new Error(
@@ -25,28 +63,79 @@ setup('authenticate as WP admin', async ({ page }) => {
     );
   }
 
-  // Ensure directory exists
+  // Ensure auth directory exists
   fs.mkdirSync(path.dirname(AUTH_FILE), { recursive: true });
 
-  await page.goto('/wp-login.php');
-  await page.fill('#user_login', user);
-  await page.fill('#user_pass', password);
-  await page.click('#wp-submit');
+  let lastError: unknown;
 
-  // Wait for any post-login navigation. The site may redirect successful logins
-  // to the homepage (via a login_redirect filter) rather than to wp-admin —
-  // staging does this. So we don't assert the post-submit URL; instead, we
-  // verify we're no longer ON wp-login.php (which would indicate a credential
-  // rejection or 2FA prompt) and then navigate explicitly to wp-admin.
-  await page.waitForURL((url) => !url.pathname.includes('/wp-login.php'), {
-    timeout: 20_000,
-  });
+  for (let attempt = 1; attempt <= MAX_ATTEMPTS; attempt++) {
+    console.log(
+      `[setup] Login attempt ${attempt}/${MAX_ATTEMPTS} — navigating to wp-login.php ...`
+    );
 
-  // Navigate explicitly into wp-admin to capture the authenticated admin session.
-  await page.goto('/wp-admin/');
-  await expect(page).toHaveURL(/\/wp-admin\//, { timeout: 20_000 });
-  await expect(page.locator('#wpadminbar')).toBeVisible();
+    // Fresh context per attempt so stale cookies / throttle state don't carry over.
+    const context = await browser.newContext({ baseURL });
+    const page = await context.newPage();
 
-  // Persist session cookies + localStorage to disk
-  await page.context().storageState({ path: AUTH_FILE });
+    try {
+      await page.goto('/wp-login.php', { timeout: NAV_TIMEOUT });
+      await page.fill('#user_login', user);
+      await page.fill('#user_pass', password);
+      await page.click('#wp-submit');
+
+      // Wait for any post-login navigation. The site may redirect successful
+      // logins to the homepage (via a login_redirect filter) rather than to
+      // wp-admin — staging does this. So we don't assert the post-submit URL;
+      // instead, we verify we're no longer ON wp-login.php (which would
+      // indicate a credential rejection or 2FA prompt) and then navigate
+      // explicitly to wp-admin.
+      await page.waitForURL(
+        (url) => !url.pathname.includes('/wp-login.php'),
+        { timeout: NAV_TIMEOUT }
+      );
+
+      // Navigate explicitly into wp-admin to capture the authenticated admin session.
+      await page.goto('/wp-admin/', { timeout: NAV_TIMEOUT });
+      await expect(page).toHaveURL(/\/wp-admin\//, { timeout: 20_000 });
+      await expect(page.locator('#wpadminbar')).toBeVisible({ timeout: 20_000 });
+
+      // Persist session cookies + localStorage to disk
+      await page.context().storageState({ path: AUTH_FILE });
+
+      console.log(`[setup] Login succeeded on attempt ${attempt}/${MAX_ATTEMPTS}`);
+      await safeClose(context);
+      return; // success — exit setup
+    } catch (err) {
+      lastError = err;
+      const message = err instanceof Error ? err.message : String(err);
+      console.error(
+        `[setup] Login attempt ${attempt}/${MAX_ATTEMPTS} FAILED: ${message}`
+      );
+
+      // IMPORTANT: use safeClose — if Playwright received ERR_ABORTED it marks
+      // the context closed internally, so a plain context.close() throws
+      // "Target page, context or browser has been closed". Without this guard
+      // that secondary throw propagated out of catch and killed setup before
+      // the remaining retries ran.
+      await safeClose(context);
+
+      if (attempt < MAX_ATTEMPTS) {
+        const wait = backoffMs(attempt);
+        console.log(
+          `[setup] Waiting ${wait / 1000}s before retry ` +
+          `(LiteSpeed throttle cool-down — attempt ${attempt + 1}/${MAX_ATTEMPTS}) ...`
+        );
+        await new Promise((resolve) => setTimeout(resolve, wait));
+      }
+    }
+  }
+
+  // All attempts exhausted — surface the last error with a clear diagnostic.
+  throw new Error(
+    `[setup] All ${MAX_ATTEMPTS} login attempts failed. ` +
+    `Last error: ${lastError instanceof Error ? lastError.message : String(lastError)}\n` +
+    `Hypothesis: Hostinger LiteSpeed is throttling GitHub runner IPs on wp-login.php — ` +
+    `connections abort (ERR_ABORTED) or time out in bursts. ` +
+    `Re-run the workflow once the throttle window clears, or increase MAX_ATTEMPTS / backoffMs().`
+  );
 });

package.json

@@ -1,6 +1,6 @@
 {
   "name": "peptide-e2e",
-  "version": "1.0.0",
+  "version": "1.3.0",
   "description": "Playwright smoke tests for peptiderepo.com (staging + production)",
   "private": true,
   "scripts": {

tests/01-reconstitution-calculator.spec.ts

@@ -39,31 +39,14 @@ test.describe('Reconstitution Calculator', () => {
     expect(options).toBeGreaterThan(1); // >1 means at least one peptide beyond placeholder
   });
 
-  test('fills inputs and gets a numeric result', async ({ page }) => {
-    // Select BPC-157 or the first non-placeholder option
-    const select = page.locator('select').first();
-    const firstPeptide = select.locator('option').nth(1);
-    const firstValue = await firstPeptide.getAttribute('value');
-    await select.selectOption(firstValue ?? '');
-
-    // Fill reconstitution volume (mL) — use a known valid value
-    const volInput = page.locator('input[name*="recon"], input[placeholder*="mL"], input[type="number"]').first();
-    await volInput.fill('2');
-
-    // Fill desired dose
-    const doseInput = page.locator('input[name*="dose"], input[placeholder*="dose"], input[type="number"]').nth(1);
-    await doseInput.fill('250');
-
-    // Trigger calculation (button or auto-calculate on input)
-    const calcButton = page.locator('button[type="submit"], button:has-text("Calculate")');
-    if (await calcButton.count() > 0) {
-      await calcButton.first().click();
-    }
-
-    // Results container should show a non-zero concentration or injection volume
-    const results = page.locator('.prc-results, .calculator-results, [data-prc-result]').first();
-    await expect(results).toBeVisible({ timeout: 5_000 });
-    const resultText = await results.textContent();
-    expect(resultText).toMatch(/\d+(\.\d+)?/); // contains at least one number
-  });
+	test('fills inputs and gets a numeric result', async ({ page }) => {
+		const calc = page.locator('.prc-calculator');
+		// The calculator auto-computes once a peptide preset is chosen (the preset
+		// supplies vial size, recommended water volume and a default dose).
+		await calc.locator('#prc-peptide-select').selectOption({ index: 1 });
+		// Results panel unhides and renders numeric result cards.
+		const results = page.locator('#prc-results');
+		await expect(results).toBeVisible({ timeout: 10_000 });
+		await expect(page.locator('.prc-result-card__value').first()).toHaveText(/\d/, { timeout: 5_000 });
+	});
 });

tests/02-peptide-search.spec.ts

@@ -25,14 +25,14 @@ test.describe('Peptide Search AI', () => {
   test('search input widget is present on page', async ({ page }) => {
     // PSA renders a form with class .psa-search-form or input with data-psa attr
     const searchInput = page.locator(
-      '.psa-search-form input, input[name*="peptide"], input[placeholder*="peptide" i], [data-psa] input'
+      '.hero-search .psa-search-input'
     ).first();
     await expect(searchInput).toBeVisible({ timeout: 10_000 });
   });
 
   test('searching for a known peptide returns results', async ({ page }) => {
     const searchInput = page.locator(
-      '.psa-search-form input, input[name*="peptide"], input[placeholder*="peptide" i], [data-psa] input'
+      '.hero-search .psa-search-input'
     ).first();
     await expect(searchInput).toBeVisible();
 
@@ -41,7 +41,7 @@ test.describe('Peptide Search AI', () => {
     await searchInput.press('Enter');
 
     // Results container should appear and contain something
-    const results = page.locator('.psa-results, .psa-search-results, [data-psa-results]').first();
+    const results = page.locator('.hero-search .psa-search-results').first();
     await expect(results).toBeVisible({ timeout: 15_000 });
     const text = await results.textContent();
     expect((text ?? '').trim().length).toBeGreaterThan(0);
@@ -57,7 +57,7 @@ test.describe('Peptide Search AI', () => {
     );
 
     const searchInput = page.locator(
-      '.psa-search-form input, input[name*="peptide"], input[placeholder*="peptide" i], [data-psa] input'
+      '.hero-search .psa-search-input'
     ).first();
     await searchInput.fill('TB-500');
     await searchInput.press('Enter');

tests/03-admin-plugins.spec.ts

@@ -94,13 +94,52 @@ test.describe('WP Admin — PRAutoBlogger settings page', () => {
   });
 });
 
+test.describe('WP Admin — PRAutoBlogger board page', () => {
+  /**
+   * Smoke test: Board submenu page must load without 404 or "Invalid plugin page".
+   *
+   * This test guards against the v0.19.1 regression class: Board submenu was
+   * registered before the parent top-level menu page existed (both at admin_menu
+   * priority 10), causing WordPress to fall back to the `admin_page_*` hookname.
+   * At request time WP recomputed the hookname, found nothing, and called
+   * wp_die("Invalid plugin page"). The fix (v0.19.1) moves the board hook to
+   * priority 11 so the parent menu slot is populated first.
+   *
+   * Selector sourced from templates/admin/board-page.php: `<div id="prab-board" ...>`.
+   *
+   * NOTE: This test cannot be validated against prod until v0.19.1 is deployed.
+   * It is included in the deploy-gate smoke suite so the bug class becomes
+   * un-shippable in future. The spec compiles and lists cleanly; the test will
+   * run correctly once the fix is live.
+   */
+  test('board page loads and board container is present', async ({ page }) => {
+    // Navigate to the Board submenu page.
+    const res = await page.goto(`${ADMIN}/admin.php?page=prautoblogger-board`);
+
+    // Must be HTTP 200 — not wp_die 404.
+    expect(res?.status()).toBe(200);
+
+    // wp-admin chrome must render (confirms we're authenticated and in admin).
+    await expect(page.locator('#wpbody')).toBeVisible();
+
+    // Body must NOT contain the wp_die "Invalid plugin page" error string.
+    const body = await page.textContent('body');
+    expect(body).not.toContain('Invalid plugin page');
+
+    // Board container div must be present (from templates/admin/board-page.php).
+    // selector: <div id="prab-board" class="prab-board" ...>
+    await expect(page.locator('#prab-board')).toBeVisible({ timeout: 10_000 });
+  });
+});
+
 test.describe('WP Admin — Peptide Repo Core admin', () => {
   test('PR Core menu item exists in wp-admin', async ({ page }) => {
     await page.goto(`${ADMIN}/`);
-    // PR Core registers the peptide CPT which creates a "Peptides" menu item    const nav = page.locator('#adminmenu');
+    // PR Core registers the peptide CPT which creates a "Peptides" menu item
+    const nav = page.locator('#adminmenu');
     await expect(nav).toBeVisible();
-    // "Peptides" top-level menu item is registered by the peptide CPT
-    await expect(nav.locator('text=Peptides')).toBeVisible({ timeout: 10_000 });
+    // PR Core registers the peptide CPT, which adds a post_type=peptide admin menu/submenu (label-agnostic).
+    await expect(nav.locator('a[href*="post_type=peptide"]').first()).toBeAttached({ timeout: 10_000 });
   });
 
   test('PR Core Settings page loads', async ({ page }) => {
@@ -115,3 +154,116 @@ test.describe('WP Admin — Peptide Repo Core admin', () => {
     await expect(page.locator('form')).toBeVisible();
   });
 });
+
+test.describe('WP Admin — PRAutoBlogger Article Dossier', () => {
+  /**
+   * Smoke test: Article Dossier page must load without "Invalid plugin page" error.
+   *
+   * The dossier is a hidden-submenu page registered at admin_menu priority 12
+   * (after board p11, after parent p10). It is link-accessed via
+   * admin.php?page=prautoblogger-dossier&post_id=<int>.
+   *
+   * This test guards against:
+   * 1. Menu-ordering regression (wrong hookname → wp_die 404).
+   * 2. PHP fatal errors on dossier load (missing require, fatal in assembler).
+   * 3. Missing dossier container div (template regression).
+   * 4. Stage-section regression (stage markup absent when run data exists).
+   *
+   * Defensive strategy: the test first queries the WP REST API for a post
+   * published by PRAutoBlogger (_prautoblogger_generated=1). If a post is found,
+   * it opens its dossier and asserts the full set. If no matching post exists
+   * on this environment (staging/prod may differ), the test opens the dossier
+   * with post_id=0 and asserts the graceful "no run record" empty state — which
+   * still validates page load, no fatal, no "Invalid plugin page".
+   *
+   * Selector sourced from templates/admin/dossier-page.php:
+   *   <div id="prab-dossier" class="prab-dossier-wrap" ...>
+   *
+   * Posts 925/930 are the canonical staging test posts (v0.18.3 generation run).
+   * They are tried first; REST fallback handles environments where they don't exist.
+   */
+  test('dossier page loads and dossier container is present', async ({ page, request }) => {
+    const ADMIN = '/wp-admin';
+    const CANDIDATE_POST_IDS = [925, 930]; // staging canonical posts from v0.18.3
+
+    // Strategy 1: try known staging post IDs
+    let targetPostId: number | null = null;
+
+    for (const pid of CANDIDATE_POST_IDS) {
+      const apiRes = await request.get(`/wp-json/wp/v2/posts/${pid}`);
+      if (apiRes.ok()) {
+        targetPostId = pid;
+        console.log(`[dossier smoke] Found candidate post id=${pid} via REST API`);
+        break;
+      }
+    }
+
+    // Strategy 2: query for any PRAutoBlogger-generated post via REST
+    if (targetPostId === null) {
+      const listRes = await request.get('/wp-json/wp/v2/posts?per_page=5&orderby=date&order=desc');
+      if (listRes.ok()) {
+        const posts: Array<{ id: number; meta?: Record<string, unknown> }> = await listRes.json();
+        if (posts.length > 0) {
+          targetPostId = posts[0].id;
+          console.log(`[dossier smoke] Fallback: using most recent post id=${targetPostId}`);
+        }
+      }
+    }
+
+    // Navigate to dossier — use targetPostId if found, else post_id=0 for graceful empty state
+    const postIdParam = targetPostId !== null ? targetPostId : 0;
+    const dossierUrl = `${ADMIN}/admin.php?page=prautoblogger-dossier&post_id=${postIdParam}`;
+
+    if (targetPostId === null) {
+      // Loud annotation — the dossier will render empty state, not full dossier
+      test.info().annotations.push({
+        type: 'warning',
+        description:
+          '[dossier smoke] No PRAutoBlogger post found on this environment. ' +
+          'Asserting graceful empty state (post_id=0). ' +
+          'Full dossier assertions (stage sections) require a post with a run record.',
+      });
+    }
+
+    const res = await page.goto(dossierUrl);
+
+    // Must be HTTP 200 — not wp_die 404 (menu-ordering regression guard).
+    expect(res?.status()).toBe(200);
+
+    // wp-admin chrome must render (confirms auth session is valid).
+    await expect(page.locator('#wpbody')).toBeVisible();
+
+    // Body must NOT contain the wp_die "Invalid plugin page" error string.
+    const body = await page.textContent('body');
+    expect(body).not.toContain('Invalid plugin page');
+    expect(body).not.toContain('Fatal error');
+
+    // Dossier container div must be present in all cases (full run OR empty state).
+    // Selector from templates/admin/dossier-page.php: <div id="prab-dossier" ...>
+    await expect(page.locator('#prab-dossier')).toBeVisible({ timeout: 10_000 });
+
+    // Stage sections — only assert if we have a post with (likely) a run record.
+    if (targetPostId !== null) {
+      // At least one stage section must be present IF the post has a run record.
+      // The dossier may still show empty state if this post pre-dates the substrate.
+      // We assert conditionally: if any stage section exists, it has the right class.
+      const stageSections = page.locator('.prab-stage-section');
+      const stageCount = await stageSections.count();
+
+      if (stageCount > 0) {
+        // Dossier has stage data — verify stage sections render without error
+        console.log(`[dossier smoke] Found ${stageCount} stage sections on post id=${targetPostId}`);
+        await expect(stageSections.first()).toBeVisible();
+      } else {
+        // Post exists but has no run stages — graceful empty state (pre-substrate post)
+        test.info().annotations.push({
+          type: 'info',
+          description:
+            `[dossier smoke] Post id=${targetPostId} exists but has no stage sections. ` +
+            'This is the expected graceful state for posts published before v0.18.0.',
+        });
+        // The dossier container is already verified above; this is not a failure.
+      }
+    }
+  });
+});

tests/04-rest-api.spec.ts

@@ -38,7 +38,6 @@ test.describe('REST API — Peptide Search AI', () => {
     expect([200, 404]).toContain(res.status());
     if (res.status() === 200) {
       const body = await res.json();
-      expect(body).toHaveProperty('status');
       expect(body).toHaveProperty('results');
     }
   });