fix: resolve script execution issue for npx and global install, bump to 0.1.8

The root issue was the import.meta.url execution check not working with npm bin symlinks.

Changes:
- Replace complex execution detection with simple main() call
- This ensures the script runs in all contexts: direct execution, npm bin, npx
- Short bin name 'ccstatus' works with npx -p syntax
- Both global install and npx now produce correct output

✅ Working: echo '...' | ccstatus
✅ Working: echo '...' | npx ./package.tgz
✅ Ready for: echo '...' | npx -p @this-dot/claude-code-context-status-line ccstatus

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

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

Author: efouts

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@this-dot/claude-code-context-status-line",
-  "version": "0.1.7",
+  "version": "0.1.8",
   "description": "Custom Claude Code status line to restore context window visibility for AWS Bedrock users by displaying token usage.",
   "type": "module",
   "main": "src/context-status.js",

src/context-status.js

@@ -160,6 +160,6 @@ function safeParseInt(value) {
 // Export the main API
 export { main, getTotalTokens, getTranscriptPathAndModel, formatStatusLine };
 
-if (import.meta.url === `file://${process.argv[1]}`) {
-  main();
-}
+// Always run main when this file is executed as a script
+// This works for both direct execution and npm bin symlinks
+main();