fathom-cli 0.3.3 → 0.3.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fathom-cli",
-  "version": "0.3.3",
+  "version": "0.3.4",
   "description": "Headless intelligence layer for AI-augmented development — intent-driven, provider-agnostic, self-improving. Active development.",
   "type": "module",
   "bin": {
@@ -42,7 +42,12 @@
   ],
   "repository": {
     "type": "git",
-    "url": "https://github.com/olivelliott/fathom"
+    "url": "https://github.com/olivelliott/fathom.git",
+    "directory": "packages/cli"
+  },
+  "homepage": "https://github.com/olivelliott/fathom",
+  "bugs": {
+    "url": "https://github.com/olivelliott/fathom/issues"
   },
   "author": "olivelliott",
   "license": "MIT",
@@ -68,15 +73,15 @@
     "tsup": "^8.3.0",
     "typescript": "^5.7.0",
     "vitest": "^2.1.0",
-    "@fathom/projections": "0.1.0",
+    "@fathom/core": "0.1.0",
+    "@fathom/intake": "0.1.0",
     "@fathom/intent": "0.1.0",
     "@fathom/reports": "0.1.0",
-    "@fathom/store": "0.1.0",
+    "@fathom/projections": "0.1.0",
     "@fathom/sync": "0.1.0",
-    "@fathom/tracker": "0.1.0",
-    "@fathom/core": "0.1.0",
-    "@fathom/intake": "0.1.0",
-    "@fathom/velocity": "0.1.0"
+    "@fathom/store": "0.1.0",
+    "@fathom/velocity": "0.1.0",
+    "@fathom/tracker": "0.1.0"
   },
   "scripts": {
     "build": "tsup",

package/plugins/fathom/.mcp.json

@@ -2,7 +2,7 @@
   "mcpServers": {
     "fathom": {
       "command": "npx",
-      "args": ["-y", "fathom-mcp@latest", "--project-dir", "."]
+      "args": ["-y", "fathom-token-mcp@latest", "--project-dir", "."]
     }
   }
 }

package/plugins/fathom/skills/budget/SKILL.md

@@ -37,4 +37,4 @@ If no budget is configured, tell the user to set one up:
 - Run `fathom init` to create a project configuration, or
 - Manually add a budget section to `.fathom/intent.yaml`
 
-If the `fathom_check_budget` MCP tool is not available, tell the user to check their MCP configuration. They may need to run `npx fathom-mcp` or verify that the Fathom MCP server is configured in their `.mcp.json`.
+If the `fathom_check_budget` MCP tool is not available, tell the user to check their MCP configuration. They may need to run `npx fathom-token-mcp` or verify that the Fathom MCP server is configured in their `.mcp.json`.

package/plugins/fathom/skills/estimate/SKILL.md

@@ -55,4 +55,4 @@ If overhead is significant, briefly note the breakdown (retries, context loading
 
 ## Error Handling
 
-If the `fathom_estimate_task_cost` MCP tool is not available, tell the user to check their MCP configuration. They may need to run `npx fathom-mcp` or verify that the Fathom MCP server is configured in their `.mcp.json`.
+If the `fathom_estimate_task_cost` MCP tool is not available, tell the user to check their MCP configuration. They may need to run `npx fathom-token-mcp` or verify that the Fathom MCP server is configured in their `.mcp.json`.

package/plugins/fathom/skills/projections/SKILL.md

@@ -33,4 +33,4 @@ After presenting the list, note:
 
 If intent.yaml is not found, tell the user to run `fathom init` first to create a project configuration with an intent file.
 
-If the `fathom_generate_tool_configs` MCP tool is not available, tell the user to check their MCP configuration. They may need to run `npx fathom-mcp` or verify that the Fathom MCP server is configured in their `.mcp.json`.
+If the `fathom_generate_tool_configs` MCP tool is not available, tell the user to check their MCP configuration. They may need to run `npx fathom-token-mcp` or verify that the Fathom MCP server is configured in their `.mcp.json`.

package/plugins/fathom/skills/recommend-model/SKILL.md

@@ -50,4 +50,4 @@ If the user provided a budget, note how the recommendation accounts for their bu
 
 ## Error Handling
 
-If the `fathom_recommend_model` MCP tool is not available, tell the user to check their MCP configuration. They may need to run `npx fathom-mcp` or verify that the Fathom MCP server is configured in their `.mcp.json`.
+If the `fathom_recommend_model` MCP tool is not available, tell the user to check their MCP configuration. They may need to run `npx fathom-token-mcp` or verify that the Fathom MCP server is configured in their `.mcp.json`.

package/plugins/fathom/skills/status/SKILL.md

@@ -39,4 +39,4 @@ Get a quick overview of the current project's state including feature progress,
 
 If the project is not initialized, tell the user to run `fathom init` to set up a Fathom project in the current directory.
 
-If the `fathom_get_project_status` MCP tool is not available, tell the user to check their MCP configuration. They may need to run `npx fathom-mcp` or verify that the Fathom MCP server is configured in their `.mcp.json`.
+If the `fathom_get_project_status` MCP tool is not available, tell the user to check their MCP configuration. They may need to run `npx fathom-token-mcp` or verify that the Fathom MCP server is configured in their `.mcp.json`.

package/plugins/fathom/tests/integrations.test.ts

@@ -47,9 +47,9 @@ for (const doc of INTEGRATION_DOCS) {
       expect(content).toContain(`"${doc.rootKey}"`);
     });
 
-    it("references fathom-mcp", () => {
+    it("references fathom-token-mcp", () => {
       const content = readFileSync(filePath, "utf-8");
-      expect(content).toContain("fathom-mcp@latest");
+      expect(content).toContain("fathom-token-mcp@latest");
     });
 
     it("contains copy-pasteable JSON config block", () => {

package/plugins/fathom/tests/plugin.test.ts

@@ -37,7 +37,7 @@ describe(".mcp.json", () => {
 
     expect(config.mcpServers.fathom.command).toBe("npx");
     expect(config.mcpServers.fathom.args).toBeInstanceOf(Array);
-    expect(config.mcpServers.fathom.args).toContain("fathom-mcp@latest");
+    expect(config.mcpServers.fathom.args).toContain("fathom-token-mcp@latest");
     expect(config.mcpServers.fathom.args).toContain("--project-dir");
   });
 });