@htilabs/platform-common-models 0.80.0 → 0.82.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 +27 -0
- package/dist/{index-DvAypMJV.d.ts → index-Bh1zO_Vu.d.ts} +1 -1
- package/dist/{index-Bj-s0nZy.d.cts → index-XWSYon40.d.cts} +1 -1
- package/dist/index.cjs +365 -47
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +3 -3
- package/dist/index.d.ts +3 -3
- package/dist/index.js +355 -47
- package/dist/index.js.map +1 -1
- package/dist/information-scope/index.cjs +290 -2
- package/dist/information-scope/index.cjs.map +1 -1
- package/dist/information-scope/index.d.cts +84 -1
- package/dist/information-scope/index.d.ts +84 -1
- package/dist/information-scope/index.js +279 -1
- package/dist/information-scope/index.js.map +1 -1
- package/dist/models/index.d.cts +2 -2
- package/dist/models/index.d.ts +2 -2
- package/dist/schemas/index.d.cts +25 -25
- package/dist/schemas/index.d.ts +25 -25
- package/dist/services/index.cjs +290 -2
- package/dist/services/index.cjs.map +1 -1
- package/dist/services/index.d.cts +1 -1
- package/dist/services/index.d.ts +1 -1
- package/dist/services/index.js +279 -1
- package/dist/services/index.js.map +1 -1
- package/dist/sharing-ceiling/index.cjs +33 -3
- package/dist/sharing-ceiling/index.cjs.map +1 -1
- package/dist/sharing-ceiling/index.d.cts +11 -7
- package/dist/sharing-ceiling/index.d.ts +11 -7
- package/dist/sharing-ceiling/index.js +33 -3
- package/dist/sharing-ceiling/index.js.map +1 -1
- package/package.json +1 -1
- package/src/generated/informationScopeUiCopy.ts +263 -0
- package/src/services/__tests__/informationScopeUiCopy.test.ts +128 -0
- package/src/services/informationScope.ts +1 -0
- package/src/services/informationScopeUiCopy.ts +98 -0
- package/src/sharingCeiling/__tests__/fixtures_starterVerdicts.json +1727 -0
- package/src/sharingCeiling/__tests__/personContactRows.test.ts +185 -0
- package/src/sharingCeiling/coverage.ts +55 -6
- package/src/sharingCeiling/resolve.ts +31 -8
- package/dist/{cvcEntry-BLeRivoF.d.cts → cvcEntry-D787utvP.d.cts} +8 -8
- package/dist/{cvcEntry-BLeRivoF.d.ts → cvcEntry-D787utvP.d.ts} +8 -8
package/README.md
CHANGED
|
@@ -16,6 +16,33 @@ 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.82.0 — the Information scope page's words and order: each category's one-line description, the hint under some rows, and canon's row order (additive, `./information-scope`; CVC-236 `core-information_scope` unchanged)
|
|
20
|
+
|
|
21
|
+
**What changed.** The Admin Hub's Information scope page could not draw three things the prototype draws, because the CVC-236 SOT does not carry them: the line under each category title ("Session timestamps, source info — always shared"), the hint under ten rows (System info → "Always included"), and canon's row order inside a category (the SOT lists a category's children in code order, so Narrative notes and Health & accommodation came out reversed). `./information-scope` (and `./services`, the root) now export them:
|
|
22
|
+
|
|
23
|
+
- `scopeCategorySub(category)` · `scopeRowHint(row)` · `scopeRowDisplayOrder(category)` (selection codes, canon order) · `sortScopeRows(category, rows)` · `sortScopeCategories(categories)` — each takes either spelling (`identifying.other` or `identifying__other`).
|
|
24
|
+
- The data: `INFORMATION_SCOPE_CATEGORY_ORDER` · `INFORMATION_SCOPE_CATEGORY_SUB` · `INFORMATION_SCOPE_ROW_ORDER` · `INFORMATION_SCOPE_ROW_HINT` (package keys), GENERATED in `src/generated/informationScopeUiCopy.ts` by `scripts/gen-information-scope-ui-copy.py <prototype root> <platform-prototype root>` (`--check` compares data). Order comes from the records repo's CVC-236 tree (`data/cvcs/core_information_scope.yaml`); the words from the Platform prototype's `sharing.scopeCatalog` `sub` / `hint`, where they are authored (the records repo's `build_information_scope_registry.py` preserves them by id). The generator refuses when the two copies disagree on a category, a row or an order. Text is carried as written.
|
|
25
|
+
- `src/services/__tests__/informationScopeUiCopy.test.ts` holds every key to a live SOT row, every category's order to exactly its live rows, and every hint to an ordered row — a codebook change fails the build instead of orphaning copy.
|
|
26
|
+
|
|
27
|
+
Nothing existing changes: the SOT JSON, `scopeRowsFromSot` and every existing export read as before.
|
|
28
|
+
|
|
29
|
+
## 0.81.0 — an internal referral carries other people's phones and emails again: the per-kind "Contact & safety" rows are no longer withheld as "under the platform safety floor" (sharing ceiling; CVC-236 `core-information_scope` unchanged)
|
|
30
|
+
|
|
31
|
+
**What changed.** Another person's phones, emails and contact log (the person who caused harm, an eligible family member, another person on the case) ride that person's **Contact & safety** row (`offenders.contact` · `family.contact` · `others.contact`): canon homes them on `contact_info` and rule 1 routes them to the deepest per-kind row whose `kindRow` is that home or an ancestor (prototype `resolveHome`; the scope tree, `INFOSCOPE_TREE_V4_PROPOSAL_2026-10-08.md`: "offenders.contact — their phones / emails — shareable yes"). Each of those rows has one child, `<kind>.safe_locations`, the platform floor. `resolveShare` counted that one floor child as "every leaf withheld" and withheld the whole row ("Never shared — under the platform safety floor"), so `shareRowCeiling` never listed it and Thread's and PAVE's composers masked it away: an internal share under the inside starter offered 3 fewer categories than the prototype's full record (`shareFullRecordIds`, whose catalog lists no floor row) and carried no other person's phone or email.
|
|
32
|
+
|
|
33
|
+
- `hasOwnScopeContent` reads rule 1 as canon does: a per-kind row holds every client field home that routes to it (`contact_info` → `<kind>.contact`). Rows with no children gain the flag too (`<kind>.services`, `<kind>.instrument_summary`, …); no verdict reads it there.
|
|
34
|
+
- `resolveShare`'s group flip skips a category that has fields of its own and whose every leaf is under the floor.
|
|
35
|
+
- `shareRowCeiling` lists such a category itself (only floor rows withheld beneath it).
|
|
36
|
+
- The floor still never leaves: under a bound ceiling a row under the floor is within only when the list names it itself, never through a listed ancestor, and `maskSelectionToCeiling` drops a floor row the ceiling does not name.
|
|
37
|
+
|
|
38
|
+
**Verdicts that move (platform starter, no account rule; every other verdict pinned unchanged in `src/sharingCeiling/__tests__/fixtures_starterVerdicts.json`):**
|
|
39
|
+
|
|
40
|
+
| Purpose × recipient | Now allowed |
|
|
41
|
+
|---|---|
|
|
42
|
+
| every purpose, inside the account (`sibling_team`) | `offenders.contact` · `family.contact` · `others.contact` |
|
|
43
|
+
| `mandatory_reporting`, `authority_reporting` to a partner or off-platform | `family.contact` (the starter lists the whole Eligible family members branch, `family`) |
|
|
44
|
+
|
|
45
|
+
Note: the Platform prototype's `HTI_SHARE_POLICY_API.effectiveCeiling` (`src/data.js`) counts the floor item in its group flip and would still withhold these rows; the monolith, which builds and sends the share, never does. This release follows the monolith and the scope-tree ruling.
|
|
19
46
|
## 0.80.0 — seatAppAccess: a seat's app access from its teams, inside the account's grant (additive, `./authz` and the root)
|
|
20
47
|
|
|
21
48
|
**What changed.** One shared answer to "may this person open this app?" for Thread's and PAVE's sign-in doors and the platform's app tiles (Kickoff 08c), so the three stop deciding from the Auth0 role alone.
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
import { F as Form, l as buildFormSchema, h as Section, q as buildSectionSchema, Q as Question, o as buildQuestionSchema, f as ScoringRule, p as buildScoringRuleSchema, P as PlatformFunction, m as buildPlatformFunctionSchema, d as PlatformRole, n as buildPlatformRoleSchema, b as CvcRegistry, k as buildCvcRegistrySchema, a as CvcEntry, j as buildCvcEntrySchema } from './cvcEntry-
|
|
1
|
+
import { F as Form, l as buildFormSchema, h as Section, q as buildSectionSchema, Q as Question, o as buildQuestionSchema, f as ScoringRule, p as buildScoringRuleSchema, P as PlatformFunction, m as buildPlatformFunctionSchema, d as PlatformRole, n as buildPlatformRoleSchema, b as CvcRegistry, k as buildCvcRegistrySchema, a as CvcEntry, j as buildCvcEntrySchema } from './cvcEntry-D787utvP.js';
|
|
2
2
|
import * as mongoose from 'mongoose';
|
|
3
3
|
import { HydratedDocument, Connection, Model } from 'mongoose';
|
|
4
4
|
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
import { F as Form, l as buildFormSchema, h as Section, q as buildSectionSchema, Q as Question, o as buildQuestionSchema, f as ScoringRule, p as buildScoringRuleSchema, P as PlatformFunction, m as buildPlatformFunctionSchema, d as PlatformRole, n as buildPlatformRoleSchema, b as CvcRegistry, k as buildCvcRegistrySchema, a as CvcEntry, j as buildCvcEntrySchema } from './cvcEntry-
|
|
1
|
+
import { F as Form, l as buildFormSchema, h as Section, q as buildSectionSchema, Q as Question, o as buildQuestionSchema, f as ScoringRule, p as buildScoringRuleSchema, P as PlatformFunction, m as buildPlatformFunctionSchema, d as PlatformRole, n as buildPlatformRoleSchema, b as CvcRegistry, k as buildCvcRegistrySchema, a as CvcEntry, j as buildCvcEntrySchema } from './cvcEntry-D787utvP.cjs';
|
|
2
2
|
import * as mongoose from 'mongoose';
|
|
3
3
|
import { HydratedDocument, Connection, Model } from 'mongoose';
|
|
4
4
|
|