Claude Code Worklog RSS

Mostly floorplan-tooltip iteration plus a handful of orthogonal fixes.

• AssetMarker.vue — restored the @mouseover="openHoverPopup" template handler. A few days back the disable-tooltip refactor accidentally renamed it to onMarkerMouseOver (no such function). Vue silently no-ops undefined template handlers, so hovering a pin did nothing. Also added pointer-events: none on the outer .leaflet-popup and re-enabled them on the visible content wrapper — the popup wrapper sits at its Leaflet layout position above the marker, so the empty area there was stealing hover events from any marker stacked above an open popup. Stripped the default Leaflet popup chrome (white bg / its own border / padding) so the inner card carries the visual styling; kept the soft drop shadow + transform for elevation and below-marker positioning.
• AssetPinTooltip.vue — replaced the bespoke two-cell status row with the shared PropertyValue component used by the dashboard widget hero, so the tooltip's hero reads identically to the matching card. Wrapped the whole tooltip in card chrome (gray bg, 10px padding, 1.5px border, 10px radius, soft shadow), centered the hero block via align-self: center, indented the friendly-name + serial subtitle 18px to align past the status dot, and pulled the photo edge-to-edge with negative margins (-12px / +24px) past both the padding and the subpixel border. Asset name now uses Vuetify text-primary to match the dashboard card's blue.
• PropertyValue.vue — added a no-tooltip opt-out so the floorplan tooltip can suppress the timestamp v-tooltip. The Vuetify overlay was throwing "Slot 'default' invoked outside of the render function" warnings every hover because it was rendered inside Leaflet's DOM (portal slot timing breaks).
• AssetChip.vue — on xs breakpoint, clicking an unplaced-asset chip no longer opens the inspector. The inspector covers the floorplan on phones, which made dragging the chip onto a floor impossible.
• Copilot review nits — updated the stale 4-step ABOUTME on InstallWizardBody.vue, removed the orphan primarySummary computed in AssetHeader.vue left over from the mono-serial split-span refactor, swapped the index-based v-for key in BuildingSensorDataReport.vue for section.id:group.label, and dropped the dead install-wizard__header--clickable class binding (no matching CSS).
• Mouseover-without-mouseout on the marker is intentional: the LPopup is configured with autoClose + closeOnClick, so the popup persists until the user hovers another marker or clicks the map — long enough to read the body and click through.
• Latest deployed commit on staging: 174151637.
• Branch: feature/surface-name-and-serial

Three coupled fixes so dashboards / breadcrumbs / inspector reflect in-wizard edits without manual refresh.

• AssetComponent.vue — root-cause fix. Cached the wrapped async component per loader fn in a WeakMap. The previous defineAsyncComponent(loader) inside a computed created a brand-new component definition every time asset.value got a new reference, which made Vue's :is resolve to a different component on every refetch and unmounted/remounted the entire dashboard subtree (visible as a full page reload, with subscriptions tearing down and re-establishing). The cache means same loader → same wrapper → no remount.
• useNavigationContext — breadcrumb / tab-title staleness. Dropped the legacy "resolve once" latch on the internal watchEffect (originally an unwatch() pattern, later switched to a let resolved = false flag in PR #1349) so the title and breadcrumbs re-run when asset.name changes mid-session. While we were there, lifted useTitle(TITLE_PREFIX) to the composable top so we update title.value instead of spinning up another watcher every reactive tick.
• InstallWizardBody → AssetView event chain. Replaced an experimental provide("refetchAsset", refetch) / inject pattern with idiomatic emit-up: body emits refresh-asset after each successful save (name, photos, floor placement / move / clear); InstallWizard and DeviceDashboardLayout declare the emit and forward; the 16 dashboard tabs need no change (single-root + no declared emits = listener falls through automatically). AssetView was already listening via @refresh-asset on <asset-component> and calling refetch.
• Net: saving a name in the wizard updates everything (dashboard widgets, asset header, breadcrumbs, browser tab title, asset inspector) reactively, with no double-reload, no flicker, and no provide/inject indirection.
• Deploying f4f69353a to staging.
• Branch: feature/surface-name-and-serial

• Why: Existing accounts already have named-and-running devices that lack photos / floor placement. The strict all-steps gate flagged every one of them as "not fully setup", lighting up the dashboard banner, the orange Set up chip on every widget, and the passive collapsed wizard on every asset dashboard. Painful for production accounts; not what we wanted that signal to mean.
• Backend (sbp-mono feature/asset-install-status 0c8b8332c): _compute_install_status in building.py now sets installed = name_filled. Building also drops out of the progress count — total_steps shifts from 3/4 to 2/3 and completed_steps no longer adds has_building. steps.building stays in the response shape (no schema change).
• Frontend (3f7c124ef): InstallWizard.vue mirrors the new derivations — effectiveInstalled = effectiveSteps.value.name, effectiveTotalSteps = floorplan === null ? 2 : 3, building dropped from effectiveCompletedSteps. InstallWizardBody.vue deletes the entire Select-building step (template, refs, useAccountBuildings / moveAssetsMutation / GqlBuilding imports, selectedBuildingUuid, onBuildingSelected, etc.). stepNumbers shrinks to { name: 1, photos: 2, floorplan: 3 }. The floorplan step's useBuilding now reads props.asset.building?.buildingUuid directly (was sourced from the now-removed selector). Other surfaces (banner, chips, passive mount, latch) all read installStatus.installed from the server response and pick up the relaxed gate automatically.
• Deployed to staging (frontend); backend deployed manually by Barry.
• Branch: feature/surface-name-and-serial

• Added an orange "Set up" v-chip next to the wizard title when the asset isn't fully installed; sits in the same slot as the green checkmark and swaps with it based on effectiveInstalled. Reuses the same Vuetify props/dimensions the dashboard widget already uses (size="x-small", color="warning", variant="flat", font-weight 600), so the chip on a card and the chip in the wizard header read as the same affordance.
• Pulled the progress bar in from a full-width strip below the title into a flex-column wrapper sized to fit the "X of N Steps complete" text — the bar now underlines just the count instead of running the full card width. Height dropped from 3 to 2 so it sits as a true underline.
• Reused the existing building.dashboard.set_up_cta i18n key — no new translations.
• Deployed 492902099 to staging.
• Branch: feature/surface-name-and-serial

• Asset dashboard now surfaces the install wizard whenever the asset is not fully installed, even without ?install=true. The passive case mounts the wizard collapsed; only the explicit ?install=true flow auto-expands.
• Added optional defaultExpanded prop on InstallWizard.vue; parent (DeviceDashboardLayout.vue) computes installRequested && !isInstalled and passes it. Wizard snapshots the value on mount so completing the final step inside an open wizard still doesn't auto-collapse.
• Behaviour matrix: ?install=true + not installed → expanded · ?install=true + installed → collapsed · no query + not installed → collapsed (new) · no query + installed → not mounted.
• Deployed 9fcb9433b to staging.
• Branch: feature/surface-name-and-serial

• Pulled Roboto Mono (400/500) into index.html via Google Fonts and added a global .ubx-serial { font-family: "Roboto Mono", monospace; } class in styles/styles.scss.
• Applied the class at every spot a UBX serial surfaces: asset header (compact summary + expanded detail row), asset inspector primary summary, floorplan pin tooltip subtitle, asset chip subtitle, dashboard widget title row, and the shared AssetsTable column (via cellClass).
• Where serial was previously joined with friendly name into a single string ({ friendlyName · serial }), the join now renders as two spans in the template so only the serial portion picks up the mono face. The friendly name and the · separator stay in the regular sans face.
• Deployed f44aa05b0 to staging.
• Branch: feature/surface-name-and-serial

• DashboardWidget.vue now shows a small warning-coloured "Set up" chip in the title row when asset.installStatus.installed === false. Click routes to that asset's dashboard with ?install=true so the install wizard mounts open. @click.stop keeps the card-level select handler from firing.
• Switched the dashboard banner copy from "uninstalled" to "not fully setup": "{count} devices not fully setup yet" / "Showing {count} devices not fully setup".
• Adopted the codebase's pipe-separated plural pattern (e.g. "1 device … | {count} devices …") used elsewhere via $t(key, count) (mirrors portfolio.portfolio_map.headings.map). Earlier _one/_other keys are gone.
• Backend installStatus rebased onto a fresh branch (feature/asset-install-status) off latest origin/develop in sbp-mono and pushed.
• Deployed 71455fb0c to staging.
• Branch: feature/surface-name-and-serial

• Backend (sbp-mono): added installStatus resolver on AssetBase with InstallSteps/InstallStatus Strawberry types. A new DataLoader batches the photo-count check (ubx_attachment.get_assets_with_image_attachments) and the building-floorplan-presence check (ubx_floor.get_buildings_with_floorplans), so a dashboard query for N assets fires exactly 2 extra SQL queries regardless of N.
• Dashboard: warning banner directly above the asset grid when any smart asset has installStatus.installed === false. Click → ?filter=uninstalled. With the filter active, the banner switches to a blue info "Showing N uninstalled · Show all" affordance that clears the filter on click. The asset grid filtering reuses the existing search-filter pipeline (added one more .filter call on smartAssets).
• Wizard: deleted useAssetInstallStatus composable. InstallWizard.vue reads asset.installStatus directly and maintains a tiny stepOverrides: Partial<AssetInstallSteps> bag for snappy in-session feedback. InstallWizardBody.vue accepts a :steps prop for the per-step checkmarks and emits step-update events on each save (name/building/photos/floorplan) instead of the previous local-update/photos-changed partial-asset shape. No more documents-query or building-query firing on wizard mount — installStatus comes inline with the asset query response.
• Frontend changes are pushed; backend changes are committed locally in sbp-mono only and need to be deployed before the frontend can be staging-deployed.
• Branch: feature/surface-name-and-serial

• Sensor Data (Tabular Review) and Wireless Device Health: replaced the inherited Device EUI column with a UBX Serial column (data key serialNumber, header "Serial #"). Both reports now identify devices by the UBX-printed serial that field techs read off the physical label.
• Asset Inventory: kept the Serial column (now provided by the shared base table) and added Device EUI back as the last column. This preserves EUI as a fallback identifier for cases where the UBX label is lost or damaged.
• Implementation: swapped the hardcoded identifier column in components/AssetsTable.vue (the shared base for all three reports) from devEui → serialNumber. InventoryAssetsTable.vue reintroduces devEui via additional-headers; it picks up the base table's existing <eui-value> rendering slot for formatting/copy-on-click. No GraphQL or i18n changes needed.
• Branch: feature/surface-name-and-serial

• Capture the install-status verdict once on first query settlement, so completing the final step inside an open wizard no longer auto-collapses it. The default expanded state is decided exactly once (via a watchEffect that fires when loading becomes false); from then on only the user's click toggles it. Already-installed assets still mount collapsed, partially-installed assets still mount expanded.
• Branch: feature/surface-name-and-serial

• Added a disableTooltip prop on FloorplanMap.vue and AssetMarker.vue and gated the <l-popup> with v-if="!disableTooltip". Wizard's <floorplan-map> usage in InstallWizardBody.vue passes disable-tooltip so the asset hover card doesn't fight with placement interactions inside the wizard.
• Default is false everywhere, so the dashboard floorplan keeps the tooltip.
• Branch: feature/surface-name-and-serial

• New useAssetInstallStatus(asset, { enabled? }) composable derives a per-asset "installed" boolean from four checks: name present, building assigned, at least one photo, and (when the building has floorplans) placed on a floorplan. Returns { installed, steps, completedSteps, totalSteps, loading }. Reusable across surfaces (next likely consumer is the building dashboard cards). The enabled flag forwards to useAssetImages.loadImages() and useBuilding, so callers can defer fetches.
• InstallWizard.vue split into a thin header component (always renders the title strip) and a heavy InstallWizardBody.vue (the four-step UI, drag-and-drop floorplan, account-buildings selector, etc.). Body is mounted lazily via v-if="expanded", so its queries only fire when the wizard is open.
• Title is now "Device setup" (i18n: install_wizard.title) with a mdiCheckCircle green check when fully installed. Each step row gets the same checkmark next to its number badge when its requirement is met. Replaced the "All steps optional" chip with {completed} of {total} Steps complete text + a thin success-coloured v-progress-linear.
• Wizard defaults to collapsed when fully installed; expanded when any step is incomplete. User clicks override for the session.
• Branch: feature/surface-name-and-serial

• Iterated on the floorplan hover card after the initial LTooltip kept auto-closing whenever the user moved off the marker (the brief mouse gap between pin and tooltip triggered Leaflet's auto-close even with interactive: true).
• Final approach: use <l-popup> for persistent open/close behavior (stays open until the user clicks the map or hovers another pin), opened on marker @mouseover via markerRef.leafletObject.openPopup() with autoClose: true + closeOnClick: true.
• Leaflet popups always anchor body-above-tip; to put the body BELOW the marker we translate the inner .leaflet-popup-content-wrapper by translateY(calc(100% + 21px)). The Leaflet wrapper element itself stays where Leaflet positioned it (above marker); only the visible body shifts. The default downward-pointing tip is hidden since it'd point at empty space now.
• Custom CSS on .leaflet-popup.asset-marker__tooltip styles the body as a Vuetify-card (white background, rounded corners, soft shadow) instead of Leaflet's default speech-bubble look.
• Branch: feature/surface-name-and-serial

• The earlier asset inspector side-by-side rework (commits 0db2fe78c and 5af5003e9) was a misread of intent. Barry only wanted the floorplan tooltip to show two primary properties next to each other; the asset inspector should keep its existing single-column layout.
• Reverted the :two-columns="false" override on AssetInspector and restored the original cols="12" single-column layouts for contact, tilt, gateway (Mobile pair), and the tstat humidity placement (back to a single card with humidity stacked under temperature when present).
• Tooltip multi-property rendering (AssetPinTooltip showing the first two primaryProperties side-by-side) stays in.
• Branch: feature/surface-name-and-serial

• The hover tooltip status row was only showing primaryProperties[0]. For UBX-TSTAT-101 (ambient_temperature + humidity) and any other asset with two featured properties, the second is now rendered inline after a separator dot. Capped at two for compactness; assets with three or more primary properties show the first two.
• Branch: feature/surface-name-and-serial

• The thermostat AssetInspectorStatus was packing ambient_temperature and humidity into a single v-list inside a single full-width card, so the two properties stacked vertically rather than rendering side-by-side. Split into one card per property and wrap each in a half-width v-col when humidity is shown (UBX-TSTAT-101). When humidity is gated off (UBX-TSTAT-100), the temperature card takes full width.
• Branch: feature/surface-name-and-serial

• AssetInspector.vue dropped the hardcoded :two-columns="false" override on <asset-component component-name="AssetInspectorStatus" />. Per-type status components and the generic fallback already default to side-by-side rendering when there are 2+ featured properties; the override was the blocker.
• contact, tilt, and gateway per-type AssetInspectorStatus components: dropped their hardcoded :sm="12" single-column layout for their property card pairs and switched to cols="6" so the featured properties render side-by-side on every viewport.
• AssetMarker.vue floorplan tooltip now uses direction: 'bottom' with offset: [0, 0] so the hover card floats just below the pin tip rather than above.
• Branch: feature/surface-name-and-serial

• Vuetify's <v-tooltip> didn't capture hover when its activator lived inside <l-icon>. Leaflet detaches/serializes the icon DOM into its marker pane, and the activator's mouseenter/mouseleave handlers never fired.
• Replaced with Vue Leaflet's <l-tooltip> (Leaflet-native, lives inside <l-marker> alongside <l-icon>). interactive: true makes the tooltip body clickable; custom className lets us override Leaflet's default black tooltip styling to look like a Vuetify card.
• Branch: feature/surface-name-and-serial

• New AssetPinTooltip.vue renders a Google-Maps-style hover card with photo (lazy-fetched on first hover), asset name (with "Unnamed" fallback), friendlyName · serialNumber subtitle, and a status row with the offline-keyed dot + the asset's first primaryProperty value (e.g. "Normal"/"Leak" for water sensors).
• AssetMarker.vue now wraps the pin in a Vuetify <v-tooltip> (location="top", 200ms open delay) whose content is the new tooltip body. Clicking anywhere on the tooltip body opens the inspector via the same floorplanStore.selectAsset path the pin's click handler uses — no new entry into the inspector flow.
• useAssetImages.loadImages() is called only once the tooltip first mounts (Vuetify mounts tooltip content lazily), so the floor doesn't issue N image queries on initial render. Apollo caches subsequent hovers.
• Branch: feature/surface-name-and-serial

• The field is consumed by both the building dashboard and the report pages now (sensor-data, thresholds), so the dashboard-only name no longer fit. reportingSection reads better as a generic categorical grouping for any report-style consumer.
• Mechanical rename — 38 references across types/index.ts, config/known-asset.ts, config/dashboard-categories.ts. No behavior change.
• Branch: feature/surface-name-and-serial

• AssetsThresholdsReport.vue now mirrors the sensor-data report layout: an <h3> section header per non-empty dashboard category (canonical order from getDashboardCategories()), then within each section a model group keyed by knownAssetUuid (config-coherent) with title Friendly Name (UBX-XXX) via getKnownAsset(...).friendlyName + KNOWN_ASSETS.name. Drops the invalid text-heading-6 class and matches the sensor-data report's lighter text-subtitle-1 weight.
• AssetsTable name column now uses SmartAssetName's displayName slot prop so blank asset names show "Unnamed", matching the rest of the surface. Same change in the asset-name span on AssetsThresholdsReport.vue.
• Sensor-data report title now reads Friendly Name (UBX-XXX) when the model code is available.
• Bumped the bottom margin between model groups to mb-12 (48px) in both reports for clearer visual separation.
• Branch: feature/surface-name-and-serial

• The previous "group by friendly name" change merged distinct knownAssetUuid templates that share a friendlyName (e.g. UBX-TSTAT100 + UBX-TSTAT101 both "Smart Thermostat") into one table. PropertiesAssetsTable derives its primary-properties config from firstAsset only, so two templates with different primaryProperties in the same table threw a render error.
• Group by knownAssetUuid (or model name for non-UBX assets) — guarantees a single config per table. Title still uses the friendly name, so distinct templates that share a friendly name now render as adjacent tables with identical titles. User-facing grouping intent is preserved; table internals stay consistent.
• Branch: feature/surface-name-and-serial

• BuildingSensorDataReport.vue now groups results by dashboard category at the top level (h3 per non-empty section, in canonical order from getDashboardCategories(); unmapped assets fall into "Other") and by friendly name within each section. Friendly name resolves via getKnownAsset(...).friendlyName; fallback is asset.assetModel?.name for non-UBX assets. Models that share a friendly name (e.g. UBX-IAQ101 + UBX-IAQ101A both "Air Quality Sensor") merge into a single table.
• Added groupAssetsByCategory<T>(assets) + DashboardCategoryWithAssets<T> to dashboard-categories.ts so other reports can reuse the canonical-ordering grouping logic.
• Branch: feature/surface-name-and-serial

• Pulled the per-asset grouping + section ordering out of use-dashboard-config.ts into dashboard-categories.ts so other consumers (reports, selectors) can reuse the canonical category list without depending on dashboard-only state.
• dashboard-categories.ts exports getDashboardCategories(): DashboardCategory[] — the ordered { id, label, knownAssetUuids } list, derived from KNOWN_ASSETS.dashboardSection walked in DASHBOARD_SECTIONS order, with unknown ids auto-appended.
• New DashboardCategory shape excludes the dashboard-only collapsed flag so report code doesn't carry irrelevant state.
• use-dashboard-config.ts:getCodebaseDefault() is now a thin layer that overlays DASHBOARD_SECTIONS' collapsed defaults onto the categories.
• No behavior change.
• Branch: feature/surface-name-and-serial

• Dashboard section assignments used to live in modules/vue-ui/src/config/dashboard-categories.json keyed by knownAssetUuid. With friendlyName already on KnownAsset and a new product spec defining both fields per UBX model from the same source, dual files were awkward. Co-located the per-asset mapping with the rest of the per-model metadata.
• KnownAsset gains optional dashboardSection: string. The JSON is replaced by dashboard-categories.ts which exports DASHBOARD_SECTIONS (an ordered list of { id, label, collapsed }) at the top of the file for easy amending. The knownAssetUuids arrays are gone — now derived.
• Each of the 32 currently-mapped UBX entries in KNOWN_ASSETS gets dashboardSection set to its previous JSON section id, preserving current dashboard behavior. Cross-checked against the new product spec PDF — all 32 mappings agree.
• use-dashboard-config.ts:getCodebaseDefault() now derives sections by walking DASHBOARD_SECTIONS in declared order, gathering knownAssetUuid from every KNOWN_ASSETS entry whose dashboardSection matches. Section ids referenced from KNOWN_ASSETS but missing from DASHBOARD_SECTIONS are auto-appended at the end with a humanized label and collapsed: false — so adding a new section is a one-line edit on a model entry.
• Runtime shape (DashboardConfig / DashboardSection in server preferences) is unchanged; existing customized accounts are unaffected. No GraphQL changes.
• Follow-up: 22 UBX models in the new spec aren't in KNOWN_ASSETS yet (UBX-IAQ102A, UBX-NRG102/104/105/201/202, UBX-OCC101, UBX-TEMP-RH100A, UBX-TSTAT-RMT1, plus the n/a and blank-category ones). Barry is taking the missing-KA list to product separately.
• Branch: feature/surface-name-and-serial

• Asset view header: for UBX assets (those whose knownAssetUuid resolves to a friendlyName), the secondary line now reads <friendlyName> · <serialNumber> to match the inspector and dashboard cards. A caret next to the edit button toggles an expansion panel showing Manufacturer, Model, and Device EUI in the same text-body-2 text-grey + bold uppercase label format as the previous detail row. Non-UBX assets keep the original Category/Type/Manufacturer/Model/Serial Number row with the existing mobile-collapse behavior. Caret shows on UBX always; on non-UBX only on mobile (unchanged).
• GraphQL fix: added devEui to use-asset.ts inside the ... on Device inline fragment. Earlier I'd placed it on the top-level asset selection, which raised "Cannot query field 'devEui' on type 'AssetBase'" since devEui lives on Device/DeviceBase.
• More Unnamed fallback adoption: dropped the inner {{ asset.name }} from AssetControlPanel, AssetConfigAssignmentList, and TaskScheduleAssignmentList so SmartAssetName's default-slot fallback applies.
• Page title + breadcrumbs: added a small assetDisplayName helper in use-navigation-context.ts so the browser tab title and breadcrumb text also show "Unnamed" for nameless assets.
• Branch: feature/surface-name-and-serial

• Dropped the inner {{ asset.name }} from <smart-asset-name> in AssetHeader.vue so the default-slot fallback (displayName → "Unnamed" when name is blank) renders, matching the inspector title and dashboard cards.
• Branch: feature/surface-name-and-serial

• The discriminator isUbxDevice = !isBlank(knownAssetUuid) was wrong: KNOWN_ASSETS includes non-UBX entries (VS-series ERV/HRV, VRF ODU/IDU, Fujitsu) that have a knownAssetUuid but no friendlyName, so any asset linked to one of those templates fell into the friendly-name branch and produced an empty primarySummary.
• Use friendlyName itself as the discriminator. When getKnownAsset(...).friendlyName resolves, show <friendlyName> · <serialNumber>; otherwise fall through to <manufacturer> · <model>. Drops the unused isUbxDevice computed.
• Branch: feature/surface-name-and-serial

• AssetInspector title now uses SmartAssetName's default-slot fallback so an unnamed asset reads "Unnamed" in the inspector header (matches the rest of the surface).
• AssetDashboardTab.vue: wrapped the loose <tr> rows inside <table> in a <tbody> to silence Vite's "<tr> cannot be child of <table>" hydration warning. Browsers were already inserting a tbody implicitly, so no visible change.
• Branch: feature/surface-name-and-serial

• Replaced text-body-2 font-weight-medium on the new primarySummary line with a dedicated .primary-summary rule: font-size: 16px and color: rgba(0, 0, 0, 0.78) so weight and tone can be tuned independently of Vuetify's text-grey utility.
• Branch: feature/surface-name-and-serial

• Replaced the three details rows (Manufacturer/Model, Serial Number, Category/Type) in AssetInspector.vue with a single contextual line: <friendlyName> · <serialNumber> for UBX devices (asset.knownAssetUuid set, friendly name looked up via getKnownAsset), <manufacturer> · <model> for non-UBX assets.
• Empty parts are filtered out, so a missing value collapses the surrounding separator; if both parts are blank the whole section hides.
• Dropped the now-unused manufacturer / model / serialNo / category / type / missingValue computeds and the i18n import.
• Branch: feature/surface-name-and-serial

• Pulled the asset display-name logic into SmartAssetName.vue. Added a displayName computed (asset.name or i18n.t("general.unnamed") when blank) exposed both as default-slot content and as a displayName slot prop. Callers opt in by either dropping slot content (new fallback renders) or reading the slot prop. Existing callers that pass their own slot content ({{ asset.name }} mustache, styled spans, etc.) are unchanged.
• Added a 4px right margin on a new .smart-asset-name__icon class so the status dot has a small consistent gap from the name. The previous zero-default left character-bearing variation as the entire visible gap (capital U vs lowercase p looked very different). Existing per-context workarounds — DashboardWidget's &__title .v-icon { margin-right: 4px } rule and the pl-1 spans in AssetsTable / CopyThresholdsDialog / AssetsThresholdsReport — keep working: the higher-specificity rules / the additional padding layer on top of the new default for places that wanted extra space.
• DashboardWidget now consumes the displayName slot prop instead of its own local fallback computed.
• AssetPin dropped its local identifier computed and lets SmartAssetName render the fallback, so unnamed assets show "Unnamed" on the floorplan pin instead of a blank label.
• AssetChip (unplaced-assets list) is now two lines: asset name (with "Unnamed" fallback) on row 1; friendlyName · serialNumber on row 2 in smaller (11px) lighter (85% opacity) text, indented when the status dot is present so it lines up with the name.
• Branch: feature/surface-name-and-serial

• Building dashboard cards (DashboardWidget.vue) now show the asset's serial number (asset.serialNumber — the unified read-only field that resolves to mfgSerialNumber for non-UBX assets and ubxSerialNumber for UBX devices) on the right side of the title row, in small muted text. Capped at 40% width with ellipsis so a long SN can't crowd out the name.
• The friendly name (from the new KnownAsset.friendlyName) is shown as a v-tooltip anchored to the SN span only, not the whole title. Set open-on-click so it surfaces on tap; added @click.stop on the SN so the tap doesn't bubble to the title/card click handlers and bring up the asset inspector on mobile.
• Added general.unnamed i18n key and use it as the fallback for asset.name when blank.
• No search-code change needed: DashboardOverview.vue:assetMatchesSearch already tests asset.serialNumber, the same unified field shown on the card.
• Branch: feature/surface-name-and-serial

• Added an optional friendlyName field to the KnownAsset type and populated it for 36 UBX-branded entries in KNOWN_ASSETS using the user-friendly model labels from UBX's master model list (e.g. UBX-IAQ101 → "Air Quality Sensor", UBX-NRG100 → "CT 100A", UBX-OCC100 → "Occupancy Sensor").
• 16 non-UBX entries (VS-series ERV/HRV, VRF ODU/IDU, Fujitsu) were intentionally left without friendlyName — they aren't on the UBX label list and carry their own marketing names. Three rows missing or red-flagged in the source PDF (UBX-HUB100/101, UBX-OCC104, UBX-TSTAT100) got sensible defaults that mirror their siblings; same pattern for four entries that aren't in the PDF at all (UBX-IAQ100, UBX-NRG200A, UBX-TSTAT-EXT1, UBX-FRIDGE).
• This is the first step on feature/surface-name-and-serial — the next step is surfacing the friendly name alongside the model number in the UI.
• Branch: feature/surface-name-and-serial (new, off main bb1a3585b)

• Three vertically stacked sections per Barry's whiteboard sketch (IMG_1174):

1. Alert Home (white card): config + recipients (unchanged AlertConfigSummary)

2. Incidents (NEW): Gantt-style Highcharts xrange chart with one row per scope asset; each bar is a firing. Bars include firings on the scope asset itself and on its linked child sensors (resolved via the asset's childLinks GraphQL field). Date range picker (shared with Details) sits above.

3. Details (only when an instance is selected via timeline click or ?ai=): a single PropertyGraph for the associated scope asset's property + the existing AlertInstanceBanner.

• Date range is shared between the timeline and the Details graph.
• Removes the per-asset PropertyGraph loop and the AlertRecentInstances table that lived below the graphs.
• Files: AlertIncidentsTimeline.vue (new), AlertConfigDashboard.vue, en.json. Deleted AlertRecentInstances.vue.

• RESOLVE_MIN/MAX raised from 2-20 min to 10 min - 8 hr per Barry's request for longer incidents. Average resolved duration now ~4h (verified: 3.92h on f5adf2c3, 4.08h on 4067f334). Zero same-asset overlaps after regeneration.
• Slot timing still safe: max_arc = dwell + 8h ≈ 8h05m; with 200 firings / 4-5 assets, slot size ≈ 43-54h, plenty of headroom.
• Branch: feature/simulate-alert-firings, commit c740182, pushed.

• Barry's dashboard graph showed 2-3 long horizontal bars per asset stretching February → present. Cause: ACTIVE alerts have no resolved_at, so the UI extended their pending_started_at to now(). Old logic placed ACTIVE/PENDING anywhere in the 90-day window, so an ACTIVE that landed 60 days back rendered as a 60-day bar.
• Fix: only the LAST slot per asset rolls weighted state. If it picks ACTIVE, pending_started_at is anchored to the last 4h via new recent_anchor_offset helper; if PENDING, anchored within the dwell window (<5min ago for default dwell). All earlier firings are RESOLVED with normal slot timing. Verified: regenerated f5adf2c3 (1 ACTIVE, 1.59h old) and 4067f334 (1 PENDING, 3.6 min old).
• Trade-off: global ACTIVE/PENDING counts drop from N * 0.10 / N * 0.05 to K * 0.10 / K * 0.05 (K = num assets). With 4-5 assets you'll typically see 0-1 of each per run; re-roll the seed for variety.
• 3 new unit tests (23 total). Branch: feature/simulate-alert-firings, commit 2e7107c, pushed.

• Dashboard graph showed concurrent same-asset alerts because RESOLVE_MAX was 4 hr — way longer than the gap between firings on dense assets. Dropped RESOLVE_MIN/MAX to 2-20 min.
• Replaced per-firing uniform-random pending_started_at with per-asset slot timing: for an asset with n firings, divide the window into n equal slots and jitter each offset within the part of its slot where a max-length arc still fits. Eliminates RESOLVED-vs-RESOLVED overlap on the same asset (verified: 0 overlaps across 329 consecutive pairs after re-running both definitions).
• Added --clear flag that deletes existing instances + transitions for the definition before inserting. Used it to regenerate f5adf2c3 (200/200 instances) and 4067f334 (200/200 instances).
• 4 new unit tests for slot_offsets; 20 tests total, all green.
• Branch: feature/simulate-alert-firings, commit b03d432, pushed.

• deploy/ubx-serial+cache-isolation was the wrong home for the simulator (it's a deploy branch and was force-pushed remote-side, so my commit was floating on stale history).
• Stashed dirty Gemfile.lock, branched off latest origin/develop, cherry-picked 9dc3b78 as 70fe620 onto feature/simulate-alert-firings, pushed with upstream tracking. Switched back to deploy/ubx-serial+cache-isolation and popped the stash.
• PR target: https://github.com/ventacity/sbp-mono/pull/new/feature/simulate-alert-firings
• Local deploy/ubx-serial+cache-isolation still has the orphan 9dc3b78 and pre-rebase history vs origin (3784 ahead / 3783 behind). Left untouched pending a separate decision on how to reconcile.

• Committed simulate_alert_firings.py + test_simulate_alert_firings.py (449 insertions) on deploy/ubx-serial+cache-isolation as commit 9dc3b78. Not pushed.

• Wrote strawberry-gql/dev-scripts/simulate_alert_firings.py plus pure-function tests in test_simulate_alert_firings.py (16 cases). Takes an existing v2 alert_definition_uuid and writes N ubx_alert_instance + ubx_alert_instance_transition rows over a configurable window (default 90 days).
• State mix: 85% resolved (full none→pending→active→resolved arc), 10% active, 5% pending; firings stratified across all in-scope assets (every asset gets floor(N/K) ± 1) instead of per-firing random.
• additional_context.affected_properties is copied from the fire trigger's backend_data.affected_properties — same shape the UI consumes at gql_server/objects/alertv2.py:391. No regex/CEL parsing needed.
• Discovered the v2 alert evaluation engine is external to this repo: nothing in sbp-mono inserts ubx_alert_instance, and the only existing ubx_alert_instance_transition insert is in close_alert_definition_instances (hvac2/hvac2/ubx/alertv2.py:469-516) on definition disable/delete. So the simulator writes directly to those tables. Out of scope (production v2 doesn't touch them either): last_alert_instance_uuid on subscriptions, ubx_event_history, MQTT publish.
• Verified against f5adf2c3-8d90-419f-978e-b649e3dc446a: 220 instances / 619 transitions inserted across a 20-row + 200-row run. State distribution, asset distribution (5×44), 90-day time window, and per-state transition counts (active=2, resolved=3) all matched expectations. Sample instance had correct dwell (5 min) and recovery delay.
• Working tree only on branch deploy/ubx-serial+cache-isolation — not yet committed.

• Added run-dev-script.sh at the standalone-dev-env top level. Mirrors start-mac.sh's prelude (activates gql-py3 venv, sources gql_env), then exec python on the named script under gql-repos/sbp-mono/strawberry-gql/dev-scripts/. 26 lines, basename lookup, clear errors for missing script (exit 66) and missing args (exit 64).
• Use: ./run-dev-script.sh simulate_alert_firings.py <uuid> --count 200 --seed 1.
• Branch: feature/dev-script-runner (off feature/mac-os-support), commit 89c697b, pushed to origin.

• Wrap alert header (name + severity chip + edit pencil) and the two config cards in a single white rounded section
• Move alert name ownership from AlertConfigSummary up to AlertConfigDashboard so the dashboard can orchestrate the order: name → instance banner → cards
• Both inner cards (Condition, Recipients) now use the DashboardWidget aesthetic — #f8f9fa bg, 1.5px soft border, 10px radius, no title bar + divider
• Condition card reordered: asset chips at the top (no "ASSETS" label, linked to the asset detail page), then CONDITION PROPERTY / rh_pct hero, then compact inline metrics row for Dwell Time + Active Periods chips
• Recipients card uses a small uppercase RECIPIENTS label with the Snooze all button inline on the right, followed by per-recipient rows separated by a subtle divider
• Files: AlertConfigDashboard.vue, AlertConfigSummary.vue

• Instance banner: replace tonal fill with a 1px severity-colored outline on transparent background
• Condition card: drop v-table; use labels-above-values, render active periods as chips, render assets as linkable chips with open-in-new icon
• Files: AlertConfigSummary.vue, AlertInstanceBanner.vue

• Split the config summary into two side-by-side cards (v-col cols="12" md="6"):

- Condition card: condition property, dwell time, active periods, assets

- Recipients card: each recipient as a row with email/SMS delivery icons (muted when disabled), per-recipient Snooze and work-schedule icon stubs, collective "Snooze all" button in the card header

• Stub controls call snackbarStore.show({ key: "building.alerts.stub_not_implemented" }) — UX preview only; no data model exists for alert snooze or user work schedules
• New AlertInstanceBanner component appears above the cards when the dashboard is opened with ?ai=xxx (i.e. via /alert-instance/... redirect); shows severity chip, state chip, fired timestamp, resolved-or-ongoing indicator, and duration (Luxon diff formatted d/h/m)
• Added i18n keys under building.alerts.config_summary.cards.*, building.alerts.stub_not_implemented, and building.alerts.instance.*
• Files: AlertConfigSummary.vue, AlertInstanceBanner.vue (new), AlertConfigDashboard.vue, en.json

• Changed "Return to Alerts" button to "Recent Alerts", linking to the Recent Alerts tab (buildingAlertsRecent route) instead of the generic alerts landing
• File: AlertConfigDashboard.vue

• Alert bars weren't rendering on Alert Config Dashboard when the firing asset was a linked sensor (e.g. a fridge alert that fires on a remote temperature sensor — alert scoped to the fridge but instance created with the sensor's asset_uuid)
• PropertyGraph's alert instance query filtered by displayedAssetUuids, excluding the sensor's instance from the fridge's graph
• Added opt-in alertsAcrossAllAssets prop on PropertyGraph — when true, passes null for assetUuids in the alert instances query (caller is expected to have already narrowed scope via alertDefinitions)
• Alert Config Dashboard sets :alerts-across-all-assets="true"
• Files: PropertyGraph.vue, AlertConfigDashboard.vue, use-alert-instances.ts

• Passing :start-date="undefined" explicitly (when no ?ai= param) appeared to disrupt the PropertyGraph's date range store wiring. Use v-bind on a conditional object so no date props are attached when there's no instance to zoom to — restores pre-redirect behavior for direct dashboard links
• File: AlertConfigDashboard.vue

• <v-btn prepend-icon="mdi-arrow-left"> passed a string name, but this codebase uses @mdi/js SVG path binding. Console error: <path> attribute d: Expected number, "mdi-arrow-left"
• Import mdiArrowLeft and bind with :prepend-icon="mdiArrowLeft"
• File: AlertConfigDashboard.vue

• New /alert-instance/:alertInstanceUuid route: resolves buildingUuid and alertDefinitionUuid from the instance (via getAlertInstance GraphQL query, extended to return buildingUuid) and redirects to the canonical dashboard URL with ?ai=xxx
• New /alert/:alertDefinitionUuid route: resolves buildingUuid from the alert definition and redirects, preserving any existing query params
• AlertConfigDashboard now reads ?ai=xxx — fetches the instance, derives a zoomed date window (pendingStartedAt ?? activatedAt − 12h to resolvedAt ?? now + 12h in building timezone), and passes :start-date / :end-date to each property-graph
• Added building.alerts.not_found i18n string used by both redirect components for the "Alert not found" fallback
• Documented the intended URL format for the future v2 firing engine in project memory (reference_v2_alert_notification_url.md)
• Branch: feat/alert-config-dashboard
• Files: AlertInstanceRedirect.vue (new), AlertRedirect.vue (new), AlertConfigDashboard.vue, use-alert-instance.ts, router/index.ts, en.json

• Three related Vue 2→3 migration stragglers on OpsAgentsConfig.vue and OpsAgentsOverview.vue:

1. Chevrons stacking below the row on the Available Agents and Active Customers lists — the icons were in v-list-item's default slot where Vuetify 3 stacks children vertically. Moved them into #append.

2. Status chip and action buttons vertically stacked on the Configured Agents list. The chip was wrapped in a second v-list-item-subtitle (new line) and the three buttons each took their own row. Put the chip inline with the title and moved the buttons into a .agent-actions flex row below the subtitle (wraps on narrow widths).

3. All list-item link text rendering in brand blue — the global .v-theme--light a:not(...) rule in styles.scss painted every anchor blue, and Vuetify 3's v-list-item with :to renders as <a>, so list-item titles and subtitles inherited the blue. Extended the :not() exclusion to skip .v-list-item and its descendants, matching the rule's original intent (V2 list items weren't anchors).

• Branch: feature/install-wizard

• OpsAgentsConfig.vue rendered an apparently-empty v-autocomplete dropdown even though opsAccounts was returning four real accounts from the backend. The #item slot was reading item.name / item.uuid directly, but in Vuetify 3 the slot prop is a wrapper — the original data lives under item.raw, and the slot also exposes a props object meant to be bound onto v-list-item. Both fields were undefined, so every row rendered with an empty title and subtitle.
• Switched to the standard Vuetify 3 pattern: <v-list-item v-bind="props" :subtitle="item.raw.uuid" />. The item-title / item-value props on the autocomplete still resolve correctly for the chip and v-model.
• Vuetify 2→3 migration straggler, pre-existing (not related to install-wizard work); fix piggybacks on feature/install-wizard.
• Branch: feature/install-wizard

• UserInfo is cached per-auth_id in UserCache and shared across every concurrent request for the same user. Its inherited_access_map was mutated in-place by Account.groups and expected to survive until Group.buildings read it later in the same request — but every sibling request's has_permission → update_cache reset the map mid-flight, so Group.buildings fell into the restrictive filter branch and returned []. Manifested as the sbg-webapp "first-call-empty, refetch-populated" bug.
• Confirmed in production logs with temporary [RACE] instrumentation: on the failing request, iam_id flipped twice between Account.groups AFTER_MUTATE and Group.buildings READ, wiping the mutation both times.
• Moved inherited_access_map onto info.context (request-scoped) seeded in HVAC2Permission.has_permission as copy.deepcopy(user_info.access_map). Moved update_inherited_access_map to a module-level helper in hvac2.ubx.permissions.permissions. Removed the attribute and duplicated method from both UserInfo and AgentInfo. Test updated to exercise the module-level helper against a request-scoped snapshot.
• Branch: fix/inherited-access-map-race

• The install wizard's building step fell through to "No buildings loaded" with a Reload link the instant allBuildings was empty, even while the Account query was still in flight — so users saw a flash of error-looking empty state on every open. Show a small primary-colored progress spinner (20px, 2px stroke) during loading instead.
• The empty-state message still shows if the query resolves with zero buildings. With cache-and-network, loading stays true until the network round-trip completes, so the spinner persists through the backend's first-call-returns-empty race (see backend investigation prompt).
• Branch: feature/install-wizard

• The floorsWithFloorplans watcher in InstallWizard re-selected the original floor after the user explicitly cleared it. The guard only checked whether selectedFloorUuid was empty, and since props.asset.floorUuid never refreshes (Apollo no-cache on useAsset), switching buildings and coming back would trip the watcher and undo the clear. Added !removedFromFloor.value to the guard and moved the removedFromFloor / localPlacement declarations above the watcher for top-to-bottom readability.
• Renamed useAssetBySerial's parameter from serialNumber to ubxSerialNumber so it matches the query variable and the /d/:serialNumber route semantics. No caller changes needed (positional).
• Branch: feature/install-wizard

• serialNumber is now a read-only helper returned from queries (it reflects mfgSerialNumber on non-UBX assets and ubxSerialNumber on UBX assets). The asset form reads and writes mfgSerialNumber directly, and the field is hidden entirely for UBX devices (assets with a knownAssetUuid).
• Both mutations updated: updateAsset sends mfgSerialNumber, and createAsset's $serialNumber parameter was swapped to $mfgSerialNumber. Neither sends serialNumber any more. ubxSerialNumber is never sent from the client.
• Added mfgSerialNumber to the Asset type, to use-asset, and to the four queries in use-assets (kept serialNumber alongside for display contexts — inventory tables, dashboards).
• Review-driven cleanups in the same commit: useAccountBuildings switched from no-cache to cache-and-network (the previous change refetched the full account/groups tree on every mount of 10+ callers); and stripped dead alert-config i18n keys (alerts.headings.config_dashboard, alerts.config_summary) that had leaked in from another branch.
• Branch: feature/install-wizard

• The width: fit-content rule introduced for the hero (so card whitespace clicks fall through to the inspector) was applied to .dashboard-widget .property-value, which also constrained the secondary properties grid.
• Moved the rule under &__hero so it only targets the hero property-value. Secondary properties go back to their natural grid sizing.
• Branch: fix/hero-property-fit-content (off latest main, post-merge of feature/dashboard-card-double-click).

• Copilot review caught a duplicate-fire bug: the fallback <dashboard-widget> inside <asset-component> had its own @dblclick handler, but native dblclick bubbles up to <asset-component>'s root <div> which also has @dblclick — so router.push to the asset dashboard ran twice for assets without a registered widget.
• Removed @dblclick from the inner element; bubble covers it. @select stays because it's a Vue custom emit (doesn't bubble through DOM).
• Branch: feature/dashboard-card-double-click

• Stripped the temporary console.log lines from onCardClick after confirming the mobile click behavior works end-to-end.
• Branch: feature/dashboard-card-double-click

• The hero .property-value element was always full card width with content left-aligned, leaving a wide whitespace area inside the box. The new card-click origin check caught clicks on that whitespace and suppressed the card handler, so users couldn't tap padding to open the inspector.
• Added .dashboard-widget .property-value { width: fit-content; } so the property-value collapses to its content. Whitespace clicks now fall through to the card handler and open the inspector. Visual rendering of the property text is unchanged (the content was already left-aligned within the wider box).
• Scoped to .dashboard-widget so other consumers (control panels, tables) keep their existing layout.
• Branch: feature/dashboard-card-double-click

• DashboardOverview.vue's wrapper <div>s around <property-value> (added while iterating on the card-click fix) added an extra DOM level that broke DashboardWidget.vue's nested CSS selectors (e.g. &__hero > div > div > div:first-child), causing the hero value to render full width.
• Removed the wrappers. Origin check for card clicks still works — .property-value lives on PropertyValue's own root div.
• Branch: feature/dashboard-card-double-click

• Earlier marker class (.dashboard-widget__noselect) only applied to the generic fallback path in DashboardOverview.vue. Custom dashboard widgets (IaqDashboardWidget, FridgeDashboardWidget, TstatDashboardWidget, etc.) wrap DashboardWidget and pass <property-value> directly, so the origin check never matched for real assets.
• Added a stable .property-value class on PropertyValue.vue's root <div>. DashboardWidget.onCardClick now checks closest(".property-value, .dashboard-widget__noselect").
• Swapped console.debug → console.log so the diagnostic line is visible without enabling the Verbose filter in Chrome.
• Branch: feature/dashboard-card-double-click

• AssetMarker.vue (floorplan pins): added @dblclick → navigates to asset dashboard. Handler calls event.originalEvent.stopPropagation() to suppress Leaflet's map-level doubleClickZoom from firing through the marker.
• AssetsTable.vue (drives Inventory / Device Health / Sensor Data reports): added @dblclick on the name cell.
• AssetsThresholdsReport.vue: added @dblclick on the asset-name-container; added useRouter import.
• Single-click (open inspector) and cmd/ctrl/shift-click (open in new tab) behaviors unchanged.
• Known caveat: handlers are not gated by smAndUp — on mobile breakpoint, double-tap anywhere could navigate. Left deliberately as-is pending mobile device testing.
• Branch: feature/dashboard-card-double-click (extends prior commit)

• stopPropagation on a wrapper <div> around <property-value> wasn't reliably stopping v-card's click — emulator breakpoint showed handlers on Vuetify's div.overlay-content fire and the v-card handler still fires afterward.
• Switched approach: DashboardWidget.vue now uses onCardClick(event) that bails if event.target.closest('.dashboard-widget__noselect') — doesn't depend on bubble semantics.
• DashboardOverview.vue wrappers now carry the .dashboard-widget__noselect marker class instead of @click.stop.
• Temporary console.debug in the handler logs the origin element for verification.
• Branch: feature/dashboard-card-double-click

• Emulator test showed tapping a property value still opened the inspector, so the bare @click.stop on the <property-value> component root wasn't intercepting the bubble as intended.
• Wrapped each <property-value> in DashboardOverview.vue (hero slot and properties slot) in an explicit <div @click.stop> — the interception point is now on a DOM element we control rather than relying on component fallthrough.
• Branch: feature/dashboard-card-double-click

• DashboardWidget.vue: dropped smAndUp gate on the v-card @click so tapping anywhere on the card (not just the title) opens the asset inspector on mobile.
• DashboardOverview.vue: added @click.stop on the <property-value> instances used in the hero and properties slots. The tooltip activator still fires on tap, but the click no longer bubbles to the card — so tapping a property value shows only the tooltip without also opening the inspector.
• Motivation: PropertyValue wraps its content in v-tooltip, whose activator opens on tap on touch devices — previously we gated the card-level click on desktop only to avoid hijacking that tooltip tap.
• Caveat: still want to verify on a real mobile device that tap → tooltip behavior is preserved.
• Branch: feature/dashboard-card-double-click

• New route /d/:serialNumber redirects to /assets/:uuid?install=true for field techs
• use-asset-by-serial.ts composable — temporarily uses UUID lookup until backend ships assetBySerialNumber query
• InstallRedirectView.vue — loading spinner while resolving, error state if not found
• Added missing i18n keys for install_wizard and install_redirect
• Removed stale alertConfigDashboard route that referenced a file only on an unmerged branch

• Root cause: useAsset query uses fetchPolicy: "no-cache", so props.asset doesn't update after the updateAssetMutation succeeds — assetPlacedOnSelectedFloor stays false, assetsOnFloor returns [], no pin renders
• Fix: added localPlacement ref to track floorUuid/floorX/floorY after successful mutation, used in the computeds that drive pin rendering (mirrors existing removedFromFloor pattern)
• Also updated onMoveAsset (drag) and onFloorSelected (clear) to maintain localPlacement
• Deployed to staging

• DashboardOverview.vue: added @dblclick handler on both <asset-component> and the fallback <dashboard-widget> that navigates to the full asset dashboard ({ name: "asset", params: { assetUuid } })
• Single-click behavior (open inspector side panel) is unchanged; double-click briefly opens the inspector then navigates away (imperceptible flash)
• Considered and deferred: floorplan pins and report tables already have cmd/ctrl/shift-click → new tab, so adding double-click there would be a redundant affordance. Thresholds report is the only remaining inspector surface without an open-dashboard shortcut — left for future decision based on user feedback.
• Branch: feature/dashboard-card-double-click

• Ran /impeccable teach to gather design context through a structured interview
• Wrote .impeccable.md at project root with full Design Context: users (mixed operators + field techs), brand personality (calm, competent, clinical), aesthetic direction (Linear/Height × Honeywell Forge), locked brand palette, WCAG 2.1 AA target, and 5 design principles
• Created CLAUDE.md at project root with a condensed summary so the design context loads into every Claude session
• Also ran the one-time post-update cleanup (no deprecated impeccable skills to remove)

• Clicking a photo thumbnail opens the fullscreen LightboxCarousel
• Hovering a thumbnail shows a red close-circle icon to delete the image (uses DocumentDeleteDialog)

• Clicking a photo thumbnail opens the fullscreen LightboxCarousel at the clicked image

• Added shimmer placeholders while photos load, empty grey box when no photos
• Set min-height: 64px on photo container to prevent layout jump between states

• Floor selector now updates when building changes — derive from selectedBuildingUuid instead of stale props.asset.building
• Pre-select floor when asset is already placed on one

• Floor selector now updates when building changes — was using props.asset.building (stale after move) instead of selectedBuildingUuid (updates immediately)
• Branch: feature/install-wizard

• Changed Auth0 redirect URI from /connect to /callback
• Fixed vite dev server host fallback from typo 127.0.1 to localhost
• Added DEV_PORT fallback for vite port config (PORT → DEV_PORT → 8090)
• Branch: feature/portless-support

• useAccountBuildings was returning empty groups after navigating around the app — cache-first default was serving a null result from an earlier failed query
• Added fetchPolicy: "no-cache" to the query
• Outstanding: on fresh page load the backend sometimes still returns empty buildings with identical query/vars/uuid as successful hot reload — tracked for later investigation
• Files: use-account-buildings.ts

• Step ordering is now: Name → Photos → Building → Floorplan
• Three-way render for the building step based on building count:

- Multiple: dropdown selector that moves the asset via moveAssetsMutation on selection

- Single: plain text (non-editable)

- Empty: "No buildings loaded." with a reload link — added for testing while the backend race condition is unresolved

• Gated the floorplan step on the current building actually having floorplans (removed old "loading"/"no floorplans" fallback messages)
• Switched building query source from navStore.contextAccountUuid to props.asset.accountUuid (computed ref) so it works on fresh page load without relying on nav state
• Files: InstallWizard.vue, en.json

• feature/portless-support had accidentally picked up a chain of earlier install-wizard commits on top of the portless commit
• Reset the branch to the merge base with main and cherry-picked just a63b41e7 (the portless commit)
• Force-pushed with --force-with-lease
• Branch now contains only the portless.sh support commit

• use-dashboard-config.ts: collapsed/expanded state of reorderable sections is no longer persisted to the server UI preference
• On load, collapsed from server preference is ignored; in-memory state is preserved across preference updates (so reorder saves don't stomp local collapse state)
• toggleCollapsed mutates config directly instead of routing through updateSection — no backend round-trip on expand/collapse
• restoreCollapsedState no longer calls save(); reorder-mode collapse-all/restore flow is now purely local
• Branch: fix/dashboard-ephemeral-collapse

• Added building selector as a step in the install wizard, only shown when the account has multiple buildings
• Uses moveAssetsMutation to reassign the device when a new building is selected
• Step numbers adjust dynamically based on whether the building step is shown
• Files: InstallWizard.vue, en.json

• Derive Auth0 redirect URI from window.location.origin instead of env var (VUE_APP_AUTH0_CALLBACK_URL)
• Read PORT and HOST from environment in vite config (previously DEV_PORT only)

• Created InstallWizard.vue — inline wizard shown at top of asset dashboard when ?install=true
• Three optional steps: name device (saves on blur), upload photos (reuses DocumentUploadDialog), place on floorplan (inline FloorplanMap with click-to-place)
• "Complete" button strips install query param to dismiss
• Modified FloorplanMap.vue to pass Leaflet click event coordinates through click-floorplan emit
• Modified DeviceDashboardLayout.vue to conditionally render wizard via defineAsyncComponent
• Added floorUuid to use-asset.ts GQL query for floorplan pre-selection
• Photo section styled with dashed drop target and thumbnail row below
• Fixed floorplan not rendering — root cause was missing explicit width: 100%; height: 100% on FloorplanMap (parent must provide dimensions)
• Fixed photo thumbnails stretching full width with flex: 0 0 80px
• Preload floorplan images via appStore.preloadImage() to avoid loading spinner

• Active alerts now grouped by definition+asset (same as recent alerts), with expandable caret but no count number (caretOnly prop)
• Fixed condensed property graph in group expansion: suppressed auto-title (title=""), hid date picker (synched-timeframe=true), passed explicit start/end dates matching the Recent Alerts date range, preserved alert event overlays
• Styled timestamp links with primary color and hover underline (were unstyled text-decoration-none)
• Extracted shared groupInstances() helper in BuildingAlertsRecent.vue to DRY up active/recent grouping logic
• Removed unused formatInstanceRow function
• Files: AlertInstanceGroupTable.vue, BuildingAlertsRecent.vue

• Renamed view switcher button "Config Alerts" → "Alert Configs" (en.json)
• Fixed column alignment between Active/Recent alert tables using table-layout: fixed with percentage widths
• Created AlertConfigDashboard.vue — new read-only page showing alert config summary + property graphs per asset with alert event overlays
• Created AlertConfigSummary.vue — reusable read-only display of alert config fields (name, severity, property, dwell, assets, periods, recipients)
• Added alertConfigDashboard route at alerts/config/:alertDefinitionUuid
• Updated Recent Alerts: alert name links to dashboard, removed asset links, timestamps now link to Alert Activity page
• Refactored AlertInstanceGroupTable.vue from v-data-table to v-table for full row control; added condensed PropertyGraph (150px) in group expansion above instance rows
• Updated Alerts Config (BuildingAlertsIndex): alert name links to dashboard, removed asset links, simplified expanded row to Assets + Recipients only (removed Active Periods)
• Branch: feat/alert-config-dashboard, 8 commits, all 417 tests passing
• Files: AlertConfigDashboard.vue, AlertConfigSummary.vue, AlertInstanceGroupTable.vue, BuildingAlertsIndex.vue, BuildingAlertsRecent.vue, router/index.ts, en.json

• date.ts: cast toHuman({ unitDisplay: "short" }) to Intl.NumberFormatOptions — @types/luxon 2.x doesn't include it in ToHumanDurationOptions
• number.ts: replaced VueI18n.NumberFormatOptions with Intl.NumberFormatOptions — Vue I18n 9 no longer exports that type
• vee-validate/utils.ts: FieldValidationMetaInfo no longer exported — derived from GenericValidateFunction parameters; added explicit cast to ExtendedValidationRuleSchema for type narrowing
• Files: date.ts, number.ts, vee-validate/utils.ts

• killall aws after deploy was killing ALL AWS CLI processes, preventing parallel deploys
• Replaced with pkill -f targeting only the tunnel for the specific deploy target's instance ID
• Resolves SSH alias → instance ID via ssh -G <host> to match the correct open-tunnel process
• Verified parallel deploys to development and staging now work simultaneously
• File: config/deploy.rb

• Clicking a group header in the asset autocomplete (e.g. on create alert page) triggered both our handleSelectAllInGroup AND Vuetify's internal item selection via v-bind="listItemProps"
• Vuetify's handler selected the group header item (value "group-xxx") which overwrote the real selection
• Root cause confirmed via debug logging: two emissions — first correct (2 assets), second incorrect (1 non-asset item, 0 matched)
• Fix: removed v-bind="listItemProps" from group header v-list-item; also extracted emitSelection helper to ensure both update:modelValue and update:selectedAssets are always emitted together
• File: AssetSelector.vue

• RecipientSelector.vue and AssetSelector.vue used item.text/item.description in #item slots — Vuetify 3 wraps slot items, raw data is at item.raw
• :filter prop renamed to :custom-filter in Vuetify 3, function signature changed to (value, query, item)
• Recipient names were blank in dropdown; asset search filtering was broken
• Files: RecipientSelector.vue, AssetSelector.vue

• When search matched no assets, categoryGroups was empty, falling through to "no assets" alert and hiding the search box
• Added hasSmartAssets computed (pre-search check) to gate the search/toolbar area
• Search box now stays visible; shows "No matching assets found." instead of misleading "no assets" message
• Added messages.no_results i18n key
• Files: DashboardOverview.vue, en.json

• Guard updateAsset splice against findIndex returning -1 (DashboardOverview.vue, AssetTableReport.vue)
• Escape user search input with lodash escapeRegExp to prevent invalid regex crashes (DashboardOverview.vue, AssetTableReport.vue, BuildingAlertsThresholds.vue)
• Replace <a> with <v-btn> for reorder toggle (DashboardOverview.vue)
• Use i18n keys for hard-coded strings: 'Reorder sections', 'Done', 'Add section' (DashboardOverview.vue, en.json)

• schedule_enabled is not a visible form field — it's inferred from schedule data
• Including it in SchedulePlan descriptors caused spurious failure icons from CONFIRM_TIMEOUT states the user can't see
• Filtered it out of timeDescriptors in SchedulePlan.vue
• File: SchedulePlan.vue

• Status icon (spinner/error) in FormExpansionPanel was centered instead of next to the title
• Used flex-grow-1 on header div so internal spacer pushes details right, matching production layout
• File: FormExpansionPanel.vue

• syncPendingStateManagementRequests checked asset.deviceLock (truthy if object exists) instead of asset.locked (false when expired)
• This caused the refresh button to show "Refreshing" with a progress bar after the lock expired
• Fix: check asset.locked instead of asset.deviceLock
• File: state-management.ts

• When device lock expires but fields still have pending: true, show failure status instead of pending spinner
• Stale pending is effectively a failed update
• File: asset-form.ts

• Schedule bank fields had stale pending: true from the server even after device lock expired
• FormExpansionPanel header aggregated all field statuses (including 48 schedule time descriptors), showing a spinner
• Fix: copySinglePropertyToForm now takes a locked parameter; when not locked, pending is treated as false
• Both status display and value selection respect effective pending state
• Files: asset-form.ts, tests/config/asset-form.spec.ts

• Added .isValid check on parsed expiration to guard against malformed date strings
• File: asset.ts

• readBanksFromSchedule crashed with TypeError when schedule_days was null (occurs for banks in RETRY_PENDING/CONFIRM_TIMEOUT states)
• Fix: (dayNames ?? []).map(...) to safely handle null values
• File: schedule-conversion.ts

• decorateAsset was treating any device with a deviceLock.expiration as locked, even if the expiration was in the past
• Fix: check DateTime.fromISO(expiration) > DateTime.now() so expired locks are ignored
• File: asset.ts

• vee-validate v4's resetForm() resets field values back to initial, unlike v3 which only cleared flags
• After reset, model sync watcher pushed current values back in, immediately re-dirtying the form
• Fix: pass current values to resetForm({ values: { ...values } }) so they become the new baseline
• File: ValidatedForm.vue

• Status tooltip overlapped select dropdowns because it stayed visible on hover while the menu opened
• Added v-model and @click handler on activator to dismiss tooltip when a field is clicked
• File: FieldStatusTooltip.vue

• Vuetify 3 tooltips use darker surface-variant background and 10px default offset vs Vuetify 2's grey-darken-2 at 90% opacity and ~4px
• Added global CSS override in styles.scss with !important (needed because vite-plugin-vuetify auto-import injects component styles after global styles)
• Set explicit offset on FieldStatusTooltip.vue; Vuetify 3 defaults config doesn't reliably override VTooltip props
• Files: styles.scss, FieldStatusTooltip.vue

• vee-validate v4's defineRule callback provides field context as a third ctx parameter; installRule wasn't capturing it
• Without ctx.field, lookupRuleMessage fell back to the rule name as the field name, producing non-existent i18n keys like fields.tstat_y1_conditions.tstat_y1_conditions
• Fix: capture ctx: FieldValidationMetaInfo and pass _field_: ctx.field into the message lookup values
• Affects all custom validation rules registered via installRule, not just tstat wiring
• Added tests for lookupRuleMessage and installRule field name propagation
• Files: vee-validate/utils.ts, tests/plugins/vee-validate-utils.spec.ts

• Moved check icon to #append slot (Vuetify 3 requirement), only show on selected preset
• Added Vuetify 2 dense list font styles (0.8125rem, weight 500, line-height 1rem) since Vuetify 3 density="compact" only affects padding
• File: DateRangeMobile.vue

• Replaced body-1 -> text-body-1, body-2 -> text-body-2, subtitle-1 -> text-subtitle-1, caption -> text-caption across 19 files
• Files: AssetControlPanel, AssetFilterMenu, AssetHeader, AssetInspector, AssetPropertyMenu, BuildingCard, BuildingHeader, DeviceDashboardLayout, FloorCard, FloorplanTopBar, PortfolioHeader, PropertyItem, CommentItem, DateRangeDateInputs, DateRangeMobile, NoteCreateMutationPresenter, SwitchScheduleDay, ScheduleDay, ScheduleBank

• Changed occupancy dashboard heading and field labels from "last 10 minutes" to "since last report"
• File: en.json

• Tooltips in PropertyValue and FieldStatusTooltip were rendering behind the inspector (z-index 10000)
• Added z-index: 10001 to both v-tooltip instances
• Files: PropertyValue.vue, FieldStatusTooltip.vue

• Changed inspector container from position: absolute to position: fixed with top: 0; bottom: 0 to match dashboard layout
• File: BuildingFloorplansTab.vue

• Used flex layout inside v-toolbar-title__placeholder so the title link truncates with ellipsis while the open-in-new icon never shrinks
• Icon flows inline with the title text; only pins to the right edge when the title overflows
• File: AssetInspector.vue

• vee-validate v4 treats false as empty for required validation (v3 did not)
• String switch fields sync a display boolean to vee-validate; toggling OFF synced false, failing required validation and cancelling the mutation
• Fix: sync the raw string value (e.g. "OFF") to vee-validate for string switches instead of the display boolean
• Affects switch_status (ubx-switch-100) and socket_status (ubx-plug-100)
• Files: FormField.vue, SwitchField.vue

• Inspector toolbar title was truncated at 140px — Vuetify 3's v-toolbar-title flex rule collapsed it; fixed with flex: 1 1 auto
• Moved open-in-new-window button out of toolbar title so it stays visible when name truncates
• Fixed desktop widget title click not opening inspector — stopPropagation was always firing, now only on mobile
• Files: AssetInspector.vue, DashboardWidget.vue

• Expanded from 4 to 10 default categories: Thermostats, Equipment, Environment, Refrigeration, Occupancy, Doors, Electrical Switches, Energy, Water Leaks, Other
• Each category lists specific knownAssetUuids; Other is empty (default bucket)
• Changed card sort from model-name/asset-name to knownAssetUuid array position then alphabetical by name
• Files: dashboard-categories.json, DashboardOverview.vue

• Replaced plain text asset count next to section headers with v-chip size="small" color="grey-lighten-3" to match tstat schedule day count style
• File: DashboardOverview.vue

• On desktop, clicking anywhere on the card opens the inspector (unchanged)
• On mobile, only clicking the asset name opens the inspector, allowing taps on property values to show tooltips
• Uses useDisplay smAndUp breakpoint to conditionally bind click handlers
• File: DashboardWidget.vue

• On mobile, StandardDialog with full-screen-on-mobile was closing when clicking v-select dropdown items
• Root cause: v-select dropdown renders outside the v-card, Vuetify treats click as click-outside and dismisses dialog
• Fix: add persistent: true to fullscreen mobile dialog props — user closes via X button only
• File: StandardDialog.vue

• Floor selector button was rendering as white solid button instead of transparent text — changed deprecated Vuetify 2 text prop to variant="text"
• Property menu icon (map marker) was on the right instead of left of floor name — moved asset-property-menu before the floor button
• File: FloorplanTopBar.vue

• Removed out-of-scope "Recent Changes" placeholder card
• Hidden "Add section" button behind ?edit=true query param

• Replaced flexbox container (d-flex flex-wrap) with CSS grid (repeat(auto-fill, minmax(280px, 1fr))) for equal-width columns
• Added height: 100% pass-through from v-lazy wrapper to card for equal-height rows
• Fixed properties grid row stretching with align-content: end (was align-content: stretch default, inflating rows when card height exceeded content)
• Barry manually tuned widget styling: border, border-radius, font sizes, font weights, property label sizing

• Entering reorder mode was calling toggleCollapsed per section, each firing a SaveUIPreference mutation; responses arriving at different times caused sections to flicker open/closed
• Added setCollapsedAll (local-only, no save) and restoreCollapsedState (single save) to useDashboardConfig
• Entering reorder mode now fires 0 mutations, exiting fires 1

• Removed hasAlerts prop, left-side red shading, #alerts slot from DashboardWidget and all 8 device-specific widgets
• Removed mock alert function and alerts summary placeholder from DashboardOverview
• Alerts are not being surfaced in this release

• Replaced My Assets / All Assets toggle with a throttled search box
• Filters dashboard cards by name, floor, category, model, manufacturer, serial number, etc.

• Moved all hardcoded report titles and descriptions to en.json under reports_tab
• Updated report cards in BuildingReportsTab and page headings in report components to use $t()

• Created AssetTableReport.vue shared wrapper with search, selection, inspector slideout, and move dialog; exposes data via scoped default slot and toolbar via named slot
• Created 3 thin report pages: BuildingSensorDataReport.vue, BuildingDeviceHealthReport.vue, BuildingAssetInventoryReport.vue
• Added routes: /buildings/:buildingUuid/reports/{sensor-data,device-health,asset-inventory}
• Added report link cards to BuildingReportsTab.vue; made BuildingReportLinkCard image prop optional
• Stripped BuildingAssetsTab.vue down to just <dashboard-overview>
• Gave DashboardOverview.vue its own inspector slideout (no longer emits select-asset)
• Deployed to staging

• Replaced settings button with inline reorder toggle and add-section button
• Disabled drag and hid handles outside reorder mode
• Fixed misleading cursor-pointer on section header row

• Replaced router-link navigation in DashboardWidget with a select emit on card click
• DashboardOverview bubbles the event as select-asset to BuildingAssetsTab
• BuildingAssetsTab wires it to the existing selectAsset() / AssetInspector flow

• Desktop: replaced centered v-dialog with a fixed slideout panel from the right (v-slide-x-reverse-transition), matching the floorplan tab pattern
• Mobile: fullscreen dialog
• Applies to all views (dashboard, properties, health, inventory)

• Added click-to-inspect on dashboard cards
• Replaced inspector dialog with fixed slideout panel (desktop) / fullscreen dialog (mobile)

• Created DashboardWidget.vue card shell with named slots (hero, properties)
• Added device-specific widgets: thermostat, IAQ, switch, plug, leak, VRF, ventilator
• Updated DashboardOverview.vue to use widget cards instead of AssetPropertyCard
• Removed AssetPropertyCard.vue
• Fixed dashboard widget styling and runtime errors

• AlertForm.vue: unused celUiData variable — wired it up to populate condition_property in edit mode
• .eslintrc.js: added defineOptions to globals (Vue 3.3+ compiler macro not recognized)
• BuildingFloorplansTab.vue: removed extra blank line before closing </div>
• BuildingEnergyReport.vue: removed unused router import/assignment

• Crawled Dashboard + Configuration tabs for all 36 asset model types using Chrome DevTools MCP
• Found 2 fixable Vue 3 warnings (VHover loading prop, markRaw on async components) — both fixed
• Found 1 data issue (orphan asset UUIDs 1b760882... and e57a0ac1... missing config) — not a code fix

• Tolerance fields (Heating/Cooling On/Off) showed "±°F" suffix wrapping to 2 lines. The suffix was rendered as a <span> in the append-inner slot, which Vuetify 3 constrains. Switched to using Vuetify 3's native :suffix prop on v-text-field, reserving append-inner for the status icon only.

• Sensors and Device Health views logged intlify warning: Not found 'properties.switch.switch_status.options.OFF'. The switch config defines options: ["ON", "OFF"] but locale file had no options block. Added "ON": "On" and "OFF": "Off" translations.

• Dashboard/Floorplans logged Apollo warning about assetDataChanges subscription data arriving as object with numeric keys instead of array. Added merge: false type policy for Subscription.assetDataChanges in InMemoryCache config to prevent Apollo from trying to normalize the union-type array.

• Configured chrome-devtools-mcp for the project to enable browser navigation, screenshots, and console error inspection from within Claude Code. Requires Chrome launched with --remote-debugging-port=9222 --user-data-dir=~/.chrome-debug-profile.

• OccupancyCurrent.vue passed :loading to MetricItem, which doesn't declare it as a prop. The attribute fell through to Vuetify 3's VHover, which doesn't accept it either, triggering Vue 3 extraneous attribute warnings on all cumulative occupancy sensors (OCC100, OCC102, OCC107, OCC400). Removed the unused :loading bindings.

• AssetComponent.vue called defineAsyncComponent() inside a computed(), making the returned component object deeply reactive. This triggered Vue 3 markRaw warnings on VS1000RTh and VS400CMh (VRF device types). Wrapped with markRaw() to prevent unnecessary reactivity tracking on component definitions.

• AssetSelector lacked inheritAttrs: false, so FormField's type prop leaked through as a fallthrough attr to v-autocomplete's inner <input>, causing number spinners. Same pattern as the FileField fix from the March 3 session.

• v-if="value" was a leftover from Vuetify 2 naming. Changed to v-if="isOpen" to match the useDialogState composable.

• Same Vuetify 3 #prepend slot auto-wiring issue as the alert copy-to-days fix. PropertySelector used v-model:selected on v-list with v-checkbox-btn in #prepend — Vuetify's internal selection overrode manual state.
• Removed v-model:selected from v-list, managed checkbox state explicitly via props and toggle events through PropertySelectorGroup → PropertySelectorRow.

• Vuetify 3's v-hover isHovering starts as null, not false. SettingCard.vue passed it to PropertyTimestamp's boolean showTimestamp prop. Added ?? false coercion.

• Route name "building" was on the floorplans child route instead of the dashboard (default) child route. Breadcrumbs, portfolio cards, map markers, and journal links all landed on floorplans.
• Swapped: "building" → dashboard route, "buildingFloorplans" → floorplans route. Updated all references across 6 files.

• 5 files still referenced buildingTStatSchedules after it was renamed to buildingConfigTStatSchedules in the router — caused navigation errors on journal schedule links and device config page.
• Fixed style="mt-2" → class="mt-2" on dashboard settings button in BuildingAssetsTab.vue.

• AlertForm.vue initialized assetLinks with text: a.assetUuid instead of text: a.name, and set condition_property before propertyOptions were available.
• Deferred both to the buildingAssets watch — asset links and property are now populated once building assets load, so selects have options to resolve display names.

• In ManageAlertActivePeriods.vue, the "copy to days" dropdown used :model-value (one-way binding) on checkboxes in v-list-item #prepend slots. Vuetify 3's list selection auto-wiring overrode the manual state.
• Switched to v-model="pendingCopyDays" + :value="dayOption.modelValue" — the standard Vuetify 3 array checkbox pattern.
• Also fixed dayOption.value → dayOption.modelValue to match the CopyDayOption interface (was resolving to undefined).

• BuildingEnergyReport.vue used router.currentRoute.params.buildingUuid — in Vue Router 4, currentRoute is a ShallowRef requiring .value.
• Replaced with useRoute() composable (route.params.buildingUuid), consistent with the rest of the codebase.
• Also fixed App.vue: two occurrences of router.currentRoute.name → router.currentRoute.value.name.

• Vuetify 3's v-date-picker emits Date objects instead of ISO strings. DateField.vue expected strings throughout.
• Added pickerValue computed to convert incoming ISO string → Date for the picker, and handleInput to convert emitted Date → ISO string for the model.
• AssetForm.vue: changed default installationDate from null to DateTime.now().startOf("day").setZone("utc") so new assets default to today.

• Missing route: JournalItemSubtitle had a fallback { name: "home" } route that doesn't exist — the route was renamed to portfolio during the Vue 3 migration. Caused a crash when rendering account-level journal events (no building/floor/asset).
• String-typed booleans: model-value="true" on v-chip passes the string "true" in Vue 3, not the boolean. Changed to :model-value="true" in AlertSubscriptionMutationPresenter, JournalAlertRecipient, and AlertRecipient.

Several drag-and-drop issues on the Building Floorplans page after the Vue 3 migration:

• Marker opacity: vue-leaflet v3 doesn't support the opacity prop on l-marker. Moved opacity from the marker to a wrapper div inside l-icon in AssetMarker.vue.
• Browser drag interference: Pin <img> elements triggered the browser's native drag instead of Leaflet's marker drag. Added draggable="false" to both images in AssetPin.vue.
• Pin container sizing: .pin-container was display: block (full-width), causing the clickable/draggable area to extend across the map. Changed to inline-block so it sizes to the pin content.
• vue-easy-dnd drag image positioning: The .__drag-image container rendered in-flow instead of off-screen because vue-easy-dnd's scoped styles are lost in the pre-built dist bundle. Added global styles to position it fixed at -10000px.

Added the ability to remove an asset from a floorplan by dragging its pin off the edge of the floorplan image. When a marker's moveend fires with coordinates outside the [0, sizeY] × [0, sizeX] bounds, a confirmation dialog appears (reusing the existing "Remove from Floor" dialog strings from the asset inspector). On confirm, the asset is unplaced; on cancel, the pin clamps to the nearest floorplan edge via forceCoordsOntoFloorplan.

Updated ~/.claude/bin/generate-worklog-rss.py to support optional HH:MM timestamps in worklog headings. Headings can now be ## YYYY-MM-DD HH:MM: title — the time flows through to RSS pubDate and HTML display. Entries without timestamps remain backward compatible (default to midnight).

Documented the 3 steps needed to backport fridge dashboard alert overlays to the Vue 2 branch, in case we need to ship this feature before the Vue 3 migration lands:

1. Add useBuildingAlerts to use-asset-alerts.ts and call from AssetView.vue (building-level definitions instead of asset-level)

2. Collect all displayed asset UUIDs in PropertyGraph.vue (not just primary asset)

3. Change assetUuid → assetUuids in useAlertInstancesForProperties

Also notes what NOT to port (DeviceDashboardLayout refactor, store rename, Vue 3 reactivity fixes).

Doc location: ~/.claude/projects/-Users-barry-Projects-sbg-webapp-vue3/memory/reference_fridge_alerts_vue2_port.md

• Renamed useAssetAlertsStore → useAlertDefinitionStore (store file assetAlerts.ts → alertDefinitionStore.ts)
• Moved store-populating composable from use-asset-alerts.ts into use-alert-store.ts as populateFromBuildingAlerts()
• Deleted use-asset-alerts.ts (both useAssetAlerts and useBuildingAlerts were dead code or moved)
• Updated imports in AssetView.vue and use-alert-instances.ts
• Added v-progress-linear loading indicator to FridgeDashboardTab while linked assets load (was showing blank area)

• Added useBuildingAlerts composable alongside existing useAssetAlerts — queries buildingAlerts(buildingUuid) instead of assetAlerts(assetUuid), same store
• Extracted shared ALERT_DEFINITION_FIELDS fragment to avoid duplication between the two queries
• AssetView now calls useBuildingAlerts instead of useAssetAlerts — the store holds definitions for all assets in the building, so every PropertyGraph can find relevant definitions for linked assets
• useBuildingAlerts accepts nullable buildingUuid and gates the query via Apollo's enabled option until the asset (and its building) loads

Tested multi-asset alert overlays on the fridge dashboard on staging. Initial deploy only had the instance query changes — discovered that alert *definitions* were still only fetched for the primary asset (AssetAlerts query), so linked asset alerts never appeared. Added useBuildingAlerts composable to fetch building-level definitions, redeployed to staging for further testing.

Built a design document for integrating an LLM-powered chat agent into the platform. Users would ask natural-language questions about their buildings' HVAC systems and get data-driven suggestions.

Key design challenge: LLMs are stateless, so every request requires full context reconstruction — user identity, current building, session history, and specialist agent selection (scheduling, energy, air quality). Solution is a layered context assembly system: platform knowledge → building config → persistent building memory → specialist agent → conversation history, assembled per call and stored in the DB.

Data access runs through existing Strawberry resolvers so auth, tenant isolation, and permissions are inherited.

Phase 1 is read-only — the agent observes and advises but doesn't modify setpoints or schedules. Future phases: autonomous conversations (e.g. triggered by alerts) and tool usage (making changes with user approval).

Resolved the "Maximum recursive updates exceeded" crash that had been blocking the fridge dashboard since 2026-03-12. This was a multi-session, multi-iteration debugging effort — at least 4-5 attempted fixes across previous sessions before landing on the working approach.

Root cause

Vue 3's Object.is() reactivity check treats every computed re-evaluation as a "change" when the computed returns a new object, even if all field values are identical. The PropertyGraph component tree (Series → Group → Graph) uses exposeDataToParent to pass data upward via use-component-tree. Each level's data computed created a fresh object every evaluation, which the parent saw as changed, which triggered its own recomputation, cascading back down — an infinite reactive loop.

The fix (applied at every level of the tree)

• PropertyGraphSeries: stabilized both seriesDetails and data with shallowRef + watch that compares individual fields before updating the ref
• PropertyGraphGroup: same pattern — field-by-field comparison before allowing the ref to update
• PropertyGraph: same pattern for its simpler 2-field data object
• use-component-tree.ts: batched registerChild/unregisterChild calls via nextTick so multiple children mounting in the same tick produce only one reactive update
• HighchartsGraph.vue: replaced direct optionsWithDefaults binding with a stableOptions ref that only updates after the chart instance exists — prevents highcharts-vue's deep watcher from crashing on null chart during mount

FridgeDashboardTab refactored to DeviceDashboardLayout

• Replaced manual GraphTimeframeSyncer / PropertyGraphList / date state with DeviceDashboardLayout, which provides alert overlays and centralized timeframe management
• Removed ~50 lines of boilerplate (date refs, canShowGraph computed, store imports)
• Added hasSensors computed + v-alert for the no-sensors case

LineGraph initialLoading bug fix

• initialLoading was checking s.series.value === undefined || s.series.value.data.length === 0 — this stays true forever for series that legitimately have no data (e.g. energy graphs), keeping the loading spinner stuck
• Changed to s.loading.value which correctly distinguishes "still fetching" from "fetched but empty"

• useAlertInstancesForProperties now accepts assetUuids: string[] instead of assetUuid: string — removed the internal single-to-array conversion, passes array straight through
• PropertyGraph.vue: new displayedAssetUuids computed collects UUIDs from all non-navigator groups, context selections, and compared selections (deduplicated via uniq)
• displayedPropertyNames no longer filters to primary asset only — includes property names from all displayed series
• Effect: fridge temperature graphs now show door alerts (from linked door sensor assets) alongside temperature alerts

Extracted all 36 alert conditions from the existing NewRelic instance managed by Mission Cloud, in preparation for decommissioning that instance and moving to a self-hosted NewRelic deployment.

• item-key renamed to item-value in Vuetify 3; without this, v-model with show-select stores undefined values instead of row identifiers
• Added return-object so v-model stores full objects (matching Vuetify 2 behavior and existing code expectations)
• Fixed in: DocumentList, AssetsTable, AssetThresholdsTable, AssetConfigAssignmentList, TaskScheduleAssignmentList
• BuildingAlertsIndex: item-key → item-value only (uses show-expand, not show-select)

• selected ref initialized to {} — Vuetify 3's v-select with return-object renders empty object as [object Object]
• Changed init/reset from {} to null; added optional chaining on invalid computed

• effectiveOptions returned SelectOption objects to ComboboxField which expects string[]
• When options prop is provided, normalizedOptions short-circuited the combobox string extraction
• Fix: extract .text from normalizedOptions when displayType is combobox

• small-chips and deletable-chips props removed in Vuetify 3 — replaced with chips and closable-chips
• Fixed in: AssetSelector, RecipientSelector, SelectField

• Vuetify 3's #item slot itemProps includes title which renders automatically — destructured it out to prevent duplicate text alongside manual v-list-item-title
• AssetSelector: also moved group header checkbox from #default to #prepend slot
• Fixed in: AssetSelector, RecipientSelector (SelectField was already fixed)

Two Vue 3 rendering errors when navigating to a fridge asset's dashboard tab. First error fixed; second still under investigation.

Fixed: Cannot read properties of null (reading 'emitsOptions')

• Root cause: highcharts-vue's options watcher fires before mounted() creates the Highcharts instance — this.chart.update() on undefined
• Fix in HighchartsGraph.vue: added chartReady ref that defers <highcharts-chart> creation by one tick via onMounted → nextTick, gating render with v-if="initialLoading || !chartReady"

Under investigation: Maximum recursive updates exceeded in component <PropertyGraphList>

• Occurs after the emitsOptions fix, when the fridge dashboard's PropertyGraphList mounts with 3 PropertyGraph children (temp, humidity, energy)
• Suspected reactive cycle involves bidirectional data flow: PropertyGraphList provides context to child PropertyGraphs, children expose data back to parent via use-component-tree, parent watches that data to update context
• Key chain: graphData → normalGraphData → categoriesToGraphIds → watch sets selectionsForExistingGraphs → children read context → children's data computed creates new object → graphData invalidated → cycle
• Apollo notifyOnNetworkStatusChange: true in useLinkedAssets may be contributing by firing multiple onResult callbacks during flush
• Attempted fixes that didn't work: shallowRecordEqual guard in PropertyGraphList's watch, nextTick batching in use-component-tree.ts's updateSortedChildren
• Next steps: need to identify the exact reactive trigger — may need to add diagnostic instrumentation to confirm which dependency is actually cycling

• Added "Set as Account Default" button to DashboardSettingsDialog.vue
• Button only visible when isCustomized is true (user has a saved preference that isn't already the account default)
• Wired promoteToAccountDefault from useDashboardConfig through DashboardOverview to the dialog via prop/event
• Added confirmation dialog before promoting
• Backend mutation and locale key already existed; this was frontend-only

• Analyzed 3.4MB main JS bundle — 39 of 48 route components statically imported, Highcharts and Google Maps loaded eagerly
• Wrote implementation plan: lazy-load route components, lazy-load Highcharts (~400KB, only needed on reports), lazy-load Google Maps (~100KB, only needed on portfolio map)
• Plan saved to ~/.claude/plans/drifting-discovering-prism.md, tracked in task list

• Created ~/.claude/bin/generate-worklog-rss.py — parses all worklog.md files into RSS 2.0 XML
• Created ~/.claude/bin/serve-feed.py — HTTP server on 127.0.0.1:8384 serving ~/.claude/feed/
• Created ~/Library/LaunchAgents/com.claude.feed-server.plist — launchd service (auto-start, keep-alive)
• Configured tailscale serve --bg to proxy port 8384 at /feed
• Added static HTML generation (index.html) alongside RSS for browser viewing
• Feed URL: https://macbook-pro-3.tail89f5bf.ts.net/feed/worklog.rss

• Added <DropList> + <Drag> (vue-easy-dnd) for reordering sections in DashboardOverview
• Compact #drag-image slot shows just the section label while dragging
• Collapse/expand chevron moved to right-aligned with card edge
• Reorder maps visible groups back to full sections array (preserving hidden sections)

• DashboardSettingsDialog.vue — section CRUD: add, edit label, remove, drag-to-reorder
• KnownAssetPicker.vue — multi-select grouped by device type, disables UUIDs in other sections
• Settings button (mdiViewDashboardEditOutline) in BuildingAssetsTab toolbar, left-justified
• Dialog opens via defineExpose({ showSettings }) on DashboardOverview
• Added .dnd-ghost { z-index: 10000 } to global styles for drag image above dialog overlay

• Asset cards wrapped in <v-lazy> for viewport-based rendering
• Removed unused Ref, unref, computed imports
• Added UseDashboardConfigResult return type interface
• Fixed trailing commas via eslint --fix

• Fixed DB.fetchone check_none=False bug in get_ui_preference
• Created feature/ui_user_preferences branch from develop, committed and pushed

• upsert_ui_preference: ON CONFLICT doesn't fire when user_uuid is NULL (NULL != NULL in SQL unique constraints). Changed to UPDATE-then-INSERT pattern for NULL case; non-NULL path keeps ON CONFLICT.
• delete_ui_preference: user_uuid = %(user_uuid)s won't match NULL. Changed to use user_uuid IS NULL for NULL case.
• get_ui_preference and promote_to_account_default needed no changes.

• .asset-control-panel > .d-flex > .v-spacer { display: none } was hiding spacers in all control panels on the dashboard (tstat, switch, plug), breaking their layout
• Added class="asset-property-card" to AssetPropertyCard's root element
• Changed selector to .asset-property-card > .d-flex > .v-spacer so it only applies to property cards

• Added uiPreference query to queries.yaml — ubx_account, any role
• Added saveUiPreference and deleteUiPreference mutations to mutations.yaml — ubx_account, >=viewer
• Added promoteUiPreferenceToAccountDefault mutation — kind: custom (admin check in resolver)
• Without these entries, server returned "Failed to test access to input - check permissions model"

• 6 unit tests covering both NULL and non-NULL paths for upsert and delete
• Mocks hvac2.db at sys.modules level to avoid psycopg2 dependency

## Known Issues to Investigate

VBtnToggle slot warning on asset config page

• URL: /assets/:assetUuid/config
• Warning: Slot "default" invoked outside of the render function in VDefaultsProvider > VIcon > VBtn > VBtnGroup > VBtnToggle
• Component trace: ButtonsField > FieldStatusTooltip > FormField > DeviceConfigTab
• Pre-existing Vuetify 3 migration issue, not caused by dashboard work

Field sizing fix for Vuetify 3

• .small-field and .medium-field classes only had max-width — added explicit width to match
• Root cause: Vuetify 3 removed flex-grow: 1 and width: 100% from .v-input__control, so control columns inside flex-wrap rows collapsed to content size instead of filling to max-width

DashboardOverview styling

• Added dashboard-overview scoping class
• Overrode .control-row column-gap to 6px, .asset-name max-width to 270px
• Added .small-property margin-left: 10px

AssetPropertyCard layout improvements

• Replaced row-grouping approach with PropertyGrid component
• PropertyGrid uses flex: 1 1 400px — fills space beside image/name, wraps to own line when < 400px available
• Right-aligned on desktop, left-aligned on smAndDown breakpoint
• Hidden v-spacer in dashboard context so grid fills available space

Control panel refinements (manual edits by Barry)

• TstatControlPanel: adjusted control-column margin from mt-8 to mt-2
• PlugControlPanel/SwitchControlPanel: replaced bare <div> wrappers with <control-column> using responsive small-field/w-100 classes

Customizable dashboard layout (backend + frontend)

• Created ubx_ui_preference table (SQL migration + create-ubx-tables.sql)
• Backend DB layer: hvac2/hvac2/ubx/ui_preference.py — get, upsert, delete, promote
• Strawberry type: gql_server/objects/ui_preference.py
• Query resolver: gql_server/queries/ui_preference.py
• Mutation resolvers: gql_server/mutations/ui_preference.py (save, delete, promote)
• Fixed DB.fetchone needing check_none=False for nullable query
• Frontend composables: use-ui-preference.ts (generic CRUD), use-dashboard-config.ts (dashboard-specific)
• dashboard-categories.json — added collapsed: false to each entry
• DashboardOverview.vue — replaced static categories with useDashboardConfig, persisted collapse state, drag-to-reorder sections (vue-easy-dnd), gear icon for settings
• DashboardSettingsDialog.vue — section CRUD: add, edit label, remove, reorder, reset to default
• KnownAssetPicker.vue — multi-select grouped by device type, disables UUIDs assigned to other sections
• Regenerated schema.graphql from live server introspection
• Added locale keys under building.dashboard.settings.*

Dashboard cards refactored to use live components

• AssetPropertyCard now wraps AssetControlPanel with PropertyValue components
• Shows asset image, SmartAssetName (online/offline dot), live-updating values
• Cards are full-width, floor groups wrapped in v-cards with titles
• DashboardOverview container changed from flex-wrap to flex-column

Building navigation defaults to Dashboard

• PortfolioBuildingCard, MapCard, JournalItemSubtitle links → buildingDashboard
• Added exact prop to Dashboard v-tab to prevent prefix route matching on child routes

SVG icons for all sensor types

• CT clamp icon: energy sensors (base-energy-sensor + ubx-nrg-103)
• Person with motion lines: occupancy sensors (both base configs)
• Thermometer + water droplet: environment/IAQ sensors (all 6 configs)
• Door sensor (two pieces with signal arcs): contact sensors (CONT-100, CONT-101)
• Generic fallback (box with signal arcs): AssetControlPanel when no image configured

Bugfixes

• Added missing units.milliamps ("mA") locale key
• Fixed buildingTStatSchedules → buildingConfigTStatSchedules route name with required buildingUuid param in 3 tstat schedule components

AppNavbar.vue + UserAvatar.vue (Profile menu)

• Dark theme from v-toolbar bled into menu's v-card → added theme="light" on v-card
• Menu icons were direct children of v-list-item → moved to #prepend slots
• Added centered-icon class to align icons under user avatar

AssetImageCarousel.vue (Lightbox)

• v-model:value → v-model on LightboxCarousel (Vue 3 v-model:value binds to value prop, not modelValue)

DocumentUploadDialog.vue (Document upload)

• Dropzone click didn't open file chooser: missing @click="openFileChooser" handler and upload template ref
• Hidden <input> had static accept="acceptedMimes" instead of bound :accept, no @change handler, no :multiple
• Added openFileChooser() and onHiddenInputChange() functions
• v-file-input #selection slot: Vuetify 3 provides { fileNames, totalBytes, totalBytesReadable } (one call for all files) instead of Vuetify 2's per-file { index, text }

Data table toolbar fixes (5 files)

• Added color="white" to <v-toolbar flat> in DocumentList, SavedScheduleList, SavedSwitchScheduleList, TaskScheduleAssignmentList, AssetConfigAssignmentList (V3 defaults to grey)
• Added variant="flat" to primary action buttons inside those toolbars (V3 VToolbar sets variant: 'text' on child buttons, making them transparent)
• Restored 16px horizontal padding on .v-data-table .v-toolbar .v-toolbar__content via global styles.scss (V3 sets padding: 0 on toolbar content; needed 3-level selector for specificity)
• Zeroed out margin-inline-start on .v-toolbar-title inside data-table toolbars (V3 adds 20px default)
• Styled document name links with text-primary cursor-pointer classes

AppFooter.vue

• Replaced V2 padless prop with pa-0 class (prop removed in V3)
• Added explicit width="150" to logo v-img (collapsed to 0x0 in flex container without it)
• Added flex-grow-0 to prevent footer from expanding (V3 v-footer defaults to flex: 1 1 auto)

SelectField.vue

• Fixed duplicate item text in dropdowns: destructured title out of itemProps since V3 includes it from item-title prop, and we render it manually via v-list-item-title slot

LightboxCarousel.vue

• Raised z-index from 2500 to 10001 on fullscreen v-dialog — asset inspector container on floorplans page has z-index: 10000
• Updated CSS selectors from .v-dialog--active to .v-dialog--fullscreen.v-overlay--active (V3 renamed the active class to .v-overlay--active; .v-dialog--active no longer exists)
• This fixes: dark backdrop (80% black + blur) not applying, and inspector panel rendering on top of lightbox

StandardDialog.vue (Edit Building timezone dropdown)

• Removed style="z-index: 99999" from v-dialog — caused child v-select dropdowns to render behind the dialog (V3 manages overlay z-index stacking automatically)

FormField.vue (Console warnings)

• textFieldType was unconditionally mapping dataType to HTML input type, causing select fields with dataType: "number" (e.g. timezone) to get type="number" on their internal input — browser warned "Pacific Standard Time cannot be parsed"
• Fix: skip setting input type for select/combobox/button display types

Global styles (styles.scss)

• Restored V2 default link color #0076bc via .v-theme--light a:not(:where(.v-theme--dark *, .v-btn, .v-btn *)) — excludes dark-themed areas and button elements
• Restored V2 dark list text color: .v-theme--dark .v-list { color: #fff }
• Restored V2 card text color: .v-theme--light .v-card { color: rgba(0,0,0,0.87) }

BuildingControlsTab.vue (Controls sidebar)

• Changed sidebar v-list from class="text-white" to theme="dark" so the global link color rule excludes it via :not(:where(.v-theme--dark *))

UnplacedAssetsCard.vue + AssetChip.vue (Building Floorplans page)

• Removed non-functional theme="dark" and color="primary" on v-expansion-panel-text
• Removed on-primary class (doesn't exist in V3)
• Fixed CSS selector __wrap → __wrapper
• Added higher-specificity CSS for min-height override
• Removed mt-1 margin from inner div
• Restored bg-grey-lighten-3 on asset list container
• AssetChip: added variant="flat", fixed .primary CSS selector

PortfolioMapTab.vue + PortfolioBuildingCard.vue (Home page)

• Changed class="primary" → class="bg-primary" on sidebar columns
• Made expansion panels transparent so sidebar blue shows through
• Removed bare <template> wrapper around group name
• Eye button: added variant="text" and density="comfortable"
• PortfolioBuildingCard: light → theme="light"
• Removed non-functional color="primary" from expansion panel text
• Added chevron rotation CSS targeting .expand-icon class only (not whole actions container)
• Set chevron icon to 24x36px

BuildingView.vue + AppLayout.vue (Tab navigation)

• Fixed tab highlight not updating when navigating between tabs
• Root cause: exact-path and exact props on v-tab are silently ignored in Vuetify 3
• Fix: Added activeTab computed based on route path, explicit value on each v-tab, model-value on v-tabs
• AppLayout: removed defunct background-color and slider-color props from v-tabs, added activeTab prop
• Added tab styling CSS (color, font-size, letter-spacing, text-transform)

FileField.vue + FormField.vue (Floorplan upload dialog)

• Bug 1: File input rendered as text input (no paperclip, no file picker)

- Root cause: FormField passes type: undefined as fallthrough attr; Vuetify's _mergeProps overrides type="file" with undefined

- Fix: Added defineOptions({ inheritAttrs: false }) to FileField.vue

• Bug 2: Selected file not filling into input / SAVE stays disabled

- Root cause: Vuetify 3 v-file-input emits single File (not File[]) when multiple is not set. onFilesChanged tried files.length on a File object → undefined → emitted null

- Fix: Handle both File and File[] in onFilesChanged via instanceof File check. Removed unnecessary filesArray array adapter — pass modelValue directly to v-file-input

• Bug 3: "Required field" error shown immediately on dialog open

- Root cause: validateOnMount was passed as a computed() ref to vee-validate's useField(). vee-validate checks if (validateOnMount) which evaluates the ref OBJECT (always truthy), never accessing .value

- Fix: Changed to pass plain boolean instead of computed ref

- Also: Skip validation on initial value sync watcher (setFieldValue(newVal, false) on first call)