docs: correct the website where it had drifted from the implementation

Several statements were wrong rather than merely thin, and each would have set
the wrong expectation:

- the conversion example implied romaji replaces the input, when the result is
  appended in parentheses and both are sent
- the handshake was described as happening at startup, when it waits for the
  first player to join, so a DISCONNECTED status on an empty server read as a
  fault
- cache eviction was called oldest-first, which the unordered in-memory map
  cannot provide
- the Velocity settings table omitted crossServerDirectMessage
- ConfigManager was described as reading Bukkit's FileConfiguration, and the
  settings storage as recovering from a backup that does not exist

It also documents behaviour that had no mention anywhere: the `!` force-global
prefix, that spy sees channel messages and not only DMs, the nightly build
warnings, the overall 1000ms conversion budget that makes api.timeout above it
ineffective, and the data files the plugin writes.

Co-Authored-By: Claude <noreply@anthropic.com>

1 files changed, 3 insertions, 1 deletions

diff --git a/website/src/ja/docs/reference/compatibility.md b/website/src/ja/docs/reference/compatibility.md
index 587261e..781dbf6 100644
--- a/website/src/ja/docs/reference/compatibility.md
+++ b/website/src/ja/docs/reference/compatibility.md
@@ -57,9 +57,11 @@ Paper / Velocity 間の通信は LunaticChat 独自のプラグインメッセ�
 
 接続時は以下の流れで互換性が確認されます：
 
-1. Paper サーバー起動時に Velocity に対してハンドシェイクを送信
+1. **最初のプレイヤーがログインした 1 秒後**に，Paper サーバーが Velocity に対してハンドシェイクを送信
 2. Velocity が Paper のプロトコルバージョンを自身のものと照合
 3. 不一致の場合は Velocity が接続を拒否し，Paper 側の状態が `FAILED` になる
 4. ハンドシェイクのタイムアウトは 5 秒
 
+ハンドシェイクはサーバー起動ごとに1回だけ送信されます．起動時ではなくプレイヤーのログインが契機になるのは，送信に使う plugin messaging チャネルがプレイヤーの接続を必要とするためです．最初のプレイヤーがログインするまで `/lcv status` は `DISCONNECTED` を報告しますが，これは正常であり異常の兆候ではありません．
+
 接続状態は `/lcv status` で確認できます．詳細は [Velocity 連携](/ja/docs/features/velocity#接続状態) を参照してください．