4 Commits

Include renames

Author	SHA1	Message	Date
steveandClaude Opus 4.8	4b18ac3b46	History panel and undo in the editor (#49) ... #48 made every change revertible; this makes that reachable. The bar was that undoing what the agent just did should take one obvious click, not a hunt. Settles the rail-layout question, which is the part #53 and #57 depend on. Four things wanted one strip of screen — inspector, history, journal, chat — so they are tabs in one EditorRail rather than each bolting on its own chrome. That keeps the canvas at one width instead of a different width per panel, and adding the journal or chat later is adding a tab. Two constraints held. Selecting an object still lands you in the inspector with no extra click: the page watches the selection and switches tabs itself, so the rail never becomes something you operate before you can edit. And the canvas stays worth watching while the agent edits it — the rail is a fixed 20rem column that closes completely when nothing needs it. On a phone the same tabs render in the bottom sheet the inspector already lived in. A reverted entry stays in the list, struck through and marked, and the revert appears as its own entry — because that is what it is. Making the original disappear would be rewriting history rather than appending to it, and would leave no way to undo the undo. Conflicts are reported as what actually happened. A 409 from a revert is not a plain failure: it carries the change set that DID apply alongside the entities deliberately left alone, so the message is "2 of 3 changes undone — “North Bed” was edited since, so it was left alone" rather than a generic toast. A bare failure would be a lie about the two that applied; a bare success would hide the one that didn't. Undo is one implementation, not two: useUndo owns the mutation, the per-change- set outcome and the phrasing, and UndoButton renders it. #57's inline undo on an agent turn uses the same hook, so undo behaves identically wherever it appears. The panel says plainly that deleting a whole garden isn't covered and can't be undone, rather than leaving that to be discovered. Closes #49 Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_01H3zbym8Doka2d7D48maSgZ	2026-07-21 01:13:19 -04:00
steve	f208da94d6	Revision history: change sets + revisions + revert — the undo substrate (#48) (#61) ... Co-authored-by: Steve Dudenhoeffer <[email protected]>	2026-07-21 05:07:30 +00:00
steve	e22bdd6cab	Copy a garden (deep duplicate) from the gardens list (#46) ... Co-authored-by: Steve Dudenhoeffer <[email protected]>	2026-07-21 03:58:39 +00:00
steveandClaude Fable 5	e71443311e	Add DESIGN.md and README overview ... Capture the v1 architecture: domain model, geometry, SVG editor with semantic zoom, REST API with version-guarded sync, service-layer seam for future majordomo/executus agent tools, OIDC-first auth (Authentik), and the phased roadmap. Co-Authored-By: Claude Fable 5 <[email protected]>	2026-07-18 14:11:46 -04:00