Company schedule: every tour says who is showing it

Before (main) and after (this branch) on the test company, Friday, October 2, at desktop and phone width.

5 Oct 2026 · branch p9-calendar-schedule-shows-host · captured against propflow-stage · at 129ea03fa1c

PR #16687

Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.

1 · Before — desktop (main)

Today's company schedule for the test company on Oct 2. Each tour row shows who is touring and the unit, but nothing says who is showing it, so the company view can't be read as the agents' schedules put together.

Asserted in the captured DOM — October 2

Before — desktop (main)
Provenance. Captured from commit 9d2d449ae8f, read from the worktree the server was started from (/Users/miniclaw/code/PropFlow/wt-p9cal-host-before) — the server could not report its own commit, so this is the weaker of the two sources. That commit is already merged into origin/main.
Sections 2–4 and notes

2 · After — desktop (this branch)

The same day. Each tour row now ends with a host line: the agent's name, or Building calendar / Company calendar when the tour is held on a shared calendar, or name not on file when the agent's profile has no name (never a guessed one). Read from the host stored on the tour, not recomputed.

Asserted in the captured DOM — Host: Building calendar · Host: Company calendar · Host: name not on file · Host:

After — desktop (this branch)

3 · Before — phone (main)

Same day at 390px, before.

Asserted in the captured DOM — October 2

Before — phone (main)
Provenance. Captured from commit 9d2d449ae8f, read from the worktree the server was started from (/Users/miniclaw/code/PropFlow/wt-p9cal-host-before) — the server could not report its own commit, so this is the weaker of the two sources. That commit is already merged into origin/main.

4 · After — phone (this branch)

Same day at 390px. The host line wraps under the unit rather than overflowing.

Asserted in the captured DOM — Host: Building calendar · Host: Company calendar · Host: name not on file · Host:

After — phone (this branch)

How the four cases were staged

Stage only had tours hosted by one named agent, so three past test-company tours on Oct 2 had their stored host pointed, for the capture only, at the building's calendar, the company's calendar, and a real test-company admin with no profile on stage. Snapshot first, read back after each write, restored after the capture and read back again. Past tours were chosen because nothing can reschedule, re-host or cancel them.

PropFlow Docs