Skip to content

Ship truthful Temporal E2E demo with verified GIF and video - #3

Open
jadenfix wants to merge 7 commits into
mainfrom
codex/fixture-temporal-demo-20261013
Open

jadenfix wants to merge 7 commits into
mainfrom
codex/fixture-temporal-demo-20261013

Conversation

@jadenfix

@jadenfix jadenfix commented Oct 13, 2026 •

Copy link
Copy Markdown
Owner

Outcome

Turns the previously empty credential-free “Quick Demo” into a truthful, deterministic workflow demo without weakening the live path.

Functional repair

  • immutable POST /api/demo fixture with three reserved .invalid evidence pages
  • real Temporal activity chain, Agent Wall persistence, snapshot storage, and metrics
  • hard provider boundary: fixture mode skips Linkup, Browser Use, Anthropic, Freepik, and SmartBuckets even when provider-looking credentials exist
  • POST /api/run_research remains live-only
  • validated Agent Wall IDs; broad /data static mount removed
  • obsolete Express scaffold removed

Browser and presentation repair

  • polished self-contained responsive interface replaces the dead stylesheet URL
  • API values use DOM text nodes and HTTP(S)-only links; no dynamic innerHTML
  • stored-XSS browser regression reproduces and blocks the former exploit
  • fixture scope is visible in UI, history, snapshot, metrics, README, GIF, and MP4
  • deterministic process readiness and guaranteed browser/process cleanup in E2E

Verified demo

The published 21-second GIF/MP4 uses actual Chromium frames from the source tree below. capture.json pins 24 source blobs and every artifact SHA-256; the verifier fully decodes GIF, MP4, and PNG.

  • Current head: 7be059cc074fdf636bf65c0bc4a05a5ab9b0c2ab
  • Current tree: 9cb0edf9086f8c5c036c6e69a1eeea4b4b3931d2
  • Captured source commit: f140c2d66339fc5cbb1cdc4804e2a791aa6207aa
  • Captured source tree: 3b6b3885381786a3e07ca9b8e941d60c15bc0302

All application/runtime capture inputs remain byte-identical. The only post-capture source change among the 24 pinned blobs is the browser test harness itself: hosted-Python selection, matching Playwright install, explicit readiness/cleanup, and CI media tooling.

Exact-head verification

  • Hosted push run 38379064170: success
  • Hosted PR run 38379072624: success
  • pytest -q: 12 passed
  • real Temporal server + worker: 3 links, 3 pages, 0 provider calls
  • separate Temporal/worker/API/Chromium E2E: fixture completed, DOM XSS blocked, provider endpoints untouched
  • media verifier: 3 artifacts, 24 source blobs, full decode
  • clean-tree gate: passed
  • npm audit: 0 vulnerabilities
  • GitGuardian: passed
  • independent exact-head review: clear

Truthful scope

This demonstrates a fictional, provider-free local fixture and real orchestration/persistence. It does not claim live company research, provider quality, outreach delivery, production deployment, accuracy, or performance. Live provider behavior remains credential-dependent and was not exercised.

Copy link
Copy Markdown
Owner Author

Independent exact-head review: CLEAR — hold lifted.

  • PR head: 7be059cc074fdf636bf65c0bc4a05a5ab9b0c2ab
  • Tree: 9cb0edf9086f8c5c036c6e69a1eeea4b4b3931d2
  • Base main: 24d422953eff842b650a22a8c1c63964ce8ee0c7
  • Captured application source: f140c2d66339fc5cbb1cdc4804e2a791aa6207aa / tree 3b6b3885381786a3e07ca9b8e941d60c15bc0302

Final hosted gates are green:

  • PR run 38379072624 / job 115234679958
  • push run 38379064170 / job 115234651059
  • GitGuardian job 115234661562

The independent reviewer reran all 12 tests, real Temporal orchestration, separate Temporal/worker/API/Chromium E2E, the full media verifier, and npm audit. Provider-looking credentials were present, but the immutable fixture path called no Linkup, Browser Use, Anthropic, Freepik, or SmartBuckets boundary. Stored-XSS, URL allowlisting, Agent Wall path validation, media full-decode/frame inspection, and remote artifact Git blobs were verified.

The GIF, MP4, and poster truthfully show the fictional provider-free workflow. They do not establish live-provider behavior, outreach delivery, deployment, accuracy, or performance.

Ready for the standing sole merger's expected-head review. This session did not merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant