allye-opencode 1.7.0 → 1.8.0

package/README.md

@@ -9,11 +9,11 @@ An [OpenCode](https://opencode.ai) plugin that registers 6 specialized Allye age
 - **Allye Review** — code review with full context
 - **Allye Deliver** — finalizes delivery, closes stories, updates docs
 
-It also injects live Allye account/session context into every conversation via a system-prompt transform hook.
+Account context is loaded through the configured `allye` MCP server, so OpenCode owns OAuth credentials and refresh.
 
 ## Installation
 
-This package is not typically installed standalone. It's installed automatically as part of the main [`allye-plugin`](https://github.com/allye-app/allye-plugin) install flow (`install.sh`), which detects OpenCode and adds `allye-opencode` to the `plugin` array in your `opencode.json` alongside the Allye MCP server configuration.
+This package is not typically installed standalone. Add it with the Allye MCP server by following the main plugin's OpenCode installation guide. The repository installer intentionally leaves shared runtime configuration unchanged unless an API-backed ownership operation authorizes the write.
 
 If you do need to add it manually, add it to the `plugin` array in your OpenCode config:
 

package/dist/index.js

@@ -109,13 +109,13 @@ Before starting meaningful work, search for team-specific skills when Allye MCP
 If NO relevant skills are found for your current work:
 1. Inform the user that no team standards were found for this type of work
 2. Suggest creating them: "I recommend creating standard templates for your team. Want to set them up now?"
-3. If the user agrees, ask which scope they want:
+3. If the user agrees, ask which internal write scope they want:
    - **personal** \u2014 only for them
-   - **team** \u2014 for their current team
-   - **organization** \u2014 for the entire organization
-   - **marketplace** \u2014 public for all Allye users
+   - **team** \u2014 for their selected team; membership is read-only and writes require owner/admin/manage or an active maintainer grant
+   - **organization** \u2014 for the authorized organization; writes require owner/admin/manage authority
+   - **Only personal, team, and organization are valid scopes** \u2014 retired public-scope requests return the API diagnostic unchanged
 4. Guide them through defining the template interactively
-5. Save it as a skill via \`skill_create\` with the chosen scope
+5. Save it as a skill via \`skill_create\` with the chosen internal scope. Use \`skill_resolve\` for canonical \`team > organization > personal\` resolution. For forks, pass an explicit \`skill_slug\` after a \`409 Conflict\` and preserve selected-team context; never silently suffix or overwrite a key.
 
 This creates a virtuous cycle \u2014 the more the team uses Allye, the more standards accumulate.
 Skills may be in any language. Adapt accordingly.
@@ -2039,11 +2039,11 @@ Before creating ANY work item, you MUST search for team standards:
 2. Ask: "Would you like to create them now? I can help you define templates for the item types you use."
 3. If yes, ask which scope:
    - **personal** \u2014 only for you
-   - **team** \u2014 for the current team
-   - **organization** \u2014 for the entire organization
-   - **marketplace** \u2014 public for all Allye users
+   - **team** \u2014 for the current selected team (requires owner/admin/manage/grant authority)
+   - **organization** \u2014 for the entire organization (requires owner/admin/manage authority)
+   - **Only personal, team, and organization are valid scopes** \u2014 use the internal library
 4. Guide them through defining each template interactively
-5. Save each as a skill via \`skill_create\` with the chosen scope
+5. Save each as a skill via \`skill_create\` with the chosen internal scope; use canonical \`team > organization > personal\` resolution and never silently suffix a slug
 
 **Do NOT assume the team uses any specific item types.** Some teams don't use stories, some don't use subtasks, some use spikes. Discover what the team uses by:
 - Checking existing work items via \`work_list\`
@@ -2377,9 +2377,9 @@ Before writing ANY code, you MUST search for project-specific standards:
 **If NO development standards are found:**
 1. Inform the user: "I didn't find development standards or coding conventions for your project."
 2. Suggest: "Would you like to create them? This helps maintain consistency across the team."
-3. If yes, ask scope (personal/team/organization/marketplace)
+3. If yes, ask scope (personal/team/organization only; the internal library is the only Skills source)
 4. Guide them through defining standards based on the project's existing code patterns
-5. Save as skills via \`skill_create\`
+5. Confirm selected-team context for team writes and save as skills via \`skill_create\`; owner/admin/maintainer policy is enforced server-side
 
 **Understand the project first:**
 - Read existing code to understand patterns BEFORE writing new code
@@ -2486,9 +2486,9 @@ Before reviewing ANY code, you MUST search for team review standards:
 **If NO review standards are found:**
 1. Inform the user: "I didn't find code review standards for your team."
 2. Suggest: "Would you like to create a review checklist? This ensures consistent reviews across the team."
-3. If yes, ask scope (personal/team/organization/marketplace)
+3. If yes, ask scope (personal/team/organization only; the internal library is the only Skills source)
 4. Guide them through defining review criteria based on the project's needs
-5. Save as a skill via \`skill_create\`
+5. Save as a skill via \`skill_create\` after confirming selected-team context and server-side owner/admin/maintainer authority
 `.trim();
 var REVIEW_IDENTITY = `
 ## Your Role
@@ -2567,9 +2567,9 @@ Before closing ANY story or updating documentation, you MUST search for team del
 **If NO delivery standards are found:**
 1. Inform the user: "I didn't find delivery or documentation standards for your team."
 2. Suggest: "Would you like to create them? This ensures consistent documentation and delivery process."
-3. If yes, ask scope (personal/team/organization/marketplace)
+3. If yes, ask scope (personal/team/organization only; the internal library is the only Skills source)
 4. Guide them through defining the standards
-5. Save as a skill via \`skill_create\`
+5. Save as a skill via \`skill_create\` after confirming selected-team context and server-side owner/admin/maintainer authority
 `.trim();
 var DELIVER_IDENTITY = `
 ## Your Role
@@ -2637,94 +2637,6 @@ var agents = {
   "allye-deliver": allyeDeliverAgent
 };
 
-// src/context.ts
-import { readFileSync, existsSync } from "fs";
-import { join } from "path";
-import { homedir } from "os";
-var MCP_URL = "https://mcp.allye.app/jsonrpc";
-var cachedContext = null;
-var cacheTimestamp = 0;
-var CACHE_TTL = 5 * 60 * 1000;
-function getAllyePat() {
-  const envPat = process.env.ALLYE_PAT || process.env.ALLYE_PAT_TOKEN;
-  if (envPat)
-    return envPat;
-  try {
-    const configPaths = [
-      join(process.cwd(), "opencode.json"),
-      join(process.env.XDG_CONFIG_HOME || join(homedir(), ".config"), "opencode", "opencode.json")
-    ];
-    for (const configPath of configPaths) {
-      if (existsSync(configPath)) {
-        const config = JSON.parse(readFileSync(configPath, "utf-8"));
-        const allyeMcp = config?.mcp?.["allye-mcp"];
-        if (allyeMcp?.headers?.Authorization) {
-          return allyeMcp.headers.Authorization.replace("Bearer ", "");
-        }
-      }
-    }
-  } catch {}
-  return null;
-}
-async function callInitialize(pat) {
-  try {
-    const response = await fetch(MCP_URL, {
-      method: "POST",
-      headers: {
-        "Content-Type": "application/json",
-        Authorization: `Bearer ${pat}`
-      },
-      body: JSON.stringify({
-        jsonrpc: "2.0",
-        id: 1,
-        method: "tools/call",
-        params: {
-          name: "initialize",
-          arguments: {
-            action: "init",
-            include_user_docs: true
-          }
-        }
-      }),
-      signal: AbortSignal.timeout(1e4)
-    });
-    if (!response.ok)
-      return null;
-    const data = await response.json();
-    const text = data?.result?.content?.[0]?.text;
-    return text || null;
-  } catch {
-    return null;
-  }
-}
-async function fetchAllyeContext() {
-  if (cachedContext && Date.now() - cacheTimestamp < CACHE_TTL) {
-    return cachedContext;
-  }
-  const pat = getAllyePat();
-  if (!pat)
-    return null;
-  const initResult = await callInitialize(pat);
-  if (!initResult)
-    return null;
-  const context = `<allye-context>
-# Allye User Context (auto-loaded)
-
-${initResult}
-
-## Instructions
-
-You are connected to the Allye platform. The user context above was loaded automatically.
-- You already know who the user is \u2014 greet them by their preferred name
-- Search for relevant memories before starting work
-- Load team-specific skills via \`skill_list\` for the current task
-- Save session state before ending
-</allye-context>`;
-  cachedContext = context;
-  cacheTimestamp = Date.now();
-  return context;
-}
-
 // src/index.ts
 var AllyePlugin = async () => ({
   config: async (config) => {
@@ -2732,12 +2644,6 @@ var AllyePlugin = async () => ({
       ...config.agent,
       ...agents
     };
-  },
-  "experimental.chat.system.transform": async (_input, output) => {
-    const context = await fetchAllyeContext();
-    if (context) {
-      output.system.push(context);
-    }
   }
 });
 export {

package/package.json

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