chore: ignore IDE/.github folders and untrack them

.github/copilot-instructions.md

@@ -1,61 +0,0 @@
-# 🧠 Custom Instructions for GitHub Copilot  
-**Project Context: Discord Bot + Game System Integration (discord.js 15.0.0-dev.1759363313-f510b5ffa)**  
-
----
-
-## 1. Primary Source of Truth
-- Always treat the **installed package** in `node_modules/discord.js` as the *definitive source* of API behavior and typings.  
-- Do **not** rely solely on public documentation or examples; cross-verify any methods, classes, or type names directly from:
-  - The source code and declaration files inside `node_modules/discord.js`
-  - The project’s internal reference file `example.ts.txt`  
-
-> If discrepancies exist, assume `example.ts.txt` and local types reflect the *intended experimental API* for this build.
-
----
-
-## 2. Secondary Sources
-Use these **only when confirmed to still be valid** for the current development version:  
-- [Discord.js Guide](https://discordjs.guide)  
-- [discord.js GitHub Repository](https://github.com/discordjs/discord.js)  
-- [Discord API Types GitHub](https://github.com/discordjs/discord-api-types)  
-- [Discord Developer Documentation](https://discord.com/developers/docs/intro)  
-
-> ⚠️ Mark explicitly when a snippet or concept originates from official docs and may be outdated.
-
----
-
-## 3. Code & Type Analysis Scope
-Copilot must **investigate, interpret, and reference** the following project directories for all game logic and command definitions:  
-
-- `src/game/**`  
-- `src/commands/game/**`  
-- `src/commands/admin/**`  
-
-### Tasks:
-- Analyze **all game-related classes, interfaces, and types**, including metadata structures (e.g., `GameAreaLevel`, `GameArea`, `ScheduledMobAttack`, and mission types).  
-- Identify how these interact with command creation and execution flows.  
-- Detect **missing type declarations**, inconsistent imports, or unreferenced type usages.  
-- Evaluate whether metadata in `GameAreaLevel` can safely include additional properties (e.g., `image`, `referenceImage`, or similar) for visual mapping of game areas.  
-- Verify that all related commands and editors properly support or update those fields.
-
----
-
-## 4. Appwrite Integration Considerations
-While analyzing the above directories, also check for:
-- Possible migration paths for mission and attack scheduling logic (`ScheduledMobAttack`, mission trackers) into **Appwrite Functions** or **Appwrite Realtime** for better live synchronization and event-driven execution.  
-- Type definitions or data structures that may need adaptation for Appwrite’s SDK.
-
----
-
-## 5. Validation
-Before finalizing any generated code or type updates:  
-- Run TypeScript validation to ensure type correctness:
-  ```bash
-  npx tsc --noEmit
-```
-
-## 6. Communication Protocol
-When Copilot suggests or modifies code, it must explicitly indicate the origin of the reference:
-- 🟩 node_modules → Authoritative source (preferred)
-- 🟦 example.ts.txt → Experimental / confirmed local reference
-- 🟨 Official docs → Secondary, possibly outdated source

.github/prompts/discord.js-v15-dev.prompt.md

@@ -1,11 +0,0 @@
-# Prompt: Discord.js 15 Development Mode
-
-When assisting with Discord.js version `15.0.0-dev.1759363313-f510b5ffa`:
-
-- Treat the installed code in `node_modules/discord.js` as the primary and most reliable reference.
-- Always analyze the file `example.ts.txt` to extract API patterns, since it reflects the intended usage of this dev version.
-- Do not rely blindly on official docs or the guide; use them only to compare and note differences with the dev version.
-- Highlight when functionality has changed from v14 to v15, based on observed code and `example.ts.txt`.
-- Encourage verification by:
-  ```bash
-  npx tsc --noEmit

.github/prompts/error-strict.prompt.md

@@ -1,28 +0,0 @@
-# Prompt: TypeScript Strict Error Resolver
-
-Whenever Copilot generates or modifies code:
-
-1. **Never ignore compiler errors** like `TS2339`, `TS2345`, or similar.
-    - Always explain what the error means in plain language.
-    - Always suggest at least one concrete fix.
-
-2. **For missing properties or methods (e.g. `TS2339`)**:
-    - Check if the method exists in the installed `node_modules`.
-    - If it doesn’t exist, assume the API changed in `discord.js@15-dev`.
-    - Propose alternatives based on actual available methods (`example.ts.txt` must be consulted).
-
-3. **For type mismatches (e.g. `TS2345`)**:
-    - Suggest code changes that handle `null`/`undefined` safely.
-    - Show how to cast or coerce types **without breaking strict typing**.
-
-4. **Validation step**:
-    - Always remind to rerun:
-      ```bash
-      npx tsc --noEmit
-      ```
-      until the project compiles cleanly.
-    - Do not consider the task “done” if compiler errors remain.
-
-5. **Explicitness**:
-    - Always specify: “This code suggestion resolves TS2339 / TS2345.”
-    - Never produce a code snippet that still triggers the same error.