V2 Claude Code: use the existing channel session and preserve native capabilities

[pc-vigil]

Outcome

Nunchi gates the persistent Claude Code session already serving the configured channel plugin. It must not replace that participant with a second, stripped subprocess.

This means the plugin-owned Discord, Telegram, or other channel session—not whichever foreground terminal happens to be open.

Why this matters

Nunchi should add social judgment to the Claude agent the user already configured, not replace it with a second agent with different memory, tools, identity, or behavior. Otherwise the room is connected, but the user's agent is not.

Current gaps

• The PR feat(claude-code): implement the V2 platform integration #32 candidate starts a private headless session with a replacement prompt and no tools, MCP servers, settings, plugins, skills, or commands.
• Its persisted session identity does not bind the selected provider/account, Claude executable and version, channel plugin, or relevant configuration.
• It accepts only Discord. V2 Claude Code: support authenticated text ingress from every channel plugin #57 tracks authenticated channel-plugin ingress.
• Installation and operation remain manual. V2 Claude Code: ship installation, configuration, supervision, and dashboard support #58 tracks the platform setup path; V2 core: ship unified setup, dashboard, and persistent services #56 tracks the shared operator surface.

Required behavior

• WAKE continues through the existing plugin-owned session's normal model, prompt, memory, tools, MCP servers, plugins, commands, and delivery path.
• Shared Nunchi core alone owns attention, scheduling, ACK, cancellation, and receipts.
• Native tool and privileged effects retain the final V2 authority check; Nunchi does not broaden permissions.
• Bind continuity to the exact channel, room, participant, Claude session, account/provider, runtime/plugin version, and relevant configuration.
• Restart resumes the same committed session.
• Identity drift produces a clear warning and offers safe rebind, reset, update, or restricted fallback instead of silently continuing.
• Rejected, cancelled, expired, malformed, or uncommitted turns cannot become authoritative resumable state.
• The isolated headless runner may remain only as an explicitly selected restricted fallback with its lost capabilities stated plainly.

Dependencies

• Requires: None among current open issues; this defines the native Claude session seam consumed downstream.
• Blocks: The participant-authentication part of Support Claude subscription auth for the V2 Claude Code participant and the attention classifier #35 and channel ingress in V2 Claude Code: support authenticated text ingress from every channel plugin #57.

Done when

• A version-checked native persistent-session seam preserves normal Claude capabilities and exact runtime, account, plugin, room, and session identity.
• Source and package-level fixture tests cover normal conversation, silence, tools, effects, identity drift, cancellation, restart, and rejected turns.
• V2 Claude Code: support authenticated text ingress from every channel plugin #57 owns multi-channel ingress, V2 Claude Code: ship installation, configuration, supervision, and dashboard support #58 owns installation and operator support, and V2 Claude Code: close live and release acceptance gaps #39 owns installed and live acceptance. Those issues consume this seam and do not block V2 Claude Code: use the existing channel session and preserve native capabilities #43.