mason-context 0.3.0 → 0.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1269,7 +1269,7 @@ function createMcpServer() {
1269
1269
  const server = new McpServer(
1270
1270
  {
1271
1271
  name: "mason",
1272
- version: "0.3.0"
1272
+ version: "0.3.1"
1273
1273
  },
1274
1274
  {
1275
1275
  instructions: "Mason is a context engineering tool. Always call get_snapshot before using Explore agents, Glob, or Grep to understand the codebase. The snapshot is a concept map that maps features and flows to their implementing files \u2014 it eliminates the need to search. This applies to ANY question about architecture, features, flows, how things work, cross-feature interactions, or bug investigation. Workflow: 1) Call get_snapshot first. 2) If no snapshot, call full_analysis and then save_snapshot to create one. 3) If the snapshot is stale, tell the user and offer to update it. 4) Use your native file reading tool to read files the snapshot points to. 5) Before modifying a file, call get_impact to check what else might be affected. 6) After making significant changes (new features, refactors, architecture changes), call save_snapshot to update the concept map."
package/dist/bin/mason.js CHANGED
@@ -1823,7 +1823,7 @@ function createMcpServer() {
1823
1823
  const server = new McpServer(
1824
1824
  {
1825
1825
  name: "mason",
1826
- version: "0.3.0"
1826
+ version: "0.3.1"
1827
1827
  },
1828
1828
  {
1829
1829
  instructions: "Mason is a context engineering tool. Always call get_snapshot before using Explore agents, Glob, or Grep to understand the codebase. The snapshot is a concept map that maps features and flows to their implementing files \u2014 it eliminates the need to search. This applies to ANY question about architecture, features, flows, how things work, cross-feature interactions, or bug investigation. Workflow: 1) Call get_snapshot first. 2) If no snapshot, call full_analysis and then save_snapshot to create one. 3) If the snapshot is stale, tell the user and offer to update it. 4) Use your native file reading tool to read files the snapshot points to. 5) Before modifying a file, call get_impact to check what else might be affected. 6) After making significant changes (new features, refactors, architecture changes), call save_snapshot to update the concept map."
@@ -2004,10 +2004,11 @@ function extractMarkdown(raw) {
2004
2004
  return trimmed;
2005
2005
  }
2006
2006
  function createCLI() {
2007
+ process.on("SIGINT", () => process.exit(130));
2007
2008
  const program2 = new Command();
2008
2009
  program2.name("mason").description(
2009
2010
  "Context engineering CLI & MCP server \u2014 generates intelligent CLAUDE.md files"
2010
- ).version("0.3.0");
2011
+ ).version("0.3.1");
2011
2012
  program2.command("setup").description("Register Mason as an MCP server with Claude Code").option("--scope <scope>", "Config scope: user or project", "user").action(async (opts) => {
2012
2013
  const { execFile: execFile9 } = await import("child_process");
2013
2014
  const { promisify: promisify9 } = await import("util");