Add shift handover and RunPod, and make CX-Tools work in a container

Handover
- The Confluence shift doc becomes the landing page: shift metadata, the
  top-of-page checks, key updates with their Zendesk/Jira refs and status, and
  the free-text comments. "Hand over shift" closes the shift, opens the next
  one and carries the live items across, dropping anything done or marked
  "remove at end of shift" - the retyping this replaces.
- The RunPod table on that page is read from live host state instead of being
  copied in by hand, with the six-colour key preserved.

RunPod
- GraphQL client keyed on CX_RUNPOD_API_KEY. The old console login is kept as a
  fallback but cannot run unattended: the account has 2FA, so Clerk verifies the
  password and then asks for an emailed code and never issues a session. That is
  the real cause of the "No active session found" failure, and the client now
  says so instead of failing opaquely. TOTP is supported if the account moves to
  an authenticator app.
- Hosts and their listing history are persisted, so "most problematic hosts" can
  be ranked and each machine has a timeline of who listed or unlisted it, with
  the Zendesk comment and the error hint.
- The unlisting emails are parsed for the error block (they arrive
  quoted-printable) and classified into a likely cause and a next step.

Zendesk and Jira
- Unlisting raises a Zendesk ticket that follows the format of RunPod's own
  email, keyed on the machine so one machine keeps one thread, posted as an
  internal note.
- Jira is split in two: the Infrahub/OIE instance and the RunPod/RMA one, which
  may be a different Atlassian site. Blank RunPod values fall back to the
  defaults rather than failing.

Running in a container
- CX-Tools reads its keys from 1Password, which needs a desktop app. Config is a
  dataclass whose lookups live in per-field default factories, so passing
  CX_INFRAHUB_TOKEN/CX_INFRAINSIGHT_TOKEN in means those factories never run and
  CX-Tools itself stays unmodified.
- CX-Tools reaches OpenStack with `docker exec <region>-osc`, so the image now
  carries the Docker client (the static binary, not the docker.io package) and
  compose mounts the host socket with group_add for it. Verified from inside the
  container: live OpenStack and Infrahub calls both succeed.

Also fixes Settings, which read the environment at class-definition time and so
ignored anything set afterwards; a fresh Settings() silently returned stale
values. Caught by the Jira scoping tests.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

.env.example

@@ -65,3 +65,43 @@ CX_JIRA_EMAIL=
 CX_JIRA_TOKEN=
 CX_JIRA_PROJECT=INFRA
 CX_JIRA_ISSUE_TYPE=Task
+
+# --- local compose paths ---------------------------------------------------
+# CX-Tools on the host. The app imports it and shells out to the *-osc
+# containers through the mounted Docker socket, so both must be present.
+CX_TOOLS_HOST_PATH=../CX-Tools
+CX_RUNPOD_EXPORT_HOST_PATH=../RunPod
+
+# Infrahub/InfraInsight keys. Set these and CX-Tools skips 1Password entirely,
+# which is the only way it can work inside a container.
+CX_INFRAHUB_TOKEN=
+CX_INFRAINSIGHT_TOKEN=
+
+# Fill an empty database with representative handover and RunPod data.
+CX_SEED_DEMO=true
+
+# --- RunPod ----------------------------------------------------------------
+# The API key is the supported path. Email/password only reaches a console
+# login that now requires a second factor, so it cannot run unattended.
+CX_FEATURE_RUNPOD=true
+CX_FEATURE_RUNPOD_WRITE=false
+CX_RUNPOD_API_KEY=
+CX_RUNPOD_EMAIL=
+CX_RUNPOD_PASSWORD=
+CX_RUNPOD_TEAM_ID=
+# Only if the account moves from emailed codes to an authenticator app.
+CX_RUNPOD_TOTP_SECRET=
+
+# --- Jira, second instance (RunPod / RMA) ----------------------------------
+# Leave blank to reuse the CX_JIRA_* values above.
+CX_RUNPOD_JIRA_BASE=
+CX_RUNPOD_JIRA_EMAIL=
+CX_RUNPOD_JIRA_TOKEN=
+CX_RUNPOD_JIRA_PROJECT=RMA
+
+CX_FEATURE_HANDOVER=true
+
+# --- Zendesk tickets for RunPod unlistings ---------------------------------
+# Uses the same Zendesk credentials as customer comms. Tickets are keyed on the
+# machine (external_id cx-triage-runpod-<machine_id>) and posted as an internal
+# note, since these are operations tickets rather than customer replies.