@outbuild-company/schedule-core 1.6.2 → 1.6.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -27,6 +27,32 @@ A change that touches both this repo and the react_client bridge is two commits:
27
27
 
28
28
  Locally nothing else is needed — the link always reflects your working tree.
29
29
 
30
+ ### Persistence boundary
31
+
32
+ This package owns the schedule domain, derived calculations and the persisted
33
+ checkpoint used by `hasUnsavedChanges()` / `getModifiedActivities()`. It does
34
+ not issue HTTP requests or build ProPlanner's private save DTO.
35
+
36
+ The consuming bridge in `pp2_node-schedule-core` owns the reverse translation:
37
+
38
+ ```text
39
+ ScheduleCore
40
+ → scheduleActions.getActivities() / getLinks()
41
+ → convertCoreActivityToActivity / convertCoreLinkToActivityRelation
42
+ → POST activitys/updateAllScheduleData
43
+ ```
44
+
45
+ The save reads all live activities and links from ScheduleCore, not from
46
+ DHTMLX. DHTMLX contributes only transient visual progress flags. The bridge
47
+ also injects `sectorId` and `ganttId`; authenticated company ownership,
48
+ timestamps and related entities remain server concerns.
49
+
50
+ `PersistableActivity` is therefore a dirty-check snapshot, not a network DTO.
51
+ End-to-end save/reload compatibility must be certified in the consuming bridge
52
+ and server repository.
53
+
54
+ _added: 2026-07-31T20:27:29Z_
55
+
30
56
  ## Build
31
57
 
32
58
  ```