olympus-ai 4.4.17 → 4.4.18

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "olympus-ai",
-  "version": "4.4.17",
+  "version": "4.4.18",
   "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.17";
+export declare const VERSION = "4.4.18";
 /** 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.17';
+export const VERSION = '4.4.18';
 /**
  * Read a content file from the resources/ directory.
  *

package/package.json

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

package/resources/rules/construction/build-and-test.md

@@ -384,7 +384,21 @@ Create `aidlc-docs/construction/build-and-test/build-and-test-summary.md`:
 1. Update `aidlc-docs/{workflow-id}/aidlc-state.md`:
    - Mark Build and Test stage as complete
    - Update current status
-2. Update `aidlc-docs/{workflow-id}/checkpoint.json` — set build-and-test status to "completed" with completed_at timestamp
+2. Update `aidlc-docs/{workflow-id}/checkpoint.json` — mark the workflow as complete:
+
+```json
+{
+  "current_stage": "complete",
+  "status": "complete",
+  "active_unit_id": null,
+  "units_completed": N
+}
+```
+
+  - `current_stage` MUST be `"complete"` (not `"build-and-test"`)
+  - `status` MUST be `"complete"` (not `"in_progress"`)
+  - Verify `units_completed` equals `units_total`
+  - Verify all units in `construction_units` have `"code_generation_status": "completed"`
 - **Do NOT proceed to the next stage without completing this step**
 
 ---

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

@@ -214,7 +214,21 @@ You may:
 
 ## Step 9: MANDATORY: Update Progress
 - [ ] **MANDATORY**: Mark Code Planning complete in `aidlc-docs/{workflow-id}/aidlc-state.md`
-- [ ] **MANDATORY**: Update `aidlc-docs/{workflow-id}/checkpoint.json` current status
+- [ ] **MANDATORY**: Update `aidlc-docs/{workflow-id}/checkpoint.json` — update the unit entry using the `ConstructionUnitProgress` schema:
+
+```json
+"u-nnn-unit-name": {
+  "unitId": "u-nnn-unit-name",
+  "stages": {
+    "code-generation": { "status": "in_progress", "artifact_path": null, "completed_at": null }
+  },
+  "code_plan_path": "construction/plans/u-nnn-unit-name-code-generation-plan.md",
+  "code_generation_status": "awaiting_approval"
+}
+```
+
+  - Set `active_unit_id` to the current unit ID
+  - Increment design stage statuses to `"skipped"` for stages that were skipped per the execution plan
 - [ ] Prepare for transition to Code Generation
 - **Do NOT proceed without completing state updates**
 
@@ -304,7 +318,20 @@ This ensures the summary always exists regardless of agent compliance.
 - Record the user's approval response with timestamp
 - **MANDATORY**: Update BOTH state files in the SAME interaction:
   1. Mark Code Generation stage as complete for this unit in `aidlc-docs/{workflow-id}/aidlc-state.md`
-  2. Update `aidlc-docs/{workflow-id}/checkpoint.json` — set code-generation status to "completed" for this unit with completed_at timestamp
+  2. Update `aidlc-docs/{workflow-id}/checkpoint.json` — update the unit entry:
+
+```json
+"u-nnn-unit-name": {
+  "stages": {
+    "code-generation": { "status": "completed", "artifact_path": "construction/u-nnn-unit-name/", "completed_at": "ISO-TIMESTAMP" }
+  },
+  "code_generation_status": "completed"
+}
+```
+
+  - Increment `units_completed`
+  - If this is the last unit: set `active_unit_id` to `null`
+  - If more units remain: set `active_unit_id` to the next unit ID
 - **Do NOT proceed to the next stage without completing state updates**
 
 ---

package/resources/rules/inception/workflow-planning.md

@@ -443,6 +443,28 @@ flowchart TD
 2. Update `aidlc-docs/{workflow-id}/checkpoint.json` — initialize workflow state with all stage statuses, current_inception_stage set to next stage after Workflow Planning
    - **Skipped stages MUST use `"status": "skipped"`** (not `"completed"`) with a `skip_reason` field. This distinguishes stages that were intentionally excluded from stages that ran and produced artifacts.
    - If Unit Registration (Step 3.5) was executed, include `"unit_registration_completed": true` on the units-generation entry.
+   - **CRITICAL: `construction_units` schema** — When initializing units, use the `ConstructionUnitProgress` object format keyed by unit folder name. Each unit MUST include the full `stages` record:
+
+```json
+"construction_units": {
+  "u-001-unit-name": {
+    "unitId": "u-001-unit-name",
+    "stages": {
+      "functional-design": { "status": "not_started", "artifact_path": null, "completed_at": null },
+      "nfr-requirements": { "status": "not_started", "artifact_path": null, "completed_at": null },
+      "nfr-design": { "status": "not_started", "artifact_path": null, "completed_at": null },
+      "infrastructure-design": { "status": "not_started", "artifact_path": null, "completed_at": null },
+      "code-generation": { "status": "not_started", "artifact_path": null, "completed_at": null },
+      "test-generation": { "status": "not_started", "artifact_path": null, "completed_at": null }
+    },
+    "code_plan_path": null,
+    "code_generation_status": "not_started"
+  }
+}
+```
+
+   - Also include these top-level fields: `"active_unit_id": null`, `"units_total": N`, `"units_completed": 0`
+   - When design stages are skipped per the execution plan, set their status to `"skipped"` (not `"not_started"`)
 - **Do NOT proceed to the next stage without completing this step**
 
 ## Step 9: Present Plan to User