nimcode 0.4.8__tar.gz → 0.4.9__tar.gz

{nimcode-0.4.8 → nimcode-0.4.9}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nimcode
-Version: 0.4.8
+Version: 0.4.9
 Summary: A standalone, robust coding agent for NVIDIA NIM models.
 Home-page: https://github.com/Batunash/nimcode
 Author: Autonomous Agent

nimcode-0.4.9/src/nimcode/__version__.py

@@ -0,0 +1 @@
+__version__ = "0.4.9"

{nimcode-0.4.8 → nimcode-0.4.9}/src/nimcode/repl.py

@@ -444,11 +444,11 @@ class NimcodeREPL:
                         "   - Write the plan directly to '.nimcode/plans/<name_timestamp>.md'.\n"
                         "   - Use this strict technical structure: # Title, ## Context, ## Root Cause Analysis, ## Execution Plan (file-by-file with line numbers/snippets), ## Verification.\n"
                         "3. IF it is a 'From-Scratch / Major Architecture' task:\n"
-                        "   - DO NOT write the final plan file immediately. This must be an ITERATIVE process.\n"
+                        "   - Work AUTONOMOUSLY in a loop using your file-writing tools. Do NOT ask the user for approval.\n"
                         "   - Step A: Explore the project/SDDs.\n"
-                        "   - Step B: Propose an architectural outline to the user in chat (Tech Stack, Repo Structure, DB Schema, Phased Implementation). Ask the user for their approval or feedback on this outline.\n"
-                        "   - Step C: ONLY after the user explicitly approves the outline, write the detailed execution plan to '.nimcode/plans/<name_timestamp>.md'.\n"
-                        "   - The final plan must be extremely detailed, phased (Phase 0, Phase 1, etc.), and file-based, similar to the approved outline.\n"
+                        "   - Step B: Write a 'Master Architecture Document' to '.nimcode/plans/<name>_master.md' (Tech Stack, Repo Structure, DB Schema, High-level Phase list).\n"
+                        "   - Step C: For EACH Phase, autonomously write a SEPARATE, EXTREMELY DETAILED execution plan file (e.g. '.nimcode/plans/<name>_phase1.md'). Each phase plan must include exact file paths, pseudo-code for every function, and strict step-by-step logic. Do this in a continuous tool-use loop.\n"
+                        "   - Step D: After writing all phase files, overwrite '.nimcode/active_plan.txt' with the master plan's path.\n"
                         "4. General Rules:\n"
                         "   - Quote real names, modules, and requirements. Do not invent generic projects.\n"
                         "   - NEVER output a generic software-lifecycle template (Phase1: MVP / Design / Development) unless instructed. Focus on code, DB schemas, and technical choices.\n"

{nimcode-0.4.8 → nimcode-0.4.9}/src/nimcode.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nimcode
-Version: 0.4.8
+Version: 0.4.9
 Summary: A standalone, robust coding agent for NVIDIA NIM models.
 Home-page: https://github.com/Batunash/nimcode
 Author: Autonomous Agent

{nimcode-0.4.8 → nimcode-0.4.9}/tests/test_repl_fixes.py

@@ -83,8 +83,8 @@ async def test_plan_message_does_not_hardcode_feature_x(agent):
     # The prompt now dynamically differentiates between Bug Fix and From-Scratch tasks
     assert "Identify the task type" in content or "Bug Fix / Minor Feature" in content
     assert "<name_timestamp>.md" in content
-    # It must enforce iterativity for major tasks
-    assert "ITERATIVE process" in content
+    # It must enforce autonomous multi-file generation for major tasks
+    assert "AUTONOMOUSLY" in content or "SEPARATE" in content
 
 
 @pytest.mark.asyncio

nimcode-0.4.8/src/nimcode/__version__.py

@@ -1 +0,0 @@
-__version__ = "0.4.8"