docs: close workflow phase one

docs/workflow-discovery.md

@@ -1,7 +1,8 @@
 # Workflow system blueprint
 
-Status: declarative core implemented; pilots remain. Current gates and the
-operational handoff live in [`plans/workflow-system.md`](plans/workflow-system.md).
+Status: phase one implemented and active; explicitly deferred pilots remain.
+The operational handoff lives in
+[`plans/workflow-system.md`](plans/workflow-system.md).
 
 This document is the durable design for the workstation and surrounding Yookr
 workflow. Implementation history belongs in Git.
@@ -160,12 +161,11 @@ generalize the exception to other repositories.
 Only the user activates a NixOS or Home Manager generation. Agents may evaluate
 and build configurations, then provide an activation command.
 
-## Remaining pilots
+## Phase-one closure
 
-- Run one real cross-system investigation. The workbench environment, all four
-  SOPS-derived Dadbod connections, read-only example-query runs, and Kulala
-  response chaining have passed. Add a Marimo report only when the investigation
-  gives it durable value.
+- The workbench environment, all four SOPS-derived Dadbod connections, read-only
+  example-query runs, and Kulala response chaining passed. The cross-system
+  investigation and Marimo report pilots move into phase two.
 - Add another ephemeral read-only rclone remote only when credentials for a new
   Leafcloud project become available. Irristaud listing has passed; do not upload.
 - Use the reviewed local Yookr OpenAPI contract while the accepted malformed
@@ -176,11 +176,12 @@ and build configurations, then provide an activation command.
   states, local branches, parallel non-overlapping plans, and the dirty-removal
   guard passed; the plans show that implementation belongs outside the dashboard
   repository.
-- Keep Bruno, DBeaver, and existing PIM clients until their independent gates are
-  resolved.
+- Keep Bruno and DBeaver; retiring old applications is outside phase one.
 
 ## Deferred pilots
 
+Revisit these alongside related phase-two ideas rather than as isolated cleanup.
+
 - Capture Zenith's external display identity during a docked session and test the
   two-output `Super+A` exchange, including name and focus restoration on failure.
 - Resume Evolution and Android PIM only when the user chooses to run those daily