[sbc1-code]

People looking to renew SENTRI encounter a guide that says “Pending Review” after expiration suspends access and that conditional approval permits lane use. The official DHS TTP renewal FAQ instead describes continued benefits for renewals submitted before expiration. This corrects the existing EN/ES guides and puts the official portal action on the first screen.

The guides now direct individual status/eligibility questions to TTP and CBP, distinguish timely and late applications, and remove unsupported fingerprint, rescheduling, mailing and processing-time promises. Original May 9 publication dates, author, slugs and translation pairing remain; the October 22 revision and correction are visible. Existing current-waits and sharing paths are retained.

Refs #64; keeps the broader growth issue open.

Validation:

• Source review against four publicly rendered TTP FAQ answers on October 22: renewal, expiration/late renewal, interview and card activation. No invented fee amount or fixed extension duration; no individual lane-access assurance.
• Rebased onto main 6da71f538e49d3caeb4ae5fe9acc65668de3ab0d; both incoming collector updates preserved byte-for-byte. Four-file diff only; no dependency, settings, collector or budget changes.
• Fresh build and complete npm test: 133 unit tests and 402 manifest browser navigations, including the new EN/ES SENTRI regression in both route profiles.
• Dedicated EN/ES QA at 1440×900, 390×844 and 320×568: first-screen official action, keyboard/new tab/null opener, publication/revision/canonical metadata, correct status distinctions, waits/Back and translation; six captures retained. Portal navigation uses a controlled destination fixture, without login, application or payment.
• Entry JS 61.73 KiB / unchanged 62 KiB; CSS 19.09 / 20 KiB. Existing audit gate passes with two moderate entries, no new exception.
• Final head 12c3767109bb458e1ef1e8d6161528db143b2d71 has the identical tested tree 7da57794f3365dfdbae1f0e5e1c34c9d4cea1026; the only post-test amendment uses the account's existing public noreply commit identity after GitHub rejected the private email metadata. No privacy setting changed.

Limits: query-to-page attribution and current on-site completion/drop-off are unverified; no CTR or conversion improvement is claimed. Existing blog prerender is crawler content, not an accessible no-JavaScript user view. No production merge/deployment is authorized at this gate.