[KazumaProject]

追加・改善（Full・Lite共通）

• カスタムキーボードにQWERTY型キーを追加しました。タップ入力、表示ラベル、押下プレビュー、長押し候補、Shift/Caps Lock用の文字列をキーごとに設定できます。
• QWERTY（ローマ字）の初期入力モードを日本語／英語から選択できるようになりました。
• 英語をEnterで確定した後も、文法訂正と後続語候補を利用できるようになりました。
• カスタムキーボードの二段フリック・固定型二段フリックを復元し、数値入力欄でのガイド表示を修正しました。
• F-Droid向けAPKのクリーンビルド比較、タグとソースの照合、署名コピー検証を追加しました。

三段フリックの停止は継続します。既存レイアウトと保存済み定義を保持し、旧形式のバックアップも読み込めます。

Improvements (Full and Lite)

• Add configurable QWERTY keys to custom keyboards, including independent labels, tap output, previews, long-press alternatives, and Shift/Caps Lock layers.
• Add Japanese/English initial input mode selection for Romaji QWERTY.
• Offer English grammar corrections and phrase continuations after Enter confirmation.
• Restore custom two-step and sticky two-step flick input, and fix custom guides in numeric fields.
• Verify clean F-Droid builds, APK source revisions, public tags, and signature copying before publication.

Three-stage flick remains suspended. Existing layouts and stored definitions are retained, and older backup formats can still be imported.

Validation: 266 custom_keyboard JVM tests, 105 focused application JVM tests, 12 release-verification tests, 11 app-device tests and one library instrumentation test pass. Lite app/test APKs build successfully. actionlint and git diff --check pass. Lite Debug lint has the same 15 errors on base dev 691e278 and this release, with no new errors. A normal fresh clone of dev 006176e with an empty Gradle user home builds Lite F-Droid Release successfully (11m 31s); APK revision, package/version 1.7.150/847, and absence of native libraries are verified. Alignment-preserved v2 signing with a temporary test key and apksigcopier 1.1.1 signature copying also pass. Fast Input Regression did not complete: the Full/API35 GitHub run https://github.com/KazumaProject/JapaneseKeyboard/actions/runs/43220668318 was canceled after over an hour without case results. On an isolated API35 ARM64 emulator, the original Lite matrix also hangs before case 1 on both base dev 691e278 and the candidate; Java thread dumps show ActivityScenario / Instrumentation idle waits. The cause of the GitHub Full hang is unconfirmed. A temporary outside-repository diagnostic harness was not a passing regression result. No unrelated legacy-test fixes or suppressions are included. Release-tag CI at b53f9f7 passed all four jobs: standard builds, two independent F-Droid clean builds, and publication. The two unsigned F-Droid APKs are byte-identical (SHA-256 60b41901219c35b939b53254e26b259f0ef50626ee2920fd060615ed6d21ccb1); apksigcopier comparison of the published signed APK against the independent unsigned build passes. All five published APKs match GitHub asset digests and have verified package/version, source revision, signatures, and signing certificate. Full and Lite AABs have verified package/version 847, source revision, JAR signatures, and native symbols where applicable. Both AABs were re-signed with the established Play upload key; every non-signature archive entry hash remains unchanged from the verified CI artifacts. Signed arm64 APK upgrades from v1.7.149 to v1.7.150 pass on the isolated API35 ARM64 emulator: actual IME startup migrates database 49 to 50 and preserves seeded legacy layout/key rows. Official F-Droid server rebuild remains unconfirmed. No generated binaries, images, logs, scripts, or credentials are committed.

Published: GitHub v1.7.150 with five APK assets (https://github.com/KazumaProject/JapaneseKeyboard/releases/tag/v1.7.150); Play Console Full 847 (1.7.150), release 418, and Lite 847 (1.7.150-lite), release 124. Both internal tracks visibly report Available to internal testers. Remote and local tags are now identical and contain only v1.7.149 and v1.7.150; the 26 older tags were removed as requested, the existing origin v1.7.149 was retained, and local v1.7.149 was synchronized to it. The worktree is clean.