@levelcode/cli 0.3.1 → 0.3.2

package/dist/index.js

@@ -75886,6 +75886,15 @@ Spawn context-gathering agents before making edits. Spawn the code-reviewer afte
 - Do not cast types as "any". Maintain strong typing throughout.
 - When modifying exported symbols, find and update all references.
 
+# Output Completeness \u2014 CRITICAL
+
+- NEVER truncate or abbreviate your output. There are NO length constraints.
+- NEVER create stubs, placeholders, or TODO comments instead of real implementations.
+- NEVER say "due to length constraints" or "for brevity" \u2014 write the complete code.
+- If the task asks for 2000+ lines, write 2000+ lines. The system handles context automatically.
+- If you run out of context, the context-pruner will handle it. Just keep writing.
+- Deliver production-ready, complete, compilable code every time.
+
 ${PLACEHOLDER.FILE_TREE_PROMPT_SMALL}
 ${PLACEHOLDER.KNOWLEDGE_FILES_CONTENTS}
 ${PLACEHOLDER.SYSTEM_INFO_PROMPT}
@@ -86733,6 +86742,22 @@ When no tasks are available for you to work on:
 2. If no tasks are available, send an idle notification by using SendMessage with type "message" to the team leader, summarizing what you completed and that you are waiting for work.
 3. Do not spin or poll repeatedly. Wait for new messages in your inbox.`;
 }
+function buildQualityStandards() {
+  return `## Output Quality Standards
+
+CRITICAL: Never truncate, abbreviate, or create stub/placeholder implementations.
+
+- **Never say** "due to length constraints" or "for brevity" \u2014 there are no length constraints. Produce complete, full implementations.
+- **Never create stubs** like "// TODO: implement" or "// remaining implementation here". Write the actual code.
+- **Never skip sections** of code with comments like "// ... rest of implementation similar to above". Write every line.
+- **If your output is getting long**, that is fine. Continue writing. The system handles context limits automatically via context-pruner.
+- **If you run out of context space**, the system will spawn a context-pruner to summarize and continue. You do not need to manage this yourself.
+- **Quality over speed.** A complete 2000-line implementation is better than a 200-line stub with TODOs.
+- **Production-ready code only.** Every file you create should compile, have proper error handling, and be ready to ship.
+- **Include all imports, all types, all tests** that were requested. Do not skip any part of the specification.
+
+If a task is genuinely too large for a single step, break it into sub-tasks and complete each one fully. Never deliver partial work.`;
+}
 function buildShutdownProtocol() {
   return `## Shutdown Protocol
 
@@ -86803,6 +86828,8 @@ function generateTeamContextPrompt(config2) {
     "",
     buildAvailableTools(config2),
     "",
+    buildQualityStandards(),
+    "",
     buildCommunicationProtocol(),
     "",
     buildTaskWorkflow(),
@@ -166215,6 +166242,15 @@ Spawn context-gathering agents before making edits. Spawn the code-reviewer afte
 - Do not cast types as "any". Maintain strong typing throughout.
 - When modifying exported symbols, find and update all references.
 
+# Output Completeness \u2014 CRITICAL
+
+- NEVER truncate or abbreviate your output. There are NO length constraints.
+- NEVER create stubs, placeholders, or TODO comments instead of real implementations.
+- NEVER say "due to length constraints" or "for brevity" \u2014 write the complete code.
+- If the task asks for 2000+ lines, write 2000+ lines. The system handles context automatically.
+- If you run out of context, the context-pruner will handle it. Just keep writing.
+- Deliver production-ready, complete, compilable code every time.
+
 {LEVELCODE_FILE_TREE_PROMPT_SMALL}
 {LEVELCODE_KNOWLEDGE_FILES_CONTENTS}
 {LEVELCODE_SYSTEM_INFO_PROMPT}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@levelcode/cli",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "description": "LevelCode CLI - Terminal-based AI coding agent that outperforms Claude Code",
   "author": {
     "name": "Yethikrishna R",