/**
 * MenteeConfig — public surface for the mentee-side receiver wiring of the
 * Agent-to-Agent Telegram comms primitive (MENTOR-LIVE-READINESS-SPEC
 * §Recipient side).
 *
 * Any instar-hosted agent can act as a mentee by enabling this block. When
 * enabled and properly configured, `AgentServer.start()` installs an
 * agent-message hook on the PRIMARY TelegramAdapter that:
 *
 *   1. Intercepts inbound a2a-marker messages BEFORE normal user routing.
 *   2. Verifies the marker's `from` is in `knownMentors` and the sender bot id
 *      matches (anti-spoof — `from.is_bot===true` or `sender_chat` required).
 *   3. Dispatches to the `mentor` role-handler, which spawns a mentee session
 *      with the body as prompt, bounded-waits, and captures the transcript.
 *   4. Sends the captured reply back via `sendAgentMessage` with
 *      `role='mentor-reply'` and `corr=<incoming marker id>`. Reply-out is
 *      wired at the orchestrator level (not inside the handler) so handlers
 *      stay capture-only per the spec's capability-handle anti-loop design.
 *
 * Ships dormant: `enabled: false` by default. The wiring stays dark even when
 * enabled if `localAgentName` / `knownMentors` / `replyChatId` /
 * `replyTopicId` are missing — each absence logs a one-line skip and bails
 * (no partial wiring).
 */
export const DEFAULT_MENTEE_CONFIG = {
    enabled: false,
    localAgentName: '',
    knownMentors: {},
    replyChatId: '',
    replyTopicId: 0,
    sessionTimeoutMs: 5 * 60 * 1000,
};
//# sourceMappingURL=MenteeReceiverConfig.js.map