📦 deps(thirdparty): update snapshots

antigravity-awesome-skills/docs/maintainers/merge-batch.md

@@ -26,6 +26,15 @@ npm run merge:batch -- --prs 450 --reviewed-head <40-character-head-sha>
 
 Use `--dry-run` to exercise local classification without approving a run or merging. An abbreviated or stale attestation is rejected.
 
+## CI Intake Contract
+
+- Before dependent required jobs do expensive setup or wait work, `pr-policy` runs the fork-safety classifier from the exact protected-base implementation and fails an unsafe fork diff early.
+- That CI result is fail-fast evidence, not merge authority. `merge:batch` independently recomputes the complete decision from trusted `main` and remains the only command allowed to approve fork runs or merge the PR.
+- `impact_profile` is shadow-only telemetry. It never skips a required job, test, review, or merge gate.
+- Normal source PRs generate derived preview state once in `source-validation`; `artifact-preview` verifies the exact-head manifest and digest instead of generating the tree again.
+- Canonical-sync PRs use the complementary path: `pr-policy` proves the exact reproduced tree, lightweight `source-validation` records that boundary, and `artifact-preview` confirms no generated drift. Final CI and CodeQL still run on the resulting `main` commit.
+- Test timing is observational. Local deterministic sharding requires the explicit `npm run test:local -- --shard-index N --shard-count M` opt-in; required CI remains complete and unsharded.
+
 ## Happy Path
 
 `merge:batch` will:
@@ -33,6 +42,7 @@ Use `--dry-run` to exercise local classification without approving a run or merg
 - fetch the exact base/head objects and classify the complete raw Git diff
 - recompute changed-skill evidence with evaluator code materialized from the trusted `main` commit
 - reject incomplete evidence coverage, deterministic quality/security/provenance regressions, and base/head drift
+- allow only exact `source_repo` transitions recorded in the trusted protected-base provenance exception ledger; unrecorded or malformed transitions still fail closed
 - for external PRs, poll for asynchronously-created fork runs and approve only runs waiting on `action_required` when every path, mode, object, size, and workflow identity is allowlisted
 - for sensitive same-repository source changes, allow the guarded exception only when the PR author is the repository owner and the exact full head SHA is attested; collaborator-authored sensitive changes fail closed under the external safety policy
 - wait for the latest required checks bound to the exact head SHA
@@ -46,12 +56,14 @@ Use `--dry-run` to exercise local classification without approving a run or merg
 
 ## What It Does Not Automate
 
+- PR-body rewriting or normalization
+- closing or reopening PRs to refresh metadata or workflow runs
 - conflict resolution on the PR branch
 - manual judgment for risky skill changes
 - semantic review when the distinct `manual-review-required` check is present; the review fingerprint covers the complete nearest skill directory, including nested examples, scripts, lockfiles, references, and assets
 - README community-source audits when the source metadata is ambiguous
 - fork-only edge cases that require contributor coordination outside GitHub permissions
-- base-branch drift: stale evidence is discarded and the batch must be rerun
+- base-branch or head drift: stale evidence is discarded, the checkout must be refreshed to the current `origin/main`, and the batch must be rerun; there is no automatic retry
 - auto-merge and merge-queue enrollment; deferred merge state is rejected
 
 ## When To Stop