Method authenticate

packages/acp-adapter/src/server.ts:564–575

* Re-check whether the on-disk token is usable; does NOT trigger an * actual OAuth flow. The stdio JSON-RPC channel has no TTY to render * the device-code prompt — clients are expected to spawn * `kimi login` themselves via the terminal-auth method advertised in * `initialize.authMethods

(params: AuthenticateRequest)

   * (plan G3, lines 68-104).
   */
  async authenticate(params: AuthenticateRequest): Promise<AuthenticateResponse | void> {
    if (params.methodId !== 'login') {
      throw RequestError.invalidParams(
        { methodId: params.methodId },
        `Unknown auth method: ${params.methodId}`,
      );
    }
    if (!(await harnessIsAuthed(this.harness))) {
      throw RequestError.authRequired();
    }
    // void = empty success body (ACP allows AuthenticateResponse | void).
  }

  async prompt(params: PromptRequest): Promise<PromptResponse> {
    const acpSession = this.sessions.get(params.sessionId);