@dotdotgod/claude-code 0.6.6 → 0.7.0

package/mcp/server.mjs

@@ -23310,7 +23310,6 @@ async function projectInitialize(input) {
   if (dryRun) args.push("--dry-run");
   if (input.projectName) args.push("--project-name", input.projectName);
   if (input.template) args.push("--template", input.template);
-  if (input.dotdotSetting) args.push("--dotdot-setting");
   return await cliJson(args, root2);
 }
 
@@ -23545,7 +23544,7 @@ function getJobs() {
   jobRunner ??= new IngestionJobRunner(getStore());
   return jobRunner;
 }
-var server = new McpServer({ name: "dotdotgod-context", version: "0.6.6" });
+var server = new McpServer({ name: "dotdotgod-context", version: "0.7.0" });
 var scopeSchema = external_exports.enum(["transient", "session", "project"]).optional();
 var outputModeSchema = external_exports.enum(["auto", "direct", "indexed", "discard"]).optional();
 var commandSchema = {
@@ -23702,8 +23701,7 @@ register("project_initialize", "Initialize project memory; dry-run is default an
   dryRun: external_exports.boolean().optional(),
   confirmWrite: external_exports.boolean().optional(),
   projectName: external_exports.string().optional(),
-  template: external_exports.string().optional(),
-  dotdotSetting: external_exports.boolean().optional()
+  template: external_exports.string().optional()
 }, (input) => projectInitialize(projectInput(input)), { destructiveHint: true });
 async function startServer() {
   await server.connect(new StdioServerTransport());

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dotdotgod/claude-code",
-  "version": "0.6.6",
+  "version": "0.7.0",
   "description": "Claude Code adapter for dotdotgod project memory workflows.",
   "type": "module",
   "license": "Elastic-2.0",
@@ -25,7 +25,7 @@
   },
   "devDependencies": {
     "esbuild": "0.27.3",
-    "@dotdotgod/context": "0.6.6"
+    "@dotdotgod/context": "0.7.0"
   },
   "files": [
     ".claude-plugin",

package/skills/project-initializer/scripts/init_project.sh

@@ -6,15 +6,13 @@ TEMPLATES_DIR="$SCRIPT_DIR/../templates"
 
 usage() {
   cat <<'EOF'
-Usage: init_project.sh <project-root> [--project-name NAME] [--template NAME] [--documentation-root PATH] [--dotdot-setting] [--dry-run]
+Usage: init_project.sh <project-root> [--project-name NAME] [--template NAME] [--documentation-root PATH] [--dry-run]
 
 Initializes:
   AGENTS.md, CLAUDE.md, CODEX.md
   dotdotgod.config.json
   docs/README.md
-  docs/spec/README.md
-  docs/test/README.md
-  docs/arch/README.md
+  Template-specific domain indexes (spec/arch/test only for software and research)
   docs/plan/README.md
   docs/archive/README.md
   .gitignore entries for docs/plan, docs/archive, and .dotdotgod
@@ -24,7 +22,6 @@ EOF
 PROJECT_ROOT=""
 PROJECT_NAME=""
 DRY_RUN=0
-DOTDOT_SETTING=0
 TEMPLATE_NAME="software"
 DOCUMENTATION_ROOT="docs"
 
@@ -51,10 +48,6 @@ while [ "$#" -gt 0 ]; do
       DOCUMENTATION_ROOT=$2
       shift 2
       ;;
-    --dotdot-setting)
-      DOTDOT_SETTING=1
-      shift
-      ;;
     --dry-run)
       DRY_RUN=1
       shift
@@ -195,21 +188,11 @@ if [ "$DRY_RUN" -ne 1 ]; then
   mkdir -p "$PROJECT_ROOT"
 fi
 
-DOTDOT_AGENT_RULE=""
-if [ "$DOTDOT_SETTING" -eq 1 ]; then
-  DOTDOT_AGENT_RULE='
-- Follow the project documentation structure in `$DOCUMENTATION_ROOT/arch/DOCS_STRUCTURE.md` and code conventions in `$DOCUMENTATION_ROOT/arch/CODE_CONVENTIONS.md`.'
-fi
-
-ARCH_README_EXTRA=""
-if [ "$DOTDOT_SETTING" -eq 1 ]; then
-  ARCH_README_EXTRA='
-
-## Index
-
-- `DOCS_STRUCTURE.md`: documentation layout, naming, README index, spec current-state writing contract, and domain directory promotion rules.
-- `CODE_CONVENTIONS.md`: dotdot code conventions, including abstraction boundaries, source file size guidance, impact hotspot handling, and extraction/testability rules. If conventions grow across multiple topics, promote them to `conventions/README.md` with supporting UPPER_SNAKE_CASE files.'
+DOMAIN_MAP=""
+if [ ! -e "$CONFIG_PATH" ]; then
+  DOMAIN_MAP=$(cat "$TEMPLATES_DIR/$TEMPLATE_NAME.map.md")
 fi
+DOMAIN_MAP=$(printf '%s' "$DOMAIN_MAP" | sed "s#\`docs/#\`$DOCUMENTATION_ROOT/#g")
 
 write_file "$PROJECT_ROOT/AGENTS.md" "# AGENTS.md
 
@@ -228,7 +211,7 @@ Canonical instructions for AI coding agents working in this repository.
 - Preserve user edits and unrelated dirty worktree changes.
 - Prefer existing local patterns over introducing new abstractions.
 - Update docs when behavior, architecture, or test strategy changes.
-- When using the dotdotgod CLI, run \`dotdotgod validate\` after docs changes and follow its traceability guidance for behavior specs.$DOTDOT_AGENT_RULE
+- When using the dotdotgod CLI, run \`dotdotgod validate\` after docs changes and follow its traceability guidance.
 
 ## dotdotgod
 
@@ -253,15 +236,12 @@ TODO
 
 ## Documentation Map
 
-- \`$DOCUMENTATION_ROOT/spec/\`: product behavior, API contracts, user-facing requirements.
-- \`$DOCUMENTATION_ROOT/test/\`: test strategy, regression cases, manual verification notes.
-- \`$DOCUMENTATION_ROOT/arch/\`: architecture decisions, code conventions, module boundaries, data flow, infrastructure/runtime dependencies, integration boundaries, and migration design.
+$DOMAIN_MAP
 - \`$DOCUMENTATION_ROOT/\`: all directories use kebab-case; all markdown file names use UPPER_SNAKE_CASE, including \`README.md\`.
 - \`$DOCUMENTATION_ROOT/\`: prefer keeping individual markdown files under 200 lines and under 10,000 characters; split larger docs into focused UPPER_SNAKE_CASE files and keep \`README.md\` as the index/overview.
 - \`$DOCUMENTATION_ROOT/\`: when adding, renaming, splitting, moving, or archiving docs, update the nearest relevant \`README.md\` index/table of contents in the same change.
 - \`$DOCUMENTATION_ROOT/\`: each docs subdirectory \`README.md\` acts as the local table of contents; list important files, task directories, status, and a one-line purpose for each entry.
 - \`$DOCUMENTATION_ROOT/\`: start small with a single focused markdown file; when one domain grows into multiple docs, promote it to \`$DOCUMENTATION_ROOT/<area>/<domain>/README.md\` plus related UPPER_SNAKE_CASE files in that directory.
-- \`$DOCUMENTATION_ROOT/arch/\`: code conventions may start as \`CODE_CONVENTIONS.md\`; when they grow across multiple topics, use \`$DOCUMENTATION_ROOT/arch/conventions/README.md\` as the index with supporting UPPER_SNAKE_CASE files.
 - \`$DOCUMENTATION_ROOT/plan/\`: local active implementation plans. Create one kebab-case directory per task (\`$DOCUMENTATION_ROOT/plan/<task-slug>/\`), keep the task overview/index in that directory's \`README.md\`, and add supporting UPPER_SNAKE_CASE plan files alongside it. Ignored by git by default.
 - \`$DOCUMENTATION_ROOT/archive/\`: local completed plans, temporary reports, historical notes, payload captures. Move completed plan task directories to \`$DOCUMENTATION_ROOT/archive/plan/<task-slug>/\`; put temporary reports and investigations under \`$DOCUMENTATION_ROOT/archive/report/<report-slug>/\`. Ignored by git by default.
 
@@ -298,111 +278,10 @@ This directory keeps project knowledge close to the code.
 
 ## Map
 
-- \`spec/\`: product behavior, API contracts, user-facing requirements.
-- \`test/\`: test strategy, regression cases, manual verification notes.
-- \`arch/\`: architecture decisions, code conventions, module boundaries, data flow, infrastructure/runtime dependencies, integration boundaries, and migration design.
+$(printf '%s' "$DOMAIN_MAP" | sed "s#\`$DOCUMENTATION_ROOT/#\`#g")
 - \`plan/\`: local active implementation plans. Create one kebab-case directory per task (\`plan/<task-slug>/\`), keep the task overview/index in that directory's \`README.md\`, and add supporting UPPER_SNAKE_CASE plan files alongside it. Ignored by git by default.
 - \`archive/\`: local completed plans, temporary reports, historical notes, payload captures. Move completed plan task directories to \`archive/plan/<task-slug>/\`; put temporary reports and investigations under \`archive/report/<report-slug>/\`. Ignored by git by default."
 
-write_file "$PROJECT_ROOT/$DOCUMENTATION_ROOT/spec/README.md" "# Specs
-
-Use this area for behavior specs, API contracts, and product requirements.
-
-For projects using the dotdotgod CLI, behavior specs may be required by \`dotdotgod validate\` to include fenced \`json dotdotgod\` traceability blocks as the final section. The CLI owns the schema and prints property-level repair guidance when validation fails."
-
-write_file "$PROJECT_ROOT/$DOCUMENTATION_ROOT/test/README.md" "# Tests
-
-Use this area for test strategy, coverage notes, regression cases, and manual verification records."
-
-write_file "$PROJECT_ROOT/$DOCUMENTATION_ROOT/arch/README.md" "# Architecture
-
-Use this area for architecture decisions, code conventions, module boundaries, data flow notes, infrastructure/runtime dependencies, integration boundaries, and migration design.$ARCH_README_EXTRA"
-
-if [ "$DOTDOT_SETTING" -eq 1 ]; then
-  write_file "$PROJECT_ROOT/$DOCUMENTATION_ROOT/arch/DOCS_STRUCTURE.md" "# Docs Structure
-
-Long-term documentation structure for this project.
-
-## Top-Level Areas
-
-- \`$DOCUMENTATION_ROOT/spec/\`: product behavior, API contracts, user-facing requirements, and feature contracts.
-- \`$DOCUMENTATION_ROOT/test/\`: test strategy, coverage notes, regression cases, and manual verification records.
-- \`$DOCUMENTATION_ROOT/arch/\`: architecture decisions, code conventions, module boundaries, data flow, infrastructure/runtime dependencies, integration boundaries, and migration design.
-- \`$DOCUMENTATION_ROOT/plan/\`: local active implementation plans.
-- \`$DOCUMENTATION_ROOT/archive/\`: local completed plans, historical notes, payload captures, and investigation notes.
-
-## Naming
-
-- Directories under \`$DOCUMENTATION_ROOT/\` use kebab-case.
-- Markdown files under \`$DOCUMENTATION_ROOT/\` use UPPER_SNAKE_CASE.
-- \`README.md\` is the only mixed-case markdown filename exception and is required for index/overview files.
-
-## File Size Guideline
-
-Prefer keeping individual markdown files under 200 lines and 10,000 characters. When either guideline is exceeded, split the document into focused UPPER_SNAKE_CASE files and keep \`README.md\` as the index/overview. Configured validation exceptions should stay narrow and intentional.
-
-## README Indexes
-
-Each docs subdirectory \`README.md\` acts as the local table of contents. It should list important files, task directories, status, and a one-line purpose for each entry.
-
-When adding, renaming, splitting, moving, or archiving docs, update the nearest relevant \`README.md\` in the same change.
-
-## Domain Directory Promotion
-
-Start small with one focused markdown file. When one domain grows into multiple docs, promote it to \`$DOCUMENTATION_ROOT/<area>/<domain>/README.md\` and place related UPPER_SNAKE_CASE markdown files in that directory.
-
-## Spec Writing Contract
-
-Behavior specs describe the current product contract: supported commands, API shapes, user-visible behavior, defaults, constraints, and validation outcomes.
-
-Specs should not describe how behavior changed over time. Rewrite historical-change wording into direct current-state rules. Historical context, migration rationale, future extension ideas, and completed-plan notes belong in \`$DOCUMENTATION_ROOT/arch/\`, \`$DOCUMENTATION_ROOT/test/\`, \`$DOCUMENTATION_ROOT/archive/\`, or active \`$DOCUMENTATION_ROOT/plan/\` files rather than behavior specs. If compatibility behavior is still user-visible, keep it in the spec but phrase it as a current supported or unsupported rule.
-
-Config/action terms such as \`remove\`, \`exclude\`, \`fallback\`, and \`replacement semantics\` are allowed when they name current behavior precisely.
-
-## Traceability Blocks
-
-Behavior specs may include fenced \`json dotdotgod\` traceability blocks as the final section to connect specs to source, tests, related docs, and verification commands. The dotdotgod CLI owns the schema and validation behavior.
-
-## Plan and Archive Directories
-
-Active task plans use \`$DOCUMENTATION_ROOT/plan/<task-slug>/README.md\`. Completed or superseded plan task directories move to \`$DOCUMENTATION_ROOT/archive/plan/<task-slug>/\`. Temporary investigations, reports, payload captures, and historical notes move to \`$DOCUMENTATION_ROOT/archive/report/<report-slug>/\`.
-
-\`$DOCUMENTATION_ROOT/plan\` and \`$DOCUMENTATION_ROOT/archive\` are ignored by git by default.
-"
-
-  write_file "$PROJECT_ROOT/$DOCUMENTATION_ROOT/arch/CODE_CONVENTIONS.md" "# Code Conventions
-
-Dotdot code conventions for keeping implementation simple and maintainable.
-
-## Abstraction Boundaries
-
-- Do not introduce unnecessary abstractions.
-- Do not abstract code that is not reused.
-- Do not abstract reused code when the reused behavior is likely to split into separate features or flows later.
-- Prefer local, explicit code until a stable reuse pattern appears.
-
-## Source File Size
-
-- Keep source files small enough to read in one focused pass by humans and coding agents.
-- If code grows beyond 150 lines, consider splitting or extracting focused units even when it is not reused.
-- Review files approaching 250 lines for focused extraction by responsibility.
-- Split by behavior or responsibility, not by arbitrary layers.
-
-## Dotdotgod Impact Hotspots
-
-- Treat repeated \`dotdotgod graph impact\` results that collapse onto one large file as a design signal, not as normal precision.
-- Dotdotgod impact reveals mixed-responsibility hotspots; it does not replace focused module boundaries.
-- When unrelated changes keep pointing to the same source file, split the file by behavior so impact results, tests, and docs can map to narrower responsibilities.
-
-## Extraction and Testability
-
-- Prefer extracting pure helpers when behavior can be tested without runtime dependencies.
-- Keep runtime integration explicit and local until reuse is stable.
-- Put testable logic in focused modules before adding broad framework abstractions.
-- Preserve plain-text readability: avoid dense clever code, hidden control flow, and large mixed-responsibility files.
-"
-fi
-
 write_file "$PROJECT_ROOT/$DOCUMENTATION_ROOT/plan/README.md" "# Plans
 
 Use this area for active implementation plans.
@@ -441,6 +320,19 @@ Use this area for local completed plans, temporary reports, historical notes, pa
 This directory is local-only and ignored by git by default."
 
 if [ ! -e "$CONFIG_PATH" ]; then
+case "$TEMPLATE_NAME" in
+  software|research)
+    write_file "$PROJECT_ROOT/$DOCUMENTATION_ROOT/spec/README.md" "# Specs
+
+Use this area for behavior specs, API contracts, and requirements. Follow \`dotdotgod validate\` traceability guidance for applicable documents."
+    write_file "$PROJECT_ROOT/$DOCUMENTATION_ROOT/arch/README.md" "# Architecture
+
+Use this area for architecture decisions, design rationale, conventions, and integration boundaries."
+    write_file "$PROJECT_ROOT/$DOCUMENTATION_ROOT/test/README.md" "# Verification
+
+Use this area for test strategy, evaluation methods, regression cases, and verification records."
+    ;;
+esac
 case "$TEMPLATE_NAME" in
   software)
     ;;

package/skills/project-initializer/templates/case-and-evidence.map.md

@@ -0,0 +1,3 @@
+- `docs/case/`: Use this area for canonical case facts, questions, and decisions.
+- `docs/evidence/`: Use this area for factual, legal, and other supporting evidence.
+- `docs/outputs/`: Use this area for maintained case outputs.

package/skills/project-initializer/templates/policy.map.md

@@ -0,0 +1,4 @@
+- `docs/policy/`: Use this area for integrated policy proposals and outputs.
+- `docs/sections/`: Use this area for source policy sections.
+- `docs/evidence/`: Use this area for evidence supporting policy proposals.
+- `docs/outputs/`: Use this area for maintained policy submission outputs.

package/skills/project-initializer/templates/portfolio.map.md

@@ -0,0 +1,4 @@
+- `docs/strategy/`: Use this area for portfolio strategy and risk rules.
+- `docs/positions/`: Use this area for position theses and investment conclusions.
+- `docs/journal/`: Use this area for dated investment decisions and reviews.
+- `docs/report/`: Use this area for maintained market research and analysis.

package/skills/project-initializer/templates/publication.map.md

@@ -0,0 +1,4 @@
+- `docs/outline/`: Use this area for publication structure and outlines.
+- `docs/chapters/`: Use this area for chapter plans and direction.
+- `docs/claims/`: Use this area for maintained claims and their support.
+- `docs/research/`: Use this area for research sources and supporting notes.

package/skills/project-initializer/templates/research.map.md

@@ -0,0 +1,6 @@
+- `docs/spec/`: Use this area for behavior specs, API contracts, and requirements. Follow `dotdotgod validate` traceability guidance for applicable documents.
+- `docs/arch/`: Use this area for architecture decisions, design rationale, conventions, and integration boundaries.
+- `docs/test/`: Use this area for test strategy, evaluation methods, regression cases, and verification records.
+- `docs/research/`: Use this area for research notes, sources, and findings.
+- `docs/record/`: Use this area for dated measurements, experiments, and execution records.
+- `docs/report/`: Use this area for research diagnoses, analyses, results, and performance reports.

package/skills/project-initializer/templates/software.map.md

@@ -0,0 +1,3 @@
+- `docs/spec/`: Use this area for behavior specs, API contracts, and requirements. Follow `dotdotgod validate` traceability guidance for applicable documents.
+- `docs/arch/`: Use this area for architecture decisions, design rationale, conventions, and integration boundaries.
+- `docs/test/`: Use this area for test strategy, evaluation methods, regression cases, and verification records.