@7365admin1/layer-common 4.2.1-staging.259 → 4.2.1

package/CHANGELOG.md

@@ -1,5 +1,37 @@
 # @iservice365/layer-common
 
+## 4.2.1
+
+### Patch Changes
+
+- b16f792: `EntryPassMain`: add the Invitation Note toggle to the Self-Service settings tab (DV-0080).
+
+  A new Invitation Note row between Auto-Approvals and Printer Setup — a switch plus a note
+  textarea — persisting to `settings.onboarding.invitationNote` through the existing save
+  payload, which the API attaches to self-service contractors at registration.
+
+  The toggle saves immediately, matching the Auto-Approvals switch above it; the note text saves
+  on blur, since the section has no Save button of its own. Turning the toggle on with an empty
+  note is refused inline rather than saved, and turning it off keeps the text so flipping it back
+  on does not lose what was typed.
+
+- b16f792: `InvitationForm`: bind an invitation to a site the caller already knows, and stop `hideApp` deciding the app.
+
+  The `site` prop had been declared on the component since it was written and was never read
+  anywhere — `invite.site` was only ever filled by the Site picker. A caller that already knows
+  which site the invitation is for (onboarding step 6, "Invite Site Admin", which is about the
+  site created in step 4) had no way to say so, and the invitation went out unbound to any site.
+  The prop is now watched and wins over the picker; the picker still works when no site is passed.
+
+  `hideApp` hides the App field. It also overwrote the value with a literal
+  `"property_management_agency"`, so an organisation that hid the field could not choose what it
+  was hiding: a security, cleaning or landscaping client was invited into property management.
+  Hiding a field is not deciding it. `adminState: false` keeps its existing fallback — that flag
+  belongs to the organisation-admin invitation, a separate flow.
+
+  No new exported API: the prop already existed and no existing caller passes it, so this is a
+  behaviour correction inside an existing component rather than a new capability.
+
 ## 4.2.0
 
 ### Minor Changes
@@ -383,11 +415,11 @@
   `utils/console-tier.ts` + `composables/useConsoleTier.ts` mirror the server's
   own rule from two endpoints the console already calls, unprojected:
 
-                GET /api/members/user/:user/app/admin    the Seven365 staff membership
-                GET /api/roles/id/:role                  that membership's role document
+                  GET /api/members/user/:user/app/admin    the Seven365 staff membership
+                  GET /api/roles/id/:role                  that membership's role document
 
-                owner  = member.type === "admin" && role.type === "admin" && role.default === true
-                staff  = member.type === "admin" && role.type === "admin"
+                  owner  = member.type === "admin" && role.type === "admin" && role.default === true
+                  staff  = member.type === "admin" && role.type === "admin"
 
   `role.default` is the marker because it is the only property of a platform
   staff role no API caller can set - `role.controller.ts` validates create and

package/package.json

@@ -2,7 +2,7 @@
   "name": "@7365admin1/layer-common",
   "license": "MIT",
   "type": "module",
-  "version": "4.2.1-staging.259",
+  "version": "4.2.1",
   "author": "7365admin1",
   "main": "./nuxt.config.ts",
   "//files": "What a consumer extending this layer actually loads. Without this npm ships the whole working tree - the changesets, the CI workflows, the render harness in tools/ and any scratch directory that happened to exist at publish time. Nuxt resolves a layer by directory, so every runtime directory below has to stay listed; adding a new top-level runtime directory means adding it here too.",