feat(feedback): FleetCrown users can finally report bugs in FleetCrown

[catomean]

Asked directly: where is the feedback widget on FleetCrown itself, and how does a user give feedback about the site they are using?

Measured on the live app — feedbackWidgetPresent: false, no widget script loaded at all. The only thing in the corner is the Loki assistant button.

A signed-in FleetCrown user has had no way to report a bug in FleetCrown.

The allowlist, and its two reasons

The widget was scoped to eleven public marketing routes. Its comment gave two justifications; both were checked:

Stated reason	Verdict
"the FAB would collide with the app shell's mobile nav"	Was true — and is exactly what auto-avoid fixed in #466/#467
"in-app feedback already has Loki"	Not true

insertSiteFeedback has exactly one caller — the widget's ingest route — and the word "feedback" does not appear in loki-core.ts. Telling the assistant "this button is broken" produces no site_feedback row, nothing in the triage inbox, nothing dispatchable.

On the collision: the desktop Loki FAB is 56px at bottom:28/right:28, which the feedback FAB at bottom:16/right:16 overlapped exactly — rectangle-matching auto-avoid now steps it up. The mobile nav is inset-x-3 (~94% of viewport), deliberately too wide for the rectangle scan to treat as an obstacle, so the ≤480px interactive hit-test catches its nav links instead. Both paths covered.

Inverted the rule

Render everywhere except a short list, each entry carrying its reason:

• /terminal — a floating button over live PTY output covers what you are reading
• the auth routes — you are not in the product yet; an anonymous FAB on a credential form is the wrong invitation
• /docs/feedback-widget — a launcher on the page that documents launchers makes "is this yours or the demo's?" unanswerable

An allowlist meant every new page shipped with no way to report a bug on it, and nobody noticed — because a missing feedback channel is invisible in exactly the way the problems it would have caught are.

PublicFeedbackWidget → DogfoodFeedbackWidget: it is no longer public-only, and a name saying otherwise is the stale labelling this area already had too much of.

Verification

scripts/test/feedback-widget-reach.ts — 42 assertions:

• every app surface reachable (/control, /projects, /today, /loki, …)
• public pages still reachable
• exclusions excluded, including nested paths
• near-misses not swallowed by prefix matching (/terminals ≠ /terminal, /settings is an app page)
• widget mounted from the root layout, so new pages inherit it
• loki-core still cannot file feedback — the premise that justified the old scoping

Proven by mutation: restoring a public-only allowlist turns 20 assertions red, including every app surface.

npm run verify exits 0.