Ask Behavision: a panel beside any screen that talks to the head-office assistant as the signed-in user - setup questions and 'is my shop working' answered by the same thing, without leaving the app. The assistant's prompt now knows how the product is set up (installation codes, adding a camera, what a placement verdict means, the model download on first run), so it is the help and not only the analyst. A PC running on its own has nobody to ask and gets the essentials as text. Cameras and Customers were still on the pre-redesign markup - the add camera drawer ran off the right edge of the window because it used a class the new stylesheet never sized. Both are rebuilt: cameras as picture-led cards with connection and 'proven' as two separate claims and a placement check laid out as the two steps it is; the customer record as a proper sheet. mock.js renders the app in a browser with fake bindings (?mock=fresh|standalone|claimed, dev server only), so a screen can be put in front of somebody without a Windows build. It is how these were reviewed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KGcjxF1cNLcuwc3DAPcnfj
12 lines
355 B
JavaScript
12 lines
355 B
JavaScript
import React from 'react'
|
|
import { createRoot } from 'react-dom/client'
|
|
import App from './App.jsx'
|
|
import './styles.css'
|
|
|
|
// Dev only: ?mock=<scenario> renders the app in a browser with fake bindings.
|
|
if (import.meta.env.DEV) await import('./mock.js')
|
|
|
|
createRoot(document.getElementById('root')).render(
|
|
<React.StrictMode><App /></React.StrictMode>
|
|
)
|