fix: suppress oclif TypeScript warning by setting NODE_ENV=production (#35)

- Set NODE_ENV=production before importing @oclif/core
- This prevents oclif from attempting TypeScript detection in production
- Reverted previous complex solution in favor of this simpler approach
- Tested with tsconfig.json in current directory - no warnings

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

Co-authored-by: Claude <[email protected]>

Author: johnlindquist

bin/run.js

@@ -1,21 +1,14 @@
 #!/usr/bin/env node
 
+// Set production mode before importing to prevent TypeScript detection
+process.env.NODE_ENV = 'production'
+
 import {execute} from '@oclif/core'
-import {dirname} from 'node:path'
-import {fileURLToPath} from 'node:url'
 
 // If no arguments provided, default to 'init' command
 const args = process.argv.slice(2)
 if (args.length === 0) {
   process.argv.push('init')
 }
 
-// Get the actual directory of this script
-const __dirname = dirname(fileURLToPath(import.meta.url))
-
-// Execute from the package root, not the current working directory
-await execute({
-  dir: dirname(__dirname),
-  // Explicitly set production mode to avoid TypeScript checks
-  development: false,
-})
+await execute({dir: import.meta.url})