feat: [1138] デバッグモード時にレーンごとの変数名をキーコンフィグ画面上に表示する機能を追加

[cwtickle]

🔨 変更内容 / Details of Changes

1. feat: デバッグモード時にレーンごとの変数名をキーコンフィグ画面上に表示する機能を追加

• デバッグモード（ローカル起動含む）のときにキーコンフィグ画面上に
  レーンごとの変数名を表示するようにしました。通常公開時は表示しません。

🔖 関連Issue, 変更理由 / Related Issues, Reason for Changes

1. カスタムキー定義時や別キーモード時の設定間違いを画面上で確認しやすくするため。

📷 スクリーンショット / Screenshot

📝 その他コメント / Other Comments

[coderabbitai]

Warning

Review limit reached

@cwtickle, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 9ebcee77-1a18-42a2-996e-25d6220f384c

📥 Commits

Reviewing files that changed from the base of the PR and between ae124d4 and 7e5caf9.

📒 Files selected for processing (1)

• js/danoni_main.js

📝 Walkthrough

Summary by CodeRabbit

• New Features
  • Added character identifiers beneath each key in the key configuration view.
  • Identifiers now hide and show alongside their associated keys when partial-key visibility is used.

Walkthrough

Debug mode now shows each lane’s character identifier below its key arrow. Partial key-group visibility also includes the corresponding debug identifier.

Changes

Debug Key Labels

Layer / File(s)	Summary
Key label rendering and visibility js/danoni_main.js	Debug mode renders character identifiers below key arrows. Partial key-group visibility toggles the associated identifiers.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• cwtickle/danoniplus#2106: Both changes modify key configuration UI behavior in js/danoni_main.js.

Suggested labels: Layout Changes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes adding debug-mode display of per-lane variable names on the KeyConfig screen.
Description check	✅ Passed	The description explains the debug-mode KeyConfig change and its purpose of identifying configuration errors.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/1138-debug-chara-name

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}