docs: sync to Claude Code v2.1.235 (#174)

* docs: sync to Claude Code v2.1.235

Syncs the tutorial repo from v2.1.233 to v2.1.235, fixes a fabricated
plugin-command reference and a wrong lesson-quiz answer, closes translation
fan-out gaps, and documents six new features from v2.1.234/v2.1.235.

* docs(slash-commands): scope v2.1.234 dialog-command claims to the fullscreen TUI

The v2.1.234 changelog carries two separate entries: /permissions opening
mid-turn unconditionally, and the /add-dir, /autocompact, /theme, /help,
/config and /advisor dialogs opening mid-turn in the fullscreen TUI. The
sync flattened both into one unqualified bullet, so a reader on the default
renderer would find the described behavior absent.

Also corrects the CATALOG usage-limit auto-continue row, which described an
on-by-default feature as opt-in ("Enable via /config"); the changelog says
"turn it off in /config".

* docs(advanced-features): correct spellcheck value shape, default, and scope

settings.md documents `spellcheck` as object-valued
(`{"enabled": true, "language": "en_GB"}`) and read from user settings, the
--settings flag, and managed settings only; interactive-mode.md adds that it
is off by default and needs aspell, hunspell, or ispell on PATH. CATALOG told
readers to set a bare `"spellcheck": true`, and both settings tables sit under
preambles promising project-scope settings work, which for this key they do
not.

Also repoints CATALOG's hook-configuration example at pre-tool-check.sh; the
table rename left the example on validate-bash.py, which is not in 06-hooks/.

* docs(plugins): drop the unsupported claim that /plugin update does not exist

The sync asserted "Updating is CLI-only — there is no `/plugin update` slash
command". The plugins reference contradicts that: it refers to running
`/plugin update` twice in present tense (the cache-key section, and the
explicit-version row that says `/plugin update` reports "already at the
latest version"). The v2.1.235 binary carries no `/plugin update` string and
its own update notices point at `claude plugin update <name>` in a terminal,
so the sources conflict and neither absolute is safe to teach.

Recommends the CLI form on its documented merits instead of asserting a
negative. Mirrored to vi/ja/zh/uk and to the lesson-quiz Q8 explanation,
which taught the same false negative. Q8's correct answer is unchanged.

* docs(advanced-features): complete the v2.1.234 env-var fan-out and 04 TOC (#175)

The env-var block was still headed (v2.1.221-v2.1.233) and omitted both
variables v2.1.234 added: CLAUDE_CODE_PROJECT_DIR_NAME, which had reached
only 10-cli and CATALOG, and CLAUDE_CODE_GOAL_CHECKIN_MINUTES, which was in
prose and a CATALOG row but no env-var table.

Also adds the one missing 04-subagents TOC entry: Additional Resources was
the only H2 without one, leaving the reconciled TOC at 26 of 27 sections.

ja/07-plugins/README.md

@@ -930,7 +930,7 @@ Complete PR review workflow with security, testing, and documentation checks.
 
 2. **プラグインの詳細を表示：**
    ```bash
-   /plugin info plugin-name
+   claude plugin details plugin-name
    ```
 
 3. **プラグインをインストール：**
@@ -953,13 +953,17 @@ Complete PR review workflow with security, testing, and documentation checks.
 ### インストール済みプラグインの一覧
 
 ```bash
-/plugin list --installed
+/plugin list             # インストール済みの全プラグイン
+/plugin list --enabled   # 有効なプラグインのみ
+/plugin list --disabled  # 無効なプラグインのみ
 ```
 
 ### プラグインの更新
 
+更新には CLI 形式を使う。これは [`plugin update`](https://code.claude.com/docs/en/plugins-reference) として文書化されている形式であり、更新がある場合に Claude Code 自身が案内する形式でもある：
+
 ```bash
-/plugin update plugin-name
+claude plugin update plugin-name
 ```
 
 ### プラグインの無効化 / 有効化
@@ -1022,7 +1026,7 @@ Complete PR review workflow with security, testing, and documentation checks.
 - `plugin.json` のパスが実際のディレクトリ構造と一致するか確認
 - ファイル権限を確認：`chmod +x scripts/`
 - コンポーネントファイルの構文を確認
-- ログを確認：`/plugin debug plugin-name`
+- コンポーネントの一覧を確認：`claude plugin details plugin-name`
 
 ### MCP 接続が失敗する
 - 環境変数が正しく設定されているか確認
@@ -1031,9 +1035,9 @@ Complete PR review workflow with security, testing, and documentation checks.
 - `mcp/` ディレクトリ内の MCP 設定を確認
 
 ### インストール後にコマンドが利用できない
-- プラグインが正しくインストールされているか確認：`/plugin list --installed`
-- プラグインが有効か確認：`/plugin status plugin-name`
-- Claude Code を再起動：`exit` して再度開く
+- プラグインが正しくインストールされているか確認：`/plugin list`
+- プラグインが有効か確認：`/plugin list --enabled`
+- すでに有効化されているか確認 — [インストール方法](#インストール方法)のインストール要約の説明を参照：`Plugin is now active.` なら追加の操作は不要、`Run /reload-plugins to activate.` ならそのコマンドを実行する（再起動は不要）
 - 既存のコマンドと名前が衝突していないか確認
 
 ### フック実行の問題
@@ -1054,8 +1058,8 @@ Complete PR review workflow with security, testing, and documentation checks.
 
 ---
 
-**最終更新**: 2026 年 8 月 15 日
-**Claude Code バージョン**: 2.1.233
+**最終更新**: 2026 年 8 月 19 日
+**Claude Code バージョン**: 2.1.235
 **出典**:
 - https://code.claude.com/docs/en/discover-plugins
 - https://code.claude.com/docs/en/settings