$ node.exe node_modules\@playwright\test\cli.js test
(cwd: .)
exit 0 after 173.3s

--- stdout ---

Running 21 tests using 1 worker

  ok  1 tests\e2e\01-journey.spec.ts:46:5 › 0 · a visitor with no session is sent to sign-in and sees the honest demo banner (1.8s)
  ok  2 tests\e2e\01-journey.spec.ts:54:5 › 1 · owner A signs in (synthetic) and uploads ten sample files with per-file progress (5.8s)
  ok  3 tests\e2e\01-journey.spec.ts:72:5 › 2 · a two-part Google Takeout import reports exactly what it did (3.7s)
  ok  4 tests\e2e\01-journey.spec.ts:85:5 › 3 · inspect the metadata conflict and resolve it; the other source stays as history (1.6s)
  ok  5 tests\e2e\01-journey.spec.ts:105:5 › 4 · run clearly-marked demo analysis on selected memories (5.1s)
  ok  6 tests\e2e\01-journey.spec.ts:115:5 › 5 · review with the keyboard: accept, edit/answer, reject; rejected text never returns (47.0s)
  ok  7 tests\e2e\01-journey.spec.ts:175:5 › 6 · record a recollection and link two memories (1.6s)
  ok  8 tests\e2e\01-journey.spec.ts:192:5 › 7 · a meme keeps owner-provided attribution (never invented) and asks what it meant (1.6s)
  ok  9 tests\e2e\01-journey.spec.ts:207:5 › 8 · build a chapter from reviewed items, click a claim to inspect its evidence, publish (2.5s)
  ok 10 tests\e2e\01-journey.spec.ts:249:5 › 9 · export the story with provenance and verify the archive offline (3.1s)
  ok 11 tests\e2e\01-journey.spec.ts:280:5 › 10 · revising an uncertain date sends dependent claims back for re-checking (nothing silently stays true) (1.8s)
  ok 12 tests\e2e\01-journey.spec.ts:299:5 › 11 · delete a source: media gone at once, dependent claims visibly invalid, purge stages complete (4.5s)
  ok 13 tests\e2e\01-journey.spec.ts:326:5 › 12 · owner B (a different tenant) sees none of owner A’s data, even by direct URL (2.6s)
  ok 14 tests\e2e\01-journey.spec.ts:340:5 › 13 · no unexpected API failures or page errors happened during the whole journey (4ms)
  ok 15 tests\e2e\02-access.spec.ts:52:5 › security headers are present on pages and on the API (production build) (77ms)
  ok 16 tests\e2e\02-access.spec.ts:67:5 › sign-in screen is accessible in light and dark (2.1s)
  ok 17 tests\e2e\02-access.spec.ts:76:5 › every screen passes axe (WCAG 2.2 AA tags) in light and dark, with a clean structure (32.7s)
  ok 18 tests\e2e\02-access.spec.ts:99:5 › the date editor, review item, evidence drawer and delete dialog are accessible too (interactive states) (4.7s)
  ok 19 tests\e2e\02-access.spec.ts:118:5 › keyboard only: skip link, tab order, nav, shortcuts, dialog focus trap and Escape (2.3s)
  ok 20 tests\e2e\02-access.spec.ts:164:5 › reduced motion: animations and transitions are switched off (1.8s)
  ok 21 tests\e2e\02-access.spec.ts:173:5 › mobile viewport: the core flow works at 390x844 with no horizontal scrolling (14.3s)

  21 passed (2.9m)

--- stderr ---
(node:2704) Warning: The 'NO_COLOR' env is ignored due to the 'FORCE_COLOR' env being set.
(Use `node --trace-warnings ...` to show where the warning was created)

