feat: Initialize firefrost-services monorepo structure

WHAT WAS DONE:
- Created npm workspaces configuration in root package.json
- Set up directory structure (services/, shared/, future/)
- Created @firefrost/shared package (v1.0.0)
- Added comprehensive .gitignore for Node.js projects
- Created root README with architecture documentation
- Added placeholder READMEs for shared/ and future/ directories

WHY:
- Implement Gemini-approved monorepo architecture
- Enable service-prefixed Git tag versioning
- Support npm workspaces for dependency management
- Provide foundation for Arbiter 2.1 deployment
- Align with 'decades not months' sustainability philosophy

STRUCTURE:
Root level:
- package.json (workspaces: services/*, shared)
- .gitignore (protects .env files from commits)
- README.md (comprehensive documentation)

Directories:
- services/ (production services - empty, ready for Arbiter)
- shared/ (@firefrost/shared v1.0.0 - placeholder)
- future/ (experimental services)

FILES:
- .gitignore (new, 39 lines)
- README.md (new, 242 lines)
- package.json (new, 27 lines)
- shared/package.json (new, 17 lines)
- shared/README.md (new, 47 lines)
- shared/src/index.js (new, 13 lines)
- future/README.md (new, 38 lines)

NEXT STEPS:
- Migrate Arbiter 2.1 code to services/arbiter/
- Create arbiter-v2.1.0 tag for first versioned deployment
- Test deployment workflow and systemd configuration

Signed-off-by: The Golden Chronicler <claude@firefrostgaming.com>

future/README.md

@@ -0,0 +1,39 @@
+# Future / Experimental Services
+
+This directory contains experimental services, proof-of-concept tools, and ideas being developed for potential inclusion in Firefrost Gaming's production infrastructure.
+
+## Purpose
+
+- **Rapid prototyping** — Test ideas without affecting production services
+- **Learning and exploration** — Try new technologies and approaches
+- **Feature incubation** — Develop features before promoting to production
+
+## Guidelines
+
+Services in this directory:
+
+- May be incomplete or unstable
+- Are not deployed to production
+- May not follow all production standards
+- Can be deleted or refactored freely
+
+## Graduation Process
+
+When an experimental service is ready for production:
+
+1. Move to `services/` directory
+2. Add proper documentation
+3. Create systemd service file
+4. Add environment variable template
+5. Tag initial release version
+6. Deploy to appropriate server
+
+## Current Experiments
+
+(List experimental services here as they're added)
+
+---
+
+**"The best way to predict the future is to build it."**
+
+💙🔥❄️