`chatDebugRuns` and `chatDebugRun` previously stopped the interval when
the query entered an error state, so a single network blip would freeze
the Debug tab until a manual remount. Switch to a longer error cadence
(30s) so the panel recovers automatically when the backend comes back
without hammering a failing endpoint at the 5s foreground cadence.

Change-Id: Ie95aee44000002aebd145fddd31a1808f4456c4f
Signed-off-by: Thomas Kosiewski <tk@coder.com>

Refetch failures were blanking the run list and step details behind an
error alert even when cached data was available. Gate the full error
state on "no data" and surface refetch errors as a non-blocking warning
above the cached content.

Change-Id: Ie36141c20e2bf32ec71be1d83e3ec75c5a38d970
Signed-off-by: Thomas Kosiewski <tk@coder.com>

When cached debug-run data is an empty array and a later poll fails,
render the refresh warning banner above the empty-state copy instead of
hiding the failure behind a misleading success-like message.

Change-Id: I08e76a84fc78285eba2d66a2a0d6badace6be97c
Signed-off-by: Thomas Kosiewski <tk@coder.com>

Change-Id: I3b397710c50449c6ac344e6f817ffdd2c7c0f64b
Signed-off-by: Thomas Kosiewski <tk@coder.com>

Both components were inherited an enabled=true default from before
DebugPanel's opt-in polling fix. The parent now always passes the value
explicitly, so the default was unreachable — and also contradicted the
guidance to never default polling gates to on.

Change-Id: I0f850a18e0029ce8631196c3dee529ca41a0f349
Signed-off-by: Thomas Kosiewski <tk@coder.com>

…al set

SidebarTabView now takes the resolved `effectiveTabId` as a prop so
AgentChatPageView owns a single source of truth. Previously both
components independently called `getEffectiveTabId` with the same
inputs; if either drifted, the child's highlight would disagree with
the parent-side `TerminalPanel.isVisible` and `DebugPanel.enabled`
gating.

Also share `TERMINAL_RUN_STATUSES` between the debug-run polling query
and the badge color logic. Deriving it from `ERROR_STATUSES` plus
`completed` guarantees every error-like status also ends polling, so
the badge can never turn red while the panel keeps hammering the API.

Change-Id: Ie6dec4968b0c4370146e0677a576357e0a04de95
Signed-off-by: Thomas Kosiewski <tk@coder.com>

`SidebarTabView` only renders the desktop tab/panel when
`workspace && workspaceAgent` is true, but `getEffectiveTabId` was
resolving against the raw `desktopChatId`. When the saved tab was
"desktop" and the agent was missing/loading, selection resolved to
"desktop" with no panel rendered, leaving the right panel empty.

Change-Id: Iff1b4a544e06a36fe1edd241de804af4d1ec4527
Signed-off-by: Thomas Kosiewski <tk@coder.com>

Align with TerminalPanel's visibility prop name so both sidebar
panels gate their background work on the same-named signal.

Change-Id: I6f1b66c45e2e50f1d94d2fd56ab5f69a63d9eebf
Signed-off-by: Thomas Kosiewski <tk@coder.com>

`border-solid` on the CollapsibleContent set `border-style: solid` on all
four sides, but only `border-t` set a width. With Tailwind's preflight
reset disabled for MUI compatibility, bottom/left/right fell back to the
browser default `border-width: medium` (3px), producing visibly
asymmetric borders on every expanded step. Adding `border-0` before
`border-t` zeroes the other sides.

Change-Id: I5c9b4231fea566ca52e2aac1acc57cbed9ea1dba
Signed-off-by: Thomas Kosiewski <tk@coder.com>

The invocation row in the debug panel was a transparent button with no
surrounding chrome, so the bordered step card underneath looked
disconnected once the row expanded — the header had no visual
relationship to its children. Add a thin rounded border around the
DebugRunCard wrapper (no background, so the nested step card's subtle
fill still reads as the "content" layer) and space runs apart in
DebugRunList so they don't sit flush against each other.

Change-Id: Ic4afaadd0877a0ead37e8eb24027758043e8e62a
Signed-off-by: Thomas Kosiewski <tk@coder.com>

Add p-4 padding and space-y-3 between debug run cards so the newly
bordered wrappers no longer touch each other or the panel edges. Tighten
the trigger and expanded content's vertical padding (py-0.5 on the
button, pt-1 pb-3 on the content) so each card reads as compact rather
than chunky.

Change-Id: I03c073aa4a1d427e31d56fe6a057015df2f3b4af
Signed-off-by: Thomas Kosiewski <tk@coder.com>

- Strip em-dash/en-dash characters from debug panel source so
  `make lint/emdash` no longer fails (replaces U+2014/U+2013 in
  strings and comments with hyphens, colons, or periods).
- Move the terminal debug-run status set from the debug panel into
  `api/queries/chats.ts` so the api layer no longer imports from
  `#/pages/`, and expand it to cover every success-like status
  (`completed`, `success`, `succeeded`, `ok`) plus every error-like
  status, so polling no longer runs forever when the backend reports
  a success status the old set did not include.
- Use the run detail query's status for the header badge and spinner
  so the run flips to its final state as soon as the detail refetch
  observes the transition instead of waiting up to 5s for the list
  query to catch up.
- Replace the misleading "enable it from Settings > Behavior" empty
  state with guidance that matches reality (the tab is only rendered
  when logging is already enabled).
- Derive `sidebarTabIds` from a single `sidebarTabConfigs` source of
  truth so tab IDs and tab content can no longer drift apart when a
  new tab is added.
- Rename `errorCode` to `errorText` (it holds the displayable error
  body, not an HTTP/error code), drop a redundant manual type
  predicate now that TypeScript infers it, switch a stray
  `React.ReactNode` to the existing named `ReactNode` import, and
  use `safeJsonStringify` inside `KeyValueGrid`'s default formatter.
- Add test coverage for `safeJsonStringify`'s circular-reference
  catch branch and its function-fallback assertion, plus the plain
  string content path in `coerceStepResponse`.

Change-Id: I45e577ec7d089395caae585a74b513ee9793ce91
Signed-off-by: Thomas Kosiewski <tk@coder.com>

- Fall back to summary status when the detail query is paused so a
  collapsed card does not show stale in_progress while the run has
  finished (Codex P2).
- Sync TERMINAL_RUN_STATUSES with the debug panel's success/error
  display sets via a new pinning test (DEREM-36).
- Reflect forced-by-deployment state in the user toggle's checked
  value so the switch matches the "locked on" copy (DEREM-37).
- Rephrase Behavior section description so "that shape how the
  agent responds" does not wrongly imply debug logging shapes
  responses (DEREM-38).
- Extract the run header label clamp threshold into
  RUN_LABEL_CLAMP_CHARS to match MESSAGE_CONTENT_CLAMP_CHARS (DEREM-39).

Change-Id: Id55eadaf72b17c8ff321c38ce1b69c6027f90d2a
Signed-off-by: Thomas Kosiewski <tk@coder.com>

Inline the single-use Debug panel class-name constants, drop the stray
blank line reintroduced between useChatStore imports, and let the Debug
step error block reuse the shared getErrorMessage helper instead of a
bespoke string-vs-object narrower.

Change-Id: Ibe3af383abcd1a589aae2bee8669f84691599a01
Signed-off-by: Thomas Kosiewski <tk@coder.com>

Change-Id: Ie077eafb5bb773607f76a8c4fc1b213af58093a3
Signed-off-by: Thomas Kosiewski <tk@coder.com>

Change-Id: I29a09eca70b69914a3a169973b0e30956846d07c
Signed-off-by: Thomas Kosiewski <tk@coder.com>