Git-synced wiki

A Sunstone Web deployment can be backed by a git remote instead of a plain folder. The server clones the repository on startup, commits every save as the signed-in user, and keeps reconciling with the remote: it fetches, rebases and pushes. Edits made in the browser and changes pushed from a clone converge on their own. Nothing runs beside it: no sidecar, no hook, no manual step.

Conflicts never block a save

It isn't real-time co-editing; concurrent work reconciles through rebase. When a browser edit and an incoming change touch the same Concept, the remote keeps the original name and your version is written beside it as an ordinary Concept (notes/foo-20260727T101500Z.md). It shows up in the tree, search and quick nav, and the editor tells you about it. History still holds every author's edit.

Everything is git

$ git log --oneline docs/
a41f2c9 web: edit concepts/rollout-plan.md (dana)
7be03d1 web: edit concepts/rollout-plan.md (jonas)
f19c884 sync: rebase onto origin/main

Anything the wiki did, you can inspect, revert or bisect from the command line. Changes pushed to the remote reach every connected reader within one sync interval.