docs: frame project and agent workflow exploration

Record the reported navigation and coordination friction, verified native capabilities, and provisional workflow comparison. Keep proposed delegation and tool choices distinct from accepted decisions; collect workload, persistence and trial constraints together.

docs/constellation.md

@@ -30,9 +30,16 @@ use a flake to declare its tools without Nix owning the surrounding workspace.
 - Outlook is acceptable as an application, but its interaction and integration
   do not fit as naturally. Accessible mail for tools and agents matters separately
   from choosing a mail reader. Preserve meaning and source context, not just text.
-- Herdr's persistent-agent concept fits; its shortcuts do not. Agent-deck is
-  already installed alongside Herdr; whether it fits through actual use remains
-  open. No replacement has been selected.
+- Herdr provides useful structure: spaces, running agents and visible attention
+  states. Its keybindings and mouse-oriented interaction fit poorly. Agent-deck
+  gave a poor first impression through startup issues; no replacement is selected.
+  Explore whether Niri/Kitty or a terminal multiplexer can provide a more composable
+  workflow while retaining that understandable overview.
+- Current friction is a lack of consistent project and agent working practices,
+  including Niri workspace use. Tool choice and agent collaboration need to be
+  considered together. Alignment, maintainability and human attention matter
+  alongside speed/cost; compare workflows through concrete tasks before adopting
+  a fixed delegation pattern.
 - Repositories should contain code and documentation needed by that code, not
   become containers for general notes and company material destined for Git remotes.
 - Company work includes repositories, reference material, notes, credentials and