octo-dev 0.8.1 → 0.9.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "octo-dev",
-  "version": "0.8.1",
+  "version": "0.9.0",
   "description": "Build orchestration, semantic versioning, and local infrastructure management for repository workspaces",
   "type": "module",
   "license": "MIT",

package/src/cli/config.command.ts

@@ -5,7 +5,7 @@ import { ask, askSecret } from '../shared/prompt.js';
 
 const PROVIDERS: Record<string, { baseUrl: string; defaultModel: string }> = {
   openai: { baseUrl: 'https://openai.com/v1', defaultModel: 'gpt-4o-mini' },
-  gemini: { baseUrl: 'https://generativelanguage.googleapis.com/v1beta/openai', defaultModel: 'gemini-2.0-flash' },
+  gemini: { baseUrl: 'https://generativelanguage.googleapis.com/v1beta/openai', defaultModel: 'gemini-2.5-flash' },
   groq: { baseUrl: 'https://api.groq.com/openai/v1', defaultModel: 'llama-3.3-70b-versatile' },
   anthropic: { baseUrl: 'https://api.anthropic.com/v1', defaultModel: 'claude-sonnet-4-20250514' },
   custom: { baseUrl: '', defaultModel: '' },

package/src/cli/index.ts

@@ -11,7 +11,7 @@ const program = new Command();
 program
   .name('octo')
   .description('Build orchestration, semantic versioning, and local infrastructure management for repository workspaces')
-  .version('0.8.1');
+  .version('0.9.0');
 
 program
   .command('init')

package/src/infra/compose-smart-merger.ts

@@ -16,8 +16,8 @@ export interface ComposeSmartMerger {
 
 /**
  * Builds the LLM prompt for optimized compose merging.
- * Instructs the model to unify redundant infrastructure (databases, caches, brokers)
- * into shared instances while preserving application-specific services.
+ * The prompt is agnostic — it describes optimization principles without
+ * referencing specific technologies or project names.
  *
  * @param composes - Array of discovered compose files to merge.
  * @returns The formatted prompt string.
@@ -27,26 +27,26 @@ function buildPrompt(composes: DiscoveredCompose[]): string {
     .map((c) => `--- ${c.serviceName} (${c.path}) ---\n${JSON.stringify(c.content, null, 2)}`)
     .join('\n\n');
 
-  return `You are a Docker Compose optimization expert. Given multiple docker-compose files from a workspace of microservices, produce the most optimized unified compose possible.
+  return `You are given multiple docker-compose files from a workspace of microservices. Produce a single optimized unified docker-compose file.
 
-Optimization goals (in priority order):
-1. UNIFY shared infrastructure — multiple PostgreSQL, Redis, MongoDB, Elasticsearch, RabbitMQ, NATS, or similar containers MUST be consolidated into a single shared instance. Create separate databases/schemas via environment variables or init scripts, not separate containers.
-2. UNIFY shared volumes — if multiple services mount the same type of volume (e.g. pg-data), consolidate into one.
-3. UNIFY networks — use a single shared network unless isolation is explicitly required for security.
-4. PRESERVE application services — each microservice container remains separate (they are distinct apps).
-5. MERGE environment variables — when unifying databases, collect all required databases/users into the shared instance config.
-6. AVOID port conflicts — if two services expose the same host port, remap one to an available port.
-7. USE latest image versions when duplicates exist with different tags.
-8. ADD healthchecks to infrastructure services (postgres, redis, etc.) if not already present.
-9. ADD depends_on with condition: service_healthy for app services that need infrastructure.
+Optimization principles:
 
-Example: If service-a has postgres:16 on port 5432 and service-b has postgres:15 on port 5433, produce ONE postgres:16 container with both databases created via POSTGRES_MULTIPLE_DATABASES env or an init script volume.
+- Infrastructure consolidation: when multiple services declare separate containers of the same database engine (e.g. multiple PostgreSQL instances), consolidate them into a single shared instance that hosts multiple databases. The same applies to message brokers, caches, search engines, and any other shared infrastructure.
+
+- Application preservation: each application service (containers with a "build" directive) must remain as a separate container. Never merge application services together.
+
+- Dependency correctness: update all environment variables in application services to point to the consolidated infrastructure container names. Ensure depends_on references the correct unified containers with condition: service_healthy.
+
+- Minimal resource footprint: use one shared network, one volume per infrastructure type, and eliminate any redundant declarations.
+
+- Healthchecks: every infrastructure container must have a healthcheck defined.
+
+- Port conflicts: if consolidation would create port conflicts on the host, remap to available ports.
 
 Input compose files:
 ${composesText}
 
-Return ONLY valid JSON with this exact structure:
-{"services": {...}, "networks": {...}, "volumes": {...}}`
+Return ONLY valid JSON with this structure: {"services": {...}, "networks": {...}, "volumes": {...}}`
 }
 
 export function createComposeSmartMerger(): ComposeSmartMerger {