mission(tess): invariant #6 — HMI agent name is config, never hardcoded

Jason design directive: the HMI agent name must be user-chosen or
system-generated at config, carried as roster/profile data. 'Tess' is
default/example + build codename only. M2 exit gate must prove a distinct
name provisions with zero code change.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QDgorbfgN4Fgi1iHGkgndn

docs/tess/MISSION-MANIFEST.md

@@ -24,6 +24,7 @@ Ship Tess as Jason's durable Pi-native GPT-5.6 Sol high-reasoning interaction ag
 3. Mos owns coding/general fleet orchestration; Tess owns human interaction, visibility, mediation, and migration access.
 4. Runtime, transport, channel, memory, and external-agent integrations are replaceable adapters.
 5. No source task completes before merged PR, terminal-green CI, independent review, and linked task/issue closure.
+6. **The HMI agent's name/identity is configuration, never a hardcoded literal.** The agent name (display + roster key) is supplied at provisioning — user-chosen or system-generated during config — and carried as data in the roster/profile. "Tess" is only the default/example instance name and this mission's build codename; no source, schema key, service identifier, or config default may hardcode it. (M2 exit gate must prove a distinct name provisions cleanly with zero code change.)
 
 ## Milestones