@yemi33/minions 0.1.2435 → 0.1.2436

package/engine/playbook.js

@@ -29,6 +29,26 @@ function getRepoHost(project) {
   return project?.repoHost || 'ado';
 }
 
+// W-ms4xyx4z — Minions attribution for generated PR descriptions.
+//
+// Every PR a Minions agent authors must say so in its description, with the
+// visible link text exactly `Minions` pointing at the canonical brand URL. The
+// guidance is host-NEUTRAL by construction: one fragment, reused verbatim by
+// both the GitHub and ADO branches of getPrCreateInstructions and exposed to
+// playbooks that author PRs outside that seam (verify.md's aggregate/E2E PR) as
+// {{pr_attribution_instructions}}. Keeping it single-sourced is what stops the
+// wording — and the link — from drifting per platform.
+const PR_ATTRIBUTION_INSTRUCTION =
+  `- Attribution (MANDATORY): the PR description must record that the PR was authored with Minions. ` +
+  `Include this line verbatim, on its own line at the end of the description body:\n` +
+  `  \`Authored with [Minions](${MINIONS_BRAND_URL}).\`\n` +
+  `  The visible link text must be exactly \`Minions\`. Attribute only PRs you author — never edit a ` +
+  `human-authored or externally linked PR's description just to add this line.`;
+
+function getPrAttributionInstruction() {
+  return PR_ATTRIBUTION_INSTRUCTION;
+}
+
 function getPrCreateInstructions(project, config) {
   const host = getRepoHost(project);
   const repoId = project?.repositoryId || '';
@@ -50,7 +70,8 @@ function getPrCreateInstructions(project, config) {
       `- Use --head to specify your feature branch name\n` +
       (createPrsAsDraft ? `- Open the PR as a DRAFT: include the \`--draft\` flag exactly as shown above (the operator has "Create PRs as draft" enabled)\n` : '') +
       `- Include a meaningful --title and body file describing the changes\n` +
-      `- If this PR contains a meaningful VISUAL/UI change (dashboard pages, slim-ux, Settings, work-item/PR/plan views, badges, layout/CSS), proactively capture + EMBED screenshots in the body — BEFORE/AFTER for fixes, AFTER-only for new UI. Publish PNGs as assets on a per-PR prerelease (\`gh release create pr-<num>-visual … --prerelease\`, or \`gh release upload … --clobber\` on re-dispatch) with a per-command \`GH_TOKEN\` for the ${org} account (NEVER \`gh auth switch\`), resolve each \`browser_download_url\`, and reference it as \`![view (after)](url)\`. Never \`git add\` a PNG; skip + record on failure. Full recipe: the "Screenshot handling" section of the PR description audit.`;
+      `- If this PR contains a meaningful VISUAL/UI change (dashboard pages, slim-ux, Settings, work-item/PR/plan views, badges, layout/CSS), proactively capture + EMBED screenshots in the body — BEFORE/AFTER for fixes, AFTER-only for new UI. Publish PNGs as assets on a per-PR prerelease (\`gh release create pr-<num>-visual … --prerelease\`, or \`gh release upload … --clobber\` on re-dispatch) with a per-command \`GH_TOKEN\` for the ${org} account (NEVER \`gh auth switch\`), resolve each \`browser_download_url\`, and reference it as \`![view (after)](url)\`. Never \`git add\` a PNG; skip + record on failure. Full recipe: the "Screenshot handling" section of the PR description audit.\n` +
+      PR_ATTRIBUTION_INSTRUCTION;
   }
   // Default: Azure DevOps — prefer `az` CLI first, ADO REST API as fallback
   const adoOrg = project?.adoOrg || '';
@@ -65,6 +86,7 @@ function getPrCreateInstructions(project, config) {
     `- Always set --target-branch to \`${mainBranch}\` (the main branch)\n` +
     (createPrsAsDraft ? `- Open the PR as a DRAFT: include \`--draft true\` exactly as shown above (the operator has "Create PRs as draft" enabled). For the REST API fallback, set \`"isDraft": true\` in the request body\n` : '') +
     `- If this PR contains a meaningful VISUAL/UI change (dashboard pages, slim-ux, Settings, work-item/PR/plan views, badges, layout/CSS), proactively capture + EMBED screenshots in the description — BEFORE/AFTER for fixes, AFTER-only for new UI. Upload via \`PUT .../pullRequests/<id>/attachments/<filename>\` with the PNG bytes and reference the returned URL. Save PNGs under \`agents/<id>/screenshots/\` only; never \`git add\` a PNG; skip + record on failure. Full recipe: the "Screenshot handling" section of the PR description audit\n` +
+    PR_ATTRIBUTION_INSTRUCTION + `\n` +
     `\n` +
     `If \`az\` is unavailable, fall back to the ADO REST API: get a token with \`az account get-access-token --resource 499b84ac-1321-427f-aa17-267ca6975798 --query accessToken -o tsv\` and \`POST .../_apis/git/repositories/${repoId}/pullrequests?api-version=7.1\` (Bearer auth). Do not use \`gh\` for Azure DevOps repositories.`;
 }
@@ -1152,6 +1174,7 @@ function renderPlaybook(type, vars) {
     ado_shared_rules: repoHost === 'ado' ? '1' : '',
     github_shared_rules: repoHost === 'github' ? '1' : '',
     pr_create_instructions: getPrCreateInstructions(renderProject, config),
+    pr_attribution_instructions: getPrAttributionInstruction(),
     pr_comment_instructions: getPrCommentInstructions(renderProject),
     pr_fetch_instructions: getPrFetchInstructions(renderProject),
     pr_vote_instructions: getPrVoteInstructions(renderProject, config),
@@ -1516,6 +1539,7 @@ module.exports = {
   getRepoHostLabel,
   getRepoHostToolRule,
   getPrCreateInstructions,
+  getPrAttributionInstruction,
   getPrCommentInstructions,
   getPrFetchInstructions,
   getPrVoteInstructions,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yemi33/minions",
-  "version": "0.1.2435",
+  "version": "0.1.2436",
   "description": "Multi-agent AI dev team that runs from ~/.minions/ — five autonomous agents share a single engine, dashboard, and knowledge base",
   "bin": {
     "minions": "bin/minions.js"

package/playbooks/verify.md

@@ -53,6 +53,8 @@ Use the template at `{{team_root}}/playbooks/templates/verify-guide.md` and clea
 
 For each project with aggregate verification changes, create or update one draft/review PR that combines the plan branches into a single reviewable diff. Reuse an existing `e2e/{{plan_slug}}` branch/PR when present. Include the plan summary, merged PRs, testing guide, and build/test status. Do not auto-complete or merge these PRs.
 
+{{pr_attribution_instructions}}
+
 Include each E2E PR in the structured completion report so the engine enrolls it in the project PR store. If manual enrollment is needed, use `POST /api/pull-requests/link`; never edit runtime state directly.
 
 ## Cross-PR Compatibility Audit