[prestoncabe]

Closes #585.

Summary

Preview and the published screener each had their own copy of the screening session flow (form-js mount, debounce, the guard against out-of-date evaluations, stale/failed state, hidden questions). The copies had drifted. Now both pages create one screening session and keep only their chrome.

 builder-frontend/src/components/
 ├── screener/
-│   ├── FormRenderer.tsx            # public copy of the flow
 │   └── Screener.tsx                # CRM bridge + chrome
 ├── screenerEditor/preview/
-│   ├── FormRenderer.tsx            # preview copy of the flow
 │   └── Preview.tsx                 # chrome only
 └── shared/
-    ├── screeningCompletionFlow.test.tsx
+    └── screeningSession/
+        └── screeningSession.tsx    # the shared module
+src/testing/formJs.ts                # type into form-js like a person

const session = createScreeningSession({
  schema,
  evaluate,          // evaluateScreener | evaluatePublishedScreener
  initialAnswers?,   // a CRM host's prefill: missing answers stay null until answered
  evaluateOnLoad?,   // Preview, and published screeners with a connected host
  onResults?,        // latest evaluation only -> bridge.result
  onEvaluationFailed?, // latest evaluation only -> bridge.error
});
<session.Form />  // plus results, stale, failed, loading, answersSent,
                  // unneeded questions, nextStepsShown, projectNextSteps

Behaviour changes:

• Published screeners evaluate 500ms after answers stop changing, not 1000ms, matching Preview.
• Preview's form no longer attaches a listener when it unmounts before its first import finishes.
• Preview still evaluates as soon as it opens. That used to happen only because form-js's first fill was mistaken for an edit. It is now the explicit evaluateOnLoad option (see the comment on #585).

Adds a root GLOSSARY.md defining Screener, Published screener, Preview and Screening session.

Evidence

• Before: the page tests mocked both FormRenderers and called submitForm / onDataChange by hand. The real chain (form-js changed → debounce → evaluate → stale/failed) never ran for published screeners.
  After: screeningSession.test.tsx (18 tests) types into a real form-js form, with a fake evaluate adapter whose promises the test settles. It covers debounce, out-of-date responses and failures, hidden questions and re-import, prefill with unknown answers, evaluate on load, teardown, and the next steps projection. Screener.test.tsx and Preview.test.tsx drive the real form too.
• builder-frontend npm test: 54 files, 389 tests passed. npm run build: passed.
• Full bin/run-e2e-tests: 25 passed. During development, "User can Preview a Screener Form" caught the evaluate-on-open regression and now passes.

Merge Danger

Door: two-way

A frontend-only refactor. No API, schema or stored-data changes. A revert restores both renderers.

Blast Radius: screening

Every screening session, in Preview and on published screeners including CRM hosts, now runs through this module. The places most likely to show a regression are the faster published debounce (more evaluations sent to builder-api while someone types) and the timing of CRM results and next steps.

🤖 Generated with Claude Code