@wral/report-it 0.1.2 → 0.1.4

package/README.md

@@ -56,6 +56,40 @@ column width (default 680px).
    `PUT /v1/requests/{requestId}` (idempotent — retries return the same
    reference) → confirmation + behind-the-scenes journey.
 
+### Skipping the account (DEV-1270)
+
+The sign-in card files its alternatives under a collapsed **"Other ways
+to send this"** disclosure — deliberately present but never the path of
+least resistance. It always offers the newsroom desk number. It offers
+an in-form anonymous submission **only when the server advertises it**:
+`GET /v1/forms` carries `anonymous: {enabled, humanCheck}`, the client
+records it (`client.anonymousCapability()`), and the route renders from
+that alone — never from anything baked into the page. A deployment with
+`enabled: false`, or an older API with no block at all, leaves the route
+dark and the phone number as the only anonymous option. A form
+suppresses the route regardless with `allowAnonymous: false`.
+
+`humanCheck` is `null` today (no proof-of-human provider is configured;
+the API defends the route with per-caller limits). When a provider is
+configured server-side it becomes `{provider, siteKey}` and the
+component will render that widget in the confirmation card and pass its
+token as `humanToken` — the server is the only party that can verify a
+captcha, so the server is the only party that may ask for one.
+
+The session itself: `createAnonSession({formId, requestId})` posts to
+`/v1/anon/sessions` unauthenticated and holds the returned token; every
+auth-bearing call then presents it as the bearer in place of the My WRAL
+identity until `endAnonSession()` — called after a successful submit and
+on Start over, so a stale anonymous session can never ride along with a
+signed-in one.
+
+Choosing it takes a confirmation card stating what the viewer gives up,
+with **Sign in instead** as the primary action. The choice is recorded
+on the gate step (`{kind: 'gate', anonymous: true}`), so it survives a
+reload; the session is minted at submit against the `requestId`, so an
+abandoned form leaves nothing behind, and a mid-upload expiry re-mints
+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
@@ -83,7 +117,12 @@ 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
 `?demofail=1` to make the second upload fail once and exercise the
-retry UX.
+retry UX. The **Anonymous route** checkbox (demo mode only, also
+settable with `?anon=1`) makes the demo client advertise anonymous
+submission the way a real server does, lighting up the in-form option;
+unchecked it stays dark. In live-dev mode the route follows the dev API's
+own `anonymous` block, so a real anonymous submission can be exercised
+end to end against the dev content stage.
 
 ## Release
 

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