@tryinget/pi-activity-strip 0.4.0 → 0.6.0

package/README.md

@@ -1,91 +1,82 @@
 ---
-summary: "Top-row live activity strip for local Pi sessions running in Ghostty or other terminals."
+summary: "Native Niri layer-shell activity ribbon for live Pi sessions."
 read_when:
   - "Starting work in this package workspace."
-  - "Installing or verifying the activity strip in Pi."
+  - "Installing or verifying the Activity Strip in Pi."
 system4d:
-  container: "Monorepo package for a local broker + Electron overlay + Pi extension telemetry seam."
-  compass: "Make Pi session activity visible at a glance without changing the operator's normal terminal workflow."
-  engine: "Pi extension emits session telemetry -> local broker aggregates -> top-row Electron strip renders live state."
-  fog: "Main risks are runtime drift across Pi host versions, Electron availability, and stale-session behavior under real long-running work."
+  container: "Monorepo package with a Node telemetry broker/controller and native GTK4 layer-shell panel."
+  compass: "Show exact workspace-local Pi activity without changing normal terminal workflows or mutating compositor configuration."
+  engine: "Pi telemetry -> local broker -> Niri workspace projection -> native layer-shell panel."
+  fog: "Main risks are native ABI availability, stale-session identity, and unverified multi-output behavior."
 ---
 
 # @tryinget/pi-activity-strip
 
-A Pi extension package that gives you a **screen-top activity strip** showing what your live Pi sessions are doing.
+A screen-top activity ribbon for the coding agents running in your Ghostty tabs. Pi sessions publish their own telemetry; other terminal agents such as Claude Code are discovered from the process table.
 
-This package is designed for the exact workflow you asked for:
-- multiple Ghostty tabs
-- multiple Pi sessions
-- a persistent top-row ribbon
-- fine-grained live detail without changing how you normally run Pi
+The runtime is Electron-free. A Node controller retains the tested telemetry, identity, ordering, and exact-focus logic; a small Rust/Relm4/GTK4 panel owns rendering and the Wayland layer-shell surface.
 
 ## What it does
 
-- auto-starts a local top-row overlay when Pi starts in a TUI session
-- tracks each active Pi session independently
-- on Niri, shows one card per tracked live Pi terminal on only the focused workspace; non-Niri desktops retain the global live-session view
-- surfaces:
-  - repo/session label
-  - current phase
-  - current tool or target
-  - fine-grained detail text
-  - elapsed time plus last-seen freshness
-  - state color (`thinking`, `tool`, `waiting`, `done`, `error`)
-- keeps a local broker so multiple Pi processes can report into one strip
-- marks the Pi session in the currently focused Niri/Ghostty terminal with a stronger border and left rail, without adding another label
-- keeps green `done`/`monitoring` cards directly beside the Activity tile, followed by active work and then other settled sessions, on a calm 15-second ordering clock
-- reveals prompt, response, path, and full activity detail on hover or keyboard focus
-- focuses the exact matching Ghostty/Niri window on click or Enter, failing closed when identity is missing or ambiguous
-- keeps an aligned strip resident on its Niri workspace while that workspace still has tracked terminals, so visiting an empty workspace does not unmap or reposition it
+- auto-starts with interactive Pi TUI sessions
+- shows one card per admitted Ghostty terminal on the focused Niri workspace, including tabs hidden behind another tab of their Ghostty window
+- covers Pi sessions and other terminal agents (Claude Code, Codex, Gemini and more) found in Ghostty tabs
+- restores tiled windows left at the wrong height when its reserved band appears or disappears
+- draws itself in Ghostty's own theme and follows the desktop between light and dark
+- sits on the same gap rhythm and corner radius as tiled windows, rather than as a bar on the screen edge
+- aggregates independent publishers beneath stable terminal cards
+- shows the AK task a session is working on: read-only `ak` output is joined onto cards, clicking the task reference focuses the claiming terminal, and claims that outlive their session or deferred tasks appear as non-clickable badges
+- displays repo, phase, tool, detail, elapsed time, and freshness
+- marks the exact currently focused terminal card and prefixes hidden-tab cards with `⧉`
+- keeps monitoring-success cards beside the Activity tile, then active and settled cards
+- expands rich details on hover or keyboard focus
+- supports Left/Right navigation and Shift+Left/Right manual movement
+- focuses the exact matching Ghostty window on click or Enter, presenting a hidden tab first
+- hides completely on workspaces without tracked cards
+- releases its 84px exclusive zone automatically when hidden or crashed
 
 ## Architecture
 
 ```text
-Pi session
-  -> activity-strip extension
-  -> local unix-socket broker
-  -> Electron top-row overlay
+Pi publisher streams
+  -> Node Unix-socket broker and session store
+  -> exact terminal identity + Niri workspace projection
+  -> versioned NDJSON child protocol
+  -> Rust / Relm4 / GTK4 panel
+  -> wlr-layer-shell top surface with an 84px exclusive zone
 ```
 
-This is intentionally **local-first**.
-It does not require moving your workflow onto `pi-server` first.
+Layer-shell replaces the old floating Electron window and dynamic Niri-config strut helper. The package no longer edits `~/.config/niri/config.kdl`, resets tiled heights, or requires Electron.
 
-## Current scope
+The compact surface is 84px tall and sits inset by an 8px margin on the top, left and right, matching the compositor's window gaps, with the same 12px corner radius as tiled windows. It therefore reserves 92px in total. One engaged card expands the surface to 276px while the reservation is unchanged, so detail overlays content without repeatedly resizing tiled windows.
 
-Implemented now:
-- local per-host broker
-- primary-display top-row strip
-- one card per tracked live Pi terminal on the focused Niri workspace, regardless of activity state
-- headless-safe telemetry publishing
-- explicit open/focus-strip/focus-session/status/doctor/snapshot/fix-top/stop commands
-- focus-scoped Left/Right navigation and Shift+Left/Right manual card movement
-- local visual capture helpers so the agent can inspect the strip directly
-
-Not implemented yet:
-- multi-monitor strip replication
-- historical timeline
-- persisted manual card order across strip restarts
-- remote observers via `pi-server`
+## Supported host
 
-## Installation in Pi
+The packaged native artifact currently supports:
 
-From this package directory:
+- Linux x86_64
+- Wayland
+- a compositor implementing `wlr-layer-shell` (dogfooded on Niri 26.04)
+- GTK4 and gtk4-layer-shell runtime libraries
+
+On Arch Linux:
 
 ```bash
-cd ~/ai-society/softwareco/owned/pi-extensions/packages/pi-activity-strip
-pi install "$PWD"
+sudo pacman -S gtk4 gtk4-layer-shell
 ```
 
-Then for **existing Pi tabs**:
-- run `/reload` in each tab you want tracked
+Multi-output replication remains unimplemented. The current surface is single-output and must not be described as multi-monitor complete.
 
-For **new Pi tabs**:
-- the package will load automatically from your Pi settings
+## Installation
 
-## Operator commands
+```bash
+cd ~/ai-society/softwareco/owned/pi-extensions/packages/pi-activity-strip
+pi install "$PWD"
+```
+
+Reload already-running Pi tabs with `/reload`. New tabs load the package automatically.
 
-### Package-local CLI
+## Commands
 
 ```bash
 npm run strip:open
@@ -96,7 +87,7 @@ npm run strip:fix-top
 npm run strip:stop
 ```
 
-or directly:
+Direct CLI:
 
 ```bash
 node ./bin/pi-activity-strip.mjs open
@@ -105,130 +96,118 @@ node ./bin/pi-activity-strip.mjs focus-session <full-pi-session-id>
 node ./bin/pi-activity-strip.mjs status
 node ./bin/pi-activity-strip.mjs doctor
 node ./bin/pi-activity-strip.mjs snapshot
-node ./bin/pi-activity-strip.mjs fix-top
+node ./bin/pi-activity-strip.mjs claude-hooks
+node ./bin/pi-activity-strip.mjs stop
 ```
 
-### Pi slash commands
+`fix-top` is now a compatibility no-op: layer-shell placement is compositor-owned.
 
-Inside Pi:
+## Keyboard-only entry
 
-```text
-/activity-strip
-/activity-strip status
-/activity-strip doctor
-/activity-strip fix-top
-/activity-strip stop
-/activity-strip-stop
-```
-
-In Pi with UI support:
-- `/activity-strip status` opens a detailed runtime status report when an editor surface is available
-- `/activity-strip doctor` opens the host-compatibility report
-
-## Interaction model
-
-- **Workspace locality:** one strip follows the Niri workspace selected with Up/Down and renders only tracked Pi terminals whose exact Ghostty windows are on that workspace. Focused-workspace events trigger reconciliation immediately, with polling retained as a fallback. When an empty workspace is visited, an aligned strip whose resident workspace still has tracked terminals remains rendered on that prior workspace; Niri keeps it off the empty workspace and returning brings the already-positioned strip back with its row. If its resident terminals disappear, the renderer is concealed and input-disabled. When an actual remap or floating correction is unavoidable, reveal waits beyond Niri's compositor movement animation and then re-verifies placement and membership. The broker remains global and non-Niri desktops retain the global card view.
-- **Ordering:** green `done` cards whose footer reads `monitoring` stay at the far left beside the Activity tile. Active tool/thinking/waiting cards follow, then other settled cards. The group order refreshes every 15 seconds rather than on every telemetry packet; text and timers still update live.
-- **Current terminal:** on Niri, the card matching the focused Ghostty window gets a stronger border and left rail without an extra label. Matching uses the same exact session-title identity seam as click-to-focus and fails closed when focus or identity is missing or ambiguous.
-- **Pointer:** hover expands the strip and reveals detail, last prompt, assistant preview, and path. Leaving the strip or activating another window collapses it immediately. Single click asks Niri to focus the one Ghostty title carrying that exact Pi session-id suffix.
-- **Keyboard inside the strip:** Left/Right changes card focus, Enter activates the focused card, and Shift+Left/Right manually moves it. Manual movement lasts until a later activity regroup or runtime restart.
-- **Fail-closed focus:** current telemetry uses the exact Pi identity directly. For already-running tabs that still publish a legacy broker id, the strip may recover only the process-bound `pi-session-presence` sidecar when its source, PID, and cwd all agree; this is not repo-name guessing or arbitrary-PID focusing. If identity still matches zero or multiple Ghostty windows, focus does nothing and asks for one `/reload`.
-
-### Keyboard-only entry on Niri
-
-The package deliberately does not reserve a global Electron shortcut. Bind one compositor key to the fail-closed CLI entrypoint instead:
+Bind a Niri key to the fail-closed CLI entrypoint:
 
 ```kdl
 binds {
-    Mod+Shift+A { spawn "node" "/home/tryinget/ai-society/softwareco/owned/pi-extensions/packages/pi-activity-strip/bin/pi-activity-strip.mjs" "focus-strip"; }
+    Mod+Shift+A repeat=false allow-inhibiting=false hotkey-overlay-title="Toggle Pi Activity Ribbon keyboard mode" { spawn "/usr/bin/node" "/home/tryinget/ai-society/softwareco/owned/pi-extensions/packages/pi-activity-strip/bin/pi-activity-strip.mjs" "focus-strip"; }
 }
 ```
 
-`focus-strip` gives keyboard focus only to the unique strip already resident on the currently focused workspace; it never moves a strip between workspaces. When the focused workspace has no tracked live Pi terminals, the command fails closed rather than forcing an empty bar into view. This keeps shortcut ownership explicit in Niri and avoids application-level global-key collisions.
-
-## Verification commands
-
-### Package checks
-
-```bash
-npm install
-npm run check
-npm run release:check:quick
-```
-
-### Run the strip locally
-
-```bash
-npm run strip:open
-npm run strip:status
-npm run strip:doctor
-npm run strip:snapshot
-```
+The shortcut toggles exclusive keyboard mode. On entry, the first card is selected. Left/Right wraps through cards, Shift+Left/Right moves the selected card with wraparound, Enter focuses its exact Ghostty terminal and exits, and Escape or a second shortcut press exits without activation. Space does not activate a card. Pointer hover expands detail but deliberately does not capture keyboard input. Empty workspaces and click-through mode reject keyboard entry.
+
+## Interaction contract
+
+- **Workspace locality:** Niri focus events trigger immediate reprojection; bounded polling remains a fallback.
+- **Hide/reclaim:** zero cards unmaps the layer surface. Niri then removes its exclusive zone as part of normal Wayland surface lifecycle.
+- **Crash behavior:** panel lifetime is bound to the Node controller through Linux parent-death signaling and stdin EOF. Unexpected panel exits are restarted with bounded backoff; a dead surface cannot retain an exclusive zone.
+- **Exact focus:** card activation returns to Node, which performs existing fail-closed terminal identity resolution and Niri focus.
+- **Hidden tabs:** a Ghostty window title only names its active tab. A bound surface whose title is not visible is placed through its Ghostty host process: one host window is exact containment; several host windows use the window remembered for that tab. Memory comes from titles seen while the strip runs and from a read-only AT-SPI inventory of tab labels, and is persisted per Niri instance under `~/.pi/agent/state/pi-activity-strip/surface-bindings.json`. A tab whose window has never been observed stays unplaced rather than guessed; `status` reports that count. Activating a hidden-tab card calls the host process's `present-surface` action on the session bus, then focuses the window, and reports success only after the title proves the tab is visible.
+- **Agent tabs:** a tab is admitted as an agent when the process owning its terminal is a recognized agent CLI, never on a window title alone, so plain terminal programs are not cards. Claude Code tabs are identified exactly through the per-session scratchpad the process holds open, which yields the session id and the title Claude Code put on the terminal; that title places the tab in its window and is remembered so the tab stays placed once hidden.
+- **AK task references:** cards can show the Agent Kernel task their session is working on. The controller reads the read-only `ak` CLI (`ak task list --status claimed --format json --all --verbose` and `ak task deferred --format json --all`) on a calm 15-second clock and joins claims by exact Pi session id under the AK5700 claim semantics: only `session-<uuid>` claims count, and an expired lease is vacant custody that renders nothing. A card whose session holds a live claim shows a clickable `AK #id · title` chip that reuses the card's own activation, so clicking it focuses the exact Ghostty window of the claiming session, presenting hidden tabs first. Claims whose lease has not lapsed but whose claiming session no longer exists ("claim outlives session") and tasks carrying an active deferral are joined by task repo onto cards working inside that repo and render as inert badges, never buttons — there is no live window to focus and no AK action is ever offered. Ambiguous session matches (one logical session resumed into two terminals), a missing `ak` binary, or malformed output bind nothing: fail closed, no chip, no invented state, strip behavior unchanged. The strip never writes AK state and never touches the society database directly.
+- **Codex telemetry:** Codex keeps a thread index naming every session's rollout file, working directory and title. A process binds to its thread by an open rollout descriptor, or, before any task has run, by being the only session created in that directory after the process started; anything ambiguous binds nothing. The rollout tail then reports the running tool and its command, turn count, approval and sandbox policy, prompt and reply. Reading the index needs the runtime's built-in SQLite, and a host without it degrades to a process-only card.
+- **Claude Code telemetry:** cards read live state from the tail of the session transcript, giving the topic, current tool and its target, last prompt, latest reply, turn count and activity clock with no configuration. That format is internal to Claude Code and can change between releases, so a transcript that no longer parses degrades to a process-only card rather than inventing activity. Optional hooks add the one state a transcript cannot express, that a session is blocked waiting for you; run `claude-hooks` for the settings fragment. Only low-frequency events are hooked, so nothing runs per tool call. OpenTelemetry is deliberately not used: it reports aggregate usage and cost, not which tool a session is running now.
+- **Appearance:** the ribbon reads the same theme files Ghostty reads. It resolves the `theme` setting for the desktop's current colour scheme, including the `light:…,dark:…` form, and takes colours set directly in the config over the theme file, exactly as Ghostty layers them. State colours reuse the terminal's own meanings, so green is settled, yellow is working, red failed, and the cursor colour marks a session waiting for you. The panel derives every shade from eight named colours, so a theme change is a handful of values and one stylesheet reload rather than a restart. A theme that cannot be read falls back to a neutral palette.
+- **Height repair:** showing or hiding the ribbon changes the output working area, and a window whose height is not automatic keeps the old value. After each change the strip compares window heights before and after, and resets to automatic only those windows still sitting at a height the moving windows just vacated. A height nobody vacated is never touched, each window is reset at most once per height, and a pass is bounded.
+- **Two identity keys:** a Ghostty surface id is a per-process handle that can drift away from the value a long-lived Pi process captured at startup, while the 32-hex session token in the same title never does. Memory therefore stores both, and lookups prefer the exact surface. A session token that two windows claim is ambiguous and binds nothing; two terminals resuming one logical session in the same window are both placed there.
+- **Ordering:** monitoring, active, and settled groups refresh on a calm 15-second clock. Manual moves survive until regroup or restart.
+- **Accessibility:** cards expose native GTK labels, selected/expanded state, activation descriptions, and GTK accessible announcements.
 
-### Capture what the agent should inspect
+## Environment controls
 
-```bash
-npm run capture:strip   # just the Pi activity strip window
-npm run capture:top     # top band of the focused output, including the strip + upper window area
-```
+- `PI_ACTIVITY_STRIP_AUTO_START=0` disables extension autostart.
+- `PI_ACTIVITY_STRIP_CLICK_THROUGH=1` installs an empty Wayland input region and disables keyboard entry.
+- `PI_ACTIVITY_STRIP_NATIVE_PANEL_BIN=/absolute/path` selects another receipted panel artifact.
+- `PI_ACTIVITY_STRIP_SOCKET_DIR` and `PI_ACTIVITY_STRIP_SOCKET_PATH` isolate broker fixtures and nested-compositor tests.
+- `PI_ACTIVITY_STRIP_TAB_INVENTORY=0` disables the read-only AT-SPI tab inventory; hidden tabs are then placed only from titles seen while the strip runs.
+- `PI_ACTIVITY_STRIP_AK_TASKS=0` disables AK task reference joining.
+- `PI_ACTIVITY_STRIP_AK_BIN=/absolute/path` selects the `ak` binary used for the read-only task queries (default `ak` on `PATH`).
+- `PI_ACTIVITY_STRIP_AGENT_TABS=0` disables discovery of non-Pi agent tabs.
+- `PI_ACTIVITY_STRIP_AGENT_KINDS_DISABLED=claude,codex` excludes named agent kinds from discovery.
+- `CODEX_HOME` selects a non-default Codex home when reading its thread index (default `~/.codex`).
+- `PI_ACTIVITY_STRIP_PYTHON` selects the interpreter for the tab inventory (default `python3`).
+- `PI_ACTIVITY_STRIP_HEIGHT_REPAIR=0` disables restoring windows stranded at the previous working-area height.
+- `PI_ACTIVITY_STRIP_COLOR_SCHEME=light|dark` pins the ribbon to one scheme instead of following the desktop.
 
-These are specifically useful so the agent can inspect the current visual state without you manually posting screenshots.
+Unverified native binaries are rejected unless `PI_ACTIVITY_STRIP_ALLOW_UNVERIFIED_PANEL=1` is explicitly set for development fixtures.
 
-### Simulate multiple sessions
+## Verification
 
 ```bash
-npm run demo:simulate
+npm run native:build   # exact Rust 1.98 build, tests, staged artifact receipt
+npm run check          # canonical Node/package quality gate
+npm run native:check   # Rust formatting and tests
+npm run release:check  # full packed install and native-artifact smoke
 ```
 
-### Real Pi smoke on the live broker
+The staged artifact receipt binds:
 
-```bash
-npm run smoke:headless-live
-```
-
-This smoke:
-- opens the strip
-- runs a real headless Pi session with this extension loaded
-- exercises a real tool call
-- verifies that the broker observed the session while it was active
+- binary SHA-256
+- Cargo lock SHA-256
+- complete Rust/CSS source SHA-256
+- Rust compiler version
+- glibc symbol floor
+- required shared libraries
 
-### Compatibility diagnostics
+Live verification must inspect Niri layers rather than regular windows:
 
 ```bash
-npm run strip:doctor
-node ./bin/pi-activity-strip.mjs doctor --json
+niri msg -j layers | jq '[.[] | select(.namespace == "pi-activity-strip")]'
 ```
 
-Use `doctor` before opening the strip when the host/display assumptions are uncertain. It reports:
-- whether a graphical session is present
-- whether Electron can be resolved
-- whether Niri-specific top-edge repair is available
-- whether the current setup is multi-display even though the strip remains primary-display-only
-
-## Environment controls
-
-- `PI_ACTIVITY_STRIP_AUTO_START=0`
-  - disable automatic strip opening on Pi session start
-- `PI_ACTIVITY_STRIP_CLICK_THROUGH=1`
-  - opt out of interaction and restore a mouse-transparent overlay; interactive hover/click/keyboard behavior is the default
-- `PI_ACTIVITY_STRIP_ELECTRON_BIN=/path/to/electron`
-  - override Electron binary discovery
-- `GLIMPSE_ELECTRON_BIN=/path/to/electron`
-  - shared Electron override also respected
-
-## Practical usage for your Ghostty tabs
-
-If you want this for all current tabs:
+## Current scope
 
-1. install the package once with `pi install`
-2. run `/reload` inside each already-open Pi tab
-3. open the strip once with `/activity-strip` or `npm run strip:open`
-4. from then on, every loaded Pi session should report into the same top-row ribbon
-5. ensure `pi-little-helpers` session presence is loaded when you want exact click-to-Ghostty focus; its `· <full-32-hex-session-id-token>` title suffix is the preferred fail-closed identity seam (an 8-hex legacy title remains usable only when no legacy duplicate or migrated full title shares its prefix)
+Implemented:
+
+- local broker and telemetry publishers
+- native GTK4 layer-shell rendering
+- workspace-local Niri projection
+- hide/reclaim and restore
+- pointer and keyboard card interaction
+- exact Ghostty activation, including hidden tabs via `present-surface`
+- hidden Ghostty tab placement through host process containment and learned window memory
+- clickable AK task references joined from read-only `ak` output, with claim-outlives-session and deferred badges
+- non-Pi agent tab discovery with an exact Claude Code adapter
+- live Claude Code telemetry from its transcript, with optional hooks for blocked-on-you states
+- live Codex telemetry from its thread index and rollout files
+- Ghostty theme following, light and dark
+- repair of windows stranded at the previous working-area height
+- bounded panel restart and parent-death cleanup
+- click-through input region
+
+Not implemented:
+
+- placement of a tab whose window has never been observed, on a host without the AT-SPI inventory (Ghostty exposes no surface listing of its own)
+- distinguishing two terminals that resume one logical session when only the drifted session token is available; both are placed in the one window that claims that token
+- live phase and tool detail for agents other than Claude Code and Codex, which have no adapter yet; their cards show the agent, directory, elapsed time and pid
+- placement of an agent other than Claude Code whose tab is hidden inside a multi-window Ghostty process, since only Claude Code exposes a per-tab title identity
+- one panel per output
+- historical timeline
+- any AK mutation from the strip (unclaim, land, reconstruct, apply); the ribbon is a read-only projection by construction
+- persisted manual ordering
+- remote observers via `pi-server`
 
 ## References
 
 - [Project vision](docs/project/vision.md)
 - [Project resources](docs/project/resources.md)
-- [Verification notes](docs/project/verification.md)
-- [Next session prompt](next_session_prompt.md)
+- [Verification evidence](docs/project/verification.md)
+- [Superseded adaptive-strut design investigation](docs/project/2026-08-31-adaptive-niri-space-design.md)

package/bin/pi-activity-strip-claude-hook.mjs

@@ -0,0 +1,71 @@
+#!/usr/bin/env node
+// ---
+// summary: "Claude Code hook entrypoint that records one session's live state for the activity ribbon"
+// read_when:
+//   - "changing how Claude Code sessions publish live state to the ribbon"
+// ---
+
+// Claude Code runs this for each configured hook event and waits for it, so it must be cheap and
+// must never fail the session: every path exits 0 and nothing is written to stdout.
+
+import fs from "node:fs";
+import {
+  CLAUDE_EVENT_DIR,
+  claudeEventPath,
+  claudeEventRecord,
+  isSessionEndEvent,
+} from "../src/common/claude-events.mjs";
+
+const STDIN_LIMIT_BYTES = 1024 * 1024;
+
+async function readPayload() {
+  const chunks = [];
+  let total = 0;
+  for await (const chunk of process.stdin) {
+    total += chunk.length;
+    if (total > STDIN_LIMIT_BYTES) break;
+    chunks.push(chunk);
+  }
+  try {
+    return JSON.parse(Buffer.concat(chunks).toString("utf8"));
+  } catch {
+    return null;
+  }
+}
+
+async function main() {
+  const payload = await readPayload();
+  if (!payload || typeof payload !== "object") return;
+  const record = claudeEventRecord(payload, { env: process.env });
+  if (!record) return;
+  const filePath = claudeEventPath(record.sessionId);
+  if (!filePath) return;
+
+  if (isSessionEndEvent(record)) {
+    try {
+      fs.unlinkSync(filePath);
+    } catch {
+      // The session never published, or another hook already retired it.
+    }
+    return;
+  }
+
+  const temporaryPath = `${filePath}.tmp.${process.pid}`;
+  try {
+    fs.mkdirSync(CLAUDE_EVENT_DIR, { recursive: true, mode: 0o700 });
+    fs.writeFileSync(temporaryPath, JSON.stringify(record), { mode: 0o600 });
+    fs.renameSync(temporaryPath, filePath);
+  } catch {
+    try {
+      fs.unlinkSync(temporaryPath);
+    } catch {
+      // Nothing was staged.
+    }
+  }
+}
+
+main()
+  .catch(() => {})
+  .finally(() => {
+    process.exitCode = 0;
+  });

package/bin/pi-activity-strip.mjs

@@ -5,11 +5,11 @@
 //   - "operating or diagnosing the activity strip from a terminal"
 // ---
 
-import { execFile, spawn } from "node:child_process";
+import { spawn } from "node:child_process";
+import fs from "node:fs";
 import path from "node:path";
 import { setTimeout as delay } from "node:timers/promises";
 import { fileURLToPath } from "node:url";
-import { promisify } from "node:util";
 import {
   getBrokerStatus,
   isBrokerAlive,
@@ -20,63 +20,24 @@ import {
   assessActivityStripCompatibility,
   formatCompatibilityReport,
 } from "../src/common/compatibility.mjs";
-import { ACTIVITY_STRIP_START_TIMEOUT_MS } from "../src/common/constants.mjs";
-import { locateElectron } from "../src/common/electron.mjs";
-import { focusNiriStrip, resolveActivityStripWindow } from "../src/common/niri-focus.mjs";
+import {
+  ACTIVITY_STRIP_SOCKET_DIR,
+  ACTIVITY_STRIP_START_TIMEOUT_MS,
+} from "../src/common/constants.mjs";
 import { makeMessage } from "../src/common/protocol.mjs";
 import { formatBrokerRuntimeStatus } from "../src/common/status-report.mjs";
 
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = path.dirname(__filename);
-const electronEntry = path.resolve(__dirname, "..", "src", "electron", "main.mjs");
-const execFileAsync = promisify(execFile);
+const nativeEntry = path.resolve(__dirname, "..", "src", "native", "main.mjs");
+const runtimeLockPath = path.join(ACTIVITY_STRIP_SOCKET_DIR, "runtime.lock");
 
 function usage() {
   console.log(
-    `Usage: pi-activity-strip <open|focus-strip|focus-session|status|doctor|snapshot|fix-top|stop|serve> [options]\n\nCommands:\n  open              Start the interactive top-row activity strip (--click-through opts out)\n  focus-strip       Focus the visible strip already resident on the focused Niri workspace\n  focus-session ID  Focus the one Ghostty/Niri window matching an exact Pi session identity\n  status            Check broker + overlay readiness and surface runtime warnings\n  doctor            Inspect host compatibility assumptions before opening the strip\n  snapshot          Print the current broker snapshot as JSON\n  fix-top           Move the strip window flush to the top edge in Niri\n  stop              Ask the running strip to shut down\n  serve             Internal helper; starts the Electron shell in the foreground\n`,
+    `Usage: pi-activity-strip <open|focus-strip|focus-session|status|doctor|snapshot|claude-hooks|fix-top|stop|serve> [options]\n\nCommands:\n  open              Start the interactive top-row activity strip (--click-through opts out)\n  focus-strip       Focus the visible strip already resident on the focused Niri workspace\n  focus-session ID  Focus the one Ghostty/Niri window matching an exact Pi session identity\n  status            Check broker + overlay readiness and surface runtime warnings\n  doctor            Inspect host compatibility assumptions before opening the strip\n  snapshot          Print the current broker snapshot as JSON\n  claude-hooks      Print the Claude Code settings fragment for live agent telemetry\n  fix-top           Confirm compositor-owned layer-shell placement\n  stop              Ask the running strip to shut down\n  serve             Internal helper; starts the native runtime in the foreground\n`,
   );
 }
 
-async function moveStripToTop() {
-  const { stdout } = await execFileAsync("niri", ["msg", "-j", "windows"], {
-    env: process.env,
-  });
-  const windows = JSON.parse(stdout);
-  if (!Array.isArray(windows)) {
-    throw new Error("Unexpected niri windows payload");
-  }
-
-  const stripWindow = resolveActivityStripWindow(windows);
-  if (!stripWindow) {
-    throw new Error("Could not find one unique Pi Activity Strip window in niri");
-  }
-
-  const layout = /** @type {{ tile_pos_in_workspace_view?: unknown[] }} */ (
-    stripWindow.layout ?? {}
-  );
-  const currentY = Number(layout.tile_pos_in_workspace_view?.[1] ?? 0);
-  if (Math.abs(currentY) < 1) {
-    return 0;
-  }
-
-  await execFileAsync(
-    "niri",
-    [
-      "msg",
-      "action",
-      "move-floating-window",
-      "--id",
-      String(stripWindow.id),
-      "-y",
-      String(-Math.round(currentY)),
-    ],
-    { env: process.env },
-  );
-
-  console.log("Moved activity strip to the top edge.");
-  return 0;
-}
-
 async function waitForBrokerReady(timeoutMs = ACTIVITY_STRIP_START_TIMEOUT_MS) {
   const timeoutAt = Date.now() + timeoutMs;
   /** @type {import("../src/common/contracts.ts").BrokerResponse | null} */
@@ -111,8 +72,19 @@ async function waitForBrokerReady(timeoutMs = ACTIVITY_STRIP_START_TIMEOUT_MS) {
 /** @param {{ detached?: boolean }} [options] @returns {Promise<number>} */
 async function openStrip({ detached = true } = {}) {
   if (await isBrokerAlive()) {
-    console.log("Activity strip is already running.");
-    return 0;
+    const status = await getBrokerStatus({ expectReply: true }).catch(() => null);
+    if (status?.runtimeStatus?.state !== "error") {
+      console.log("Activity strip is already running.");
+      return 0;
+    }
+    await requestBrokerShutdown().catch(() => null);
+    for (let attempt = 0; attempt < 20 && (await isBrokerAlive()); attempt += 1) {
+      await delay(50);
+    }
+    if (await isBrokerAlive()) {
+      console.error(formatBrokerRuntimeStatus(status));
+      return 1;
+    }
   }
 
   const compatibility = await assessActivityStripCompatibility();
@@ -121,11 +93,11 @@ async function openStrip({ detached = true } = {}) {
     return 1;
   }
 
-  const electron = await locateElectron();
-  const child = spawn(electron, [electronEntry], {
+  fs.mkdirSync(ACTIVITY_STRIP_SOCKET_DIR, { recursive: true, mode: 0o700 });
+  const child = spawn("flock", ["--nonblock", runtimeLockPath, process.execPath, nativeEntry], {
     detached,
     stdio: detached ? "ignore" : "inherit",
-    env: process.env,
+    env: { ...process.env, PI_ACTIVITY_STRIP_RUNTIME_LOCK_HELD: "1" },
   });
 
   if (detached) {
@@ -166,7 +138,9 @@ async function main() {
           process.exitCode = 1;
           return;
         }
-        const result = await focusNiriStrip(execFileAsync, process.env, status?.snapshot?.sessions);
+        const result = await sendBrokerMessage(makeMessage("focus-strip"), {
+          expectReply: true,
+        });
         if (!result.ok) console.error(result.error || "Strip focus did nothing.");
         process.exitCode = result.ok ? 0 : 1;
       } catch {
@@ -234,15 +208,31 @@ async function main() {
       }
       return;
     }
-    case "fix-top": {
-      try {
-        process.exitCode = await moveStripToTop();
-      } catch (error) {
-        console.error(error instanceof Error ? error.message : String(error));
-        process.exitCode = 1;
+    case "claude-hooks": {
+      const { claudeHookSettings } = await import("../src/common/claude-hook-config.mjs");
+      const hookPath = path.join(
+        path.dirname(fileURLToPath(import.meta.url)),
+        "pi-activity-strip-claude-hook.mjs",
+      );
+      const settings = claudeHookSettings(`${process.execPath} ${hookPath}`);
+      if (jsonOutput) {
+        console.log(JSON.stringify(settings, null, 2));
+      } else {
+        console.log(
+          "Merge this into ~/.claude/settings.json so Claude Code sessions report live state:\n",
+        );
+        console.log(JSON.stringify(settings, null, 2));
+        console.log(
+          "\nOnly low-frequency events are hooked, so nothing runs per tool call. Tool and thinking",
+        );
+        console.log("state already come from the transcript without any configuration.");
       }
       return;
     }
+    case "fix-top":
+      console.log("Native layer-shell placement is compositor-owned; no repair was needed.");
+      process.exitCode = 0;
+      return;
     case "stop": {
       try {
         const result = await requestBrokerShutdown();

package/native/bin/linux-x64-gnu/artifact.json

@@ -0,0 +1,21 @@
+{
+  "schema": "pi-activity-strip-native-artifact.v1",
+  "target": "x86_64-unknown-linux-gnu",
+  "sha256": "999724e6bb34a0cceea631d1cbe58541f20221291b3e9d065e9bb19e193a3b27",
+  "cargoLockSha256": "f8ebc11bc721c569af982169e448a5ea4fed15bc06001017d97acda22b1c890b",
+  "sourceSha256": "1fa65ddf13e1a3c1267081de641e65617822fd409c88e865fec6f769b8161a35",
+  "rustc": "rustc 1.98.0 (88d9e12ae 2026-08-18)",
+  "glibcFloor": "GLIBC_2.34",
+  "neededSonames": [
+    "libgtk4-layer-shell.so.0",
+    "libgtk-4.so.1",
+    "libcairo.so.2",
+    "libgio-2.0.so.0",
+    "libgobject-2.0.so.0",
+    "libglib-2.0.so.0",
+    "libgcc_s.so.1",
+    "libm.so.6",
+    "libc.so.6",
+    "ld-linux-x86-64.so.2"
+  ]
+}