refactor: move all remaining files to orig/ directory

Completed clean root directory structure:
- Root now contains only: .git, .env, docs/, orig/
- Moved all remaining files and directories to orig/:
  - Config files (.claude, .dockerignore, .drone.yml, etc.)
  - All .env variants (except active .env)
  - Git config (.gitconfig, .github, .gitignore, etc.)
  - Tool configs (.golangci.yml, .revive.toml, etc.)
  - Documentation (*.md files, @prompts)
  - Build files (Dockerfiles, Makefile, go.mod, go.sum)
  - Docker compose files
  - All source directories (scripts, tests, tools, etc.)
  - Runtime directories (logs, monitoring, reports)
  - Dependency files (node_modules, lib, cache)
  - Special files (--delete)

- Removed empty runtime directories (bin/, data/)

V2 structure is now clean:
- docs/planning/ - V2 planning documents
- orig/ - Complete V1 codebase preserved
- .env - Active environment config (not in git)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

orig/@prompts/security.md

@@ -0,0 +1,24 @@
+You are an expert in blockchain security and MEV bot development. I'm building an MEV bot in Go that needs to be secure against various attack vectors.
+
+I need help with:
+
+1. Protecting private keys and signing credentials
+2. Preventing frontrunning by other bots
+3. Securing RPC endpoint connections
+4. Handling MEV submission securely
+5. Preventing sandwich attacks
+6. Implementing secure configuration management
+
+Please provide production-ready Go code that:
+- Implements secure key management practices
+- Protects against common MEV bot vulnerabilities
+- Handles sensitive data securely
+- Follows security best practices
+- Includes comprehensive comments
+
+The code should:
+- Store private keys securely using hardware wallets or secure enclaves
+- Use encrypted connections for RPC endpoints
+- Implement proper access controls
+- Handle errors without exposing sensitive information
+- Include security checks and validations