docs: accept Herdr bindings and keep Niri workspaces flexible

docs/constellation-work.md

@@ -153,9 +153,10 @@ The focus is the broader environment, not further API/database polish. Candidate
 areas remain places/ownership, navigation/interaction, human/agent collaboration,
 and system operation/maintenance; these are discussion areas, not a work queue.
 
-Current focus: resume project/workspace organization after the dictation detour.
-Herdr's keys are configured below; their practical fit still needs user feedback.
-The user likes its structure, spaces and overview. Agent evaluation is
+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
 explicitly deferred. Do not resume replacement-tool comparisons or ask for an
 evaluation task/budget as a prerequisite for this work.
 
@@ -170,7 +171,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 workflow, awaiting discussion: organize human-visible work by project/task;
+Proposed agent workflow, awaiting discussion (not 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
@@ -198,14 +199,12 @@ file. Direct Ctrl+Alt bindings supplement the existing Ctrl+B prefix shortcuts:
 Inside workspace navigation, U/I moves down/up and H/J/K/L retains pane navigation.
 Niri and Kitty bindings are unchanged. Syntax and action names were checked against
 the installed Herdr 0.9.0 default config and current upstream documentation.
-Interactive delivery through Kitty remains for user acceptance after activation.
+The user reports that the bindings work well in practice.
 Reload Herdr with its existing Ctrl+B then Shift+R binding after activating Nix.
 Verification: repository formatting, rendered TOML parsing, flake evaluation,
 Zenith no-link system build and whitespace checking passed. No tests or live Herdr
 session changes performed by the agent. The user's activation installed the Herdr
 config and preserved `config.toml.bak`, but Home Manager later timed out (below).
-After retrying activation, reload Herdr and gather combined feedback on
-pane/workspace movement, the pickers and agent jumps.
 
 Activation fix (2026-09-09): Home Manager's service switch stopped and restarted
 the running SharePoint oneshot, then waited until Home Manager's five-minute start

docs/constellation.md

@@ -36,13 +36,15 @@ use a flake to declare its tools without Nix owning the surrounding workspace.
   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 is the chosen agent workspace manager: its spaces, running-agent overview
-  and attention states fit. Adapt its keybindings to the keyboard-driven setup.
+  and attention states fit. Its configured keybindings are accepted in daily use.
   Use Ctrl+Alt for direct Herdr actions alongside Super for Niri and Ctrl navigation
   in Neovim; retain Herdr's prefix bindings. Agent-deck's startup issues and other
   session-manager alternatives are not the current focus.
-- 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
+- Keep Niri workspaces flexible. Herdr supplies enough structure that no strict
+  desktop grouping, fixed workspace names or project-to-workspace mapping is
+  needed now. Let actual use inform any later organization.
+- Project and agent working practices remain exploratory.
+  Alignment, maintainability and human attention matter
   alongside speed/cost. Agent-workflow evaluation is deferred; no fixed delegation
   pattern has been selected.
 - Repositories should contain code and documentation needed by that code, not