Implement persistent Line ordering for project specs and update bible

bible/02-architecture.md

@@ -144,7 +144,7 @@ This prevents selecting empty/incomplete snapshots and removes nondeterministic
 
 ### Principle
 
-Append-only: every save creates an immutable snapshot in `local_configuration_versions`.
+Append-only for **spec+price** changes: immutable snapshots are stored in `local_configuration_versions`.
 
 ```
 local_configurations
@@ -153,9 +153,11 @@ local_configurations
                               local_configuration_versions (v1)
 ```
 
-- `version_no = max + 1` on every save
+- `version_no = max + 1` when configuration **spec+price** changes
 - Old versions are never modified or deleted in normal flow
 - Rollback does **not** rewind history — it creates a **new** version from the snapshot
+- Operational updates (`line_no` reorder, server count, project move, rename)
+  are synced via `pending_changes` but do **not** create a new revision snapshot
 
 ### Rollback
 
@@ -181,6 +183,19 @@ local → pending → synced
 
 ---
 
+## Project Specification Ordering (`Line`)
+
+- Each project configuration has persistent `line_no` (`10,20,30...`) in both SQLite and MariaDB.
+- Project list ordering is deterministic:
+  `line_no ASC`, then `created_at DESC`, then `id DESC`.
+- Drag-and-drop reorder in project UI updates `line_no` for active project configurations.
+- Reorder writes are queued as configuration `update` events in `pending_changes`
+  without creating new configuration versions.
+- Backward compatibility: if remote MariaDB schema does not yet include `line_no`,
+  sync falls back to create/update without `line_no` instead of failing.
+
+---
+
 ## Sync Payload for Versioning
 
 Events in `pending_changes` for configurations contain: