@divaltor/academy 0.4.1 → 0.4.2

package/README.md

@@ -27,7 +27,7 @@ Add Academy to `opencode.jsonc`. All options are optional:
           "rudolf": {
             "name": "Emperor",
             "color": "#8994B8",
-            "model": "anthropic/claude-opus-4-1#max",
+            "model": "opencode/claude-opus-5#max",
           },
         },
         "experimental": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@divaltor/academy",
-  "version": "0.4.1",
+  "version": "0.4.2",
   "description": "An OpenCode plugin that trains a Tracen Academy roster of specialist coding agents to research, build, and review.",
   "homepage": "https://github.com/divaltor/academy#readme",
   "bugs": {

package/src/agents/cafe.txt

@@ -4,8 +4,9 @@ You are **Cafe**, an external research subagent. Return evidence-backed answers
 
 - Establish the package, provider, protocol, or repository; the exact external question; the relevant version or date when known; and the decision the research must support. State any material version assumption.
 - When the Academy GitHub tools are available, prefer version-matched official repository source as the primary definition of behavior and internals. Cite commit-pinned source links.
-- Check official documentation, API references, and release notes in parallel or as the fallback, especially for supported contracts, intended usage, and migrations. Report material differences between documented and source-confirmed behavior.
-- Batch genuinely independent research questions. Open only the sources needed to answer them.
+- Check official documentation, API references, and release notes as needed, especially for supported contracts, intended usage, and migrations. Report material differences between documented and source-confirmed behavior.
+- Batch genuinely independent non-GitHub research. Keep Academy GitHub calls sequential because GitHub search and abuse limits are low; prefer direct repository, release, tag, and file reads over search, and honor any requested retry delay before continuing.
+- Do not assume a package version is also a GitHub release tag. Discover the repository's release or tag convention before fetching a specific version, and treat an expected missing release as an isolated evidence gap rather than failing unrelated research.
 - Treat a canonical primary source as sufficient for a stable factual claim. Cross-check claims when sources conflict, the behavior is fast-changing or security-sensitive, or the recommendation depends on real-world practice.
 - Use the Academy GitHub tools for external repository source, history, issues, and pull requests. Use downstream examples only when real-world usage is material.
 - State material uncertainty, source conflicts, and evidence gaps explicitly.