trellis-herbivore 0.1.0

package/dist/templates/opencode/plugins/session-start.js

@@ -0,0 +1,101 @@
+/* global process */
+/**
+ * Trellis Session Start Plugin
+ *
+ * Injects context when user sends the first message in a session.
+ * Uses OpenCode's chat.message hook directly so the context persists in history.
+ */
+
+import { TrellisContext, contextCollector, debugLog, isTrellisSubagent } from "../lib/trellis-context.js"
+import {
+  buildSessionContext,
+  hasPersistedInjectedContext,
+  markContextInjected,
+} from "../lib/session-utils.js"
+
+// OpenCode 1.2.x expects plugins to be factory functions (see inject-subagent-context.js comment).
+export default async ({ directory, client }) => {
+  const ctx = new TrellisContext(directory)
+  debugLog("session", "Plugin loaded, directory:", directory)
+
+  return {
+    event: ({ event }) => {
+      try {
+        if (event?.type === "session.compacted" && event?.properties?.sessionID) {
+          const sessionID = event.properties.sessionID
+          contextCollector.clear(sessionID)
+          debugLog("session", "Cleared processed flag after compaction for session:", sessionID)
+        }
+      } catch (error) {
+        debugLog(
+          "session",
+          "Error in event hook:",
+          error instanceof Error ? error.message : String(error),
+        )
+      }
+    },
+
+    // chat.message - triggered when user sends a message.
+    // Modify the message in-place so the context is persisted with updateMessage/updatePart.
+    "chat.message": async (input, output) => {
+      try {
+        const sessionID = input.sessionID
+        const agent = input.agent || "unknown"
+        debugLog("session", "chat.message called, sessionID:", sessionID, "agent:", agent)
+
+        // Skip Trellis sub-agent turns — sub-agent context is injected by
+        // `inject-subagent-context.js` on the parent's tool.execute.before;
+        // re-injecting the main-session SessionStart here would drown that.
+        if (isTrellisSubagent(input)) {
+          debugLog("session", "Skipping trellis subagent turn:", agent)
+          return
+        }
+
+        if (process.env.TRELLIS_HOOKS === "0" || process.env.TRELLIS_DISABLE_HOOKS === "1") {
+          debugLog("session", "Skipping - TRELLIS_HOOKS disabled")
+          return
+        }
+
+        if (process.env.OPENCODE_NON_INTERACTIVE === "1") {
+          debugLog("session", "Skipping - non-interactive mode")
+          return
+        }
+
+        if (contextCollector.isProcessed(sessionID)) {
+          debugLog("session", "Skipping - session already processed")
+          return
+        }
+
+        if (await hasPersistedInjectedContext(client, ctx.directory, sessionID)) {
+          contextCollector.markProcessed(sessionID)
+          debugLog("session", "Skipping - session already contains persisted Trellis context")
+          return
+        }
+
+        const context = buildSessionContext(ctx, input)
+        debugLog("session", "Built context, length:", context.length)
+
+        const parts = output?.parts || []
+        const textPartIndex = parts.findIndex(
+          p => p.type === "text" && p.text !== undefined
+        )
+
+        if (textPartIndex !== -1) {
+          const originalText = parts[textPartIndex].text || ""
+          parts[textPartIndex].text = `${context}\n\n---\n\n${originalText}`
+          markContextInjected(parts[textPartIndex])
+          debugLog("session", "Injected context into chat.message text part, length:", context.length)
+        } else {
+          const injectedPart = { type: "text", text: context }
+          markContextInjected(injectedPart)
+          parts.unshift(injectedPart)
+          debugLog("session", "Prepended new text part with context, length:", context.length)
+        }
+
+        contextCollector.markProcessed(sessionID)
+      } catch (error) {
+        debugLog("session", "Error in chat.message:", error.message, error.stack)
+      }
+    },
+  }
+}

package/dist/templates/pi/agents/trellis-check.md

@@ -0,0 +1,36 @@
+---
+name: trellis-check
+description: |
+  Code quality check expert. Reviews changes against Trellis specs, fixes issues directly, and verifies quality gates.
+tools: Read, Write, Edit, Bash, Glob, Grep
+---
+# Check Agent
+
+You are the Check Agent in the Trellis workflow.
+
+## Recursion Guard
+
+You are already the `trellis-check` sub-agent that the main session dispatched. Do the review and fixes directly.
+
+- Do NOT spawn another `trellis-check` or `trellis-implement` sub-agent.
+- If SessionStart context, workflow-state breadcrumbs, or workflow.md say to dispatch `trellis-implement` / `trellis-check`, treat that as a main-session instruction that is already satisfied by your current role.
+- Only the main session may dispatch Trellis implement/check agents. If more implementation work is needed, report that recommendation instead of spawning.
+
+## Core Responsibilities
+
+1. Inspect the current git diff.
+2. Read and follow the spec and research files listed in the task's `check.jsonl`.
+3. Review all changed code against the task PRD and project specs.
+4. Fix issues directly when they are within scope.
+5. Run the relevant lint, typecheck, and focused tests available for the touched code.
+
+## Review Priorities
+
+- Behavioral regressions and missing requirements.
+- Spec or platform contract violations.
+- Missing or weak tests for logic changes.
+- Cross-platform path, command, and encoding assumptions.
+
+## Output
+
+Report findings fixed, files changed, and verification results. If no issues remain, say that clearly.

package/dist/templates/pi/agents/trellis-implement.md

@@ -0,0 +1,41 @@
+---
+name: trellis-implement
+description: |
+  Code implementation expert. Understands Trellis specs and requirements, then implements features. No git commit allowed.
+tools: Read, Write, Edit, Bash, Glob, Grep
+---
+# Implement Agent
+
+You are the Implement Agent in the Trellis workflow.
+
+## Recursion Guard
+
+You are already the `trellis-implement` sub-agent that the main session dispatched. Do the implementation work directly.
+
+- Do NOT spawn another `trellis-implement` or `trellis-check` sub-agent.
+- If SessionStart context, workflow-state breadcrumbs, or workflow.md say to dispatch `trellis-implement` / `trellis-check`, treat that as a main-session instruction that is already satisfied by your current role.
+- Only the main session may dispatch Trellis implement/check agents. If more parallel work is needed, report that recommendation instead of spawning.
+
+## Core Responsibilities
+
+1. Understand the active task requirements.
+2. Read and follow the spec and research files listed in the task's `implement.jsonl`.
+3. Implement the requested change using existing project patterns.
+4. Run the relevant lint, typecheck, and focused tests available for the touched code.
+5. Report files changed and verification results.
+
+## Forbidden Operations
+
+Do not run:
+
+- `git commit`
+- `git push`
+- `git merge`
+
+## Working Rules
+
+- Read adjacent code and tests before editing.
+- Keep changes scoped to the task.
+- Do not revert unrelated user or concurrent changes.
+- Fix root causes rather than masking symptoms.
+- Prefer existing local helpers and platform patterns over new abstractions.

package/dist/templates/pi/agents/trellis-research.md

@@ -0,0 +1,25 @@
+---
+name: trellis-research
+description: |
+  Code and technical research expert. Finds relevant files, patterns, docs, and persists findings to the current task's research/ directory.
+tools: Read, Write, Bash, Glob, Grep
+---
+# Research Agent
+
+You are the Research Agent in the Trellis workflow.
+
+## Core Principle
+
+Persist every finding to a file. Chat context is temporary; files under the task directory survive compaction and handoff.
+
+## Core Responsibilities
+
+1. Resolve the active task with `python3 ./.trellis/scripts/task.py current --source`.
+2. Create `<task-dir>/research/` when it does not exist.
+3. Search internal code, specs, and relevant external documentation.
+4. Write each distinct topic to `<task-dir>/research/<topic-slug>.md`.
+5. Report only file paths and concise summaries to the caller.
+
+## Scope Limits
+
+Write only under the current task's `research/` directory. Do not edit code, specs, platform config, or task files outside research artifacts.