olympus-ai 4.5.12 → 4.5.13

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "olympus-ai",
3
- "version": "4.5.12",
3
+ "version": "4.5.13",
4
4
  "description": "Olympus: Multi-agent orchestration for Claude Code. Summon the gods of code.",
5
5
  "author": {
6
6
  "name": "mikev10",
@@ -24,7 +24,7 @@ export declare const HOOKS_DIR: string;
24
24
  export declare const SETTINGS_FILE: string;
25
25
  export declare const VERSION_FILE: string;
26
26
  /** Current version - MUST match package.json */
27
- export declare const VERSION = "4.5.12";
27
+ export declare const VERSION = "4.5.13";
28
28
  /** Installation result */
29
29
  export interface InstallResult {
30
30
  success: boolean;
@@ -40,7 +40,7 @@ export const HOOKS_DIR = join(CLAUDE_CONFIG_DIR, 'hooks');
40
40
  export const SETTINGS_FILE = join(CLAUDE_CONFIG_DIR, 'settings.json');
41
41
  export const VERSION_FILE = join(CLAUDE_CONFIG_DIR, '.olympus-version.json');
42
42
  /** Current version - MUST match package.json */
43
- export const VERSION = '4.5.12';
43
+ export const VERSION = '4.5.13';
44
44
  /**
45
45
  * Read a content file from the resources/ directory.
46
46
  *
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "olympus-ai",
3
- "version": "4.5.12",
3
+ "version": "4.5.13",
4
4
  "description": "Olympus: Multi-agent orchestration for Claude Code. Summon the gods of code.",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -8,23 +8,15 @@ Check if any `aidlc-docs/*/aidlc-state.md` exists (glob for workflow subdirector
8
8
  - **If exists**: Resume the most recent workflow (load context from previous phases)
9
9
  - **If not exists**: Continue with new project assessment
10
10
 
11
- ## Step 2: Scan Workspace for Existing Code
11
+ ## Step 2: Count Source Files
12
12
 
13
- **Determine if workspace has existing code:**
14
- - Scan workspace for source code files (.java, .py, .js, .ts, .jsx, .tsx, .kt, .kts, .scala, .groovy, .go, .rs, .rb, .php, .c, .h, .cpp, .hpp, .cc, .cs, .fs, etc.)
15
- - Check for build files (pom.xml, package.json, build.gradle, etc.)
16
- - Look for project structure indicators
17
- - Identify workspace root directory (NOT aidlc-docs/)
13
+ Count source files in the workspace to determine brownfield vs greenfield classification.
14
+ Skip `node_modules`, `.git`, `dist`, `build`, and other common non-source directories.
18
15
 
19
- **Record findings:**
20
- ```markdown
21
- ## Workspace State
22
- - **Existing Code**: [Yes/No]
23
- - **Programming Languages**: [List if found]
24
- - **Build System**: [Maven/Gradle/npm/etc. if found]
25
- - **Project Structure**: [Monolith/Microservices/Library/Empty]
26
- - **Workspace Root**: [Absolute path]
27
- ```
16
+ - **3+ source files** → Brownfield
17
+ - **< 3 source files** → Greenfield
18
+
19
+ Do NOT analyze languages, build systems, or project structure here — Reverse Engineering handles that in depth for brownfield projects.
28
20
 
29
21
  ## Step 3: Determine Next Phase
30
22
 
@@ -51,9 +43,8 @@ Create `aidlc-docs/{workflowId}/aidlc-state.md`:
51
43
  - **Current Stage**: INCEPTION - Workspace Detection
52
44
 
53
45
  ## Workspace State
54
- - **Existing Code**: [Yes/No]
46
+ - **Source File Count**: [Number]
55
47
  - **Reverse Engineering Needed**: [Yes/No]
56
- - **Workspace Root**: [Absolute path]
57
48
 
58
49
  ## Code Location Rules
59
50
  - **Application Code**: Workspace root (NEVER in aidlc-docs/)
@@ -70,9 +61,7 @@ Create `aidlc-docs/{workflowId}/aidlc-state.md`:
70
61
  ```markdown
71
62
  # 🔍 Workspace Detection Complete
72
63
 
73
- Workspace analysis findings:
74
- • **Project Type**: Brownfield project
75
- • [AI-generated summary of workspace findings in bullet points]
64
+ **Project Type**: Brownfield ([N] source files detected)
76
65
  • **Next Step**: Proceeding to **Reverse Engineering** to analyze existing codebase...
77
66
  ```
78
67