@7365admin1/layer-common 3.2.2-staging.122 → 3.2.2-staging.124

package/components/ScheduleTaskAreaFormDialog.vue

@@ -1,141 +0,0 @@
-<template>
-  <v-dialog
-    :model-value="modelValue"
-    @update:model-value="(v) => emit('update:modelValue', v)"
-    max-width="520"
-  >
-    <!-- 520px is the handoff's `--modal-w`, and the card wears `.screen-modal`
-         for the 16px corner, the `--card` surface and the modal shadow. The
-         two `v-toolbar`s standing in for the title row and the footer were
-         fixed grey slabs that stay grey on the dark theme, and the Create
-         button was a hardcoded `color="black"` fill on a `rounded-0` square. -->
-    <v-card class="screen-modal">
-      <template v-if="$slots.header">
-        <slot
-          name="header"
-          :title="
-            mode === 'edit' ? `Edit ${entityType}` : `Add New ${entityType}`
-          "
-          :onClose="onClose"
-        />
-      </template>
-      <v-card-title v-else class="text-capitalize">{{
-        mode === "edit" ? `Edit ${entityType}` : `Add New ${entityType}`
-      }}</v-card-title>
-
-      <v-card-text class="screen-modal__body">
-        <v-form ref="formRef" v-model="valid">
-          <v-row>
-            <v-col cols="12">
-              <InputLabel for="name" :title="label" required />
-              <!-- Still a `v-text-field`: Submit is gated on `valid`, which
-                   only exists because this `:rules` runs. `.filter-field` gives
-                   it the design's 40px / 10px / 13.5px shape without taking the
-                   validation away. -->
-              <v-text-field
-                v-model="nameValue"
-                class="filter-field"
-                :rules="[requiredRule]"
-              />
-            </v-col>
-          </v-row>
-        </v-form>
-      </v-card-text>
-
-      <div class="screen-modal__footer">
-        <v-btn
-          variant="outlined"
-          class="screen-btn-ghost"
-          @click="close"
-        >
-          Cancel
-        </v-btn>
-
-        <!-- Kept a `v-btn`: `loading` is the only in-flight signal this form
-             has, and `AppButton` has no equivalent. -->
-        <v-btn
-          variant="flat"
-          class="screen-btn-primary"
-          :loading="submitting"
-          @click="submit"
-        >
-          {{ mode === "edit" ? "Save" : "Create" }}
-        </v-btn>
-      </div>
-    </v-card>
-  </v-dialog>
-</template>
-
-<script setup lang="ts">
-const props = defineProps({
-  modelValue: { type: Boolean, required: true },
-  mode: { type: String as PropType<"add" | "edit">, default: "add" },
-  area: { type: Object as PropType<Record<string, any> | null>, default: null },
-  label: { type: String, default: "Name" },
-  nameModel: { type: String as PropType<string | null>, default: null },
-  entityType: { type: String, default: "Area" }, // values: "Area", "Unit"
-});
-
-const emit = defineEmits([
-  "update:modelValue",
-  "saved",
-  "update:nameModel",
-] as const);
-
-const formRef = ref(null);
-const valid = ref(false);
-const submitting = ref(false);
-
-const form = reactive({ name: "", description: "", status: "active" });
-
-watchEffect(() => {
-  if (props.area) {
-    form.name = props.area.name || "";
-    form.description = props.area.description || "";
-    form.status = props.area.status || "active";
-  } else {
-    form.name = "";
-    form.description = "";
-    form.status = "active";
-  }
-});
-
-const { requiredRule } = useUtils();
-
-const nameValue = computed({
-  get: () => {
-    return props.nameModel !== null ? props.nameModel : form.name;
-  },
-  set: (v: string) => {
-    if (props.nameModel !== null) {
-      emit("update:nameModel", v);
-    } else {
-      form.name = v;
-    }
-  },
-});
-
-function close() {
-  emit("update:modelValue", false);
-}
-
-const onClose = () => close();
-
-async function submit() {
-  if (!valid.value) return;
-  submitting.value = true;
-  try {
-    await new Promise((r) => setTimeout(r, 500));
-    emit("saved", { ...form, _id: props.area?._id || Date.now().toString() });
-
-    form.name = "";
-    form.description = "";
-    form.status = "active";
-
-    emit("update:modelValue", false);
-  } catch (e) {
-  } finally {
-    submitting.value = false;
-  }
-}
-</script>

package/components/ScheduleTaskAreaUpdateMoreAction.vue

@@ -1,104 +0,0 @@
-<template>
-  <!-- The schedule-area copy of `Dialog/UpdateMoreAction`, converted the same
-       way: two `v-toolbar`s (fixed grey slabs that stay grey on the dark
-       theme) for the title row and the footer, and a hardcoded `color="black"`
-       fill on a square 48px tile. -->
-  <v-card class="screen-modal" width="100%">
-    <template v-if="$slots.header">
-      <slot name="header" :title="title" :onClose="onClose" />
-    </template>
-    <v-card-title v-else class="text-capitalize">{{ title }}</v-card-title>
-
-    <v-card-text class="screen-modal__body pb-0">
-      <slot name="content" />
-    </v-card-text>
-
-    <div class="screen-modal__footer">
-      <v-btn
-        variant="outlined"
-        class="screen-btn-ghost"
-        @click="emit('close')"
-      >
-        Close
-      </v-btn>
-
-      <v-menu>
-        <template #activator="{ props }">
-          <v-btn
-            variant="flat"
-            class="screen-btn-primary"
-            v-bind="props"
-          >
-            More actions
-          </v-btn>
-        </template>
-
-        <!-- Dropdown shape left as Vuetify draws it - the handoff specifies
-             the profile dropdown only. `text-red` (Vuetify's fixed #f44336,
-             the same red on both themes) becomes `text-error`, which is
-             `--v-theme-error`, i.e. the design's `--err`, matching the
-             handoff's "red Logout row (err color, err-bg hover)". -->
-        <v-list class="pa-0 area-more__list">
-          <v-list-item v-if="canUpdate" @click="emit('edit')">
-            <v-list-item-title>
-              {{ editButtonLabel }}
-            </v-list-item-title>
-          </v-list-item>
-
-          <v-list-item
-            v-if="canDelete"
-            @click="emit('delete')"
-            class="text-error"
-          >
-            <v-list-item-title>
-              {{ deleteButtonLabel }}
-            </v-list-item-title>
-          </v-list-item>
-        </v-list>
-      </v-menu>
-    </div>
-  </v-card>
-</template>
-
-<script setup lang="ts">
-const prop = defineProps({
-  canUpdate: {
-    type: Boolean,
-    default: true,
-  },
-  canDelete: {
-    type: Boolean,
-    default: true,
-  },
-  editButtonLabel: {
-    type: String,
-    default: "Edit Area",
-  },
-  deleteButtonLabel: {
-    type: String,
-    default: "Delete Area",
-  },
-  title: {
-    type: String,
-    default: "Area Actions",
-  },
-});
-
-const emit = defineEmits(["close", "manage", "edit", "delete"]);
-const {
-  canUpdate,
-  editButtonLabel,
-  deleteButtonLabel,
-  manageButtonLabel,
-  title,
-} = prop;
-</script>
-
-<style scoped>
-/* `text-subtitle-2` was Vuetify's 0.875rem/500; the handoff names no type for
-   a menu row, so it takes the established cell type. */
-.area-more__list :deep(.v-list-item-title) {
-  font-size: var(--fs-cell);
-  font-weight: var(--fw-cell);
-}
-</style>

package/components/TableWithButton.vue

@@ -1,94 +0,0 @@
-<template>
-  <v-card flat border="sm black" :loading="loading" class="px-0" :ripple="false">
-    <v-toolbar class="px-5">
-      <template #prepend>
-        <span class="text-subtitle-1 font-weight-black">{{ tableTitle }}</span>
-      </template>
-      <template #append>
-        <v-btn color="primary" variant="flat" size="large" density="comfortable" :text="buttonLabel"
-          class="text-capitalize" />
-      </template>
-    </v-toolbar>
-    <v-card-text class="pa-0 bg-red">
-      <v-data-table :headers="headers" :items="items" :item-value="itemValue" :items-per-page="itemsPerPage"
-        fixed-header hide-default-footer hide-default-header @click:row="$emit('row-click', $event)"
-        style="max-height: calc(100vh - (200px))">
-        <template v-for="(_, slotName) in $slots" #[slotName]="slotProps">
-          <slot :name="slotName" v-bind="slotProps" />
-        </template>
-      </v-data-table>
-    </v-card-text>
-  </v-card>
-</template>
-
-<script setup lang="ts">
-const selected = defineModel({
-  type: Array as PropType<Array<string>>,
-  default: () => [],
-});
-const page = defineModel("page", { type: Number, default: 0 });
-
-const props = defineProps({
-  headers: {
-    type: Array as PropType<Array<Record<string, string | number>>>,
-    required: true,
-    default: () => [],
-  },
-  items: {
-    type: Array as PropType<Array<Record<string, any>>>,
-    required: true,
-    default: () => [],
-  },
-
-  itemValue: {
-    type: String,
-    default: "_id",
-  },
-    itemsPerPage: {
-    type: Number,
-    default: 20,
-  },
-  loading: {
-    type: Boolean,
-    required: true,
-    default: true,
-  },
-  tableTitle: {
-    type: String,
-    default: "",
-    required: false
-  },
-  buttonLabel: {
-    type: String,
-    default: "Add",
-    required: false
-  }
-});
-
-const emit = defineEmits(["refresh", "update:pagination", "row-click"]);
-
-function increment() {
-  page.value++;
-  emit("update:pagination", page.value);
-}
-
-function decrement() {
-  page.value--;
-  emit("update:pagination", page.value);
-}
-
-function tableRowClickHandler(_: any, row: any) {
-  const item = props.items[row.index];
-  emit("row-click", item);
-}
-
-const selectAll = ref(false);
-
-watch(selectAll, (curr) => {
-  selected.value.splice(0, selected.value.length);
-  if (curr) {
-    const ids = props.items.map((i) => i._id as string);
-    selected.value.push(...ids);
-  }
-});
-</script>

package/test/visitor-socket.test.mjs

@@ -1,36 +0,0 @@
-import assert from "node:assert/strict";
-import { test } from "node:test";
-
-import { cameraAlertMessage } from "./.build/useVisitorSocket.mjs";
-
-/*
- * The reported symptom was one camera raising a red toast every 10 seconds on
- * an unrelated page. API-core now paces the alert; this side has to make sure
- * several cameras failing at once still cannot become several snackbars.
- */
-
-test("nothing is shown when no camera is down", () => {
-  assert.equal(cameraAlertMessage([]), "");
-});
-
-test("one failing camera shows the server's own message, which names it", () => {
-  const text = "The entry and exit ANPR camera at Seventh Condominium is not responding.";
-  assert.equal(cameraAlertMessage([text]), text);
-});
-
-test("several failing cameras collapse into a single line", () => {
-  const many = ["camera one is down", "camera two is down", "camera three is down"];
-  const text = cameraAlertMessage(many);
-  assert.match(text, /^3 cameras at this site are not responding/);
-  for (const message of many) assert.doesNotMatch(text, new RegExp(message));
-});
-
-test("the collapsed line points at the page that lists them", () => {
-  assert.match(cameraAlertMessage(["a", "b"]), /Site Settings > Cameras/);
-});
-
-test("no camera message tells the operator to deactivate anything", () => {
-  for (const messages of [["a camera is down"], ["a", "b"]]) {
-    assert.doesNotMatch(cameraAlertMessage(messages), /inactive|deactivat/i);
-  }
-});

package/tools/render-harness/README.md

@@ -1,87 +0,0 @@
-# Render harness hardening
-
-Tooling, not product code. Nothing here ships in `@7365admin1/layer-common` and
-nothing here is imported by any component — it exists to stop the theme-review
-harness reporting a pass it has not earned.
-
-The harness itself (vite + Vuetify + a mirror of this package, driven by
-Playwright) lives outside the repo, under
-`_scratch-theme-review/harness`. These four files attach to it.
-
-| File | What it does |
-|---|---|
-| `harness-init.ps1` | Makes a private harness for one worktree: fork directory and dev port both derived from the worktree path, own vite cache, mirror stamped with what was synced. |
-| `render-check.mjs` | The run. Refuses to measure an unprovable mirror, then measures each screen at 360/768/1024/1440 × light/dark. |
-| `probe.mjs` | The in-page half — what is actually read off the glass. |
-| `render-check.selftest.mjs` | Proves every detector fails the scenario it was written for. `node render-check.selftest.mjs`, no server needed. |
-| `baselines.json` | Per-screen recorded element and painted-text counts. |
-
-## Use
-
-```powershell
-cd <worktree>
-..\iservice365-layer-common\tools\render-harness\harness-init.ps1     # prints fork + port
-Start-Process -WorkingDirectory <fork> cmd.exe -ArgumentList '/c','npx vite --port <port> --strictPort'
-cd <fork>; $env:PORT=<port>
-node render-check.mjs <label> CameraMain NotificationSettings
-```
-
-Re-run `harness-init.ps1` after any edit to `assets`, `components`,
-`composables`, `constants`, `types` or `utils` — `render-check.mjs` compares the
-mirror to the worktree file by file and refuses to run when they disagree.
-
-## What each guard is for
-
-Every one of these was a real false pass on 2026-08-14, not a hypothetical.
-
-- **Shared mirror.** One `lc/` copy meant two agents silently measured each
-  other's branch. Isolation is now derived from the worktree, so there is
-  nothing to remember, and the mirror carries a stamp the run checks.
-- **Empty state.** A panel scored 8/8 dark-clean while drawing "No access logs
-  found". A table was signed off with zero header columns and "No data
-  available", so the header and cell rules under review had never been drawn. A
-  screen showing its empty state is a fixture bug and fails.
-- **Empty form.** The same bug in a shape nothing else can see — 1112 elements,
-  nothing blank, and not one control holding a value.
-- **Blank screen.** Six elements, zero page errors, and a counter read it as a
-  pass. Painted text is the honest signal.
-- **Element counts.** `MIN_ELS = 20` was at once too low (a cold partial paint
-  at 32 scored ok where warm is 49) and too high (a drawing screen at 19 was
-  reported NOT-MOUNTED). Screens legitimately range from 3 to 1100 elements, so
-  each carries its own baseline and an un-baselined screen is refused rather
-  than guessed at.
-- **Cold compile.** The run waits for the DOM to stop growing instead of a fixed
-  timeout, warms every screen first, prints the discarded warm-up numbers so the
-  gap is visible, and re-measures any row well under that screen's own best.
-- **Undefined custom properties.** `var(--success)` where the token is `--ok`:
-  the declaration is invalid, the element inherits, and nothing reports it. Now
-  caught even when the rule matches nothing on the screen — which is how the
-  original survived a full 8-shot render.
-- **Disabled controls.** WCAG-1.4.3-exempt, so logging them as failures put
-  fictional entries in an AA ledger. Classified as exempt, and the enabled state
-  is probed separately so the exemption cannot hide a real failure.
-- **Vuetify defaults.** `VAutocomplete` was missing from the harness, and 19
-  components in this package use one — the run would have invented a defect the
-  product does not have. The defaults are diffed against `plugins/vuetify.ts`
-  every run.
-
-## Baselines
-
-`--record` writes the current run's element and painted-text counts:
-
-```powershell
-node render-check.mjs --record base CameraMain
-```
-
-Only record from a run whose **screenshots you have opened**. A baseline
-recorded from a broken render makes the break permanent. A conversion that
-genuinely shrinks a screen below 70% of its baseline will flag — look at the
-shot, then re-record.
-
-`baselines.json` accepts `"allowEmpty": true` per screen for the rare component
-whose empty state IS the thing under review.
-
-## Rule that does not bend
-
-Fixtures are harness-only. Package code is never bent to suit the harness. If a
-screen will not draw, the fixture is wrong.

package/tools/render-harness/baselines.json

@@ -1,117 +0,0 @@
-{
-  "CameraMain": {
-    "els": 55,
-    "textChars": 85,
-    "recordedFrom": "0642279"
-  },
-  "NotificationSettings": {
-    "els": 150,
-    "textChars": 485,
-    "recordedFrom": "0642279"
-  },
-  "OvernightParkingAvailability": {
-    "els": 1132,
-    "textChars": 385,
-    "recordedFrom": "0642279"
-  },
-  "BulletinExpirationChip": {
-    "els": 3,
-    "textChars": 2,
-    "recordedFrom": "0642279"
-  },
-  "AccessCardAssignToUnitForm": {
-    "els": 177,
-    "textChars": 131,
-    "recordedFrom": "178ebf0"
-  },
-  "AccessCardReplaceForm": {
-    "els": 68,
-    "textChars": 83,
-    "recordedFrom": "178ebf0"
-  },
-  "AddEqupmentForm": {
-    "els": 90,
-    "textChars": 99,
-    "recordedFrom": "178ebf0"
-  },
-  "BuildingForm": {
-    "els": 126,
-    "textChars": 69,
-    "recordedFrom": "178ebf0"
-  },
-  "BulletinBoardForm": {
-    "els": 172,
-    "textChars": 165,
-    "recordedFrom": "178ebf0"
-  },
-  "CameraForm": {
-    "els": 127,
-    "textChars": 80,
-    "recordedFrom": "178ebf0"
-  },
-  "DocumentForm": {
-    "els": 52,
-    "textChars": 57,
-    "recordedFrom": "178ebf0"
-  },
-  "InvitationClientForm": {
-    "els": 101,
-    "textChars": 47,
-    "recordedFrom": "178ebf0"
-  },
-  "InvitationForm": {
-    "els": 86,
-    "textChars": 43,
-    "recordedFrom": "178ebf0"
-  },
-  "ServiceProviderFormCreate": {
-    "els": 51,
-    "textChars": 38,
-    "recordedFrom": "178ebf0"
-  },
-  "AcceptDialog": {
-    "els": 24,
-    "textChars": 106,
-    "recordedFrom": "178ebf0"
-  },
-  "Card/DeleteConfirmation": {
-    "els": 21,
-    "textChars": 129,
-    "recordedFrom": "178ebf0"
-  },
-  "Dialog/DeleteConfirmation": {
-    "els": 21,
-    "textChars": 129,
-    "recordedFrom": "178ebf0"
-  },
-  "HidAccessLogDashboard": {
-    "els": 172,
-    "textChars": 437,
-    "recordedFrom": "178ebf0"
-  },
-  "HidIntercomManagement": {
-    "els": 148,
-    "textChars": 167,
-    "recordedFrom": "178ebf0"
-  },
-  "HidUserEnrollment": {
-    "els": 142,
-    "textChars": 287,
-    "recordedFrom": "178ebf0"
-  },
-  "HidReaderManagement": {
-    "els": 112,
-    "textChars": 377,
-    "recordedFrom": "178ebf0"
-  },
-  "HidQrCodeConfiguration": {
-    "els": 106,
-    "textChars": 453,
-    "recordedFrom": "178ebf0"
-  },
-  "HidServiceSettingsPanel": {
-    "els": 18,
-    "textChars": 164,
-    "recordedFrom": "178ebf0"
-  }
-}