@protolabsai/proto 0.26.0 → 0.26.3

package/bundled/coding-agent-standards/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: coding-agent-standards
-description: Implementation quality checklist for coding agents - ensures code changes meet production standards before completion
+description: Implementation quality checklist — invoke only when explicitly asked to run a standards check or quality gate review
 agentOnly: true
 ---
 

package/bundled/verification-before-completion/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: verification-before-completion
-description: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
+description: Verification checklist for claims of correctness — invoke only when explicitly asked to verify or audit work before a PR or release
 ---
 
 # Verification Before Completion

package/cli.js

@@ -148789,7 +148789,7 @@ var init_tokenLimits = __esm({
     "use strict";
     init_esbuild_shims();
     DEFAULT_TOKEN_LIMIT = 131072;
-    DEFAULT_OUTPUT_TOKEN_LIMIT = 32e3;
+    DEFAULT_OUTPUT_TOKEN_LIMIT = 16e3;
     LIMITS = {
       "32k": 32768,
       "64k": 65536,
@@ -171109,7 +171109,7 @@ __export(geminiContentGenerator_exports, {
   createGeminiContentGenerator: () => createGeminiContentGenerator
 });
 function createGeminiContentGenerator(config2, gcConfig) {
-  const version2 = "0.26.0";
+  const version2 = "0.26.3";
   const userAgent2 = config2.userAgent || `QwenCode/${version2} (${process.platform}; ${process.arch})`;
   const baseHeaders = {
     "User-Agent": userAgent2
@@ -172766,7 +172766,7 @@ You are proto, an interactive CLI agent built by protoLabs.studio, specializing
 - **Style & Structure:** Mimic the style (formatting, naming), structure, framework choices, typing, and architectural patterns of existing code in the project.
 - **Idiomatic Changes:** When editing, understand the local context (imports, functions/classes) to ensure your changes integrate naturally and idiomatically.
 - **Comments:** Add code comments sparingly. Focus on *why* something is done, especially for complex logic, rather than *what* is done. Only add high-value comments if necessary for clarity or if requested by the user. Do not edit comments that are separate from the code you are changing. *NEVER* talk to the user or describe your changes through comments.
-- **Proactiveness:** Fulfill the user's request thoroughly. When adding features or fixing bugs, this includes adding tests to ensure quality. Consider all created files, especially tests, to be permanent artifacts unless the user says otherwise.
+- **Proactiveness:** Fulfill the user's request thoroughly. Do not add tests, documentation, or other artifacts beyond the scope of the request unless explicitly asked.
 - **Confirm Ambiguity/Expansion:** Do not take significant actions beyond the clear scope of the request without confirming with the user. If asked *how* to do something, explain first, don't just do it.
 - **Explaining Changes:** After completing a code modification or file operation *do not* provide summaries unless asked.
 - **Path Construction:** Before using any file system tool (e.g., ${ToolNames.READ_FILE}' or '${ToolNames.WRITE_FILE}'), you must construct the full absolute path for the file_path argument. Always combine the absolute path of the project's root directory with the file's path relative to the root. For example, if the project root is /path/to/project/ and the file is foo/bar/baz.txt, the final path you must use is /path/to/project/foo/bar/baz.txt. If the user provides a relative path, you must resolve it against the root directory to create an absolute path.
@@ -172836,7 +172836,7 @@ When requested to perform tasks like fixing bugs, adding features, refactoring,
 - **Plan:** After understanding the user's request, create an initial plan based on your existing knowledge and any immediately obvious context. Use '${ToolNames.TASK_CREATE}' to capture this rough plan for complex or multi-step work. Don't wait for complete understanding - start with what you know.
 - **Implement:** Begin implementing the plan while gathering additional context as needed. Use '${ToolNames.GREP}', '${ToolNames.GLOB}', and '${ToolNames.READ_FILE}' tools strategically when you encounter specific unknowns during implementation. Use the available tools (e.g., '${ToolNames.EDIT}', '${ToolNames.WRITE_FILE}' '${ToolNames.SHELL}' ...) to act on the plan, strictly adhering to the project's established conventions (detailed under 'Core Mandates').
 - **Adapt:** As you discover new information or encounter obstacles, update your plan and tasks accordingly. Use ${ToolNames.TASK_UPDATE} to mark tasks as in_progress when starting and completed when finishing. Use ${ToolNames.TASK_CREATE} to add new tasks if the scope expands. Refine your approach based on what you learn.
-- **Verify (Tests):** If applicable and feasible, verify the changes using the project's testing procedures. Identify the correct test commands and frameworks by examining 'README' files, build/package configuration (e.g., 'package.json'), or existing test execution patterns. NEVER assume standard test commands.
+- **Verify (Tests):** Only run tests if the user asks, or if a task.yaml / verification script is specified for the task.
 - **Verify (Match the verifier):** When a task specifies a test file, task.yaml, or verification script, read it before verifying your own output. Your implementation must satisfy the *exact* tool or function the verifier uses \u2014 not just produce plausible-looking output using a different library or algorithm. A self-check that passes with the wrong tool is not a passing check.
 - **Verify (Standards):** VERY IMPORTANT: After making code changes, execute the project-specific build, linting and type-checking commands (e.g., 'tsc', 'npm run lint', 'ruff check .') that you have identified for this project (or obtained from the user). This ensures code quality and adherence to standards. If unsure about these commands, you can ask the user if they'd like you to run them and if so how to.
 
@@ -416089,7 +416089,7 @@ __name(getPackageJson, "getPackageJson");
 // packages/cli/src/utils/version.ts
 async function getCliVersion() {
   const pkgJson = await getPackageJson();
-  return "0.26.0";
+  return "0.26.3";
 }
 __name(getCliVersion, "getCliVersion");
 
@@ -423861,7 +423861,7 @@ var formatDuration = /* @__PURE__ */ __name((milliseconds) => {
 
 // packages/cli/src/generated/git-commit.ts
 init_esbuild_shims();
-var GIT_COMMIT_INFO = "7640dccc2";
+var GIT_COMMIT_INFO = "e2418fd12";
 
 // packages/cli/src/utils/systemInfo.ts
 async function getNpmVersion() {
@@ -476480,6 +476480,11 @@ var StatusBar = /* @__PURE__ */ __name(({
       paddingX: 1,
       children: [
         /* @__PURE__ */ (0, import_jsx_runtime136.jsx)(Text3, { color: theme.text.accent, bold: true, children: "\u27E1" }),
+        /* @__PURE__ */ (0, import_jsx_runtime136.jsx)(Sep, {}),
+        /* @__PURE__ */ (0, import_jsx_runtime136.jsxs)(Badge, { dim: true, children: [
+          /* @__PURE__ */ (0, import_jsx_runtime136.jsx)(Text3, { children: "\u2B21 " }),
+          /* @__PURE__ */ (0, import_jsx_runtime136.jsx)(Text3, { children: os38.hostname() })
+        ] }),
         activeAgents.map((agent) => {
           const label = agent.agentName === "session-memory" ? agent.toolName ? "\u21BA notes: writing" : `\u21BA notes: turn ${agent.round}` : agent.toolName ? `\u27F3 ${agent.agentName}: ${agent.toolName}` : `\u27F3 ${agent.agentName}: turn ${agent.round}`;
           return /* @__PURE__ */ (0, import_jsx_runtime136.jsxs)(import_react132.default.Fragment, { children: [
@@ -491526,7 +491531,7 @@ var QwenAgent = class {
   async initialize(args2) {
     this.clientCapabilities = args2.clientCapabilities;
     const authMethods = buildAuthMethods();
-    const version2 = "0.26.0";
+    const version2 = "0.26.3";
     return {
       protocolVersion: PROTOCOL_VERSION,
       agentInfo: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@protolabsai/proto",
-  "version": "0.26.0",
+  "version": "0.26.3",
   "description": "proto - AI-powered coding agent",
   "repository": {
     "type": "git",
@@ -21,7 +21,7 @@
     "bundled"
   ],
   "config": {
-    "sandboxImageUri": "ghcr.io/qwenlm/qwen-code:0.26.0"
+    "sandboxImageUri": "ghcr.io/qwenlm/qwen-code:0.26.3"
   },
   "dependencies": {},
   "optionalDependencies": {