The shop app gets its help panel, and its last two old screens catch up

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

desktop/app.go

@@ -659,6 +659,15 @@ func (a *App) Sites() ([]cloud.SiteHealth, error) {
 }
 
 // VisitorHistory is one customer's timeline, for the customer record screen.
+// Ask is the help panel. It needs head office: the assistant runs there,
+// against this company's own data, as this signed-in user. A PC running on
+// its own has nobody to ask, and the panel says so rather than erroring.
+func (a *App) Ask(history []cloud.AssistantTurn) (cloud.AssistantAnswer, error) {
+	ctx, cancel := context.WithTimeout(a.ctx, 90*time.Second)
+	defer cancel()
+	return a.cloud.Ask(ctx, history)
+}
+
 func (a *App) VisitorHistory(id string, limit int) ([]cloud.Visit, error) {
 	if limit <= 0 {
 		limit = 100