docs: close herdr pilot

docs/plans/workflow-system.md

@@ -62,6 +62,9 @@ restarted Kitty and closed the user's terminal session.
   approval-blocked states behaved correctly, and dirty worktree removal was
   refused. Nothing reached company GitHub. Both plans found that password reset
   belongs to the separate account service rather than `yookr-dashboard`.
+  Documented named-session detach/reattach persistence is accepted without a
+  redundant live trial; notifications are intentionally disabled after their
+  live pilot.
 
 ## Active pilot gates
 
@@ -73,13 +76,9 @@ These gates do not block work on each other.
 - Route issue 197 to the actual account repositories before implementation;
   leave the two local dashboard planning branches available as evidence.
 
-The remaining Herdr observations are that detach and reattach preserve output
-and each completed event produces exactly one notification. Short, long,
-approval-blocked, fallback-agent, predictable-path, non-overlapping-write,
-dirty-removal, and branch-retention behavior already passed. If a remaining
-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.
+Herdr's bounded pilot is complete. If later use exposes a problem, fall back
+independently to native agent sessions or native `git worktree add/list/remove`;
+do not add a wrapper or Worktrunk without a demonstrated gap.
 
 ## Deferred pilots
 
@@ -184,6 +183,5 @@ the fresh-shell GitHub read and restarted-Codex Context7 lookup must both work.
 
 ## Next step
 
-Confirm the two MariaDB examples inside Dadbod. Then confirm Herdr notifications
-and detach/reattach persistence, and run one real cross-system investigation
-without mutating company GitHub.
+Confirm the two MariaDB examples inside Dadbod, then run one real cross-system
+investigation without mutating company GitHub.