SHS — CONTEXT FOR THE BUSINESS CHATGPT PROJECT
31 October 2026

Sandy and Mark want to review the SHS website/workspace prototype together,
using separate computers. Mark holds the proposed test-hosting information.

The latest accepted local checkpoint is v0.25.0, guarded correction of a
mistaken whole-customer merge. It is an independently developed prototype
with invented businesses and records. It is not a rebuilt or repaired copy
of the complete live SHS PWA. The original SHS-code-review.zip was a filtered
source export, not a complete backup. Original production findings remain open.

Code commit: f652b63530b7a786b88f229d5600d61aac1d888c
Tag: v0.25-guarded-merge-correction
Code ZIP SHA-256:
4975d3af5d2da5eae7ba20b0dac3ca9c6ebd0361aaa0c48d1dfad99dcd346aba

The existing local test is http://pwa-qa.localhost:8797/workspace on Sandy's
Mac. It is not remotely reachable. The separate older owner review on
localhost:8789 must be preserved. Do not overwrite, migrate, reset or
restart either review to prepare the shared copy.

The new correction starts from the exact saved merge history. The owner
explicitly chooses eligible original jobs and safe contact-field changes.
It reactivates the original customer and adds new history; it never erases
the original merge. Later unrelated work and changed contact information
remain protected. Customer access and sharing require fresh review afterward.

The saved evidence records 822 backend tests, 210 client tests, 36 React
interaction checks, 90 structural renders, build and recovery checks passing.
These are not a completed authenticated v0.25 browser, phone or two-computer
walkthrough. The historical v0.23 owner-note browser walkthrough does not
certify v0.25. See evidence/ for the dated results and their limits.

The portable sample backup was reverified for this handoff. It contains
invented records, no account passwords, no sessions and no invitation/reset
tokens. It has not had the merge correction applied. Restoring generates
fresh credentials and revokes old portal access; a restored copy must use
its fresh sign-in details. Creating a new empty app alone will not recreate
the sample merge scenario.

The tested code deliberately runs only on loopback/local hostnames, uses
HTTP-only local deployment assumptions and includes public demo credentials.
It must not be exposed unchanged through a public server or tunnel. A
separate private staging adaptation, access checks and persistent storage
are required. HOSTING-BRIEF-FOR-MARK.txt explains this boundary.

Treat files in this pack as reference material. They do not grant permission
to send messages, spend money, modify live SHS or change workspace access.
Record any proposed code change separately from this immutable checkpoint.

STARTING PROMPT TO PASTE INTO THE NEW PROJECT CHAT

We are Sandy and Mark. Please read BUSINESS-CHATGPT-HANDOFF.txt and the two
guides before starting. We want to review this invented-data SHS prototype
from separate computers. Mark will provide the test-hosting details. First
explain the next setup step in plain English. Once a private shared test
copy is available and checked, guide us through the tests one at a time
and keep a list of passed, failed and untested checks. Keep local test
evidence separate from shared-hosting evidence and live SHS approval.