@7365admin1/layer-common 3.2.2-staging.121 → 3.2.2-staging.123

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"
-  }
-}

package/tools/render-harness/harness-init.ps1

@@ -1,127 +0,0 @@
-# Per-worktree render-harness isolation.
-#
-# WHY THIS EXISTS. The theme-review harness renders ONE `harness/lc/` mirror,
-# synced from a layer-common checkout by `sync-lc.ps1`. When two agents work at
-# once, the second `sync-lc.ps1` overwrites the first agent's mirror, and both
-# then measure whichever checkout synced last. That is silent - the run still
-# prints element counts, contrast readings and screenshots, all of the WRONG
-# branch. On 2026-08-14 it happened repeatedly, and every batch worked around it
-# by hand-forking the harness and hand-picking a port. Hand-picking is what
-# fails: forget it once and the whole run is fiction.
-#
-# So: isolation is DERIVED, never chosen. The fork directory and the dev port
-# both come from the worktree path, so the same worktree always gets the same
-# private harness and the same port, and two different worktrees cannot collide.
-#
-#   cd <worktree>; ..\iservice365-layer-common\tools\render-harness\harness-init.ps1
-#
-# Prints the fork path and port. Re-running is safe: it re-syncs `lc/` and
-# leaves the port alone.
-[CmdletBinding()]
-param(
-  # The layer-common worktree to render. Defaults to the current git worktree.
-  [string]$Worktree = (git rev-parse --show-toplevel),
-  # The canonical harness this fork is copied from.
-  [string]$Canonical = "C:\Seven365Projects\iService365\_scratch-theme-review\harness"
-)
-
-$ErrorActionPreference = "Stop"
-
-if (-not (Test-Path "$Worktree\.git")) { throw "not a git worktree: $Worktree" }
-if (-not (Test-Path "$Canonical\src\main.js")) { throw "canonical harness not found: $Canonical" }
-
-$slug = Split-Path $Worktree -Leaf
-$fork = Join-Path (Split-Path $Canonical -Parent) "harness-$slug"
-
-# --- port, derived ----------------------------------------------------------
-# FNV-1a over the worktree path: same worktree -> same port, every session, on
-# every machine. Then step upward past anything already listening, so a hash
-# collision or a stale server degrades to "next free port" instead of two
-# agents sharing one vite and measuring each other.
-function Get-DerivedPort([string]$s) {
-  $h = [uint32]2166136261
-  foreach ($c in $s.ToLower().ToCharArray()) {
-    # uint64 multiply, then modulo back into 32 bits. PowerShell widens past
-    # uint32 and refuses the cast rather than wrapping, and `-band 0xFFFFFFFF`
-    # is not the mask it looks like - 5.1 parses that literal as int -1.
-    $h = [uint32]((([uint64]($h -bxor [uint32][int]$c)) * 16777619) % 4294967296)
-  }
-  $p = 5400 + [int]($h % 200)
-  $busy = (Get-NetTCPConnection -State Listen -ErrorAction SilentlyContinue).LocalPort
-  while ($busy -contains $p) { $p++ }
-  return $p
-}
-
-$portFile = Join-Path $fork ".harness-port"
-if (Test-Path $portFile) {
-  $port = [int](Get-Content $portFile -Raw).Trim()
-} else {
-  $port = Get-DerivedPort $Worktree
-}
-
-# --- fork -------------------------------------------------------------------
-# Keyed on a file the copy produces, not on the directory: a run that died
-# half-way would otherwise leave a directory that looks finished forever.
-if (-not (Test-Path "$fork\vite.config.mjs")) {
-  New-Item -ItemType Directory -Path $fork -Force | Out-Null
-  # An ALLOWLIST, not "everything minus the big things": the canonical harness
-  # has accumulated hundreds of one-off runners, .json measure dumps and logs,
-  # and it also contains a stray `nul` that Copy-Item cannot read at all.
-  # `node_modules` becomes a junction (a full copy is ~400MB per agent) and
-  # `lc` is re-synced below.
-  foreach ($n in "src", "apps", "public", "index.html", "package.json", "yarn.lock", "vite.config.mjs", "sync-lc.ps1") {
-    Copy-Item (Join-Path $Canonical $n) -Destination $fork -Recurse -Force
-  }
-  cmd /c mklink /J "$fork\node_modules" "$Canonical\node_modules" | Out-Null
-}
-
-# The hardened runner lives in the repo, next to this script, so a fork always
-# gets the CURRENT one rather than whatever the canonical harness was carrying.
-Copy-Item (Join-Path $PSScriptRoot "render-check.mjs") -Destination $fork -Force
-# `probe.mjs` is imported by the runner, so a fork without it dies on
-# ERR_MODULE_NOT_FOUND before it measures anything. It was missing from this
-# list, which every fork made before now had to work around by hand.
-Copy-Item (Join-Path $PSScriptRoot "probe.mjs") -Destination $fork -Force
-Copy-Item (Join-Path $PSScriptRoot "baselines.json") -Destination $fork -Force -ErrorAction SilentlyContinue
-
-# A junctioned `node_modules` SHARES `node_modules/.vite` with the harness it
-# points at. Two servers writing one dep-cache produced 504s that photograph as
-# a blank screen - i.e. a fake "conversion broke the page". Own cache, always.
-$vite = Join-Path $fork "vite.config.mjs"
-$cfg = [System.IO.File]::ReadAllText($vite)
-if ($cfg -notmatch "cacheDir") {
-  $cfg = $cfg -replace "(?m)^\s*server:\s*\{", "  cacheDir: `"./.vite-cache`",`r`n  server: {"
-  # UTF8Encoding($false): Set-Content -Encoding utf8 writes a BOM on Windows
-  # PowerShell 5.1, and a BOM in a config file makes PostCSS's loader throw,
-  # which 500s EVERY .vue file - indistinguishable from a broken checkout.
-  [System.IO.File]::WriteAllText($vite, $cfg, (New-Object System.Text.UTF8Encoding($false)))
-}
-
-$pkgPath = Join-Path $fork "package.json"
-$pkg = [System.IO.File]::ReadAllText($pkgPath)
-$pkg = $pkg -replace '--port \d+', "--port $port"
-[System.IO.File]::WriteAllText($pkgPath, $pkg, (New-Object System.Text.UTF8Encoding($false)))
-[System.IO.File]::WriteAllText($portFile, "$port", (New-Object System.Text.UTF8Encoding($false)))
-
-# --- mirror -----------------------------------------------------------------
-& "$fork\sync-lc.ps1" -Src $Worktree
-
-# Stamp WHAT was mirrored, so a measurement can prove which checkout it rendered
-# rather than assume it. `render-check.mjs` refuses to run when this disagrees
-# with the worktree it was pointed at - which is what a foreign `sync-lc.ps1`
-# stamping over the mirror looks like. Written after the sync, because
-# `sync-lc.ps1` deletes everything in `lc/` that is not one of its six dirs.
-$stamp = @{
-  worktree = $Worktree
-  head     = (git -C $Worktree rev-parse HEAD)
-  branch   = (git -C $Worktree rev-parse --abbrev-ref HEAD)
-  port     = $port
-} | ConvertTo-Json -Compress
-[System.IO.File]::WriteAllText((Join-Path $fork "lc\.synced-from.json"), $stamp, (New-Object System.Text.UTF8Encoding($false)))
-
-Write-Output "harness  : $fork"
-Write-Output "port     : $port"
-Write-Output "renders  : $Worktree @ $(git -C $Worktree rev-parse --short HEAD)"
-Write-Output ""
-Write-Output "  Start-Process -WorkingDirectory '$fork' npx -ArgumentList 'vite','--port','$port','--strictPort'"
-Write-Output "  cd '$fork'; `$env:PORT=$port; node render-check.mjs <label> <Screen> [Screen...]"