@htilabs/platform-common-models 0.67.0 → 0.68.0
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 +35 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -16,6 +16,41 @@ Package exports are organized into a public root API and a small number of
|
|
|
16
16
|
dedicated subpaths (`/validation`, `/cvcs`) — consult `package.json` for the
|
|
17
17
|
authoritative `exports` map.
|
|
18
18
|
|
|
19
|
+
## 0.68.0 — folding a copy into the real organization: the merge step (scripts only)
|
|
20
|
+
|
|
21
|
+
One record per real-world organization. Where the same organization was typed
|
|
22
|
+
in twice, a person names the copy and the row that is kept, and this step
|
|
23
|
+
folds the one into the other. Nothing in the published package changes; it is
|
|
24
|
+
all in `scripts/` (runbook: `scripts/FILL_ORG_REGISTRY_RUNBOOK.md`, "Folding
|
|
25
|
+
a copy into the real organization").
|
|
26
|
+
|
|
27
|
+
- `fill-org-registry --apply-merges <sheet.csv> [--thread-db <names>]
|
|
28
|
+
[--pave-db <names>]`. The sheet is written by a person (`source_db,
|
|
29
|
+
duplicate_id, duplicate_name, kept_id, kept_name, different_name_ok,
|
|
30
|
+
approved`); there is no propose step, and nothing works out which rows are
|
|
31
|
+
copies. Same standard as the other sheets: both names checked on every
|
|
32
|
+
line, another database's sheet refused, the whole plan printed before the
|
|
33
|
+
database name is asked for, before-images saved first, per-line results,
|
|
34
|
+
undo through `--rollback`.
|
|
35
|
+
- A merge is pure re-pointing (ruled 2026-10-20): every stored reference to
|
|
36
|
+
the copy's `_id` moves to the kept Org, in the stored form it had. The kept
|
|
37
|
+
row gains `legacy_ids.merged_from` (the copy's id) and nothing else. No
|
|
38
|
+
name, type, VSP answer or sharing rule is combined.
|
|
39
|
+
- The copy is deleted only when nothing in the platform database points at
|
|
40
|
+
it and every Thread and PAVE database was named and nothing there does
|
|
41
|
+
either. Otherwise it is kept, marked inactive (`status` 2), and the line
|
|
42
|
+
says which database could not be checked.
|
|
43
|
+
- Refused: a missing row; a name that is not the stored name; Thread's
|
|
44
|
+
development sample rows; a copy that is an Agency's own organization or has
|
|
45
|
+
programs; a kept row that is inactive or declined, or a unit of the copy; two
|
|
46
|
+
different names without `different_name_ok` = `yes` on the line; a kept row
|
|
47
|
+
the copy's users could not see (another Agency's list and no shared,
|
|
48
|
+
non-blank community); chains. A copy's identifier (`key`) and a sharing
|
|
49
|
+
grant naming it are never moved; either keeps the copy, inactive.
|
|
50
|
+
- A list that already names the kept Org loses the copy's id instead of naming
|
|
51
|
+
the kept Org twice; the undo puts the whole list back.
|
|
52
|
+
- Before-image files gain an optional `merges` list. Files from 0.65.0 to
|
|
53
|
+
0.67.0 still read.
|
|
19
54
|
## 0.67.0 — coreFunctions 1.6.0: four permission descriptions reworded (additive; codes, keys, titles and bounds unchanged)
|
|
20
55
|
|
|
21
56
|
**What changed.** Crysta approved new descriptions for four permissions on her
|