@auto-engineer/server-implementer 0.6.0 → 0.6.2

package/.turbo/turbo-build.log

@@ -1,5 +1,5 @@
 
-> @auto-engineer/server-implementer@0.6.0 build /Users/sam/WebstormProjects/top/auto-engineer/packages/server-implementer
+> @auto-engineer/server-implementer@0.6.1 build /Users/sam/WebstormProjects/top/auto-engineer/packages/server-implementer
 > tsc && tsx ../../scripts/fix-esm-imports.ts
 
 Fixed ESM imports in dist/

package/.turbo/turbo-format.log

@@ -1,19 +1,20 @@
-
-> @auto-engineer/server-implementer@0.5.1 format /Users/sam/WebstormProjects/top/auto-engineer/packages/server-implementer
-> prettier --write "**/*.{js,ts,json,md,yml,yaml}" --ignore-path ../../.prettierignore
-
-CHANGELOG.md 26ms (unchanged)
-DEBUG.md 4ms (unchanged)
-package.json 19ms (unchanged)
-README.md 68ms (unchanged)
-src/agent/runAllSlices.ts 4ms (unchanged)
-src/agent/runFlows.ts 5ms (unchanged)
-src/agent/runSlice.ts 37ms (unchanged)
-src/agent/runTests.ts 9ms (unchanged)
-src/cli-manifest.ts 2ms (unchanged)
-src/commands/implement-server.ts 5ms (unchanged)
-src/commands/implement-slice.ts 12ms (unchanged)
-src/index.ts 2ms (unchanged)
-src/prompts/systemPrompt.ts 1ms (unchanged)
-src/utils/extractCodeBlock.ts 1ms (unchanged)
-tsconfig.json 2ms (unchanged)
+
+
+> @auto-engineer/server-implementer@0.6.1 format /Users/sam/WebstormProjects/top/auto-engineer/packages/server-implementer
+> prettier --write "**/*.{js,ts,json,md,yml,yaml}" --ignore-path ../../.prettierignore
+
+CHANGELOG.mdCHANGELOG.md 27ms (unchanged)
+DEBUG.mdDEBUG.md 5ms (unchanged)
+package.jsonpackage.json 17ms (unchanged)
+README.mdREADME.md 75ms (unchanged)
+src/agent/runAllSlices.tssrc/agent/runAllSlices.ts 4ms (unchanged)
+src/agent/runFlows.tssrc/agent/runFlows.ts 5ms (unchanged)
+src/agent/runSlice.tssrc/agent/runSlice.ts 37ms (unchanged)
+src/agent/runTests.tssrc/agent/runTests.ts 13ms (unchanged)
+src/cli-manifest.tssrc/cli-manifest.ts 1ms (unchanged)
+src/commands/implement-server.tssrc/commands/implement-server.ts 9ms (unchanged)
+src/commands/implement-slice.tssrc/commands/implement-slice.ts 14ms (unchanged)
+src/index.tssrc/index.ts 1ms (unchanged)
+src/prompts/systemPrompt.tssrc/prompts/systemPrompt.ts 1ms (unchanged)
+src/utils/extractCodeBlock.tssrc/utils/extractCodeBlock.ts 1ms (unchanged)
+tsconfig.jsontsconfig.json 4ms (unchanged)

package/.turbo/turbo-lint.log

@@ -1,4 +1,5 @@
-
-> @auto-engineer/server-implementer@0.5.1 lint /Users/sam/WebstormProjects/top/auto-engineer/packages/server-implementer
-> eslint 'src/**/*.ts' --max-warnings 0 --config ../../eslint.config.ts
-
+
+
+> @auto-engineer/server-implementer@0.6.1 lint /Users/sam/WebstormProjects/top/auto-engineer/packages/server-implementer
+> eslint 'src/**/*.ts' --max-warnings 0 --config ../../eslint.config.ts
+

package/.turbo/turbo-test.log

@@ -1,5 +1,5 @@
 
-> @auto-engineer/server-implementer@0.5.1 test /Users/sam/WebstormProjects/top/auto-engineer/packages/server-implementer
+> @auto-engineer/server-implementer@0.6.2 test /Users/sam/WebstormProjects/top/auto-engineer/packages/server-implementer
 > vitest run
 
 

package/.turbo/turbo-type-check.log

@@ -1,4 +1,4 @@
 
-> @auto-engineer/server-implementer@0.5.1 type-check /Users/sam/WebstormProjects/top/auto-engineer/packages/server-implementer
+> @auto-engineer/server-implementer@0.6.2 type-check /Users/sam/WebstormProjects/top/auto-engineer/packages/server-implementer
 > tsc --noEmit
 

package/CHANGELOG.md

@@ -1,5 +1,23 @@
 # @auto-engineer/server-implementer
 
+## 0.6.2
+
+### Patch Changes
+
+- renamed packages
+- Updated dependencies
+  - @auto-engineer/message-bus@0.5.2
+  - @auto-engineer/ai-gateway@0.6.2
+
+## 0.6.1
+
+### Patch Changes
+
+- version bump for testihng
+- Updated dependencies
+  - @auto-engineer/ai-gateway@0.6.1
+  - @auto-engineer/message-bus@0.5.1
+
 ## 0.6.0
 
 ### Minor Changes

package/README.md

@@ -33,7 +33,7 @@ This plugin provides the following commands:
 
 ## What does this plugin do?
 
-The Server Implementer uses AI capabilities to implement business logic, database operations, and integration code for backend services. It bridges the gap between generated code scaffolds and functional implementations.
+The Server Implementer uses AI capabilities to implement business logic, database operations, and integration code for server services. It bridges the gap between generated code scaffolds and functional implementations.
 
 ## Key Features
 
@@ -227,9 +227,9 @@ export default {
 
 Works with the Auto Engineer ecosystem:
 
-- **@auto-engineer/emmett-generator**: Implements generated command handlers and queries
-- **@auto-engineer/backend-checks**: Validates implementations pass type checking and tests
-- **@auto-engineer/flowlang**: Uses flow specifications to understand business requirements
+- **@auto-engineer/server-generator-apollo-emmett**: Implements generated command handlers and queries
+- **@auto-engineer/server-checks**: Validates implementations pass type checking and tests
+- **@auto-engineer/flow**: Uses flow specifications to understand business requirements
 - **@auto-engineer/ai-gateway**: Leverages AI models for intelligent code generation
 
 ## Quality Assurance
@@ -261,4 +261,4 @@ The AI understands:
 - Adapts to project-specific requirements and constraints
 - Supports incremental improvement over time
 
-The Server Implementer transforms code scaffolds into implementations, accelerating backend development while maintaining code quality and consistency.
+The Server Implementer transforms code scaffolds into implementations, accelerating server development while maintaining code quality and consistency.

package/dist/commands/implement-slice.js

@@ -40,7 +40,7 @@ function findFilesToImplement(contextFiles) {
 }
 // System prompt for AI implementation
 const SYSTEM_PROMPT = `
-You are a software engineer implementing missing logic in a sliced event-driven TypeScript backend. Each slice contains partially scaffolded code, and your task is to complete the logic following implementation instructions embedded in each file.
+You are a software engineer implementing missing logic in a sliced event-driven TypeScript server. Each slice contains partially scaffolded code, and your task is to complete the logic following implementation instructions embedded in each file.
 
 Project Characteristics:
 - Architecture: sliced event-sourced CQRS (Command, Query, Reaction slices)

package/dist/prompts/systemPrompt.d.ts

@@ -1,2 +1,2 @@
-export declare const SYSTEM_PROMPT = "\nYou are a software engineer implementing missing logic in a sliced event-driven TypeScript backend. Each slice contains partially scaffolded code, and your task is to complete the logic following implementation instructions embedded in each file.\n\nProject Characteristics:\n- Architecture: sliced event-sourced CQRS (Command, Query, Reaction slices)\n- Language: TypeScript with type-graphql and Emmett\n- Each slice has scaffolded files with implementation instructions clearly marked with comments (e.g., '## IMPLEMENTATION INSTRUCTIONS ##') or TODOs.\n- Tests (e.g., *.specs.ts) must pass.\n- Type errors are not allowed.\n\nYour Goal:\n- Read the implementation instructions from the provided file.\n- Generate only the code needed to fulfill the instructions, nothing extra and provide back the whole file without the instructions.\n- Maintain immutability and adhere to functional best practices.\n- Use only the types and domain constructs already present in the slice.\n- Do not remove existing imports or types that are still referenced or required in the file.\n- Return the entire updated file, not just the modified parts and remove any TODO comments or instructions after implementing the logic\n\nKey rules:\n- Never modify code outside the TODO or instruction areas.\n- Ensure the code is production-ready and type-safe.\n- Follow the slice type conventions:\n  - **Command slice**: validate command, inspect state, emit events, never mutate state. Uses graphql mutations.\n  - **Reaction slice**: respond to events with commands.\n  - **Query slice**: maintain projections based on events, do not emit or throw. Uses graphql queries.\n- All code must be TypeScript compliant and follow functional patterns.\n- If a test exists, make it pass.\n- Keep implementations minimal and idiomatic.\n\nAvoid:\n- Adding new dependencies.\n- Refactoring unrelated code.\n- Changing the structure of already scaffolded files unless instructed.\n\nYou will receive:\n- The path of the file to implement.\n- The current contents of the file, with instruction comments.\n- Other relevant files from the same slice (e.g., types, test, state, etc.).\n\nYou must:\n-  Return the entire updated file (no commentary and remove all implementation instructions).\n- Ensure the output is valid TypeScript.\n";
+export declare const SYSTEM_PROMPT = "\nYou are a software engineer implementing missing logic in a sliced event-driven TypeScript server. Each slice contains partially scaffolded code, and your task is to complete the logic following implementation instructions embedded in each file.\n\nProject Characteristics:\n- Architecture: sliced event-sourced CQRS (Command, Query, Reaction slices)\n- Language: TypeScript with type-graphql and Emmett\n- Each slice has scaffolded files with implementation instructions clearly marked with comments (e.g., '## IMPLEMENTATION INSTRUCTIONS ##') or TODOs.\n- Tests (e.g., *.specs.ts) must pass.\n- Type errors are not allowed.\n\nYour Goal:\n- Read the implementation instructions from the provided file.\n- Generate only the code needed to fulfill the instructions, nothing extra and provide back the whole file without the instructions.\n- Maintain immutability and adhere to functional best practices.\n- Use only the types and domain constructs already present in the slice.\n- Do not remove existing imports or types that are still referenced or required in the file.\n- Return the entire updated file, not just the modified parts and remove any TODO comments or instructions after implementing the logic\n\nKey rules:\n- Never modify code outside the TODO or instruction areas.\n- Ensure the code is production-ready and type-safe.\n- Follow the slice type conventions:\n  - **Command slice**: validate command, inspect state, emit events, never mutate state. Uses graphql mutations.\n  - **Reaction slice**: respond to events with commands.\n  - **Query slice**: maintain projections based on events, do not emit or throw. Uses graphql queries.\n- All code must be TypeScript compliant and follow functional patterns.\n- If a test exists, make it pass.\n- Keep implementations minimal and idiomatic.\n\nAvoid:\n- Adding new dependencies.\n- Refactoring unrelated code.\n- Changing the structure of already scaffolded files unless instructed.\n\nYou will receive:\n- The path of the file to implement.\n- The current contents of the file, with instruction comments.\n- Other relevant files from the same slice (e.g., types, test, state, etc.).\n\nYou must:\n-  Return the entire updated file (no commentary and remove all implementation instructions).\n- Ensure the output is valid TypeScript.\n";
 //# sourceMappingURL=systemPrompt.d.ts.map

package/dist/prompts/systemPrompt.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"systemPrompt.d.ts","sourceRoot":"","sources":["../../src/prompts/systemPrompt.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,aAAa,owEA0CzB,CAAC"}
+{"version":3,"file":"systemPrompt.d.ts","sourceRoot":"","sources":["../../src/prompts/systemPrompt.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,aAAa,mwEA0CzB,CAAC"}

package/dist/prompts/systemPrompt.js

@@ -1,5 +1,5 @@
 export const SYSTEM_PROMPT = `
-You are a software engineer implementing missing logic in a sliced event-driven TypeScript backend. Each slice contains partially scaffolded code, and your task is to complete the logic following implementation instructions embedded in each file.
+You are a software engineer implementing missing logic in a sliced event-driven TypeScript server. Each slice contains partially scaffolded code, and your task is to complete the logic following implementation instructions embedded in each file.
 
 Project Characteristics:
 - Architecture: sliced event-sourced CQRS (Command, Query, Reaction slices)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@auto-engineer/server-implementer",
-  "version": "0.6.0",
+  "version": "0.6.2",
   "type": "module",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
@@ -14,15 +14,15 @@
     "access": "public"
   },
   "dependencies": {
-    "@auto-engineer/ai-gateway": "^0.6.0",
-    "@auto-engineer/message-bus": "^0.5.0",
+    "@auto-engineer/ai-gateway": "^0.6.2",
+    "@auto-engineer/message-bus": "^0.5.2",
     "@modelcontextprotocol/sdk": "^1.3.0",
     "debug": "^4.3.4",
     "fast-glob": "^3.3.3",
     "vite": "^5.4.1"
   },
   "devDependencies": {
-    "@auto-engineer/cli": "^0.7.0",
+    "@auto-engineer/cli": "^0.7.2",
     "@types/fs-extra": "^11.0.4",
     "dotenv": "^16.6.1",
     "execa": "^9.6.0",

package/src/commands/implement-slice.ts

@@ -76,7 +76,7 @@ function findFilesToImplement(contextFiles: Record<string, string>): Array<[stri
 
 // System prompt for AI implementation
 const SYSTEM_PROMPT = `
-You are a software engineer implementing missing logic in a sliced event-driven TypeScript backend. Each slice contains partially scaffolded code, and your task is to complete the logic following implementation instructions embedded in each file.
+You are a software engineer implementing missing logic in a sliced event-driven TypeScript server. Each slice contains partially scaffolded code, and your task is to complete the logic following implementation instructions embedded in each file.
 
 Project Characteristics:
 - Architecture: sliced event-sourced CQRS (Command, Query, Reaction slices)

package/src/prompts/systemPrompt.ts

@@ -1,5 +1,5 @@
 export const SYSTEM_PROMPT = `
-You are a software engineer implementing missing logic in a sliced event-driven TypeScript backend. Each slice contains partially scaffolded code, and your task is to complete the logic following implementation instructions embedded in each file.
+You are a software engineer implementing missing logic in a sliced event-driven TypeScript server. Each slice contains partially scaffolded code, and your task is to complete the logic following implementation instructions embedded in each file.
 
 Project Characteristics:
 - Architecture: sliced event-sourced CQRS (Command, Query, Reaction slices)