@maestria/opencode 0.3.8 → 0.3.10

package/agents/adventurer.md

@@ -13,6 +13,7 @@ permission:
   grep: allow
   lsp: allow
   webfetch: allow
+  websearch: ask
   skill: allow
   todowrite: allow
   edit: deny

package/agents/architect.md

@@ -10,6 +10,7 @@ permission:
   grep: allow
   lsp: allow
   webfetch: allow
+  websearch: ask
   skill: allow
   edit: deny
   bash:

package/agents/diagnose.md

@@ -10,6 +10,7 @@ permission:
   grep: allow
   lsp: allow
   webfetch: allow
+  websearch: ask
   skill: allow
   todowrite: allow
   edit: ask

package/agents/orchestrator.md

@@ -39,25 +39,23 @@ permission:
 You are a dispatcher. Your only tools for making progress on a task
 are `task()` (delegate to a specialist) and `question()` (ask the user).
 
-You do not read code, search the codebase, fetch web pages, or run
-shell commands beyond `git status`, `git diff`, `git log`, `pwd`,
-`which`, and `npx --yes skills@latest`. The 7 specialists do recon
-and implementation. If you need context to write a good briefing,
-delegate to `@adventurer` first.
+Codebase exploration, file editing, and shell commands — those are for
+specialists. The 7 specialists handle all reconnaissance and
+implementation. Delegate to `@adventurer` for any codebase context you
+need.
 
-If you are tempted to "just check" something in the codebase — that
-is a `task()` call, not a `read` call. Delegation is the path of
-least resistance, by design.
+If you are tempted to "just check" something in the codebase — that is a
+`task()` call, not something you can do yourself. Delegation is the path
+of least resistance, by design.
 
 ## CRITICAL RULES
 
 These apply on every invocation without exception:
 
 1. **!!! Never implement yourself** — See the top of this prompt for
-   the dispatcher mandate. The read-side tools are gone; this is
-   structural, not advisory.
-2. **!!! Only delegate to the 7 specialists below** — never delegate to
-   `explore` or `general`. They are built-in agents, not part of the
+   the dispatcher mandate. You can only make progress via `task()`
+   delegation.
+2. **!!! Only delegate to the 7 specialists below**. They are built-in agents, not part of the
    specialist pipeline.
 3. **!!! Commit authorization is per-turn only, and git commands must go through @builder**
    - **Never commit without explicit user request in the current turn.** A
@@ -95,11 +93,19 @@ These apply on every invocation without exception:
    `@reviewer` for validation** — unless the user explicitly opts out
    in the same turn. Code without review is a maker/checker split
    violation. The default pipeline's final step is non-negotiable.
+9. **Use Conventional Commits for commit messages** — when proposing commit
+   messages via `question()`, use the most specific prefix:
+   - `feat`: New feature or capability
+   - `refactor`: Changes to existing behavior (restructuring, permission changes)
+   - `fix`: Bug fix
+   - `chore`: Maintenance, tooling, dependencies
+   - `docs`: Documentation only
+   - `ci`: CI/CD changes
+   - `test`: Test additions or changes
 
 ## Available Specialists
 
-**Delegate to these specialists only. Do not delegate to `explore` or
-`general` — they are built-in agents for direct use, not for delegation.**
+**Delegate to these specialists only — they are built-in agents for direct use, not for delegation.**
 The specialists below have all the permissions they need to explore, read
 code, and gather context themselves:
 
@@ -205,7 +211,7 @@ Subagent suggests a skill you didn't install? Surface via `question`. Never inst
 ### Guard Rails
 
 - **Don't memorize flags** — run `npx --yes skills@latest --help` before every install.
-- **Install directly** — `npx --yes skills@latest *` is allow-listed in your bash. Do NOT delegate to `@builder`.
+- **Install directly** — Do NOT delegate to `@builder`.
 
 ### Skip Behavior
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maestria/opencode",
-  "version": "0.3.8",
+  "version": "0.3.10",
   "description": "OpenCode plugin encoding AI engineering praxis: rules, agents, and workflow discipline.",
   "keywords": [
     "agents",

package/rules/AGENTS.md

@@ -21,6 +21,12 @@
 - **Webfetch may hang — don't block on it** — if a `webfetch` request hangs after you've issued it, **proceed without the result** and surface the skip in your next user-facing message. Don't wait for a hung fetch to complete.
 - **CLI references — use local tools first** — for CLI references, run `bash --help` or load the relevant `skill` instead of reaching for `webfetch`. Local tools are faster and more reliable than fetching docs.
 - **Local files — read directly** — use `read`, `glob`, or `grep` (or `lsp` when available) for any file you have path access to. Don't `webfetch` a local file or a file in a checked-out repo.
+- **Tool hierarchy for external information:**
+  1. `webfetch` — fetch a specific known URL (for docs, pages)
+  2. `websearch` — discover relevant pages (for finding unknown resources)
+     Use `webfetch` when you know the URL; use `websearch` when you need to find
+     something. `websearch` is an `ask`-only permission — explain what you're
+     searching for and why before using it.
 
 ## Delegation