📦 deps(thirdparty): update snapshots

2026-07-18 00:02:59 +00:00
parent 82f7c6e56a
commit 47ce7f78dc
1446 changed files with 141041 additions and 6442 deletions
@@ -1,6 +1,6 @@
 {
  "name": "agentic-bundle-oss-maintainer",
-  "version": "14.3.1",
+  "version": "14.6.0",
  "description": "Editorial \"OSS Maintainer\" bundle for Claude Code from Agentic Awesome Skills.",
  "author": {
    "name": "sickn33 and contributors",
@@ -1,6 +1,6 @@
 {
  "name": "aasb-oss-maintainer",
-  "version": "14.3.1",
+  "version": "14.6.0",
  "description": "Install the \"OSS Maintainer\" editorial skill bundle from Agentic Awesome Skills.",
  "author": {
    "name": "sickn33 and contributors",
@@ -22,7 +22,7 @@ Before committing, always check the current branch:
 git branch --show-current
 ```

-**If you're on `main` or `master`, you MUST create a feature branch first** — unless the user explicitly asked to commit to main. Do not ask the user whether to create a branch; just proceed with branch creation. The `create-branch` skill will still propose a branch name for the user to confirm.
+**If you're on `main` or `master`, you MUST create a feature branch first** — unless the user explicitly asked to commit to main and the server permits direct pushes. A user request does not bypass protected-branch rules; when the remote rejects direct updates, use the repository's required pull-request path. Do not ask the user whether to create a branch; just proceed with branch creation. The `create-branch` skill will still propose a branch name for the user to confirm.

 Use the `create-branch` skill to create the branch. After `create-branch` completes, verify the current branch has changed before proceeding:

@@ -168,5 +168,6 @@ Reason: Caused performance regression in production.

 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.
+- Direct-to-main instructions remain subordinate to server-side branch protection and required checks.
 - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
 - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
@@ -49,9 +49,11 @@ git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null

 Or ask: "This branch split from main - is that correct?"

+Read `AGENTS.md` and maintainer documentation, then inspect effective protection for the base branch. If pull requests or required checks are enforced, mark local merge as unavailable and use the repository's guarded PR/merge workflow. In `agentic-awesome-skills`, defer maintainer merges to `antigravity-maintainer-batch-release` and `npm run merge:batch`.
+
 ### Step 3: Present Options

-Present exactly these 4 options:
+For an unprotected base branch, present exactly these 4 options:

 ```
 Implementation complete. What would you like to do?
@@ -66,10 +68,14 @@ Which option?

 **Don't add explanation** - keep options concise.

+For a protected base branch, do not offer local merge. Present only push/create PR, keep as-is, and discard, while preserving the same confirmation rule for discard.
+
 ### Step 4: Execute Choice

 #### Option 1: Merge Locally

+Use this option only after proving that repository policy and server-side protection permit local integration into the base branch. Otherwise stop and route through Option 2.
+
 ```bash
 # Switch to base branch
 git checkout <base-branch>