@wral/report-it 0.1.4 → 0.2.1

package/README.md

@@ -36,6 +36,8 @@ Keep this first in the host page's `<head>`:
 | --- | --- | --- | --- |
 | `api` | attribute | `https://api.wral.com/forms` | api-forms base URL (dev: `https://api.wral.com/dev/forms`) |
 | `client` | property | — | Full I/O surface override (API + auth); wins over `api`. See `src/demo/demo-client.mjs` for the shape |
+| `facts-api` | attribute | — | api-user-facts v1 base (e.g. `https://api.wral.com/user-facts/v1`). Unset, a new account is never offered to save its details |
+| `flow` | attribute | — | Open one form directly by its `formId` (e.g. `investigates`). The host page's `?flow=<formId>` does the same; the attribute wins |
 
 Styling hooks: design tokens are read as `var(--wral-…, fallback)` with
 prototype-accurate fallbacks, so the component renders correctly with no
@@ -44,7 +46,8 @@ column width (default 680px).
 
 ## How a submission flows
 
-1. `GET {api}/v1/forms` (public) — one button per published form.
+1. `GET {api}/v1/forms` (public) — one button per published form
+   (forms with `listed: false` are served but not shown; see below).
 2. The chosen form's tree walks client-side: `choice` chips, `collect`
    cards (text/textarea/url/datetime/location/media/consent/select),
    the `gate` (My WRAL email + one-time code — skipped with a
@@ -56,6 +59,62 @@ column width (default 680px).
    `PUT /v1/requests/{requestId}` (idempotent — retries return the same
    reference) → confirmation + behind-the-scenes journey.
 
+### Hand-offs, unlisted forms and deep links (DEV-1305)
+
+A choice option may carry `form` (and optionally `path`) instead of
+`next`: choosing it switches to that form document and replays the
+`path` choice steps there first. News → "5 On Your Side" lands on the
+consumer form's complaint card, past its own "5 On Your Side or
+Investigates?" question. The submission is made against the target
+form, with the preset steps at the head of its `path`; a path through
+a hand-off option itself is never sent (the API rejects one).
+
+The form the viewer came from is kept as an origin (`src/lib/handoff.mjs`),
+persisted with the draft: the transcript reads as one conversation, a
+reload rebuilds it, and **Back** from the first card after a hand-off
+returns to the choice that made it, skipping the preset steps. A
+hand-off to a form that is not loaded shows the load-error notice and
+stays put.
+
+An unlisted form (`listed: false`, e.g. `investigates`) is fetched with
+the rest and reachable by hand-off or deep link, just not offered on the
+entry screen. `?flow=<formId>` on the host page (or the `flow`
+attribute) opens a form directly; a draft for that form (or one handed
+off to or from it) resumes instead, and a draft for any other form
+yields to the link.
+
+### Fields
+
+- `text` fields pass `inputMode` and `autocomplete` from the form
+  document through to the input, and each collect card is a real
+  `<form autocomplete="on">`, so the browser can fill name, phone,
+  address and zip from the viewer's saved details. Nothing is prefilled
+  from My WRAL or stored anywhere else. (Autofill inside shadow DOM
+  varies by browser — verify on iOS Safari and Android Chrome.)
+- A `text` field's `pattern` is checked before submit the way the
+  server checks it (a zip gets its own message).
+- `consent` copy comes from the field's `text`. With
+  `requiredIf: "media"` the checkbox appears only once a file is
+  attached, is required only then, and is not sent without files.
+
+### Saving details to a new account
+
+Off unless the host sets `facts-api` to an api-user-facts v1 base, e.g.
+`<wral-report-it api="…" facts-api="https://api.wral.com/user-facts/v1">`.
+With it set, when the sign-in card created the viewer's My WRAL account
+on this page load, a successful submit adds one more step before the
+confirmation: an offer to save their answers as user facts (the store
+the audience dashboard reads). The confirmation shows only after
+**Save to my account** succeeds or **No thanks**.
+Only the `name` field (as `preferred_name`, at most 100 characters) and
+the `postal-code` field (as `zipcode`, first five digits) are saved,
+matched by `autocomplete` (`src/lib/user-facts.mjs`). Nothing is saved
+without the viewer's click, for an existing account, or for an anonymous
+report. A save clears the dashboard's `wral_user_facts` cache. A reload
+between sign-in and submit drops the offer. In the demo,
+`?demoexisting=1` makes accounts existing and `?demofactsfail=1` fails
+the first save.
+
 ### Skipping the account (DEV-1270)
 
 The sign-in card files its alternatives under a collapsed **"Other ways
@@ -92,7 +151,11 @@ in place instead of opening the sign-in card.
 
 Auth uses `@wral/sdk-auth-audience` directly (`sendCode`/`verifyCode`);
 `requireAuth`/`authFetch` are deliberately avoided — their 401 paths
-redirect to `/login/`, which would destroy an unsubmitted form. A 401
+redirect to `/login/`, which would destroy an unsubmitted form. The
+bearer on uploads and submit is the viewer's Cognito **ID token** (not
+the access token the SDK's `getAuthHeaders` sends): same `sub`, but it
+also carries the verified `email`, which api-forms writes onto the
+record beside the account id (`src/lib/id-token.mjs`). A 401
 mid-submit re-opens the gate in place and resumes where it parked.
 
 ## Drafts
@@ -115,7 +178,10 @@ npm run dev       # vite harness at http://localhost:5173
 
 The harness runs against the live dev API by default (real My WRAL
 login — your email receives a real code) or fully offline with the
-in-memory demo client (any email, any six digits). Append
+in-memory demo client (any email, any six digits). The demo client
+serves the form documents in `src/demo/fixtures/` (copies of api-forms'
+seeds), so hand-offs, `?flow=investigates` and the files-only consent
+all work offline. Append
 `?demofail=1` to make the second upload fail once and exercise the
 retry UX. The **Anonymous route** checkbox (demo mode only, also
 settable with `?anon=1`) makes the demo client advertise anonymous
@@ -134,6 +200,25 @@ Repo variables: `NPM_TOKEN`, `AWS_ACCESS_KEY_ID`,
 `S3_BUCKET=cdn.wral.com`, `S3_PREFIX=@wral/report-it`,
 `AWS_DISTRIBUTION_ID`.
 
+## Staging pages
+
+Both load the component from the CDN `latest` alias, so a release reaches
+them without a republish. Each is a staging.wral.com publication whose
+template is an HTML asset in the editorial DAM (`content: {}`,
+`template: {"$ref": "https://assets.wral.com/<asset id>"}`):
+
+| Page | api-forms stage | DAM asset |
+| --- | --- | --- |
+| [/test/report-it/](https://staging.wral.com/test/report-it/) | prod (`/forms`): real desk lists and the Studio queue | `39c268dd-06eb-46f9-a6bf-74d04af45bae`, i.e. `pages/report-it.html` as of DEV-1300 |
+| [/test/report-it-dev/](https://staging.wral.com/test/report-it-dev/) | dev (`/dev/forms`): the `ReportIt_Dev` list and the dev content stage | `3c78d978-bcd3-44f9-9906-c417db80de14`, the same page before DEV-1300 (only the `api` attribute and its comment differ) |
+
+To change a page:
+1. Upload the new HTML as a new asset. Use `POST https://api.wral.com/dam/v1/asset/<new uuid>/upload-url` with `dam:write`, then PUT the file with `Content-Type: text/html`.
+2. `POST https://api.wral.com/publisher/v1/publications` with `publisher:write`, sending `{site, path, content: {}, template: {"$ref": …}, metadata: {httpStatusCode: 200}}`.
+3. Invalidate the path on CloudFront distribution `E2PUK7RNR73BP4`, because the page is cached for about 6 h.
+
+Leave the previous asset in place. Republishing with its `$ref` is the rollback.
+
 ## Notes
 
 - `wral-code-input` + helpers are copied from

package/dist/define.mjs

@@ -1,5 +1,5 @@
 import * as n from "amazon-cognito-identity-js";
-import { W as i, a as r, b as a } from "./wral-code-input-DCemMj53.js";
+import { W as i, a as r, b as a } from "./wral-code-input-BH_1EP8b.js";
 typeof window < "u" && !window.AmazonCognitoIdentity && (window.AmazonCognitoIdentity = n);
 const d = {
   "wral-report-it": a,