v1.3.85

LAN Chat: Team Concept + P2P Broadcast

Team-based identity and messaging — Each LAN Chat participant now has a
three-layer identity: name@role@team (e.g. alice@frontend@platform).

/nick alice@frontend@platform sets all three layers at once
Defaults: role=developer, team=dev-team (backward compatible)
Role and team persist per-session, restored on reload
New send_team action: message all members of a specific team
Unknown team names trigger a helpful error listing valid teams
LLM system prompt includes team/role/workspace/languages for each online instance

P2P broadcast via to='*' — The send action now supports to='*' to
broadcast to all participants, unifying DM and broadcast into one action:

lanchat(action='send', to='node-id')   → direct message
lanchat(action='send', to='*')         → broadcast to everyone

LAN Chat stability: Decoupled liveness heartbeat from mDNS discovery to
eliminate excessive online/offline churn when peers briefly drop off mDNS
LLM team awareness: System prompt lists online instances with team, role,
workspace, and language info so the LLM can proactively identify collaborators
Presence metadata: Workspace path, project name, languages, and frameworks
are exchanged via presence and visible in list output
Comprehensive test coverage: 15 new tests covering team data model,
P2P broadcast routing, send_team validation, and session persistence

Full rewrite of LAN Chat guide with team concept,
send_team, P2P broadcast, presence fields, and team-based collaboration
Added /nick entry to Slash Commands
Updated GGCODE.md architecture and tool descriptions