hephaestus/docs/explanation
Erich Blume 00da36c637
All checks were successful
Build / validate (pull_request) Successful in 6m18s
doc(explanation): hub+spoke data-evolution / migration rules
Document why heph's op-based sync lets most new features (new link types,
read-side queries, optional payload fields) ship without a coordinated
migration across the hub and spokes, and the narrow case — a new required
SQLite column the apply path writes — that does need a hub-first rollout.

Groundwork for the indented/counted project sidebar, which is pure read-side
(existing parent links + a GROUP BY) and needs no migration.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-05 17:31:11 -07:00
..
design.md
explanation.md doc(explanation): hub+spoke data-evolution / migration rules 2026-06-05 17:31:11 -07:00
hub-spoke-data-evolution.md doc(explanation): hub+spoke data-evolution / migration rules 2026-06-05 17:31:11 -07:00
task-lifecycle.md