record Jason's comms rule and working preferences in the repository (#1503)

Co-Authored-By: Claude Fable 5.1 <[email protected]>

skills/ms-communications/SKILL.md

@@ -12,6 +12,11 @@ SESSIONS.md, never in a pane that scrolls away.
 
 ## Channel
 
+- Harness-native cross-session messaging (Claude Code's SendMessage and
+  ListAgents, or any equivalent built into a harness) is not a Mosaic
+  channel. Jason, 2026-09-12: Mosaic Stack develops and uses its own
+  cross-harness comms; a harness feature may be used only as a stated
+  stopgap when the tmux path is unreachable, and never designed against.
 - `tools/tmux/agent-send.sh` is the only send path. It prepends the preamble,
   submits reliably (bracketed paste, Enter flush, draft detection), and ships
   itself over ssh for remote targets. Never raw `tmux send-keys`; that is how

user/USER.md

@@ -3,3 +3,14 @@
 This is an isolated local runtime test.
 
 The user's name is Jason.
+
+## How Jason works with agents (2026-09-12)
+
+- Honest critique, never flattery. He asks to be told when he is wrong.
+- One pushback, in a sentence or two, then execute under stated assumptions.
+  Repeated reframing after he has decided reads as stalling; he called it
+  "arguing over semantics and pedantics".
+- One piece at a time, each with a yes/no gate; the deferred list
+  (`docs/plans/DEFERRED.md`) holds everything noticed and not fixed.
+- Project facts, plans and rules belong in this repository, not in a
+  harness's private memory.