olympus-ai 4.4.6 → 4.4.7

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "olympus-ai",
-  "version": "4.4.6",
+  "version": "4.4.7",
   "description": "Olympus: Multi-agent orchestration for Claude Code. Summon the gods of code.",
   "author": {
     "name": "mikev10",

package/dist/installer/index.d.ts

@@ -24,7 +24,7 @@ export declare const HOOKS_DIR: string;
 export declare const SETTINGS_FILE: string;
 export declare const VERSION_FILE: string;
 /** Current version - MUST match package.json */
-export declare const VERSION = "4.4.6";
+export declare const VERSION = "4.4.7";
 /** Installation result */
 export interface InstallResult {
     success: boolean;

package/dist/installer/index.js

@@ -40,7 +40,7 @@ export const HOOKS_DIR = join(CLAUDE_CONFIG_DIR, 'hooks');
 export const SETTINGS_FILE = join(CLAUDE_CONFIG_DIR, 'settings.json');
 export const VERSION_FILE = join(CLAUDE_CONFIG_DIR, '.olympus-version.json');
 /** Current version - MUST match package.json */
-export const VERSION = '4.4.6';
+export const VERSION = '4.4.7';
 /**
  * Read a content file from the resources/ directory.
  *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "olympus-ai",
-  "version": "4.4.6",
+  "version": "4.4.7",
   "description": "Olympus: Multi-agent orchestration for Claude Code. Summon the gods of code.",
   "type": "module",
   "main": "dist/index.js",

package/resources/rules/common/session-continuity.md

@@ -31,6 +31,12 @@ B) Review a previous stage ([Show available stages])
    - **Application Design**: Read application-design artifacts (components.md, component-methods.md, services.md)
    - **Design (Units)**: Read unit-of-work.md, unit-of-work-dependency.md, unit-of-work-story-map.md
    - **Per-Unit Design**: Read functional-design.md, nfr-requirements.md, nfr-design.md, infrastructure-design.md
+   - **Construction In-Progress Artifacts**: Before creating any new construction artifacts, scan for existing ones:
+     - Check `construction/plans/` for code generation plans
+     - Check `construction/u-*-{unit-name}/` for legacy per-unit artifacts
+     - Check for partially-generated code files referenced in any existing plan
+     - Present an inventory of found artifacts to the user: "Found N existing construction artifacts: [list]. These will be loaded as the starting point."
+     - Do NOT create new artifacts that duplicate existing ones — always check first
    - **Code Stages**: Read all code files, plans, AND all previous artifacts
 4. **Smart Context Loading by Stage**:
    - **Early Stages (Workspace Detection, Reverse Engineering)**: Load workspace analysis

package/resources/rules/construction/code-generation.md

@@ -51,6 +51,19 @@ When managing code generation, the orchestrator MUST leverage Olympus capabiliti
 
 # PART 1: PLANNING
 
+## Step 0: Check for Existing Artifacts (Idempotency Gate)
+- [ ] Scan `aidlc-docs/{workflow-id}/construction/` for any existing code generation plan for this unit
+  - Check canonical path: `construction/plans/{unit-name}-code-generation-plan.md`
+  - Check legacy paths: `construction/u-*-{unit-name}/code-generation-plan*`, `construction/{unit-name}/code-generation-plan*`
+- [ ] If a plan exists:
+  - Read it and present a summary to the user
+  - Ask: "An existing code generation plan was found at `{path}`. Would you like to (A) reuse it as-is, (B) update it, or (C) replace it with a new plan?"
+  - If at a non-canonical path, migrate it to the canonical location: `construction/plans/{unit-name}-code-generation-plan.md`
+  - If reusing (A): skip to Step 7 (approval) with the existing plan
+  - If updating (B): load it as the starting point for Steps 1-6
+  - If replacing (C): proceed to Step 1 as normal
+- [ ] If no plan exists: proceed to Step 1
+
 ## Step 1: Analyze Unit Context
 - [ ] Read unit design artifacts from Unit Design Generation
 - [ ] Read unit story map to understand assigned stories
@@ -92,7 +105,7 @@ When managing code generation, the orchestrator MUST leverage Olympus capabiliti
   - Service boundaries and responsibilities
 
 ## Step 4: Create Unit Plan Document
-- [ ] Save complete plan as `aidlc-docs/construction/plans/{unit-name}-code-generation-plan.md`
+- [ ] Save complete plan as `aidlc-docs/{workflow-id}/construction/plans/{unit-name}-code-generation-plan.md` (CANONICAL PATH — do not use any other location)
 - [ ] Include step numbering (Step 1, Step 2, etc.)
 - [ ] Include unit context and dependencies
 - [ ] Include story traceability
@@ -239,6 +252,12 @@ When managing code generation, the orchestrator MUST leverage Olympus capabiliti
 - **STORY TRACEABILITY**: Mark unit stories [x] when functionality is implemented
 - **RESPECT DEPENDENCIES**: Only implement when unit dependencies are satisfied
 
+### Canonical Path Rules
+- **Code generation plans MUST be saved at**: `aidlc-docs/{workflow-id}/construction/plans/{unit-name}-code-generation-plan.md`
+- Do NOT create code generation plans at any other path (e.g., `construction/u-nnn-{name}/`, `construction/{name}/`)
+- If a plan is found at a non-canonical path during Step 0, migrate it to the canonical location before proceeding
+- Per-unit directories (`construction/u-nnn-{name}/`) are reserved for construction output artifacts (code summaries, documentation), NOT plans
+
 ### Automation Friendly Code Rules
 When generating UI code (web, mobile, desktop), ensure elements are automation-friendly:
 - Add `data-testid` attributes to interactive elements (buttons, inputs, links, forms)