This week focused on document movement and version visibility. The goal was to make document structure feel editable without making published state feel fragile.

What shipped

Continued the move/republish work by fixing document card relocation after moves and republishes, then added coverage for destination preselection. See commit c4d0d75e and commit 3cea8ebf.

Allowed users to remove a configured default agent server from settings, which keeps the agents configuration from becoming sticky in a bad state. See commit 6769a8ac.

Renamed the directory panel to “Subdocuments” and tightened the Share → Copy link language so the UI names the thing it actually does. See commit 4ef1f700 and commit d8105c12.

Added web support for moving documents, including parent-card reconciliation after publish, move, and delete. The shared cleanup coordinator and destination dialog now work across desktop and web, and the move dialog defaults to the current parent. See PR #826.

Clarified restore dialogs and allowed danger-style actions where needed. See commit 989c29a6.

Added a document version graph inspector so version relationships can be inspected directly instead of inferred from scattered UI hints. See PR #837.

Notes

The main product idea this week was that document structure is content too. If moving a document leaves cards, parents, refs, or restore state behind, the user experiences that as data corruption even when the storage layer is technically fine.

My question from this week:

What is the smallest UI that makes document history understandable without asking users to think like a version-control tool?