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/.qwen/QWEN_PRODUCTION_GUIDE.md

@@ -0,0 +1,31 @@
+# Qwen Production Checklist
+
+Use this guide when Qwen supports production-readiness tasks for the MEV Bot. Treat it as a supplement to `docs/6_operations/` and `PROJECT_SPECIFICATION.md`—resolve any open math or precision issues before sign-off.
+
+## 1. Build & Dependency Health
+- `make build` and `go build ./...` must succeed without warnings.
+- Run `.qwen/scripts/math-test.sh`, `./scripts/run_audit_suite.sh`, and `make test-coverage`; ensure math packages stay above the 85% target and the global suite meets the 80% CI threshold.
+- Execute `make simulate-profit` to capture the profitability replay summary before sign-off (attach `reports/simulation/latest/summary.md`).
+- Verify modules with `go mod tidy && go mod verify`; track changes in `go.mod` within the PR.
+
+## 2. Precision & Performance Validation
+- Capture before/after benchmarks (`go test -bench=. -benchmem ./pkg/math/... ./pkg/uniswap/...`). Attach summaries to the release PR.
+- Inspect generated `cpu.prof` and `mem.prof` artefacts via `go tool pprof` to confirm no new regressions.
+- Cross-check critical formulas against `docs/MATH_OPTIMIZATIONS.md` and `docs/MATH_PERFORMANCE_ANALYSIS.md` when adjusting algorithms.
+
+## 3. Security & Risk Controls
+- Execute `gosec ./pkg/math/... ./pkg/uniswap/...` and a full `gosec ./...`; resolve or triage findings.
+- Confirm gas, slippage, and opportunity thresholds match operational expectations in `config/*.yaml`.
+- Ensure RPC failover lists and rate limits align with `PROJECT_SPECIFICATION.md` recommendations.
+
+## 4. Operational Readiness
+- Validate `.env` and deployment manifests (`compose.yaml`, `docker-compose.*.yaml`) reflect current secrets handling—never commit raw keys.
+- Run `./scripts/run.sh` against staging settings to confirm metrics (`METRICS_ENABLED=true`) and logging behave as documented in `docs/6_operations/`.
+- Coordinate with observability owners to verify dashboards and alerts cover math-critical latency (tick conversion, arbitrage scoring).
+
+## 5. Release Handoff
+- Summarize math or precision adjustments, benchmark deltas, profitability replay output, and configuration updates in the release notes.
+- Reference executed commands and attach relevant artefacts (coverage reports, benchmark logs) in the PR description.
+- Confirm post-release monitoring steps and rollback plans are captured in the operations checklist.
+
+Following these steps keeps Qwen’s specialised contributions in lockstep with the broader repository standards while safeguarding production deployments.