[Pletor]

Adds an Opora process wall above the north-wall Issues, Task queue and Pull Requests boards. Aim and press E/click to inspect live workers, queue tasks, branches, GitHub checks, review and blockers. Selecting overview, workers or blockers also changes the physical screen; pagination covers additional rows. Animated spider markers move only for workers reporting work on a connected, synchronized session.

The detail window joins existing office observations rather than creating another backend or socket. It shows source freshness, disconnect/reconnect state, PR evidence links and an 80-entry local observation history. Finished turns, passing checks, approved reviews and confirmed merges remain distinct; a merge never claims deployment. The modal uses the existing focus lifecycle and restores mouse-look on X or Escape, including Escape from the embedded demo.

The same window also includes a real, read-only OpenViking panel through Opora's existing memory API. With OPORA_CONTROL_CENTER_URL set to the local Opora origin, admins/shared-password sessions can inspect service status and eight registered roles, then explicitly recall existing records with provenance and scores. The server permits only fixed loopback API paths, limits response sizes and deadlines, refuses redirects, checks recall Origin, and selects response fields. Keys remain in Opora; the adapter has no provisioning, write, settings or session-commit endpoints.

The window embeds a separately labeled Czech Process Observatory demo. Its four agents, six-phase pipeline and 17 handoffs cover planning, source research, worktrees, counterexamples, repair, review, documentation, PR dependencies, staging, task closure and memory reuse/evaluation. Repository-role inputs extend the deterministic demo; snapshot replay and JSON export expose its evidence. External plan/learning events, Lean and deployment are not live integrations. The standalone session-protected /process-studio route remains available.

Implementation is isolated in features/process-wall/ and process-studio/, joined through install, fixture, HTTP and Vite registries. No global store or protocol logic is added. Only the authenticated studio page opts into same-origin framing; static pages otherwise retain DENY, with matching CSP frame-ancestors. README, help and both feature docs explain controls and limitations.

Validation:

• npm run typecheck and npm run build passed.
• Focused memory adapter/authorization, wall, framing, studio, client structure and size tests: 25/25 passed.
• Headless Chrome on the built office passed wall interaction, projection from synthetic worker messages on an isolated server, view filtering, history, embedded demo, nested dialog Escape, X/Escape mouse-look restoration, disconnected state and mobile layout. Screenshots captured of the physical wall and detail. Test fixtures are not claims of real worker activity.
• The standalone studio previously passed full replay, extensions, gates, memory, export, reduced motion and responsive checks in both Vite and offline HTML.
• Headless Chrome also verified the real Opora/OpenViking connection (Opora 8740, OpenViking 1933): configured status, eight roles, one returned source record, preservation of typed input across polling and mouse-look restoration. This proves retrieval, not learned improvement or a full memory-event stream. A separate visible preview is running locally.
• Full npm test was attempted on Windows and stalled after test 195. Existing failures concern Windows path separators in client-registry tests, POSIX shell clone fixtures and a symlink EPERM in codex-usage. Registry/symlink failures were previously reproduced at clean base 852e2ab. The owned stalled test tree was stopped; unrelated tests/runtime behavior were not changed.