chain-insights 0.2.16

package/dist/init-BjuFt54X.cjs

@@ -0,0 +1,232 @@
+const require_chunk = require("./chunk-CZWwpsFl.cjs");
+let node_path = require("node:path");
+node_path = require_chunk.__toESM(node_path, 1);
+let node_fs_promises = require("node:fs/promises");
+//#region src/workspace/init.ts
+const WORKSPACE_DIRS = [
+	".chain-insights",
+	".chain-insights/schema",
+	".chain-insights/runtime",
+	".chain-insights/runtime/logs",
+	".chain-insights/runtime-skill",
+	"cases",
+	"imports",
+	"reports",
+	"reports/graphs",
+	"reports/tables",
+	"templates"
+];
+function todayIso() {
+	return (/* @__PURE__ */ new Date()).toISOString().slice(0, 10);
+}
+function workspaceJson(workspaceRoot) {
+	return JSON.stringify({
+		schema: "chain-insights.workspace.v1",
+		name: "Chain Insights Investigations",
+		workspace_root: workspaceRoot,
+		default_network: "bittensor",
+		graph_mcp_endpoint: "https://staging-mcp.chain-insights.ai/mcp",
+		cases_dir: "cases",
+		imports_dir: "imports",
+		reports_dir: "reports",
+		templates_dir: "templates",
+		created_at: todayIso()
+	}, null, 2) + "\n";
+}
+const README = `# Chain Insights Investigations
+
+This is a workspace for Chain Insights AML investigations.
+
+## Start
+
+\`\`\`bash
+chain-insights mcp tools --refresh
+chain-insights wallet balance
+\`\`\`
+
+## Layout
+
+\`\`\`text
+.chain-insights/   Workspace metadata
+cases/             Case exports and notes
+imports/           External reports, CSVs, screenshots, raw notes
+reports/           Final or interim analyst reports
+reports/graphs/    Graph JSON for visualization
+reports/tables/    Compact tabular extracts
+templates/         Reusable case/report templates
+.chain-insights/schema/         Runtime graph schema captures
+.chain-insights/runtime/        Workspace-local runtime process state and debug logs
+.chain-insights/runtime-skill/  Workspace-specific agent schema notes
+\`\`\`
+`;
+const AGENTS = `# Agent Instructions
+
+You are operating inside a Chain Insights investigation workspace.
+
+- Read README.md first.
+- If this directory is not initialized, run \`cia init .\` before investigation-producing commands.
+- Do not rerun init in an existing workspace unless replacing scaffolding with \`--force\`.
+- Read .chain-insights/runtime-skill/SKILL.md before graph queries.
+- Preserve full blockchain addresses exactly.
+- Do not guess the network for graph queries.
+- Capture or refresh graph schema before the first case query.
+- Save compact evidence with original graph field names.
+- Put canonical graph JSON in reports/graphs/ and analyst tables in reports/tables/.
+- Evidence files should summarize and point to graph/table outputs; do not paste large raw JSON blobs into evidence Markdown.
+- Investigation output must stay in this initialized workspace.
+- Never write cases, evidence, reports, graph JSON, HTML, schema captures, or logs to ~/.chain-insights.
+- Keep theories lightweight until evidence supports them.
+`;
+const CLAUDE = AGENTS;
+const CASE_BRIEF = `# Case Brief
+
+## Summary
+
+Status:
+Network:
+Current Assessment:
+
+## Known Addresses
+
+## Claims To Validate
+
+## Evidence
+
+## Next Steps
+`;
+const IMPORTS_README = `# External Investigation Inputs
+
+Put user-provided or third-party investigation material here before turning it
+into case evidence.
+
+Examples:
+
+- Exchange support exports
+- CSV extracts
+- Screenshots
+- Raw notes
+- Partner reports
+
+Files in this directory are inputs, not verified evidence. When an import
+supports a claim, summarize it into the case evidence manifest and reference
+the original file path.
+`;
+const TEMPLATES_README = `# Reusable Workspace Templates
+
+Store local report, case, prompt, and evidence templates here.
+
+Templates are optional workspace helpers. They are not evidence and should not
+be treated as case state until copied into a case, evidence file, dossier, or
+report.
+`;
+const RUNTIME_SKILL = `---
+name: chain-insights-runtime-schema
+description: Workspace-local Chain Insights runtime schema notes. Refresh this after connecting to a graph MCP endpoint.
+---
+
+# Runtime Graph Schema
+
+Before the first investigation query, capture the live graph schema into:
+
+\`\`\`text
+.chain-insights/schema/<network>.graph-schema.json
+\`\`\`
+
+Use \`graph_query_batch\` for schema capture. Prefix current topology reads
+with \`USE live_topology\`, historical topology reads with
+\`USE archive_topology\`, and fact reads with \`USE facts\`, for example:
+
+\`\`\`bash
+cia mcp call graph_query_batch network=<network> 'queries=[{"id":"node_labels","query":"USE live_topology MATCH (n:Address) RETURN \"Address\" AS node_label, count(n) AS sample_count LIMIT 1"},{"id":"archive_flow_sample","query":"USE archive_topology MATCH (:Address)-[f:FLOWS_TO]->(:Address) RETURN f.period_granularity AS granularity, f.amount_sum AS amount_sum LIMIT 20"}]'
+\`\`\`
+
+Then update this file with observed labels, relationship types, and allowed
+property names for the active network.
+
+Rules:
+
+- Prefer \`graph_query\` and \`graph_query_batch\` for graph-language reads.
+- Use \`USE live_topology\` for Memgraph RAM topology, \`USE archive_topology\`
+  for StarRocks historical topology, and \`USE facts\` for StarRocks fact
+  labels such as \`AddressLabel\`, \`AddressFeature\`,
+  \`RiskScore\`, and \`Asset\`. Address facts can be reached through
+  relationships such as \`(:Address)-[:HAS_FEATURE]->(:AddressFeature)\`.
+  Archived money-flow topology is exposed as
+  \`(:Address)-[:FLOWS_TO]->(:Address)\` with \`period_granularity\`,
+  \`period_start_date\`, and \`period_end_date\` on the relationship.
+- Preserve source schema field names in evidence and generated data files.
+- Do not rename, reinterpret, or add unit labels to graph fields unless the
+  schema or query result explicitly supports that interpretation.
+- Keep evidence compact: select only the fields needed to support the claim.
+  Avoid storing whole node or relationship property blobs in evidence unless
+  the purpose of the query is schema discovery or debugging.
+- Keep analysis products separate from evidence: graph JSON belongs under
+  \`reports/graphs/\`, tabular extracts under \`reports/tables/\`, and analyst
+  narrative under \`reports/\`.
+- Evidence Markdown should be a short provenance record with key facts and
+  pointers. Large JSON belongs in \`reports/tables/\`, not inline in evidence.
+`;
+const SCHEMA_README = `# Runtime Schema Captures
+
+Store graph schema captures here, for example:
+
+\`\`\`text
+bittensor.graph-schema.json
+\`\`\`
+
+Schema captures should be generated before the first case query in a fresh
+workspace, then referenced by evidence, reports, and runtime skill notes.
+`;
+function workspaceFiles(workspaceRoot) {
+	return [
+		[".chain-insights/workspace.json", workspaceJson(workspaceRoot)],
+		["README.md", README],
+		["AGENTS.md", AGENTS],
+		["CLAUDE.md", CLAUDE],
+		["imports/README.md", IMPORTS_README],
+		["templates/README.md", TEMPLATES_README],
+		["templates/case-brief.md", CASE_BRIEF],
+		[".chain-insights/runtime-skill/SKILL.md", RUNTIME_SKILL],
+		[".chain-insights/schema/README.md", SCHEMA_README],
+		[".chain-insights/runtime/.keep", ""],
+		[".chain-insights/runtime/logs/.keep", ""]
+	];
+}
+async function assertNoFileCollisions(workspaceRoot) {
+	for (const [relativePath] of workspaceFiles(workspaceRoot)) {
+		const filePath = node_path.default.join(workspaceRoot, relativePath);
+		try {
+			await (0, node_fs_promises.access)(filePath);
+			throw new Error(`Refusing to overwrite ${filePath}. Re-run with --force to replace workspace files.`);
+		} catch (err) {
+			if (err.code === "ENOENT") continue;
+			throw err;
+		}
+	}
+}
+async function initWorkspace(options) {
+	const workspaceRoot = node_path.default.resolve(options.targetDir);
+	if (!options.force) await assertNoFileCollisions(workspaceRoot);
+	for (const dir of WORKSPACE_DIRS) await (0, node_fs_promises.mkdir)(node_path.default.join(workspaceRoot, dir), { recursive: true });
+	const filesWritten = [];
+	const flag = options.force ? "w" : "wx";
+	for (const [relativePath, content] of workspaceFiles(workspaceRoot)) {
+		const filePath = node_path.default.join(workspaceRoot, relativePath);
+		try {
+			await (0, node_fs_promises.writeFile)(filePath, content, {
+				mode: 384,
+				flag
+			});
+			filesWritten.push(relativePath);
+		} catch (err) {
+			if (err.code === "EEXIST") throw new Error(`Refusing to overwrite ${filePath}. Re-run with --force to replace workspace files.`);
+			throw err;
+		}
+	}
+	return {
+		workspaceRoot,
+		filesWritten
+	};
+}
+//#endregion
+exports.initWorkspace = initWorkspace;

package/dist/init-CaOsHTIo.mjs

@@ -0,0 +1,232 @@
+import path from "node:path";
+import { access, mkdir, writeFile } from "node:fs/promises";
+//#region src/workspace/init.ts
+const WORKSPACE_DIRS = [
+	".chain-insights",
+	".chain-insights/schema",
+	".chain-insights/runtime",
+	".chain-insights/runtime/logs",
+	".chain-insights/runtime-skill",
+	"cases",
+	"imports",
+	"reports",
+	"reports/graphs",
+	"reports/tables",
+	"templates"
+];
+function todayIso() {
+	return (/* @__PURE__ */ new Date()).toISOString().slice(0, 10);
+}
+function workspaceJson(workspaceRoot) {
+	return JSON.stringify({
+		schema: "chain-insights.workspace.v1",
+		name: "Chain Insights Investigations",
+		workspace_root: workspaceRoot,
+		default_network: "bittensor",
+		graph_mcp_endpoint: "https://staging-mcp.chain-insights.ai/mcp",
+		cases_dir: "cases",
+		imports_dir: "imports",
+		reports_dir: "reports",
+		templates_dir: "templates",
+		created_at: todayIso()
+	}, null, 2) + "\n";
+}
+const README = `# Chain Insights Investigations
+
+This is a workspace for Chain Insights AML investigations.
+
+## Start
+
+\`\`\`bash
+chain-insights mcp tools --refresh
+chain-insights wallet balance
+\`\`\`
+
+## Layout
+
+\`\`\`text
+.chain-insights/   Workspace metadata
+cases/             Case exports and notes
+imports/           External reports, CSVs, screenshots, raw notes
+reports/           Final or interim analyst reports
+reports/graphs/    Graph JSON for visualization
+reports/tables/    Compact tabular extracts
+templates/         Reusable case/report templates
+.chain-insights/schema/         Runtime graph schema captures
+.chain-insights/runtime/        Workspace-local runtime process state and debug logs
+.chain-insights/runtime-skill/  Workspace-specific agent schema notes
+\`\`\`
+`;
+const AGENTS = `# Agent Instructions
+
+You are operating inside a Chain Insights investigation workspace.
+
+- Read README.md first.
+- If this directory is not initialized, run \`cia init .\` before investigation-producing commands.
+- Do not rerun init in an existing workspace unless replacing scaffolding with \`--force\`.
+- Read .chain-insights/runtime-skill/SKILL.md before graph queries.
+- Preserve full blockchain addresses exactly.
+- Do not guess the network for graph queries.
+- Capture or refresh graph schema before the first case query.
+- Save compact evidence with original graph field names.
+- Put canonical graph JSON in reports/graphs/ and analyst tables in reports/tables/.
+- Evidence files should summarize and point to graph/table outputs; do not paste large raw JSON blobs into evidence Markdown.
+- Investigation output must stay in this initialized workspace.
+- Never write cases, evidence, reports, graph JSON, HTML, schema captures, or logs to ~/.chain-insights.
+- Keep theories lightweight until evidence supports them.
+`;
+const CLAUDE = AGENTS;
+const CASE_BRIEF = `# Case Brief
+
+## Summary
+
+Status:
+Network:
+Current Assessment:
+
+## Known Addresses
+
+## Claims To Validate
+
+## Evidence
+
+## Next Steps
+`;
+const IMPORTS_README = `# External Investigation Inputs
+
+Put user-provided or third-party investigation material here before turning it
+into case evidence.
+
+Examples:
+
+- Exchange support exports
+- CSV extracts
+- Screenshots
+- Raw notes
+- Partner reports
+
+Files in this directory are inputs, not verified evidence. When an import
+supports a claim, summarize it into the case evidence manifest and reference
+the original file path.
+`;
+const TEMPLATES_README = `# Reusable Workspace Templates
+
+Store local report, case, prompt, and evidence templates here.
+
+Templates are optional workspace helpers. They are not evidence and should not
+be treated as case state until copied into a case, evidence file, dossier, or
+report.
+`;
+const RUNTIME_SKILL = `---
+name: chain-insights-runtime-schema
+description: Workspace-local Chain Insights runtime schema notes. Refresh this after connecting to a graph MCP endpoint.
+---
+
+# Runtime Graph Schema
+
+Before the first investigation query, capture the live graph schema into:
+
+\`\`\`text
+.chain-insights/schema/<network>.graph-schema.json
+\`\`\`
+
+Use \`graph_query_batch\` for schema capture. Prefix current topology reads
+with \`USE live_topology\`, historical topology reads with
+\`USE archive_topology\`, and fact reads with \`USE facts\`, for example:
+
+\`\`\`bash
+cia mcp call graph_query_batch network=<network> 'queries=[{"id":"node_labels","query":"USE live_topology MATCH (n:Address) RETURN \"Address\" AS node_label, count(n) AS sample_count LIMIT 1"},{"id":"archive_flow_sample","query":"USE archive_topology MATCH (:Address)-[f:FLOWS_TO]->(:Address) RETURN f.period_granularity AS granularity, f.amount_sum AS amount_sum LIMIT 20"}]'
+\`\`\`
+
+Then update this file with observed labels, relationship types, and allowed
+property names for the active network.
+
+Rules:
+
+- Prefer \`graph_query\` and \`graph_query_batch\` for graph-language reads.
+- Use \`USE live_topology\` for Memgraph RAM topology, \`USE archive_topology\`
+  for StarRocks historical topology, and \`USE facts\` for StarRocks fact
+  labels such as \`AddressLabel\`, \`AddressFeature\`,
+  \`RiskScore\`, and \`Asset\`. Address facts can be reached through
+  relationships such as \`(:Address)-[:HAS_FEATURE]->(:AddressFeature)\`.
+  Archived money-flow topology is exposed as
+  \`(:Address)-[:FLOWS_TO]->(:Address)\` with \`period_granularity\`,
+  \`period_start_date\`, and \`period_end_date\` on the relationship.
+- Preserve source schema field names in evidence and generated data files.
+- Do not rename, reinterpret, or add unit labels to graph fields unless the
+  schema or query result explicitly supports that interpretation.
+- Keep evidence compact: select only the fields needed to support the claim.
+  Avoid storing whole node or relationship property blobs in evidence unless
+  the purpose of the query is schema discovery or debugging.
+- Keep analysis products separate from evidence: graph JSON belongs under
+  \`reports/graphs/\`, tabular extracts under \`reports/tables/\`, and analyst
+  narrative under \`reports/\`.
+- Evidence Markdown should be a short provenance record with key facts and
+  pointers. Large JSON belongs in \`reports/tables/\`, not inline in evidence.
+`;
+const SCHEMA_README = `# Runtime Schema Captures
+
+Store graph schema captures here, for example:
+
+\`\`\`text
+bittensor.graph-schema.json
+\`\`\`
+
+Schema captures should be generated before the first case query in a fresh
+workspace, then referenced by evidence, reports, and runtime skill notes.
+`;
+function workspaceFiles(workspaceRoot) {
+	return [
+		[".chain-insights/workspace.json", workspaceJson(workspaceRoot)],
+		["README.md", README],
+		["AGENTS.md", AGENTS],
+		["CLAUDE.md", CLAUDE],
+		["imports/README.md", IMPORTS_README],
+		["templates/README.md", TEMPLATES_README],
+		["templates/case-brief.md", CASE_BRIEF],
+		[".chain-insights/runtime-skill/SKILL.md", RUNTIME_SKILL],
+		[".chain-insights/schema/README.md", SCHEMA_README],
+		[".chain-insights/runtime/.keep", ""],
+		[".chain-insights/runtime/logs/.keep", ""]
+	];
+}
+async function assertNoFileCollisions(workspaceRoot) {
+	for (const [relativePath] of workspaceFiles(workspaceRoot)) {
+		const filePath = path.join(workspaceRoot, relativePath);
+		try {
+			await access(filePath);
+			throw new Error(`Refusing to overwrite ${filePath}. Re-run with --force to replace workspace files.`);
+		} catch (err) {
+			if (err.code === "ENOENT") continue;
+			throw err;
+		}
+	}
+}
+async function initWorkspace(options) {
+	const workspaceRoot = path.resolve(options.targetDir);
+	if (!options.force) await assertNoFileCollisions(workspaceRoot);
+	for (const dir of WORKSPACE_DIRS) await mkdir(path.join(workspaceRoot, dir), { recursive: true });
+	const filesWritten = [];
+	const flag = options.force ? "w" : "wx";
+	for (const [relativePath, content] of workspaceFiles(workspaceRoot)) {
+		const filePath = path.join(workspaceRoot, relativePath);
+		try {
+			await writeFile(filePath, content, {
+				mode: 384,
+				flag
+			});
+			filesWritten.push(relativePath);
+		} catch (err) {
+			if (err.code === "EEXIST") throw new Error(`Refusing to overwrite ${filePath}. Re-run with --force to replace workspace files.`);
+			throw err;
+		}
+	}
+	return {
+		workspaceRoot,
+		filesWritten
+	};
+}
+//#endregion
+export { initWorkspace };
+
+//# sourceMappingURL=init-CaOsHTIo.mjs.map

package/dist/init-CaOsHTIo.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"init-CaOsHTIo.mjs","names":[],"sources":["../src/workspace/init.ts"],"sourcesContent":["import { access, mkdir, writeFile } from 'node:fs/promises'\nimport path from 'node:path'\n\nexport interface InitWorkspaceOptions {\n  targetDir: string\n  force?: boolean\n}\n\nexport interface InitWorkspaceResult {\n  workspaceRoot: string\n  filesWritten: string[]\n}\n\nconst WORKSPACE_DIRS = [\n  '.chain-insights',\n  '.chain-insights/schema',\n  '.chain-insights/runtime',\n  '.chain-insights/runtime/logs',\n  '.chain-insights/runtime-skill',\n  'cases',\n  'imports',\n  'reports',\n  'reports/graphs',\n  'reports/tables',\n  'templates',\n]\n\nfunction todayIso(): string {\n  return new Date().toISOString().slice(0, 10)\n}\n\nfunction workspaceJson(workspaceRoot: string): string {\n  return JSON.stringify({\n    schema: 'chain-insights.workspace.v1',\n    name: 'Chain Insights Investigations',\n    workspace_root: workspaceRoot,\n    default_network: 'bittensor',\n    graph_mcp_endpoint: 'https://staging-mcp.chain-insights.ai/mcp',\n    cases_dir: 'cases',\n    imports_dir: 'imports',\n    reports_dir: 'reports',\n    templates_dir: 'templates',\n    created_at: todayIso(),\n  }, null, 2) + '\\n'\n}\n\nconst README = `# Chain Insights Investigations\n\nThis is a workspace for Chain Insights AML investigations.\n\n## Start\n\n\\`\\`\\`bash\nchain-insights mcp tools --refresh\nchain-insights wallet balance\n\\`\\`\\`\n\n## Layout\n\n\\`\\`\\`text\n.chain-insights/   Workspace metadata\ncases/             Case exports and notes\nimports/           External reports, CSVs, screenshots, raw notes\nreports/           Final or interim analyst reports\nreports/graphs/    Graph JSON for visualization\nreports/tables/    Compact tabular extracts\ntemplates/         Reusable case/report templates\n.chain-insights/schema/         Runtime graph schema captures\n.chain-insights/runtime/        Workspace-local runtime process state and debug logs\n.chain-insights/runtime-skill/  Workspace-specific agent schema notes\n\\`\\`\\`\n`\n\nconst AGENTS = `# Agent Instructions\n\nYou are operating inside a Chain Insights investigation workspace.\n\n- Read README.md first.\n- If this directory is not initialized, run \\`cia init .\\` before investigation-producing commands.\n- Do not rerun init in an existing workspace unless replacing scaffolding with \\`--force\\`.\n- Read .chain-insights/runtime-skill/SKILL.md before graph queries.\n- Preserve full blockchain addresses exactly.\n- Do not guess the network for graph queries.\n- Capture or refresh graph schema before the first case query.\n- Save compact evidence with original graph field names.\n- Put canonical graph JSON in reports/graphs/ and analyst tables in reports/tables/.\n- Evidence files should summarize and point to graph/table outputs; do not paste large raw JSON blobs into evidence Markdown.\n- Investigation output must stay in this initialized workspace.\n- Never write cases, evidence, reports, graph JSON, HTML, schema captures, or logs to ~/.chain-insights.\n- Keep theories lightweight until evidence supports them.\n`\n\nconst CLAUDE = AGENTS\n\nconst CASE_BRIEF = `# Case Brief\n\n## Summary\n\nStatus:\nNetwork:\nCurrent Assessment:\n\n## Known Addresses\n\n## Claims To Validate\n\n## Evidence\n\n## Next Steps\n`\n\nconst IMPORTS_README = `# External Investigation Inputs\n\nPut user-provided or third-party investigation material here before turning it\ninto case evidence.\n\nExamples:\n\n- Exchange support exports\n- CSV extracts\n- Screenshots\n- Raw notes\n- Partner reports\n\nFiles in this directory are inputs, not verified evidence. When an import\nsupports a claim, summarize it into the case evidence manifest and reference\nthe original file path.\n`\n\nconst TEMPLATES_README = `# Reusable Workspace Templates\n\nStore local report, case, prompt, and evidence templates here.\n\nTemplates are optional workspace helpers. They are not evidence and should not\nbe treated as case state until copied into a case, evidence file, dossier, or\nreport.\n`\n\nconst RUNTIME_SKILL = `---\nname: chain-insights-runtime-schema\ndescription: Workspace-local Chain Insights runtime schema notes. Refresh this after connecting to a graph MCP endpoint.\n---\n\n# Runtime Graph Schema\n\nBefore the first investigation query, capture the live graph schema into:\n\n\\`\\`\\`text\n.chain-insights/schema/<network>.graph-schema.json\n\\`\\`\\`\n\nUse \\`graph_query_batch\\` for schema capture. Prefix current topology reads\nwith \\`USE live_topology\\`, historical topology reads with\n\\`USE archive_topology\\`, and fact reads with \\`USE facts\\`, for example:\n\n\\`\\`\\`bash\ncia mcp call graph_query_batch network=<network> 'queries=[{\"id\":\"node_labels\",\"query\":\"USE live_topology MATCH (n:Address) RETURN \\\"Address\\\" AS node_label, count(n) AS sample_count LIMIT 1\"},{\"id\":\"archive_flow_sample\",\"query\":\"USE archive_topology MATCH (:Address)-[f:FLOWS_TO]->(:Address) RETURN f.period_granularity AS granularity, f.amount_sum AS amount_sum LIMIT 20\"}]'\n\\`\\`\\`\n\nThen update this file with observed labels, relationship types, and allowed\nproperty names for the active network.\n\nRules:\n\n- Prefer \\`graph_query\\` and \\`graph_query_batch\\` for graph-language reads.\n- Use \\`USE live_topology\\` for Memgraph RAM topology, \\`USE archive_topology\\`\n  for StarRocks historical topology, and \\`USE facts\\` for StarRocks fact\n  labels such as \\`AddressLabel\\`, \\`AddressFeature\\`,\n  \\`RiskScore\\`, and \\`Asset\\`. Address facts can be reached through\n  relationships such as \\`(:Address)-[:HAS_FEATURE]->(:AddressFeature)\\`.\n  Archived money-flow topology is exposed as\n  \\`(:Address)-[:FLOWS_TO]->(:Address)\\` with \\`period_granularity\\`,\n  \\`period_start_date\\`, and \\`period_end_date\\` on the relationship.\n- Preserve source schema field names in evidence and generated data files.\n- Do not rename, reinterpret, or add unit labels to graph fields unless the\n  schema or query result explicitly supports that interpretation.\n- Keep evidence compact: select only the fields needed to support the claim.\n  Avoid storing whole node or relationship property blobs in evidence unless\n  the purpose of the query is schema discovery or debugging.\n- Keep analysis products separate from evidence: graph JSON belongs under\n  \\`reports/graphs/\\`, tabular extracts under \\`reports/tables/\\`, and analyst\n  narrative under \\`reports/\\`.\n- Evidence Markdown should be a short provenance record with key facts and\n  pointers. Large JSON belongs in \\`reports/tables/\\`, not inline in evidence.\n`\n\nconst SCHEMA_README = `# Runtime Schema Captures\n\nStore graph schema captures here, for example:\n\n\\`\\`\\`text\nbittensor.graph-schema.json\n\\`\\`\\`\n\nSchema captures should be generated before the first case query in a fresh\nworkspace, then referenced by evidence, reports, and runtime skill notes.\n`\n\nfunction workspaceFiles(workspaceRoot: string): Array<[string, string]> {\n  return [\n    ['.chain-insights/workspace.json', workspaceJson(workspaceRoot)],\n    ['README.md', README],\n    ['AGENTS.md', AGENTS],\n    ['CLAUDE.md', CLAUDE],\n    ['imports/README.md', IMPORTS_README],\n    ['templates/README.md', TEMPLATES_README],\n    ['templates/case-brief.md', CASE_BRIEF],\n    ['.chain-insights/runtime-skill/SKILL.md', RUNTIME_SKILL],\n    ['.chain-insights/schema/README.md', SCHEMA_README],\n    ['.chain-insights/runtime/.keep', ''],\n    ['.chain-insights/runtime/logs/.keep', ''],\n  ]\n}\n\nasync function assertNoFileCollisions(workspaceRoot: string): Promise<void> {\n  for (const [relativePath] of workspaceFiles(workspaceRoot)) {\n    const filePath = path.join(workspaceRoot, relativePath)\n    try {\n      await access(filePath)\n      throw new Error(`Refusing to overwrite ${filePath}. Re-run with --force to replace workspace files.`)\n    } catch (err) {\n      if ((err as NodeJS.ErrnoException).code === 'ENOENT') {\n        continue\n      }\n      throw err\n    }\n  }\n}\n\nexport async function initWorkspace(options: InitWorkspaceOptions): Promise<InitWorkspaceResult> {\n  const workspaceRoot = path.resolve(options.targetDir)\n  if (!options.force) {\n    await assertNoFileCollisions(workspaceRoot)\n  }\n\n  for (const dir of WORKSPACE_DIRS) {\n    await mkdir(path.join(workspaceRoot, dir), { recursive: true })\n  }\n\n  const filesWritten: string[] = []\n  const flag = options.force ? 'w' : 'wx'\n  for (const [relativePath, content] of workspaceFiles(workspaceRoot)) {\n    const filePath = path.join(workspaceRoot, relativePath)\n    try {\n      await writeFile(filePath, content, { mode: 0o600, flag })\n      filesWritten.push(relativePath)\n    } catch (err) {\n      if ((err as NodeJS.ErrnoException).code === 'EEXIST') {\n        throw new Error(`Refusing to overwrite ${filePath}. Re-run with --force to replace workspace files.`)\n      }\n      throw err\n    }\n  }\n\n  return { workspaceRoot, filesWritten }\n}\n"],"mappings":";;;AAaA,MAAM,iBAAiB;CACrB;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACD;AAED,SAAS,WAAmB;AAC1B,yBAAO,IAAI,MAAM,EAAC,aAAa,CAAC,MAAM,GAAG,GAAG;;AAG9C,SAAS,cAAc,eAA+B;AACpD,QAAO,KAAK,UAAU;EACpB,QAAQ;EACR,MAAM;EACN,gBAAgB;EAChB,iBAAiB;EACjB,oBAAoB;EACpB,WAAW;EACX,aAAa;EACb,aAAa;EACb,eAAe;EACf,YAAY,UAAU;EACvB,EAAE,MAAM,EAAE,GAAG;;AAGhB,MAAM,SAAS;;;;;;;;;;;;;;;;;;;;;;;;;;AA2Bf,MAAM,SAAS;;;;;;;;;;;;;;;;;;AAmBf,MAAM,SAAS;AAEf,MAAM,aAAa;;;;;;;;;;;;;;;;AAiBnB,MAAM,iBAAiB;;;;;;;;;;;;;;;;;AAkBvB,MAAM,mBAAmB;;;;;;;;AASzB,MAAM,gBAAgB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAgDtB,MAAM,gBAAgB;;;;;;;;;;;AAYtB,SAAS,eAAe,eAAgD;AACtE,QAAO;EACL,CAAC,kCAAkC,cAAc,cAAc,CAAC;EAChE,CAAC,aAAa,OAAO;EACrB,CAAC,aAAa,OAAO;EACrB,CAAC,aAAa,OAAO;EACrB,CAAC,qBAAqB,eAAe;EACrC,CAAC,uBAAuB,iBAAiB;EACzC,CAAC,2BAA2B,WAAW;EACvC,CAAC,0CAA0C,cAAc;EACzD,CAAC,oCAAoC,cAAc;EACnD,CAAC,iCAAiC,GAAG;EACrC,CAAC,sCAAsC,GAAG;EAC3C;;AAGH,eAAe,uBAAuB,eAAsC;AAC1E,MAAK,MAAM,CAAC,iBAAiB,eAAe,cAAc,EAAE;EAC1D,MAAM,WAAW,KAAK,KAAK,eAAe,aAAa;AACvD,MAAI;AACF,SAAM,OAAO,SAAS;AACtB,SAAM,IAAI,MAAM,yBAAyB,SAAS,mDAAmD;WAC9F,KAAK;AACZ,OAAK,IAA8B,SAAS,SAC1C;AAEF,SAAM;;;;AAKZ,eAAsB,cAAc,SAA6D;CAC/F,MAAM,gBAAgB,KAAK,QAAQ,QAAQ,UAAU;AACrD,KAAI,CAAC,QAAQ,MACX,OAAM,uBAAuB,cAAc;AAG7C,MAAK,MAAM,OAAO,eAChB,OAAM,MAAM,KAAK,KAAK,eAAe,IAAI,EAAE,EAAE,WAAW,MAAM,CAAC;CAGjE,MAAM,eAAyB,EAAE;CACjC,MAAM,OAAO,QAAQ,QAAQ,MAAM;AACnC,MAAK,MAAM,CAAC,cAAc,YAAY,eAAe,cAAc,EAAE;EACnE,MAAM,WAAW,KAAK,KAAK,eAAe,aAAa;AACvD,MAAI;AACF,SAAM,UAAU,UAAU,SAAS;IAAE,MAAM;IAAO;IAAM,CAAC;AACzD,gBAAa,KAAK,aAAa;WACxB,KAAK;AACZ,OAAK,IAA8B,SAAS,SAC1C,OAAM,IAAI,MAAM,yBAAyB,SAAS,mDAAmD;AAEvG,SAAM;;;AAIV,QAAO;EAAE;EAAe;EAAc"}