@wral/report-it 0.2.0 → 0.2.2

package/README.md

@@ -36,6 +36,7 @@ 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
@@ -56,7 +57,7 @@ column width (default 680px).
    `POST /v1/uploads` (Bearer) → presigned S3 PUTs with per-file
    progress and retry (expired presigns re-mint per file) →
    `PUT /v1/requests/{requestId}` (idempotent — retries return the same
-   reference) → confirmation + behind-the-scenes journey.
+   reference) → confirmation.
 
 ### Hand-offs, unlisted forms and deep links (DEV-1305)
 
@@ -96,6 +97,24 @@ yields to the link.
   `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
@@ -181,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
@@ -192,5 +230,3 @@ Repo variables: `NPM_TOKEN`, `AWS_ACCESS_KEY_ID`,
   prefers `field.counties` if a form document ever ships it.
 - Required `location` fields need a county or a written place — one
   notch stricter than the server schema, deliberately.
-- `routing.state: "failed"` on a successful submission renders honest
-  "delivery being retried" journey copy, never fake delivery.

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-BZTBgLk3.js";
+import { W as i, a as r, b as a } from "./wral-code-input-BA1oCHMu.js";
 typeof window < "u" && !window.AmazonCognitoIdentity && (window.AmazonCognitoIdentity = n);
 const d = {
   "wral-report-it": a,