FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Finishing the Public Web and local synchronization foundation
Displaying only real data while aligning fixture ownership and Thread-tree retrieval with actual operation
Purpose
The initial Public Web still generated Demo data in the interface and could not distinguish public-data retrieval failure from having no published Rooms. Local fixtures and real-synchronization initialization were also mixed in one command, allowing Connector state to diverge from the database after reset.
The goal was to limit the public interface to actual data, separate synchronization data, product defaults, and rich dummy data, and create a local verification foundation that reliably collects every Thread under a root.
Implementation
Generated Demo snapshots were removed from 3D client. No published Room produces an empty state, while connection or configuration failures produce a maintenance state without preserving stale display as success. Search results and the Room timeline now use separate state.
root-task reader no longer scans all Threads and filters by session ID. It paginates active and archived results with ancestorThreadId, verifies each candidate through thread/read, and retains the descendant limit.
pnpm db:fixtures now inserts only the owner, Connector, origin digest, and product-default Agents, without dummy Rooms or Threads. pnpm db:fixtures:all is separated for the rich local dataset so real synchronization checks and visual checks do not silently depend on the same data.
local-database reset process stops the development Connector and resets synchronization targets, outbox, and sequence together with the local database. Web environment generation writes the raw token paired with the fixture digest to an owner-only file without mutating the database.
Rendering diagram…
What was confirmed
Verification results
The Public Web no longer displays fabricated Demo data and treats an empty state separately from retrieval failure.
The Connector queries descendants for one root across active and archived sets without relying on a global scan.
Minimal and rich fixtures use separate commands, and Connector local state is reset together with the database.
At the cutoff, these finishing changes were applied to the target. Adding the CEO portrait and final confirmation of the complete Story belong to later activities.
Basis for completion
The finishing work was complete when real-data-only Web states, root-scoped Thread-tree retrieval, minimal and rich fixture separation, and coordinated database and Connector-state reset agreed across code and verification procedures.