docs: clarify global config as planned feature

• Remove misleading claim about global config fallback
• Add Global Configuration to Planned Features section
• Document use cases and OS-specific file locations
• Link from configuration discovery section to planned features
• Ensures documentation accurately reflects current implementation

Author: SatanshuMishra

README.md

@@ -289,8 +289,8 @@ See [`docs/CONFIG_SCHEMA.md`](docs/CONFIG_SCHEMA.md) for complete configuration
 
 **Configuration discovery:**
 - Searches from current directory up to project root
-- Falls back to global configuration if available
 - Uses sensible defaults if no configuration found
+- Global configuration support is planned for future releases (see [Planned Features](#planned-features))
 
 ---
 
@@ -382,4 +382,25 @@ If you have questions or need clarification, feel free to open a discussion or i
 
 ## Planned Features
 
-_No planned features at this time. Check back later or open an issue to suggest new features!_
+### Global Configuration
+
+Support for user-level global configuration files to enable consistent commit conventions across multiple projects. This will allow you to:
+
+- Set default commit types and preferences in a single location
+- Apply your preferred commit conventions to all projects automatically
+- Override global settings on a per-project basis when needed
+
+**Use cases:**
+- Developers working across multiple repositories who want consistent commit message formats
+- Teams that want to standardize commit conventions organization-wide
+- Personal projects where you want the same commit types everywhere
+
+The global configuration will be stored in OS-specific locations:
+- **macOS/Linux**: `~/.labcommitr.config.yaml` or XDG config directory
+- **Windows**: `%USERPROFILE%\.labcommitr.config.yaml` or AppData directory
+
+Project-specific configurations will always take precedence over global settings.
+
+---
+
+_Have a feature idea? Open an issue to suggest new features!_