allye-opencode 1.6.0 → 1.6.1

package/dist/index.js

@@ -41,15 +41,16 @@ The conversation itself is the primary signal, and it overrides everything else
 All responses, questions, suggestions, and confirmations must be in the user's language. If the user switches language mid-conversation, follow them.
 `.trim();
 var ALLYE_INIT_PROTOCOL = `
-## Allye Initialization (mandatory)
+## Allye Context (adaptive)
 
-At the START of every conversation, you MUST:
-
-1. **Call \`initialize\`** (action: \`init\`) to load your user context, team info, and core documents. This is mandatory.
-2. **Check active team** \u2014 If the response shows the user belongs to multiple teams and no team is active, ask which team they want to work with and call \`team_switch\`. Do not proceed until a team is selected.
+When Allye MCP is available and the work benefits from durable context, call \`initialize\` (action: \`init\`) to load user context, team info, and core documents.
+If initialization fails or is unavailable, state the limitation and continue locally unless Allye is required.
+If multiple teams exist without an active selection, ask before team-scoped operations; non-team-scoped work may continue.
 `.trim();
 var MEMORY_SEARCH_PROTOCOL = `
-## Memory Search (mandatory at start)
+## Memory Search (proportional)
+
+For consequential, multi-step, resumed, or team-scoped work, search relevant memories before acting. For short, low-risk, local work, memory search may be skipped. Never claim a search was performed when Allye is unavailable.
 
 After initialization, search for relevant memories:
 
@@ -76,7 +77,9 @@ Relation types: \`similar | extends | caused_by | supersedes | contradicts | dep
 If graph traversal times out (408): reduce depth, add relation_types filter.
 `.trim();
 var MEMORY_SAVE_PROTOCOL = `
-## Memory Save (mandatory at end)
+## Memory Save (when useful)
+
+For consequential sessions or durable decisions, save session state before ending. Skip trivial local work. If persistence is unavailable, report that continuity was not saved.
 
 Before ending your work, save session state:
 
@@ -95,9 +98,9 @@ Also save memories mid-conversation when:
 - A blocker is identified
 `.trim();
 var DYNAMIC_SKILL_LOADING = `
-## Dynamic Skill Loading (mandatory before main work)
+## Dynamic Skill Loading (when relevant)
 
-Before starting your main work, you MUST search for team-specific skills:
+Before starting meaningful work, search for team-specific skills when Allye MCP is available and the task benefits from team standards:
 
 1. Call \`skill_list\` with queries matching your task domain (e.g., "planning", "code review", "development standards", "story template", "task template")
 2. For each relevant skill found, call \`skill_get\` to read its full content
@@ -118,12 +121,15 @@ This creates a virtuous cycle \u2014 the more the team uses Allye, the more stan
 Skills may be in any language. Adapt accordingly.
 `.trim();
 var WORKFLOW_GATES = `
-## Non-Negotiable Rules
-
-1. **No implementation without tasks.** Do not write code for a story that has no tasks. Run planning first.
-2. **No skipping the discussion phase.** When planning tasks, identify gray areas and present options before creating tasks. Capture locked decisions as memories.
-3. **No status changes without work.** Do not move an item to "done" unless the work is completed and verified.
-4. **TDD when applicable.** If you can write \`expect(fn(input)).toBe(output)\` before writing \`fn\`, you MUST write the test first. If not (UI, infra), test after \u2014 but always test.
+## Adaptive Checkpoints and Guardrails
+
+Choose the smallest useful loop: intent \u2192 context \u2192 research (optional) \u2192 consent \u2192 action \u2192 verification \u2192 persistence (optional).
+- Recommend tasks for meaningful, multi-step, shared, delegated, or review-heavy work; create them only after approval.
+- For an explicitly approved no-task path, keep scope visible and verify proportionally.
+- Ask before consequential mutations, status changes, publication, deployment, or broad scope.
+- Surface ambiguity that changes scope, risk, or architecture; use reversible defaults for minor details.
+- Use TDD when deterministic behavior can be specified first; otherwise test after implementation, but do not skip verification.
+- Claim completion only from actual verification evidence, distinguishing implementation from review or deployment.
 `.trim();
 var TOOLS_QUICKREF = `
 ## Allye MCP Tools

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "allye-opencode",
-  "version": "1.6.0",
+  "version": "1.6.1",
   "description": "Allye multi-agent plugin for OpenCode — planning, building, reviewing, and delivering with structured workflows",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",