Expose project revision timeline

docs/circuit-list-editor-api.md

@@ -14,6 +14,16 @@ this value for optimistic concurrency checks.
 - `GET /projects/:projectId/history`
   - returns `currentRevision`, `undoDepth`, `redoDepth` and the current top
     change-set id for both persistent stacks
+- `GET /projects/:projectId/history/revisions`
+  - returns revision metadata in descending `revisionNumber` order
+  - optional query: `limit` (default `25`, maximum `100`) and exclusive
+    `beforeRevision`
+  - returns `projectId`, `currentRevision`, `revisions` and
+    `nextBeforeRevision`; use the latter as the next page's
+    `beforeRevision`
+  - each revision contains ids, number, timestamp, actor, source, description,
+    command type and payload schema version
+  - stored forward/inverse command payloads are intentionally not exposed
 - `POST /projects/:projectId/commands`
   - executes a supported versioned command as a new user revision
   - body: `{ "expectedRevision": 0, "command": { ... } }`

docs/circuit-list-editor-known-limitations.md

@@ -4,8 +4,9 @@
   persistent project commands and project-wide toolbar undo/redo, including
   moves, atomic multi-section reorders and explicit renumbering. Undo/redo
   eligibility is restored from server history after a page reload.
-- There is no browsable revision timeline yet; the editor currently exposes
-  only the next eligible Undo/Redo actions.
+- A paginated revision-metadata API exists, but there is no browsable timeline
+  UI yet; the editor currently exposes only the next eligible Undo/Redo
+  actions.
 - Named logical project snapshots and restore are not implemented yet.
 - No Revit/CSV/IFCGUID import and export workflow is implemented yet.
 - Persistence currently targets local SQLite; PostgreSQL is an architectural option, not an implemented runtime.

docs/current-architecture.md

@@ -78,7 +78,9 @@ Gerätezeilen-Kommandos bewahren dabei auch lokale ProjectDevice-Overrides und
 prüfen Projektzugehörigkeit von Verknüpfungen und Räumen. Projektweite,
 persistente Undo-/Redo-Stacks verwalten die zulässige LIFO-Reihenfolge und
 verwerfen den Redo-Zweig bei einem neuen Benutzerkommando. Ihr Status ist über
-`GET /api/projects/:projectId/history` lesbar. Ein zentraler Dispatcher führt
+`GET /api/projects/:projectId/history` lesbar. Die unveränderliche,
+absteigend paginierte Revisions-Timeline ist ohne Befehls-Payloads über
+`GET /api/projects/:projectId/history/revisions` lesbar. Ein zentraler Dispatcher führt
 die unterstützten Typen `circuit.update` und `circuit-device-row.update` über
 öffentliche Command-, Undo- und Redo-Endpunkte aus. Zusätzlich sind
 `circuit-device-row.insert` und `circuit-device-row.delete` als atomare

docs/project-history-and-external-model-architecture.md

@@ -170,6 +170,9 @@ Completed foundation:
   a forced stack failure rolls all of them back
 - `GET /api/projects/:projectId/history` exposes current revision, stack depths
   and top change-set ids
+- `GET /api/projects/:projectId/history/revisions` exposes a descending,
+  cursor-paginated metadata timeline without leaking persisted forward or
+  inverse command payloads
 - a central application dispatcher executes the supported `circuit.update`
   and `circuit-device-row.update` envelopes without coupling the domain service
   to SQLite
@@ -226,7 +229,7 @@ Completed foundation:
 
 Remaining constraints before completing project version history:
 
-- add a browsable revision timeline plus named logical snapshots and restore
+- add a browsable timeline UI plus named logical snapshots and restore
 - extend project-scoped commands only when further project mutations are
   deliberately added to history; the generic versioned envelope is complete
 - do not model IFCGUID as an overloaded circuit equipment identifier

docs/spec/07-implementation-phases-todo.md

@@ -364,6 +364,8 @@ Tasks:
 - [x] persist undo/redo eligibility on the server
 - [x] expose public command, undo and redo endpoints for the first supported
   update command types
+- [x] expose a cursor-paginated, read-only revision metadata timeline without
+  command payloads
 - add named and periodic logical project snapshots
 - restore a historical snapshot as a new revision
 - keep database backups separate from logical history
@@ -387,6 +389,8 @@ Implemented foundation:
   late-failure rollback coverage
 - a read-only project history endpoint exposes revision, stack depths and top
   change-set ids
+- a separate read-only timeline endpoint exposes immutable revision metadata
+  in descending, cursor-paginated pages without forward/inverse payloads
 - a central application dispatcher reconstructs persisted commands and exposes
   optimistic command, undo and redo endpoints for Circuit and CircuitDeviceRow
   field updates