Test coverage and limits

New scenario lab (implemented only here)

Both profiles are regenerated deterministically; these counts are coverage fixtures, not real customer activity or proof of an exhaustive application test.

Existing app functions exercised with all 2,880 mapped scenarios

`existing-model-test.cjs` calls the original release-99 coverage-check, customer-revenue, internal-cost and labor functions. Independent expected values: three labor hours; SAR 400 internal cost; SAR 0 covered customer charge or SAR 260 chargeable; invalid positive covered labor charge rejected. This does not mean the prototype's new scheduling/policy objects are accepted by existing live APIs.

Existing baseline suites actually run

PASS:

• workspace: 15 page render paths, uploads, service metrics, five labor activities, coverage finances, report escaping, read-only behavior
• inventory: moving average, reservation/issue/return/transfer, overdraw, expiry, review locks, ledger integrity, failed-save atomicity
• dispatch: ownership, capacity fallback, availability, full kits, duplicate protection, warranty/chargeable offers, release guard and work types
• trial-demo: existing 1,000-case trial isolation and analytics
• client-setup: fixed arithmetic, schedule/weekend/holiday/pause and invalid-input tests
• extension: CSV/XLSX price catalog, formula rejection, snapshots, coverage suppression, uptime and interval/delivery math
• marketing: existing marketing surface static checks
• connected-intelligence: existing report engine/session checks, including connected report data
• numerical-previews and csv-exports: existing preview/export tests
• forms-deep and client-request-feedback: client demo validation/feedback
• owner-notifications: isolated local notification/auth fixtures; no live notification sent

PARTIAL / BLOCKED:

• Backend suite: 31 tests ran, 30 passed, 1 errored because optional `resend` SDK is absent (`test_real_sdk_webhook_signature_and_allowlist`). Not a complete backend pass. No live email integration test claimed.
• Private-feedback cross-project script: Service fixture passed after replacing its absolute source root with this isolated copy. The second, unrelated Title project path is absent, so script overall failed; do not count as a full suite pass.
• Browser QA: Chromium could not launch: socket operation prohibited in this managed runtime. No screenshots or visual/interaction pass claimed. `browser-test.cjs` is ready for a browser-capable environment.

Not established

Real login/logout or organization tenancy isolation in a browser; real five-area server migration; transaction/concurrent slot locking; real contract approval; email or Apple share dispatch; live SAP/SSO; iOS compile/device QA; clinical suitability; real manufacturer entitlement; production readiness; integration of the new lab with the live navigation. Existing baseline tests do not remove these limits.

Independent final review

56/56 independent oracle groups pass against engine SHA-256 `22eb173af8ea16eb5194df06121425d688da7a9dcbabb9f1f7ebfb389ccd8e43`. Oracles independently reconstruct stock balances, check eligibility/capacity/intervals and reusable-item quarantine, verify no feasible remaining dispatch gaps, all 96 type×priority combinations, invalid-input rejection and reason-tagged pauses. Balanced has 83 part shortages; surge has 536. These are declared stock assumptions, not evidence of real supply adequacy.

Linked lifecycle report coverage

• The dashboard preview, report library, client-request demo and Simulation Lab now embed the same lifecycle projection and UI. Their own-snapshot links carry account, demand, status, search, SLA diagnostic setting and UTC snapshot. Customer links select one fictional account when the administrative selection is all accounts.
• 2,880 balanced/surge source cases have deterministic lifecycle events. The default snapshot is October 17, 2026 at 20:00 UTC; only cases and events at or before it appear. Full-horizon mode includes 1,440 cases for the selected profile. Event timestamps are generated test assumptions, not real observations or forecasts.
• Representative patterns: new/open, customer-access wait, ordered parts, reserved stock, submitted quotation pending approval, rejected quote, accepted paid or entitled loaner, entitlement review, backup shortage/delivery, reinstallation scheduled/completed, report submitted, resolved awaiting confirmation, customer-confirmed closed, backup return pending inspection.
• Status totals partition all matching tickets; quotation states separately partition the same matching tickets. Not-closed includes resolved. Quotation value is not invoiced revenue. Original equipment remains open after backup/loaner delivery. Rejected or unapproved quotations never release paid loaners.
• Lifecycle state is distinct from the pre-existing independent dispatch/SLA boundary arithmetic. That diagnostic data is collapsed, staff-simulation only and explicitly labeled; future arithmetic observations do not claim a pending ticket is restored.
• `node tests/lifecycle.cjs` validates event-time boundaries, future exclusion, per-account scoping, all five statuses, parts/quotation/continuity combinations, chart/count reconciliation, empty filters, and invalid or out-of-order transition guards. `node tests/auxiliary-design.cjs` exercises UI rendering and repeated filter/mode changes in a mocked DOM.
• Limitations: 12 representative lifecycle patterns are not exhaustive combinations. Lifecycle stock references and separate explicit backup entitlements are fixture assumptions, not a global transactional inventory ledger. No real quotation send/acceptance, invoices, payment, repairs, email delivery, customer authentication, production tenant isolation, distributed contention, audited reopen flow or real customer data changes are implemented. UI selectors do not enforce privacy; all source fixtures are public synthetic data.
• Existing static report/dashboard examples remain separately labeled fixed samples; their historic graphics are not presented as this lifecycle snapshot. Live production reports still require authorized server integration.