Add virtualized Revit object planning
This commit is contained in:
parent
bfdd048269
commit
4ac32e103d
17 changed files with 277 additions and 9 deletions
|
|
@ -339,6 +339,11 @@ external model state atomically; its inverse powers persistent Undo/Redo
|
|||
without parsing workbook bytes. Apply retransmits and reparses the XLSX,
|
||||
verifies its preview SHA-256 and creates no circuit, equipment identifier or
|
||||
CircuitDeviceRow.
|
||||
R6 adds one compact project-wide external-object GET without pagination or
|
||||
batch payloads. The Revit page filters and sorts it in the client and renders a
|
||||
virtualized window. `external-object.update-planning` applies multi-object
|
||||
board, ProjectDevice and planning-value changes as one persistent command;
|
||||
linked objects are excluded because they follow their CircuitDeviceRow board.
|
||||
|
||||
The target configuration has no independent version counter; `expectedRevision`
|
||||
invalidates stale plans, and each import batch stores a configuration copy.
|
||||
|
|
@ -592,7 +597,7 @@ Critical target rules:
|
|||
selected combined/separate mode block export.
|
||||
- Missing GZF defaults visibly to 1 without separate confirmation.
|
||||
- The corrected R2 return workbook was successfully imported into Linear on
|
||||
2026-09-30; R3 through R5 are complete and R6 is the next package.
|
||||
2026-09-30; R3 through R6 are complete and R7 is the next package.
|
||||
- All confirmed writes use typed project commands with `expectedRevision`,
|
||||
complete inverse data and the shared project-command transaction boundary.
|
||||
- Do not add automatic circuit planning, Revit circuit adoption, multi-source
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue