allye-opencode 1.7.0 → 1.7.1

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
+   - **Marketplace is not a write scope** \u2014 it is legacy read-only browsing/source material
 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)
+   - **Marketplace is not a write scope** \u2014 it is legacy read-only browsing/source material
 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; Marketplace is legacy read-only browsing/source material, never a write destination)
 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; Marketplace is legacy read-only browsing/source material, never a write destination)
 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; Marketplace is legacy read-only browsing/source material, never a write destination)
 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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "allye-opencode",
-  "version": "1.7.0",
+  "version": "1.7.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",