@protolabsai/proto 0.14.0

package/LICENSE

@@ -0,0 +1,203 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+  Copyright 2025 Google LLC
+  Copyright 2025 Qwen
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,286 @@
+# proto
+
+A multi-model AI agent for the terminal. Part of the [protoLabs Studio](https://protolabs.studio) ecosystem.
+
+[![License](https://img.shields.io/github/license/QwenLM/qwen-code.svg)](./LICENSE)
+[![Node.js Version](https://img.shields.io/badge/node-%3E%3D20.0.0-brightgreen.svg)](https://nodejs.org/)
+
+proto is a fork of [Qwen Code](https://github.com/QwenLM/qwen-code) (itself forked from [Gemini CLI](https://github.com/google-gemini/gemini-cli)), rebuilt as a model-agnostic coding agent. It connects to any OpenAI-compatible, Anthropic, or Gemini API endpoint.
+
+## What's Different
+
+| Feature          | Qwen Code               | proto                                                                          |
+| ---------------- | ----------------------- | ------------------------------------------------------------------------------ |
+| Default model    | Qwen3-Coder             | Any (configurable)                                                             |
+| Task management  | In-memory JSON          | [beads_rust](https://github.com/Dicklesworthstone/beads_rust) (SQLite + JSONL) |
+| Memory           | Single append-only file | File-per-memory with YAML frontmatter, 4-type taxonomy, auto-extraction        |
+| MCP servers      | None                    | Configurable via `~/.proto/settings.json`                                      |
+| Plugin discovery | Qwen only               | Auto-discovers Claude Code plugins from `~/.claude/plugins/`                   |
+| Skills           | Nested superpowers      | Flat bundled skills (16 skills, all discoverable)                              |
+
+## Installation
+
+Requires Node.js 20+ and Rust toolchain (for beads_rust).
+
+```bash
+# Clone and build
+git clone https://github.com/protoLabsAI/protoCLI.git
+cd protoCLI
+npm install
+npm run build
+
+# Link globally
+npm link
+
+# Install beads_rust task manager (optional but recommended)
+cargo install beads_rust
+```
+
+## Quick Start
+
+### 1. Configure your endpoint
+
+proto connects to any OpenAI-compatible API. Create `~/.proto/settings.json`:
+
+```json
+{
+  "modelProviders": {
+    "openai": [
+      {
+        "id": "my-model",
+        "name": "My Model",
+        "baseUrl": "http://localhost:8000/v1",
+        "envKey": "MY_API_KEY"
+      }
+    ]
+  },
+  "security": {
+    "auth": { "selectedType": "openai" }
+  },
+  "model": { "name": "my-model" }
+}
+```
+
+### 2. Set your API key
+
+Create `~/.proto/.env`:
+
+```
+MY_API_KEY=sk-your-key-here
+```
+
+Or export it in your shell: `export MY_API_KEY=sk-your-key-here`
+
+### 3. Run proto
+
+```bash
+proto                            # interactive mode
+proto -p "explain this codebase" # one-shot mode
+```
+
+No auth screen — proto connects directly to your endpoint.
+
+### Example: Multiple models via a gateway
+
+If you run a gateway like [LiteLLM](https://github.com/BerriAI/litellm) in front of multiple providers, register them all under `modelProviders.openai` and switch between them with `/model`:
+
+```json
+{
+  "modelProviders": {
+    "openai": [
+      {
+        "id": "local/qwen-122b",
+        "name": "Qwen3.5-122B (local vLLM)",
+        "baseUrl": "http://my-gateway:4000/v1",
+        "envKey": "GATEWAY_KEY",
+        "generationConfig": { "contextWindowSize": 65536 }
+      },
+      {
+        "id": "claude-sonnet-4-6",
+        "name": "Claude Sonnet 4.6",
+        "baseUrl": "http://my-gateway:4000/v1",
+        "envKey": "GATEWAY_KEY",
+        "capabilities": { "vision": true },
+        "generationConfig": { "contextWindowSize": 200000 }
+      },
+      {
+        "id": "gpt-5.4",
+        "name": "GPT-5.4",
+        "baseUrl": "http://my-gateway:4000/v1",
+        "envKey": "GATEWAY_KEY",
+        "capabilities": { "vision": true },
+        "generationConfig": { "contextWindowSize": 200000 }
+      }
+    ]
+  },
+  "security": {
+    "auth": { "selectedType": "openai" }
+  },
+  "model": { "name": "local/qwen-122b" }
+}
+```
+
+### Model config reference
+
+| Field                                | Required | Description                                                      |
+| ------------------------------------ | -------- | ---------------------------------------------------------------- |
+| `id`                                 | yes      | Model ID sent to the API (must match what your endpoint expects) |
+| `name`                               | no       | Display name in proto UI (defaults to `id`)                      |
+| `baseUrl`                            | no       | API base URL (defaults to OpenAI's)                              |
+| `envKey`                             | no       | Environment variable name for the API key                        |
+| `description`                        | no       | Shown in model picker                                            |
+| `capabilities.vision`                | no       | Enable image/vision inputs                                       |
+| `generationConfig.contextWindowSize` | no       | Context window in tokens                                         |
+
+## Configuration
+
+proto uses `~/.proto/settings.json` for global config and `.proto/settings.json` for per-project overrides.
+
+### MCP Servers
+
+Add MCP servers directly in settings:
+
+```json
+{
+  "mcpServers": {
+    "my_server": {
+      "command": "node",
+      "args": ["/path/to/mcp-server/dist/index.js"],
+      "env": { "API_KEY": "..." },
+      "trust": true
+    }
+  }
+}
+```
+
+Tools are exposed as `mcp__<server_name>__<tool_name>` and available to the agent immediately.
+
+### Plugin Discovery
+
+proto auto-discovers Claude Code plugins installed at `~/.claude/plugins/`. Any plugin's `commands/` directory is automatically loaded as slash commands — no additional config needed.
+
+## Task Management
+
+proto integrates [beads_rust](https://github.com/Dicklesworthstone/beads_rust) for persistent, SQLite-backed task tracking. When `br` is on PATH, the 6 task tools (`task_create`, `task_get`, `task_list`, `task_update`, `task_stop`, `task_output`) use it as the backend. Tasks persist across sessions in `.beads/` within the project directory.
+
+If `br` is not installed, tasks fall back to the original in-memory JSON store.
+
+```bash
+# The agent uses these automatically, but you can also use br directly:
+br list              # See all tasks
+br list --json       # Machine-readable output
+br create --title "Fix auth bug" --type task --priority 1
+br close <id> --reason "Fixed in commit abc123"
+```
+
+## Memory
+
+proto has a persistent memory system inspired by Claude Code. Memories are individual markdown files with YAML frontmatter, organized by type and stored per-project or globally.
+
+### Memory types
+
+| Type        | Purpose                               | Example                                        |
+| ----------- | ------------------------------------- | ---------------------------------------------- |
+| `user`      | Preferences, role, knowledge          | "prefers tabs over spaces"                     |
+| `feedback`  | Approach corrections or confirmations | "don't mock the database in integration tests" |
+| `project`   | Deadlines, decisions, ongoing work    | "merge freeze starts April 5"                  |
+| `reference` | Pointers to external systems          | "bugs tracked in Linear project INGEST"        |
+
+### How it works
+
+Each memory is a `.md` file in `.proto/memory/` (project) or `~/.proto/memory/` (global):
+
+```markdown
+---
+name: prefer-dark-theme
+description: User prefers dark themes in all editors
+type: user
+---
+
+User explicitly stated they prefer dark themes.
+```
+
+A `MEMORY.md` index is auto-generated and loaded into the system prompt at the start of each session. The agent can create memories via the `save_memory` tool, or you can use slash commands:
+
+```
+/memory add --project I prefer dark themes
+/memory list
+/memory forget prefer-dark-theme
+/memory show
+/memory refresh
+```
+
+After each conversation turn, a background extraction agent reviews recent messages and auto-creates memories for notable facts. This runs fire-and-forget with restricted tools (read/write/glob in the memory directory only).
+
+## Skills
+
+proto ships with 16 bundled skills for agentic workflows:
+
+- **brainstorming** — Structured ideation
+- **dispatching-parallel-agents** — Fan-out/fan-in subagent patterns
+- **executing-plans** — Step-by-step plan execution
+- **finishing-a-development-branch** — Pre-merge cleanup
+- **qc-helper** — Quality control checks
+- **receiving-code-review** — Process review feedback
+- **requesting-code-review** — Generate review requests
+- **review** — Code review workflow
+- **subagent-driven-development** — Delegate to specialized subagents
+- **systematic-debugging** — Structured debug methodology
+- **test-driven-development** — TDD workflow
+- **using-git-worktrees** — Isolated branch work
+- **using-superpowers** — Advanced agent capabilities
+- **verification-before-completion** — Pre-commit verification
+- **writing-plans** — Plan authoring
+- **writing-skills** — Skill authoring
+
+Use `/skills` to list available skills in a session.
+
+## Commands
+
+| Command                 | Description                               |
+| ----------------------- | ----------------------------------------- |
+| `/help`                 | Show available commands                   |
+| `/auth`                 | Configure authentication                  |
+| `/model`                | Switch models                             |
+| `/skills`               | List available skills                     |
+| `/memory show`          | Display loaded memory content             |
+| `/memory list`          | List all memories with type, scope, age   |
+| `/memory add <fact>`    | Save a memory (`--global` or `--project`) |
+| `/memory forget <name>` | Delete a memory                           |
+| `/memory refresh`       | Reload memories from disk                 |
+| `/clear`                | Clear conversation                        |
+| `/compress`             | Compress history to save tokens           |
+| `/stats`                | Session info                              |
+| `/exit`                 | Exit proto                                |
+
+## Keyboard Shortcuts
+
+| Shortcut  | Action                   |
+| --------- | ------------------------ |
+| `Ctrl+C`  | Cancel current operation |
+| `Ctrl+D`  | Exit (on empty line)     |
+| `Up/Down` | Navigate command history |
+
+## IDE Integration
+
+proto works with VS Code, Zed, and JetBrains IDEs. See the upstream [Qwen Code docs](https://qwenlm.github.io/qwen-code-docs/en/users/overview) for setup instructions.
+
+## Architecture
+
+```
+packages/
+├── cli/           # Terminal UI (Ink + React)
+├── core/          # Agent engine, tools, skills, MCP client
+├── sdk-typescript/# TypeScript SDK
+├── web-templates/ # Shared web templates
+├── webui/         # Shared UI components
+└── test-utils/    # Testing utilities
+```
+
+## Acknowledgments
+
+Built on [Qwen Code](https://github.com/QwenLM/qwen-code) (Apache 2.0), which is built on [Gemini CLI](https://github.com/google-gemini/gemini-cli) (Apache 2.0). Task management powered by [beads_rust](https://github.com/Dicklesworthstone/beads_rust).
+
+## License
+
+Apache 2.0 — see [LICENSE](./LICENSE).

package/dist/bundled/adversarial-verification/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: adversarial-verification
+description: Use when you need to verify code changes by actively trying to break them - not just confirming they work, but probing for failures through boundary testing, concurrency, and edge cases
+agentOnly: true
+---
+
+# Adversarial Verification
+
+## Purpose
+
+Your job is NOT to confirm the implementation works. Your job is to try to break it.
+
+## Two Failure Modes That Will Get You
+
+1. **Check-skipping:** Finding reasons not to actually run checks. Reading source and deciding it "looks correct." Writing PASS with no supporting command output. This is not verification — it is storytelling.
+
+2. **Getting lulled by the obvious 80%:** Seeing a polished UI or green test suite and feeling inclined to pass. Meanwhile half the buttons do nothing, state vanishes on refresh, backend crashes on malformed input.
+
+## Rationalization Traps
+
+If you catch yourself thinking any of these, stop and course-correct:
+
+- "The code looks correct based on my reading" — Inspection alone does not constitute proof. Execute it.
+- "The implementer's tests already pass" — Tests may rely on mocks, contain circular assertions, or cover only the happy path. Verify independently.
+- "This is probably fine" — "Probably" is not "verified." Run the check.
+- "Let me start the server and check the code" — No. Start the server and HIT THE ENDPOINTS.
+- "This would take too long" — That is not your decision to make.
+
+## Universal Required Steps
+
+Regardless of what changed:
+
+1. Read the project's PROTO.md, README, or equivalent to discover build and test commands.
+2. Run the build. Broken build = automatic FAIL.
+3. Run the full test suite. Any failing test = automatic FAIL.
+4. Run linters and type-checkers if the project has them configured.
+5. Check for regressions in areas adjacent to the change.
+
+## Adversarial Probes
+
+Run at least one of these before issuing ANY pass:
+
+- **Concurrency:** Fire parallel requests at the same resource. Do duplicate records appear? Does data corrupt?
+- **Boundary values:** Feed 0, -1, empty string, extremely long strings, unicode characters, MAX_INT.
+- **Idempotency:** Submit the same request twice. Does the system handle it gracefully?
+- **Orphan operations:** Attempt to delete a nonexistent resource, or reference an ID that was never created.
+
+## Verification Strategies by Change Type
+
+- **Frontend/UI:** Start dev server. Navigate pages, click elements, fill forms. Curl subresources (JS bundles, CSS, images) to confirm they load.
+- **Backend/API:** Start server. Curl each relevant endpoint. Check response status codes, headers, body shapes. Send bad input to test error handling.
+- **CLI/script:** Execute with representative arguments. Check stdout, stderr, exit codes. Feed edge-case inputs.
+- **Infrastructure/config:** Validate syntax. Perform dry-run commands where available (terraform plan, docker build --check, nginx -t).
+- **Bug fixes:** Reproduce the original bug FIRST. Confirm the fix resolves it. Run regression tests. Check for side effects.
+- **Refactoring:** Existing test suite MUST pass without modification. Diff public API surface to confirm nothing changed unintentionally.
+
+## Output Format
+
+Every verification step must follow this exact format:
+
+```
+### Check: [what you are verifying]
+**Command:** `[exact command executed]`
+**Output:** [actual terminal output, copy-pasted verbatim]
+**Result: PASS** (or **FAIL** with Expected vs Actual)
+```
+
+Bad example (REJECTED):
+
+```
+### Check: API returns correct data
+**Command:** (reviewed the handler source code)
+**Output:** The logic appears correct
+**Result: PASS**
+```
+
+This contains no executed command and no real output. It proves nothing.
+
+Good example (ACCEPTABLE):
+
+```
+### Check: API returns correct data
+**Command:** `curl -s http://localhost:3000/api/users/1 | jq .`
+**Output:** {"id": 1, "name": "Alice", "email": "alice@example.com"}
+**Result: PASS** - response contains expected fields with valid values
+```
+
+## Final Verdict
+
+End every verification report with exactly one of:
+
+```
+VERDICT: PASS
+VERDICT: FAIL
+VERDICT: PARTIAL
+```
+
+Use PARTIAL only when environmental limitations genuinely prevented certain checks. Uncertainty = FAIL, not PARTIAL.