[WebServer] (node:14168) Warning: The 'NO_COLOR' env is ignored due to the 'FORCE_COLOR' env being set.
[WebServer] (Use `node --trace-warnings ...` to show where the warning was created)
[WebServer] (node:17840) Warning: The 'NO_COLOR' env is ignored due to the 'FORCE_COLOR' env being set.
[WebServer] (Use `node --trace-warnings ...` to show where the warning was created)
[WebServer] (node:33608) Warning: The 'NO_COLOR' env is ignored due to the 'FORCE_COLOR' env being set.
[WebServer] (Use `node --trace-warnings ...` to show where the warning was created)
[WebServer] (node:23744) Warning: The 'NO_COLOR' env is ignored due to the 'FORCE_COLOR' env being set.
[WebServer] (Use `node --trace-warnings ...` to show where the warning was created)

Running 21 tests using 1 worker

[WebServer] (node:35108) Warning: The 'NO_COLOR' env is ignored due to the 'FORCE_COLOR' env being set.
[WebServer] (Use `node --trace-warnings ...` to show where the warning was created)
(node:35064) 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)
  ok  1 tests\e2e\01-journey.spec.ts:57:5 › 0 · a visitor with no session is sent to sign-in and sees the honest demo banner (1.0s)
  ok  2 tests\e2e\01-journey.spec.ts:66:5 › 1 · owner A signs in (synthetic) and uploads ten sample files with per-file progress (5.2s)
  ok  3 tests\e2e\01-journey.spec.ts:87:5 › 2 · a two-part Google Takeout import reports exactly what it did (3.3s)
  ok  4 tests\e2e\01-journey.spec.ts:102:5 › 3 · inspect the metadata conflict and resolve it; the other source stays as history (1.3s)
  ok  5 tests\e2e\01-journey.spec.ts:126:5 › 4 · run clearly-marked demo analysis on selected memories (3.4s)
  ok  6 tests\e2e\01-journey.spec.ts:137:5 › 5 · review with the keyboard: accept, edit/answer, reject; rejected text never returns (27.2s)
  ok  7 tests\e2e\01-journey.spec.ts:198:5 › 6 · record a recollection and link two memories (2.0s)
  ok  8 tests\e2e\01-journey.spec.ts:216:5 › 7 · a meme keeps owner-provided attribution (never invented) and asks what it meant (1.2s)
  ok  9 tests\e2e\01-journey.spec.ts:231:5 › 8 · build a chapter from reviewed items, click a claim to inspect its evidence, publish (2.0s)
  ok 10 tests\e2e\01-journey.spec.ts:274:5 › 9 · export the story with provenance and verify the archive offline (3.5s)
  ok 11 tests\e2e\01-journey.spec.ts:306:5 › 10 · revising an uncertain date sends dependent claims back for re-checking (nothing silently stays true) (2.7s)
  ok 12 tests\e2e\01-journey.spec.ts:328:5 › 11 · delete a source: media gone at once, dependent claims visibly invalid, purge stages complete (4.3s)
  ok 13 tests\e2e\01-journey.spec.ts:356:5 › 12 · owner B (a different tenant) sees none of owner A’s data, even by direct URL (2.9s)
  ok 14 tests\e2e\01-journey.spec.ts:370:5 › 13 · no unexpected API failures or page errors happened during the whole journey (4ms)
  ok 15 tests\e2e\02-access.spec.ts:67:5 › security headers are present on pages and on the API (production build) (98ms)
  ok 16 tests\e2e\02-access.spec.ts:82:5 › sign-in screen is accessible in light and dark (7.8s)
  ok 17 tests\e2e\02-access.spec.ts:91:5 › every screen passes axe (WCAG 2.2 AA tags) in light and dark, with a clean structure (45.9s)
  ok 18 tests\e2e\02-access.spec.ts:114:5 › the date editor, review item, evidence drawer and delete dialog are accessible too (interactive states) (6.7s)
  ok 19 tests\e2e\02-access.spec.ts:134:5 › keyboard only: skip link, tab order, nav, shortcuts, dialog focus trap and Escape (4.0s)
  ok 20 tests\e2e\02-access.spec.ts:180:5 › reduced motion: animations and transitions are switched off (1.6s)
  ok 21 tests\e2e\02-access.spec.ts:189:5 › mobile viewport: the core flow works at 390x844 with no horizontal scrolling (17.2s)

  21 passed (2.6m)
