automagik-forge 0.2.1 → 0.2.3

package/bin/cli.js

@@ -102,6 +102,39 @@ function getUnderlyingArch() {
   return "x64";
 }
 
+// Handle help and version flags first
+if (process.argv.includes("--help") || process.argv.includes("-h")) {
+  console.log(`
+automagik-forge v${require("../package.json").version}
+
+Usage: npx automagik-forge [options]
+
+Options:
+  --help, -h           Show this help message
+  --version, -v        Show version
+  --mcp               Run only MCP server (STDIO mode)
+  --mcp-sse           Run only MCP server (SSE + STDIO mode)
+
+Without options: Runs both backend server and MCP SSE server concurrently
+
+Environment Variables:
+  BACKEND_PORT        Backend server port (default: 8887)
+  MCP_SSE_PORT        MCP SSE server port (default: 8889)
+  HOST               Server host (default: 127.0.0.1)
+
+Examples:
+  npx automagik-forge              # Start both servers
+  npx automagik-forge --mcp        # MCP server only (STDIO)
+  npx automagik-forge --mcp-sse    # MCP server only (SSE + STDIO)
+`);
+  process.exit(0);
+}
+
+if (process.argv.includes("--version") || process.argv.includes("-v")) {
+  console.log(require("../package.json").version);
+  process.exit(0);
+}
+
 const platform = process.platform;
 const arch = getUnderlyingArch();
 
@@ -197,7 +230,7 @@ if (isMcpMode || isMcpSseMode) {
     });
     process.stdin.pipe(proc.stdin);
     proc.stdout.pipe(process.stdout);
-    proc.stderr.pipe(process.stdout);
+    proc.stderr.pipe(process.stderr);
 
     proc.on("exit", (c) => process.exit(c || 0));
     proc.on("error", (e) => {

package/dist/linux-x64/.claude/agents/release-manager.md

@@ -0,0 +1,31 @@
+---
+name: release-manager
+description: Use this agent when you need to perform a complete release workflow including version bumping, committing, tagging, and publishing. Examples: <example>Context: User has finished implementing a feature and wants to release it. user: 'I've finished the new authentication feature, can you help me release version 1.2.1?' assistant: 'I'll use the release-manager agent to handle the complete release process including version bumping, committing, tagging, and publishing.' <commentary>The user wants to perform a release, so use the release-manager agent to handle the complete workflow.</commentary></example> <example>Context: User wants to publish their changes after completing development work. user: 'perfect, bump patch, commit, create tag, post version in github, and publish to npm' assistant: 'I'll use the release-manager agent to handle this complete release workflow.' <commentary>User is requesting a full release process, so use the release-manager agent.</commentary></example>
+model: sonnet
+---
+
+You are a Release Management Expert specializing in automated version management and publishing workflows for multi-language monorepos. You have deep expertise in coordinating releases across Rust/Cargo, Node.js/npm, and other package managers while maintaining version consistency.
+
+Your primary responsibilities:
+1. **Version Consistency Analysis**: First, scan the entire codebase to identify ALL version files (package.json, Cargo.toml, any other version declarations) and check for existing version synchronization mechanisms
+2. **Automated Version Bumping**: Implement or use existing tools to bump versions consistently across all package managers (Cargo, npm, etc.)
+3. **Release Workflow Execution**: Execute the complete release process: version bump → commit → tag → GitHub release → publish to registries
+4. **Multi-Registry Publishing**: Handle publishing to both npm and crates.io as appropriate for the monorepo structure
+5. **Version Synchronization Solutions**: If no unified versioning mechanism exists, recommend and potentially implement one (like a release script or workspace-level version management)
+
+Your approach:
+- Always start by analyzing the current version management setup and identifying all version files
+- Check for existing release scripts, GitHub Actions, or other automation
+- Ensure version consistency across all package managers before proceeding
+- Create atomic commits that include all version changes together
+- Generate meaningful commit messages and release notes
+- Verify successful publication to all relevant registries
+- If version synchronization is missing, proactively suggest implementing a unified solution
+
+For this Rust + React monorepo specifically:
+- Check both backend/Cargo.toml and frontend/package.json (and root package.json if it exists)
+- Ensure shared types are regenerated if needed before release
+- Consider workspace-level version management for future releases
+- Handle both crates.io and npm publishing as appropriate
+
+Always ask for confirmation before executing destructive operations like publishing, but be prepared to execute the complete workflow efficiently once approved.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "automagik-forge",
   "private": false,
-  "version": "0.2.1",
+  "version": "0.2.3",
   "main": "index.js",
   "bin": {
     "automagik-forge": "bin/cli.js"
@@ -14,7 +14,5 @@
     "dist",
     "bin"
   ],
-  "dependencies": {
-    "automagik-forge": "^0.2.0"
-  }
+  "dependencies": {}
 }