fix: three small defects with consequences out of proportion to their size

[petergstfsn]

Three items from the "Refinements" tier that are not cosmetic — each one costs a user something real.

1. An overlong feature name made every later cloud save fail, permanently

packages/document-core/src/index.ts:2898

Command labels interpolate user text (Edit ${value.name}), and the feature Name field has no maxLength. A long enough name pushes the revision past the 500-character bound the account enforces on every write — a 400 that no retry can fix.

The client maps an unrecognised failure to offline (it names 409/413/403/401 explicitly), so a permanently unsaveable document presents as a network problem. On reload normalizeDocument filters the offending revision out silently, taking that save point with it — and re-editing the same feature brings it straight back.

Clamped in appendRevision with the shared constant, truncating rather than replacing so the label still says what it was.

2. A command that changed nothing burned an undo slot and rebuilt the model

packages/command-system/src/index.ts — execute()

runTransaction and applyDocumentEdit both refuse a command that returns the same document. execute did not.

moveFeature returns its input for an out-of-range index — exactly what ArrowUp on the first row produces. So each press appended a "Reorder" revision, pushed a dead undo entry, and bumped version, which is part of the geometry sync key, posting a whole-document WASM rebuild. Around a hundred presses evicts the user's real undo history.

Guarded in execute; the Sidebar also clamps, so a keypress that cannot do anything no longer travels through the command layer to find out.

3. Row controls were invisible but still tappable on touch

apps/web/src/styles/components/sidebar.css

These are revealed by :hover, and a touch device resolves neither :hover nor :focus-visible on a tap — so they sat at opacity: 0 while remaining laid out and hit-testable. On an iPad the first tap near a row's right edge hits an unseen button.

The report named .row-delete. Reading the file, four controls share the defect: delete, Tweak-expose, suppress/rollback, and the drag grip. Rolling the timeline back by accident is nearly as bad as deleting, so all four are fixed rather than the one that was reported.

Revealing them is the right fix rather than pointer-events: none — a touch user has no hover with which to reach them at all. Same fix and reasoning as .sharing-row-action in modals.css.

Verification

All three regression tests fail against the unmodified source.

lint (0 errors, 22 pre-existing advisory warnings), typecheck, 1991 + 748 unit tests, parity corpus 170, build (no budget failures), e2e 155 passed / 0 failed at --workers=2. check-css-classes clean: 208 files against 707 classes.

🤖 Generated with Claude Code

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	openzcad	8368398	Aug 27 2026, 08:56 PM