Rewrite project documentation
This commit is contained in:
parent
30d6f1a2e1
commit
6b6d2c2a42
17 changed files with 535 additions and 221 deletions
|
|
@ -129,13 +129,19 @@ Drizzle schemas and migrations are dialect-specific and will require a deliberat
|
|||
|
||||
## Near-Term Refactoring Constraints
|
||||
|
||||
Before implementing the future features:
|
||||
Completed foundation:
|
||||
|
||||
- add real SQLite rollback tests around the persistence boundary
|
||||
- stop adding direct imports of the global SQLite client to domain services
|
||||
- extract transaction ownership from oversized repositories incrementally
|
||||
- modularize editor history commands independently from UI rendering
|
||||
- preserve stable domain IDs during legacy cleanup
|
||||
- real SQLite commit/rollback tests cover critical multi-write commands
|
||||
- transaction ownership for row moves, synchronization, renumbering and migration
|
||||
is isolated in injected persistence adapters
|
||||
- database backup and independent restore verification are automated
|
||||
- the Consumer application path is removed and stable domain IDs are preserved
|
||||
- editor grid projection and safety rules are separated from React rendering
|
||||
|
||||
Remaining constraints before implementing history:
|
||||
|
||||
- model project-scoped command descriptions independently from React callbacks
|
||||
- route all future history-enabled mutations through one project revision boundary
|
||||
- do not model IFCGUID as an overloaded circuit equipment identifier
|
||||
- keep database backup/restore checks separate from project history tests
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue