From ffb3ac5c661f5bf18f37b8153232d553ef42070a Mon Sep 17 00:00:00 2001
From: Tajim <com.tajim@gmail.com>
Date: Sat, 5 Sep 2026 21:58:28 +0600
Subject: [PATCH 1/4] fix: prevent bottom navigation appearing above mobile
 keyboard (#315)

---
 resources/views/app.blade.php | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/resources/views/app.blade.php b/resources/views/app.blade.php
index cd0f9d50..a2bebafa 100644
--- a/resources/views/app.blade.php
+++ b/resources/views/app.blade.php
@@ -18,7 +18,7 @@
                 } catch (_) {}
             })();
         </script>
-        <meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">
+        <meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover, interactive-widget=overlays-content">
         <meta name="csrf-token" content="{{ csrf_token() }}">
         <meta name="color-scheme" content="light dark">
         {{-- Browser chrome: top status bar + bottom nav bar (Chrome / Edge / Samsung Internet) --}}

From 17f86a7310060fd1f68eb361e8321e5c33f1b1af Mon Sep 17 00:00:00 2001
From: Tajim <com.tajim@gmail.com>
Date: Sat, 5 Sep 2026 21:59:42 +0600
Subject: [PATCH 2/4] docs: update git workflow guidelines in GEMINI.md

---
 GEMINI.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/GEMINI.md b/GEMINI.md
index 853540da..6b018581 100644
--- a/GEMINI.md
+++ b/GEMINI.md
@@ -6,3 +6,18 @@ When asked to fix or check formatting/linting issues, or before committing code
 ```bash
 npm run format && composer lint && npm run lint
 ```
+
+## Git Workflow & Push
+When asked to push:
+1. Always create a new branch from `main` (pulling the latest changes first):
+   ```bash
+   git checkout main && git pull origin main && git checkout -b <new-branch>
+   ```
+2. Switch to that branch.
+3. Use atomic commits where applicable.
+4. Never force push (`--force` or `-f`).
+5. Push the branch to the remote:
+   ```bash
+   git push -u origin <new-branch>
+   ```
+

From 66d03ceb1a0be171eab2be974098fd5ccb17bf14 Mon Sep 17 00:00:00 2001
From: Tajim <com.tajim@gmail.com>
Date: Sat, 5 Sep 2026 22:00:16 +0600
Subject: [PATCH 3/4] docs: clarify formatting check and push rules in
 GEMINI.md

---
 GEMINI.md | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/GEMINI.md b/GEMINI.md
index 6b018581..f2dddec2 100644
--- a/GEMINI.md
+++ b/GEMINI.md
@@ -15,9 +15,14 @@ When asked to push:
    ```
 2. Switch to that branch.
 3. Use atomic commits where applicable.
-4. Never force push (`--force` or `-f`).
-5. Push the branch to the remote:
+4. Run formatting and linting checks before committing:
+   ```bash
+   npm run format && composer lint && npm run lint
+   ```
+5. Never force push (`--force` or `-f`).
+6. Push the branch to the remote repository:
    ```bash
    git push -u origin <new-branch>
    ```
 
+

From 79a3bd10718c7790b0629e0a35952e198980b359 Mon Sep 17 00:00:00 2001
From: Tajim <com.tajim@gmail.com>
Date: Sat, 5 Sep 2026 22:01:04 +0600
Subject: [PATCH 4/4] docs: add PR creation requirement to GEMINI.md

---
 GEMINI.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/GEMINI.md b/GEMINI.md
index f2dddec2..1d000fdb 100644
--- a/GEMINI.md
+++ b/GEMINI.md
@@ -24,5 +24,7 @@ When asked to push:
    ```bash
    git push -u origin <new-branch>
    ```
+7. Create a Pull Request (PR) with a clear, respective title and description linking relevant issues.
+