Not yet covered (honest pending list)
This page is our promise to you about honesty: it lists everything this guide does not yet have verified proof for. Nothing here is a promise of behaviour — an item only stops being "pending" when a future retained, qualified run says otherwise. Chapters in this guide document only journeys that retained, qualified receipts actually cover, from the guide's five Main evidence roots — or, from 2026-10-25, its worker-tested 3867 lane.
Newly documented on 2026-10-25 (no longer pending)
Two journeys that previously had no qualified receipt now have reproducible worker-lane receipts and full chapters. They remain labelled worker-tested, isolated lane (re-run green twice, but not independently Chief-accepted and not on Main):
- Import phone outcomes — per-row refusals with readable reasons and row numbers, international imports, 8/15-digit bounds, duplicate handling, safe retry and whole-file refusal: documented in Contacts.
- SMS delivery-evidence journeys — real navigation to the deliveries surface, account link, window refusals, exact-phone filtering with date refine and pagination, every supported error with its recovery, and the no-auto-replay save path: documented in SMS delivery evidence.
Still pending on those two journeys (honest scope limits)
- Independent Chief acceptance of the 3867 lane — both suites are worker-authored, worker-run and worker-reproduced; no Chief admission run is recorded yet.
- Live-provider delivery behaviour — every deliveries receipt used synthetic loopback fixtures; no live provider read, no live delivery and no production provider outage was observed.
- Import UI rendering of refused rows in a browser — the phone-outcome run asserts the real server pipeline against real tenant PostgreSQL; the on-screen refused-row list of that exact path is covered only at component level by the existing migration receipt surface.
- Deliveries pagination beyond page 2, MFA-prompt interplay on the deliveries/account-link/save actions, and an XLSX import variant — not exercised by any retained run; scope limits, not known defects.
Activation and entry
- Production activation over a real SMS provider — every retained activation receipt used loopback synthetic providers. Live smoke, provider-failure behaviour in production and a real rollback were explicitly still open at the 2026-10-14 corrective acceptance.
- An observed real production customer journey — the corrected entry page
was independently released and verified byte-for-byte on both workspace
nodes, but no actual customer login through the live link has been observed
and recorded. A green link or a GET 200 is not customer acceptance
(
docs/reviews/2026-10-18-sms-crm-entry-rca.md). - CapCore SSO acceptance — the overview lane explicitly claims none; all identities in these runs are locally signed synthetic bearers.
Features the product does not have yet (open dependencies)
These are not missing tests — the features themselves do not exist, and the retained evidence records the honest workaround:
- Assignee/owner on pipelines, deals and tasks — no assignment field or control exists in the current contracts; the accepted overview shows real lead counts where invented owners would have gone.
- Business-level time-zone preference — task times necessarily use the browser's resolved time zone (displayed explicitly) because the read contract exposes no business time zone.
- Aggregate activity / attribution — no SMS reply, click, enquiry, lead-source or revenue attribution feed exists; the activity card leads to the bounded per-contact timeline only. (Delivery evidence is per-contact and exact-phone; saving it establishes no interest or consent.)
- Contact editor, global consent writer, campaign composer — not exposed by this lane; import/export/search/timeline, the existing CRM forms and the delivery-evidence surface are what exists.
- Lead-scoring semantics — the existing scoring utility is retained unchanged; its signal semantics and any SMS campaign association are outside the retained acceptance.
Screenshot labelling
All screenshots in this guide are from synthetic fixtures on loopback (desktop or mobile as labelled). None depicts live delivery, a real customer, or production data. Where a journey's evidence is "independently accepted" (activation, 2026-10-14) or "independently executed" (entry first-use and connected regression), the chapter says so; the 2026-10-25 import-phone and deliveries chapters are worker-tested lane evidence with the same synthetic-fixture rule, and everything else is locally qualified lane evidence.