plcode-linux-x64-baseline-musl 2.1.0

package/.plcode/skill/experimental/agnos/ROUTING.md

@@ -0,0 +1,128 @@
+# AGNOS Routing — When to Delegate to Which Agent
+
+> The AGNOS layer routes work to 12 specialized sub-agents. The decision
+> of **which agent for which task** is implicit today. This document
+> makes it explicit, following the cavecrew `Locate → fix → verify`
+> pattern. **Use the table below; do not improvise.**
+
+---
+
+## The three canonical chains
+
+### Chain 1 — Locate → fix → verify (most common)
+
+For "find X, change Y, check Z":
+
+```
+[Main thread]
+   ↓
+   └─→ code-agent (scope analysis, returns OutputContract)
+         ├─ "OK. + summary"           → continue
+         ├─ "PARTIAL. ..."            → dispatch sub-task
+         ├─ "FAIL. too-big. split: …" → split the work, spawn N code-agents
+         ├─ "FAIL. regressed. …"      → revert, dispatch investigator
+         ├─ "NEED_INPUT. ask: …"      → ask user, halt
+         └─ "TIMEOUT. raw: …"         → inspect raw, retry or split
+   ↓
+   └─→ review-agent (severity-prefixed findings)
+         ├─ "🔴 bug: …"               → fix immediately
+         ├─ "🟡 risk: …"              → discuss with user
+         ├─ "🔵 nit: …"               → optional, low priority
+         └─ "❓ q: …"                 → answer, then fix
+```
+
+### Chain 2 — Plan → execute → validate
+
+For "design X, implement, test":
+
+```
+[Main thread]
+   ↓
+   └─→ planner-agent (returns implementation plan as OutputContract)
+   ↓
+   └─→ code-agent (per step)
+   ↓
+   └─→ test-agent (validates each step)
+```
+
+### Chain 3 — Triage → fix → document
+
+For "PR review, find issues, fix":
+
+```
+[Main thread]
+   ↓
+   └─→ review-agent (severity-prefixed)
+   ↓
+   └─→ code-agent (per finding)
+   ↓
+   └─→ planner-agent (CHANGELOG entry)
+```
+
+---
+
+## Agent selection table
+
+| Task shape                               | First agent                     | Then               | Notes                                              |
+| ---------------------------------------- | ------------------------------- | ------------------ | -------------------------------------------------- |
+| "Where is X defined?" / "list uses of Y" | investigator (read-only, haiku) | —                  | Use `OutputContract` with `artifacts: file:line`   |
+| "Refactor this 1-2 file scoped change"   | code-agent                      | review-agent       | If `too-big.`, split into N code-agents            |
+| "Add new feature spanning 3+ files"      | planner-agent                   | code-agent × N     | NEVER send to a single code-agent first            |
+| "Review this PR / diff"                  | review-agent                    | code-agent per bug | Reviewer uses severity prefix                      |
+| "Run the test suite"                     | executor-agent                  | —                  | Returns TIMEOUT on long runs, raw has logs         |
+| "Why is X broken?"                       | investigator → code-agent       | test-agent         | Investigator first, then fix, then test            |
+| "Generate a commit message"              | planner-agent                   | —                  | Small scope, no need for code-agent first          |
+| "Compare two approaches"                 | critic-agent                    | —                  | Returns critique as OutputContract with confidence |
+| "Continuous improvement of repo"         | background-agent                | —                  | Runs async, results come back via `raw`            |
+| "Generate media (image, video)"          | media-agent                     | —                  | Generates `artifacts: kind=url`                    |
+| "User-facing chat"                       | chat-agent                      | —                  | Skips OutputContract, returns natural prose        |
+| "API/SDK support question"               | support-agent                   | —                  | Returns `NEED_INPUT` if question is unclear        |
+
+---
+
+## When NOT to delegate
+
+- **Simple lookups** — just `Grep`/`Glob` in the main thread. No
+  sub-agent needed.
+- **Single-line edits** — handle directly. Spinning a code-agent
+  for a typo fix costs more than the fix.
+- **Confirmation questions** — answer directly, no delegation.
+- **Anything that requires the user's immediate input** — ask
+  first, dispatch after.
+
+---
+
+## Terminal handling
+
+When a sub-agent emits a terminal, the main thread follows these
+rules:
+
+| Terminal         | Status     | Action                                                         |
+| ---------------- | ---------- | -------------------------------------------------------------- |
+| `too-big.`       | FAIL       | Split into N tasks, spawn N sub-agents in parallel             |
+| `needs-confirm.` | NEED_INPUT | Show the user the op, wait for confirmation                    |
+| `ambiguous.`     | NEED_INPUT | Ask the user the question, halt the chain                      |
+| `regressed.`     | FAIL       | Revert the change, dispatch investigator to debug              |
+| `TIMEOUT`        | TIMEOUT    | Inspect `raw`; if useful, mark PARTIAL and continue, else halt |
+
+---
+
+## Cost discipline
+
+- **Investigator runs on haiku** by default. Never use opus/haiku
+  for a task that can be answered with `Grep` + a 1-line table.
+- **Code-agent with `too-big. split: [a, b]`** triggers N parallel
+  code-agents, each with a small scope. Total cost is similar to
+  one large call but with better quality (each agent has full
+  context for its scope).
+- **Background-agent** should be used for work that does not block
+  the user. The main thread continues and the result arrives as
+  a contract injected into the next turn.
+
+---
+
+## Changelog
+
+- v1: initial routing table. Mirrors the cavecrew `Locate → fix →
+verify` pattern from
+  [cavecrew/SKILL.md](https://github.com/JuliusBrussee/caveman).

package/.plcode/skill/experimental/agnos/SKILL.md

@@ -0,0 +1,142 @@
+---
+name: agnos
+description: AGNOS multi-agent orchestration. When delegating work to a sub-agent (code_agent, planner_agent, review_agent, test_agent, etc.), always produce a structured OutputContract as the final response so the parent thread can branch on the status token without parsing prose.
+compatibility: PLCODE >= 2026.06
+license: MIT
+metadata:
+  category: orchestration
+  priority: high
+---
+
+# AGNOS — Multi-Agent Orchestration
+
+The AGNOS layer routes work to 12 specialized sub-agents. To keep the
+parent thread's context budget predictable, every sub-agent response
+MUST conform to the **OutputContract** described in
+`packages/plcode/opencode/src/agnos/contracts/output.ts`.
+
+This skill is loaded automatically when a session starts with
+`isAgnosEnabled() === true`. The wrapping layer
+`src/agnos/contracts/output-wrap.ts` post-processes raw
+`AgentResult` objects into OutputContract format if an agent forgot
+to construct one — but agents that emit the contract directly are
+preferred.
+
+## When to Use
+
+You MUST emit an OutputContract when:
+
+- A sub-agent finishes executing a delegated task.
+- The main thread is about to inject a sub-agent result back into its
+  own context.
+- A planning step is asking the user to confirm before continuing.
+
+You SHOULD also emit an OutputContract when:
+
+- A long-running tool has produced a structured result (test run,
+  build, lint) and you want to compress it before the next turn.
+
+You do NOT need an OutputContract for:
+
+- A direct reply to the user with no delegation involved.
+- A simple "yes/no" answer where `OutputStatus` adds no value.
+
+## Status Tokens
+
+The first line of every OutputContract is `<status>. <summary>`. Pick
+exactly one:
+
+| Status       | When                                                      | Caller should                          |
+| ------------ | --------------------------------------------------------- | -------------------------------------- |
+| `OK`         | Work is done. `artifacts` describe what was produced.     | Continue.                              |
+| `PARTIAL`    | Some work done, more to do. `next` suggests the step.     | Dispatch the next step.                |
+| `FAIL`       | Hard failure. `summary` is the reason.                    | Retry with different inputs, or stop.  |
+| `NEED_INPUT` | The agent needs clarification. `summary` is the question. | Ask the user, then re-dispatch.        |
+| `TIMEOUT`    | Budget / wall-clock exhausted. `raw` has partial work.    | Inspect `raw` if available, else stop. |
+
+## Schema
+
+```ts
+type OutputContract = {
+  status: "OK" | "PARTIAL" | "FAIL" | "NEED_INPUT" | "TIMEOUT"
+  summary: string // one line, <= 280 chars
+  artifacts: Array<{
+    kind: string // "file" | "branch" | "url" | "decision" | "measurement"
+    ref: string // path, branch name, URL or identifier
+    note: string // one line, <= 120 chars
+  }> // max 16 entries
+  next?: string // suggested next action, <= 140 chars
+  confidence?: number // 0-1
+  raw?: string // full output (only if caller asked)
+}
+```
+
+## Constructing a Contract
+
+Use the helpers in `contracts/output.ts`:
+
+```ts
+import { ok, fail, partial, needInput, timeout, format } from "@/agnos/contracts/output"
+
+// Success
+const c = ok(
+  "Refactored auth middleware",
+  [
+    { kind: "file", ref: "src/auth/middleware.ts", note: "split into verify + refresh" },
+    { kind: "file", ref: "src/auth/refresh.ts", note: "new module" },
+  ],
+  { next: "Run plcode test src/auth", confidence: 0.9 },
+)
+return { agent, status: "completed", contract: c, formatted: format(c) }
+
+// Hard failure
+const c = fail("npm install failed: peer dep conflict", {
+  next: "Use --legacy-peer-deps or pin react@18.2.0",
+})
+return { agent, status: "failed", contract: c, formatted: format(c) }
+
+// Need input
+const c = needInput("Two valid refactor strategies — pick one?", {
+  next: "A: keep public API, extract helper. B: rename to match domain.",
+})
+return { agent, status: "waiting", contract: c, formatted: format(c) }
+```
+
+## Token Savings
+
+A typical un-wrapped `code_agent` result is 2-5 KB. The wrapped
+OutputContract is 200-600 chars. For a session that delegates 10
+agents, that is ~40 KB saved in the parent context.
+
+Caveman comparison: the same compression ratio the
+[cavecrew-builder](https://github.com/JuliusBrussee/caveman) hits
+with its `.`, `?.`, `!`, `!!` terminal tokens. We use full words for
+clarity in logs but the principle is identical — **first token
+branches the caller, prose is optional**.
+
+## Routing Hints
+
+When a sub-agent produces an OutputContract, the main thread
+should branch on `status`:
+
+- `OK` → continue with the next planned step.
+- `PARTIAL` → call `next` to decide; usually dispatch a follow-up
+  sub-agent (often the same one with the partial context).
+- `FAIL` → if `next` suggests a retry, do it; else surface the
+  failure to the user and stop.
+- `NEED_INPUT` → ask the user. Do not retry until the user replies.
+- `TIMEOUT` → inspect `raw` if present. If the partial result is
+  usable, mark it `PARTIAL` and continue. Else surface to the user.
+
+## Anti-Patterns
+
+- Do not include a long preamble before the status token. The
+  first character of the first line MUST be one of `OK`, `PARTIAL`,
+  `FAIL`, `NEED_INPUT`, `TIMEOUT`.
+- Do not nest OutputContract. If the contract needs to refer to
+  another agent's contract, put the referenced contract in `raw`,
+  not in `artifacts`.
+- Do not include `confidence` unless the agent actually computed
+  one. Do not default it to 0.5.
+- Do not use `OK` to mask a `FAIL` because the user expects success.
+  Honesty in the status token is the whole point of the contract.

package/.plcode/skill/experimental/algorithmic-art/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 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 [yyyy] [name of copyright owner]
+
+   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.