Stage 0 dry run on the TEST pair

Plan row R 0.9a for Yale 25's go-live: the lead, tour and emergency paths walked end to end on Fixture North Court (TEST), a building owned by one TEST company and managed by another. Email only. No texts, no calls.

2026-11-05 00:00–03:00 UTC · propflow-prod · TEST companies only · Lane H · plan: pms-agnostic-architecture-2026-11

The lead and tour paths work on a co-managed building. A reply was held, approved and delivered. A tour note was held and released, and the team closed it with the no-login link. Two real bugs surfaced (below); both need fixing before Yale goes live.

Result per step

Lead → held reply → approved → emailed: pass.
Tour request → held note → released → no-login confirm: pass.
Timer from release, not hold: pass.
Emergency: proven in CI and the readout only, no live chain.
Two tour-note bugs to fix before Yale (below).

Receipts per step

Step	Result	Receipts	Carrier
Lead by email → reply held → approved → sent	Pass	Reply held under Supervised (`eschold_825309ce…`). Approved 02:52:47Z by the test presser through the hold-approve CLI. Received by the sandbox prospect at 02:52:51Z. The outbound row is on the conversation (`a8e26902…`).	Email: SendGrid, from clara@propflowai.co. The building has no connected mailbox.
Tour request → note held → released → confirm link	Pass	Clara: "I've put in your request … Saturday, November 7 at 11:00 AM, but it isn't booked yet. The team will confirm the time with you within two business hours." Note `…a7118f0b601c40dd` held, approved 02:53:28Z and delivered to the team inbox. The no-login page opened (GET changed nothing); the button marked the ask confirmed at 02:53:59Z, and pressing it again changed nothing.	Email: SendGrid to our M365 sandbox
Unconfirmed timer	Pass	The timer workflow started when the note was released, not when it was held: 02:48:50Z for a note held at 02:41Z. A rejected note started no timer.	Temporal
Emergency	Pass, no live chain	CI walked the front door's call routing (TwiML) and ran the no-number-promise tests: 55/55, run 41923555956. The readout shows nobody is rung (message only) and no job number is promised without a work-order system. No live chain ran: it would post to #emergency, and phone tests are off everywhere.	None: no call, text or page

Bugs, fixes, revert and follow-ups

Bugs found

Fixed or set along the way

The script that gives a building an inbound email address could not be run by an agent on prod. #25262 (merged) makes its duplicate-address check a bounded read. #25285 refuses a mismatched data backend.
Inbound mail needs its own SES rule for each address; the domain is not a catch-all. With Gera's go, one rule was added for fixture-north-court@inbound.propflowai.co, after the Yale sandbox rule. All seven existing rules were read back unchanged. It stays in place. Rollback: aws ses delete-receipt-rule --rule-set-name propflowai-rules --rule-name fixture-north-court-inbound.

Reverted, same session

The building's leasing row is cleared. The owner TEST company's leasing plan is back to Off / Setting up, matching the snapshot taken before the run. The test team inbox is cleared. After the revert, the building readout matches the 11-04 baseline, apart from pmsSource=tenio, which Lane G's Tenio work set and this run did not touch. The inbound address and its SES rule are kept on purpose.

Follow-ups

Fix the two tour-note bugs above: 0.4 follow-up PRs, in progress.
A CLI command for setting a company's module mode: in progress.
SES receipt-rule operations for the prod-write tool: agent-harness #1928, awaiting Gera's review.
Done 11-05: the TEST building now has a time zone (America/Denver) and office hours (Mon–Fri 9–5, Sat 10–4).
The first held reply carried the label of a send-check guard hold, not a Supervised hold, worth checking.
Both timers wake at about 18:00Z on 11-05. Both asks are confirmed, so they must page nobody. This hasn't been observed yet and will be checked after 18:05Z.