fix: restore workflow ownership and pilot gates

docs/plans/workflow-system.md

@@ -2,9 +2,9 @@
 
 Source: [`../workflow-discovery.md`](../workflow-discovery.md)
 
-The declarative workflow implementation is complete. This file is the living
-handoff for operational constraints and external gates; implementation history
-is available in Git.
+The declarative workflow core is complete; pilots remain. This file is the
+living handoff for operational constraints and external gates; implementation
+history is available in Git.
 
 ## Activation boundary
 
@@ -29,28 +29,37 @@ restarted Kitty and closed the user's terminal session.
 
 ## Current checkpoint
 
-- State: declarative implementation and autonomous verification complete.
+- State: declarative core complete; corrective activation and pilots remain.
 - Branch: `chore/workflow-system`.
-- Validation: `nix flake check --no-build --quiet` plus no-link Zenith and Orion
-  system builds passed on 2026-09-06 after Orion became the sole transcription
-  owner. The expected dirty-tree and unknown `modules` warnings were emitted.
+- Validation: `nix flake check --no-build --quiet`, all three no-link system
+  builds, generated Zenith and Polaris Niri validation, and all six companion
+  flake evaluations passed on 2026-09-06. The updated data-science shell exposes
+  Python 3.14.7 and its full project check passes. The expected dirty-tree and
+  unknown `modules` warnings were emitted.
 - Live state: Walker project and terminal actions, daily notes, stable web apps,
   Evolution D-Bus activation, the Zenith VPN, invocation-scoped GitHub and
   Context7 credentials, Pinta, and Orion transcription passed their completed
   pilots.
 
-## External or deferred gates
+## Active pilot gates
 
 These gates do not block work on each other.
 
-- During a docked Zenith session, capture the external display's stable identity
-  and test the two-output `Super+A` exchange. The current recorded session exposed
-  only `eDP-1`.
-- Resume Evolution only when the user chooses to configure the personal,
-  old-personal, university, work, and Radicale accounts. Keep Thunderbird and
-  Outlook until the daily-use gate passes.
-- On Android, complete the DAVx5/Radicale and Tasks.org pilots, including default
-  accounts, recurrence, reminders, and Microsoft To Do within documented limits.
+- Add `RabbitMQ — TEST` for `https://test.rabbitmq.yookr.org` and
+  `RabbitMQ — LIVE` for `https://rabbitmq.yookr.org` to a Vivaldi `Operations`
+  bookmark folder. Vivaldi remains the bookmark owner.
+- Supply approved test RabbitMQ management credentials at runtime, then verify
+  the Nix-provided client without installing it permanently:
+
+  ```console
+  RABBITMQADMIN_BASE_URI=https://test.rabbitmq.yookr.org nix run --quiet nixpkgs#rabbitmqadmin-ng -- show overview
+  RABBITMQADMIN_BASE_URI=https://test.rabbitmq.yookr.org nix run --quiet nixpkgs#rabbitmqadmin-ng -- queues list
+  ```
+
+  Export `RABBITMQADMIN_USERNAME` and `RABBITMQADMIN_PASSWORD` from the approved
+  credential source first; do not place their values in documentation or shell
+  history. Keep publishing, getting, and purge visibly interactive in the
+  management UI.
 - Supply one real Yookr S3 task, a least-privileged remote, and explicit permission
   for any upload. `rclone` is installed; no remote or wrapper is preconfigured.
 - Deploy a GET image exposing `/full-api-docs/openapi.json`, then rerun
@@ -64,6 +73,36 @@ These gates do not block work on each other.
 - Wait for a real Monday ticket before adding anything beyond native GitHub,
   Herdr, Git, and worktree workflows.
 
+The Herdr pilot passes only when short, long, and approval-blocked sessions have
+accurate attention state; detach and reattach preserve output; one Claude or Pi
+fallback works; and each completed event produces exactly one notification.
+Create two independently writing, non-overlapping task worktrees under
+`~/dev/work/.worktrees/<repository>/<branch-slug>`, explicitly authorize each
+`.envrc`, and confirm paths are predictable, dirty removal is refused, and the
+branches remain for review. If a component fails, fall back independently to
+native agent sessions and Codex TUI notifications or native
+`git worktree add/list/remove`; do not add a wrapper or Worktrunk yet.
+
+## Deferred pilots
+
+- During a docked Zenith session, capture the external display's stable identity
+  and test the two-output `Super+A` exchange. The current recorded session exposed
+  only `eDP-1`.
+- Resume Evolution only when the user chooses to configure the personal,
+  old-personal, university, work, and Radicale accounts. Keep Thunderbird and
+  Outlook until the daily-use gate passes.
+- On Android, complete the DAVx5/Radicale and Tasks.org pilots, including default
+  accounts, recurrence, reminders, and Microsoft To Do within documented limits.
+- Do not replicate the workstation workflow on Polaris until the user resumes
+  the procedure below.
+
+The Niri pilot is two-output-only. It passes when the active workspaces exchange
+physical outputs, both arrivals are active, original names are preserved, and
+focus returns to the original physical output. Any temporary names must be
+collision-free and restored on success or failure; missing output or workspace
+state must leave the session unchanged. Keep the helper only after repeated
+reliable swaps with an acceptable visible transition.
+
 ## Deferred Polaris replication
 
 Do not access or test Polaris unless the user resumes this deferred replication.
@@ -81,6 +120,11 @@ Zenith's result remains representative meanwhile.
 7. Create mode-0600 `~/.config/context7/api-key` without a trailing newline,
    restart Codex after activation, and run one Context7 lookup.
 
+Replication passes only when the VPN has the expected route and DNS behavior,
+reaches a test service, reconnects after disconnect and suspend, and survives a
+reboot without autoconnecting. The two credential files must remain mode 0600;
+the fresh-shell GitHub read and restarted-Codex Context7 lookup must both work.
+
 ## Durable implementation decisions
 
 - Active work repositories live under `~/dev/work`, archives under `.archive`,
@@ -88,6 +132,12 @@ Zenith's result remains representative meanwhile.
 - Participating repositories expose non-mutating direnv shells, minimal flake
   checks, native commands through `just`, concise `AGENTS.md`, and machine-local
   credential inputs.
+- `yookr-data-science/conf/local/credentials.yml` is an approved narrow
+  application-owned exception to the external credential-file default: Kedro's
+  named credential dataset resolves it from the native ignored `conf/local`
+  hierarchy. Keep it untracked and mode 0600.
+- `yookr-data-science` follows ordinary `nixos-unstable`, like the other
+  companion repositories; it needs no `devenv-nixpkgs` compatibility input.
 - `yookr-workbench` starts with cross-system work only; isolation and additional
   tools wait for observed needs.
 - Walker's native Elephant menu scans repository roots and calls one Nix-owned
@@ -111,5 +161,6 @@ Zenith's result remains representative meanwhile.
 
 ## Next step
 
-Continue an external pilot only when its real input arrives. Otherwise no workflow
-implementation action remains.
+Activate the verified corrective generation on Zenith, confirm Vivaldi cannot
+replace the managed launchers, then collect all inputs for the active pilots
+before running them in the order RabbitMQ, OpenAPI/API, workbench, S3, and Herdr.