Editor and page actions
Dragging blocks into a page, Undo after adding a block and the Dashboard New Page button now work. A disabled Preview button explains why it is unavailable. Never-published pages read Draft in the Pages list and on the Dashboard. A route or schema error shows a CMS error page or notice instead of the developer screen, and the branch-name field formats as you type. These were everyday actions that did nothing or showed the wrong state.
Technical detail
- Puck ignores a press on a real
<button>, so the block-list item is a div role="button" again, and an empty page says how to add a block (#299). Undo and Redo remove and restore a block added by drag or double-click (#306). - The Dashboard New Page button opens the create-page dialog in place (#302). One
pageStatusOf() and a LocaleVersion.unpublished marker decide page status, and saving a new translation keeps a never-published page a draft (#296, #307). - A route that fails to render shows
RouteErrorPage, and a site schema that is not a generated host schema shows a notice instead of crashing the CMS (#301, #293, #295). The disabled Preview button shows its explanation when clicked (#262). - The New branch field lowercases, hyphenates and keeps the caret in place as you type (#297, #316). The editor opens pages with no English variant (#196), and draft previews parse records with each collection’s schema so dates and defaults match the build (#248).
- Frontmatter keys such as
__proto__.polluted cannot mutate Object.prototype, while own-data keys, including legitimate constructor and prototype names, are kept (#239). The sign-in divider is readable in dark mode; login-theme.spec.ts checks light and dark at 390 and 1280 px (#220).
Key pull requests: #299 · #306 · #302 · #296 · #301 · #297 · 15 pull requests in this group, all in the source record · CI run for #299 · CI run for #302 · CI run for #296
Invites, tabs and sign-in stay in the right place
Accepting an invite lands in the invited workspace, from both the in-app button and the emailed link. Each editor tab sends its repository, branch and site with every write, and the server rejects a mismatch with a 409 instead of writing to the wrong place. Tabs of one browser origin that refresh at the same moment share one token rotation instead of revoking the whole token family.
Technical detail
- Mutations carry
X-Conloca-Editor-Repo, -Branch and -Site headers. The worker answers 409 workspace-mismatch before any billing, storage or Git work, and the tab re-enters its own branch and retries once (#192, #224). - Accept waits at most 5 seconds for the membership flush and the Org Durable Object’s alarm delivers the rest; an invite screen that would stay on “accepting” is released after 20 seconds (#292, #305). A deployed-stage proof,
invite-landing.spec.ts, covers an invitee who already has a workspace (#294). - A second use of a refresh cookie within 10 seconds gets the live token from the rotation chain, and the browser refreshes under a Web Lock so same-origin tabs send one request per rotation (#240). An OAuth failure shows its failure screen instead of looping (#225).
- Splitting the sign-in and Members screens into props-only views fixed a double submit that requested two sign-in links and a double click that sent two invitations (#253, #223).
- Cloudflare Access configuration fails closed with 401 when only one of its two settings is present (#191). Overlay rows for pages deleted in Git are pruned (#188). Workspace and flag types are narrowed instead of cast (#222).
Key pull requests: #288 · #289 · #192 · #224 · #240 · #225 · 14 pull requests in this group, all in the source record · CI run for #288 · CI run for #289 · CI run for #192
Scoped content commits, safe asset moves and correct write-back
CMS commits include only content files, so other people’s staged work is left out, and an asset move claims its destination instead of overwriting an existing file. Draft images render in the canvas before Publish, and a docs-root page is written back to the file it was read from. The hosted preview shows pages committed after its build, and a site snapshot over Cloudflare’s 32 MiB call limit imports in bounded parts.
Technical detail
- CMS commits build their tree in a private index seeded from HEAD and move HEAD by compare-and-swap with
update-ref, so a concurrent commit is not reverted. Asset moves run one at a time and claim the destination with a hard link. Tests use real temporary repositories: foreign staged files, two concurrent instances, a held index.lock and concurrent moves racing for one name (#197). - Draft images are served from
/api/v1/assets/draft/<folder>/<file> while stored data keeps the canonical /assets/... reference (#243). A docs-root MDX page used to be written to a shadow file; mdx-pages-root.test.ts covers edit, delete, create-after-delete and a collision (#235). - The hosted preview records its own
buildCommit and sends it as ?build=; the worker diffs that commit against the branch head and matches entries by blob id. A deployed-stage test commits a title without redeploying and expects the new heading (#247, spec change #228). - The depth-1 snapshot of one pull request packs to about 33.6 MB, over the 32 MiB RPC limit. It now lands in parts of at most 16 MiB with the tree and commit last, and a live check against github.com imported the full closure of 4,836 objects (#259). A missing base tree is fetched by object id instead of failing the import (#256).
- Org import now always retries the tracker reconcile when a ref already matches upstream, so a stale preview session recovers (#177). Only three of Ultra’s 29 commits in #177 are credited: the repair, its at-head regression test and the browser publication proof. The vocabulary sample stays off the Git lookup behind the unpublished marker (#308).
Key pull requests: #197 · #243 · #235 · #247 · #259 · #177 · 9 pull requests in this group, all in the source record · CI run for #197 · CI run for #247 · CI run for #259
The finished How it works page is on conloca.com
The production How it works page uses the completed design: a four-step flow with MDX, JSON and editor visuals, twelve responsive images and an install banner that survives 200% text. The design is by Saba; our work is the integration into the production site and its checks. In the pull request’s delayed-hydration test, images moved 397.6 px before the fix and 0 px after it.
Technical detail
- The twelve PNGs were imported byte for byte, with SHA-256 and byte lengths checked on the preview. Existing routes, app links, docs links and install tabs are kept, and text is darkened where the original failed contrast (#342).
- The test measured 397.587 px of movement before and 0 px across 53 frames after. Twenty-one website targets and 50 browser checks were rerun.
- The merge to the main branch ran Validate, deployed-stage browser tests and Deploy Production, all successful. Locally, the split-port development stack redirects backend landings to the app and keeps published media on local origins (#231).
Key pull requests: #342 · #231 · CI run for #342 · conloca.com/how-it-works
Browser and story coverage for the editor
The CMS and the app each build a static Storybook catalogue in CI, and state stories cover save, sync and workspace status, the page list and the conflict dialogs. Deployed-stage browser tests walk every CMS route, create a branch through the Branch menu, confirm a new page reads Draft and check that typed text survives reopening the editor in both themes. CI keeps the proof folder of every deployed-stage run.
Technical detail
- State stories render the real components with fixtures that stop at
HostClient and the content API fetch, so nothing reaches the network. Counts: SaveSlot 6 plus phone, SyncStatusSlot 8 plus phone, WorkspaceStatusSlot 8 plus phone, CmsHostPlaceholder 9 (#244). CI saves a screenshot of every story at 1280 × 800 and 390 × 844. The app Storybook runner now compiles Tailwind, because classes such as max-sm:hidden were missing from all app examples. - A flaky failure in the Several Locales scenario, caused by a viewport resize landing mid-play, is gone: resizes during play went from 30 and 11 to 0 and 0 in the probe runs (#257).
- The deployed-stage job keeps its proof folder on every run and the Playwright report on failed runs (#320). A manual staging proof workflow adds two new legs (#261), and the emitted billing deploy bundle runs in CI (#238).
- Real-engine and typed tests for Git paths, billing identity mapping, workspace recovery and memory behaviour were added or made deterministic (#198, #234, #221, #236, #201, #254). Branch creation and the Draft check are in #229 and #309, and the editor-reopen check is in #226.
Key pull requests: #217 · #244 · #304 · #229 · #300 · #320 · 17 pull requests in this group, all in the source record · CI run for #229 · CI run for #300
A pull-request stage environment that keeps working
Pull-request stages are cleaned up on a schedule with capacity reporting and stage leases, which brought the Cloudflare namespace count to 386 of 500 after the first eviction run. Each stage uses one Durable Object namespace fewer, and each deployment attempt gets its own preview fixture without resetting drafts. Before this, Deploy Stage was failing account-wide with Cloudflare error 10067 after about 170 namespaces leaked from closed pull requests.
Technical detail
- A scheduled workflow runs every six hours, reports capacity and fails above 400 of 500 namespaces. Drafts hold a stage for 24 hours and ready pull requests for 72 hours;
keep-stage and evict-stage override that. tooling/pr-stage-gc.test.ts checks that only closed same-repo pull requests are selected (#200). - Deleting the unused
EventLogDO takes each stage from 10 namespaces to 9, which the pull request estimates moves live capacity from about 48 to about 53 stages (#241). - Readiness rejects dirty overlays and divergent session heads, and older attempt orgs are retired after 24 hours (#169). A read-only inventory of legacy preview resources deletes nothing (#155). A Deploy Production failure on a missing generated contracts module was fixed (#258), and E2E runs leave branches clean (#193).
Key pull requests: #200 · #241 · #169 · #155 · 7 pull requests in this group, all in the source record
Typed contracts and delivery gates
Project validation moved from hand-written Zod schemas to validators generated from the TypeScript types with Typia, in a 160-file change; we adapted the existing generated-contract work to the editor, loader, CLI and sites. CI gates now block only the debt a change adds, and dependency review, mirror sync and the devenv install kept running when GitHub-hosted jobs could not start. DOMPurify moved to 3.4.17 for a critical advisory.
Technical detail
- Site schemas become
HostSchema<T>: a generated validator with JSON Schema metadata. The editor builds its forms from that metadata, and the loader reports field paths. content-api drops zod and conformance rule A76 forbids it in every workspace package (#251). - Before #263 a rebased pull request got 141 findings, 116 of them on lines it never touched; the gate now looks at changed lines. A per-file type-assertion ratchet refuses to count when a library has no
dist, because counts differ without built declarations (2,311 versus 2,325) (#263, #303, #322, #319). - GitHub-hosted jobs stopped starting from about 23 October because of a billing block, so dependency review and mirror sync moved to the self-hosted pool. devenv main had moved to a Nix version the cache does not serve, so the install is pinned to v2.4.0. A test now fails on unjustified
sudo in workflows (#311, #313, #255, #314). - DOMPurify has a failing-then-passing floor test (#290, #315). Tests use a RAM-backed temp directory and Git without fsync: summed over 141 test tasks, time went from 1,164 s to 1,079 s and 1,097 s, about 6% less (#194). Bun installs stay out of Bun’s global store (#232).
- Smaller changes in this group: Rig verification contract and commands (#174, #230), warning-only pre-push anti-slop check (#167), changed-source gates in CI (#166), dependency review green on private (#260), mirror and tooling fixes (#129, #158, #175, #176, #178, #195, #204, #233, #237, #298).
Key pull requests: #251 · #166 · #263 · #303 · #311 · #255 · #315 · 28 pull requests in this group, all in the source record
