docs: defer Herdr and project workflow work

docs/constellation-work.md

@@ -86,7 +86,7 @@ coherent commit before starting unrelated work.
 - **Agents:** Herdr is selected; agent-deck and tmux remain installed alongside it.
   Codex has agent-deck notifications and hooks enabled. Shared Context7/NixOS skills
   live under `.agents/skills`; a Nix-managed marketplace exposes Ponytail.
-  Zellij is also declared on workstations. Detailed project workflow remains open.
+  Zellij is also declared on workstations. Further project workflow work is deferred.
 - **SharePoint:** Zenith declares an hourly service syncing `company-sharepoint:`
   into `~/.local/share/yookr-reference/sharepoint/Algemeen` and
   `company-sharepoint-projecten:` into `Projecten`. Each invocation has
@@ -156,7 +156,10 @@ and system operation/maintenance; these are discussion areas, not a work queue.
 Herdr's configured keys are accepted: the user reports liking them in practice.
 Niri workspace grouping stays informal while the user discovers what fits; Herdr
 provides enough structure for now. No workspace rules or fixed layout are needed.
-Detailed project/agent working practices remain open. Agent evaluation is
+Further Herdr configuration, agent workflows and project management are explicitly
+deferred at the user's request. Do not use them as the default next task or request
+workflow feedback unless the user reopens the topic. The next area is not selected.
+Agent evaluation is
 explicitly deferred. Do not resume replacement-tool comparisons or ask for an
 evaluation task/budget as a prerequisite for this work.
 
@@ -171,7 +174,7 @@ provide authoritative agent attention states. tmux detach keeps processes alive;
 Zellij resurrection recreates layouts/commands, not process memory. None of these
 capabilities was exercised interactively; no sessions were inspected or changed.
 
-Proposed agent workflow, awaiting discussion (not a Niri workspace requirement):
+Deferred agent workflow proposal (not accepted or a Niri workspace requirement):
 one lead conversation owns each coherent change. Use bounded subagents when work
 is independent, with explicit ownership and evidence returned to the lead. Separate
 worktrees for independent writing efforts, one integration owner. Keep enduring