yaga-cli 0.2.1__tar.gz → 0.3.0__tar.gz

{yaga_cli-0.2.1 → yaga_cli-0.3.0}/.github/workflows/ci.yml

@@ -25,7 +25,7 @@ jobs:
           ref: ${{ github.event_name == 'pull_request' && github.event.pull_request.head.sha || github.sha }}
           fetch-depth: 0
           persist-credentials: false
-      - uses: astral-sh/setup-uv@c18668ad3cf93ea998bef934396af7bb5c839dc7 # v10.2.0
+      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884 # v10.3.0
         with:
           enable-cache: true
           version: "0.13.0"
@@ -150,7 +150,7 @@ jobs:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:
           persist-credentials: false
-      - uses: astral-sh/setup-uv@c18668ad3cf93ea998bef934396af7bb5c839dc7 # v10.2.0
+      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884 # v10.3.0
         with:
           enable-cache: true
           version: "0.13.0"

{yaga_cli-0.2.1 → yaga_cli-0.3.0}/.github/workflows/commit-adoption-qualification.yml

@@ -15,7 +15,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        scenario: [valid, invalid, stale, nondefault, nondefault-invalid, advanced-main, typos-valid, typos-message, typos-title, typos-missing, typos-broken, typos-bot, typos-author-bot, typos-author-unlisted, typos-author-stale]
+        scenario: [valid, invalid, stale, nondefault, nondefault-invalid, advanced-main, typos-valid, typos-message, typos-title, typos-missing, typos-broken, typos-bot, typos-bot-unsigned, typos-author-bot, typos-author-unlisted, typos-author-stale]
     steps:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:

{yaga_cli-0.2.1 → yaga_cli-0.3.0}/.github/workflows/commit-quality.yml

@@ -33,7 +33,7 @@ jobs:
           ref: ${{ github.event_name == 'pull_request' && github.event.pull_request.head.sha || github.sha }}
           fetch-depth: 0
           persist-credentials: false
-      - uses: astral-sh/setup-uv@c18668ad3cf93ea998bef934396af7bb5c839dc7 # v10.2.0
+      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884 # v10.3.0
         with:
           enable-cache: true
           version: "0.12.7"

{yaga_cli-0.2.1 → yaga_cli-0.3.0}/.github/workflows/docs.yml

@@ -30,7 +30,7 @@ jobs:
         with:
           persist-credentials: false
       - uses: actions/configure-pages@45bfe0192ca1faeb007ade9deae92b16b8254a0d # v6
-      - uses: astral-sh/setup-uv@c18668ad3cf93ea998bef934396af7bb5c839dc7 # v10.2.0
+      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884 # v10.3.0
         with:
           version: "0.12.7"
       - run: uv sync --frozen --group dev --python 3.12

{yaga_cli-0.2.1 → yaga_cli-0.3.0}/.github/workflows/release.yml

@@ -32,7 +32,7 @@ jobs:
         run: |
           test "$(git rev-parse HEAD)" = "$EVENT_SHA"
           git merge-base --is-ancestor HEAD "refs/remotes/origin/$DEFAULT_BRANCH"
-      - uses: astral-sh/setup-uv@c18668ad3cf93ea998bef934396af7bb5c839dc7 # v10.2.0
+      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884 # v10.3.0
         with:
           version: "0.12.7"
           enable-cache: false
@@ -51,14 +51,14 @@ jobs:
         run: cargo install typos-cli --version 1.49.0 --locked
       - name: Run the full gate and retain its validated distributions
         run: uv run --frozen make ci BUILD_ARGS="--output-dir dist"
-      - uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
+      - uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7.0.2
         with:
           name: distributions
           path: dist/
           if-no-files-found: error
           retention-days: 7
 
-      - uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
+      - uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7.0.2
         with:
           name: release-notes
           path: release-notes.md
@@ -77,7 +77,7 @@ jobs:
     permissions:
       id-token: write
     steps:
-      - uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
+      - uses: actions/download-artifact@9000827ccba6bdab643e8b6fd33ac0654aef8333 # v8.0.2
         with:
           name: distributions
           path: dist/
@@ -92,11 +92,11 @@ jobs:
     permissions:
       contents: write
     steps:
-      - uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
+      - uses: actions/download-artifact@9000827ccba6bdab643e8b6fd33ac0654aef8333 # v8.0.2
         with:
           name: distributions
           path: dist/
-      - uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
+      - uses: actions/download-artifact@9000827ccba6bdab643e8b6fd33ac0654aef8333 # v8.0.2
         with:
           name: release-notes
           path: release-notes/

{yaga_cli-0.2.1 → yaga_cli-0.3.0}/AGENTS.md

@@ -27,9 +27,19 @@ Agent review gate is the public review contract. Its current provider adapter re
   read-only commit Action after complete event, runner-context, checkout, configuration, and range
   validation. Require an exact strictly parsed PR author login `dependabot[bot]`, type `Bot`, and
   bounded positive ID. Never infer trusted bot identity from Git author/committer data, messages,
-  titles, branches, actors, or footers. Emit skipped title and commit results with the stable
-  `Dependabot pull request` reason; ordinary commit/repository checks and every other provider keep
-  running.
+  titles, branches, actors, or footers. Narrow this already eligible quality exemption per commit
+  using bounded exact author/committer metadata compatibility. Keep the schema-v1 boolean
+  `dependabot-require-github-signature` defaulted to `true`: additionally verify each skipped
+  commit's exact object bytes offline against the pinned GitHub signing key using a trusted
+  bounded `gpgv` process and private keyring. Missing, failed, unsupported, or over-budget
+  verification runs normal checks. `false` retains the forgeable per-commit metadata filter only.
+  Ordinary human additions and human rebases must be checked, and mixed PR titles/proposed
+  messages must be checked. The shared GitHub key is not exclusive Dependabot identity; never
+  use a Signed-off-by footer as proof, query a live badge, fetch keys, or import REST/token code.
+  The separate `skip-pull-request-authors` list remains a broad independent explicit exemption;
+  do not turn this option into generic bot identity configuration. Preserve the complete selected
+  SHA set and stable `Dependabot pull request` skip reason; ordinary commit/repository checks and
+  every other provider keep running.
 - Keep `scope-policy-by-type` as an empty-default schema-v1 mapping with at most 128 safe,
   case-insensitively unique type keys and closed presence-policy values. Overrides replace the
   global scope policy for full commits and PR titles; `scope-case` and `allowed-scopes` remain
@@ -100,6 +110,25 @@ Agent review gate is the public review contract. Its current provider adapter re
   Git paths, visible gitlink changes, disabled rename/external-diff/textconv behavior,
   unique-pattern caching, and the shared 10,000,000-unit matcher-work ceiling. Keep it out of both
   Action import graphs.
+- Keep test planning installed-only under `src/yaga/test_planning/`. `test policy check` requires
+  one explicit file and no Git access. `test plan` requires explicit policy, profile, and exactly
+  one range or revision; revision-only planning requires a full profile. Never discover policy,
+  infer HEAD/event/branch/worktree state, fetch, or execute bindings. Keep the pure planner free
+  of I/O and collect Git sources through the shared bounded runtime and neutral changed-path
+  reader. Require complete range history, one three-dot merge base, and exact endpoint/comparison/
+  execution identities; allow shallow revision-only plans with the selected commit/tree present.
+  Reject graft overlays before and after collection. Preserve version-one semantic/envelope
+  contracts, exact policy-byte SHA-256, optional binding identity, canonical plan digests, complete
+  JSON within 4 MiB, at most 256 human reasons with exact omitted counts, and exits 0/2 only.
+  Planning never claims tests passed and stays outside repository plans and both Action graphs.
+  Keep executor handoff pure and installed-only: a complete fixed registry maps every suite exactly
+  once, preserves all variants and required capabilities, and binds executor-definition hashes.
+  Require non-null matching binding identity and independent expected policy/commit/tree identities.
+  Preserve version-one registry/handoff documents, complete 4 MiB bounded output, prerequisite
+  order, and one dispatch per suite even for a matrix. No commands or receipt evaluation enter this
+  API. Consumer adapters own real capability checks, execution, cancellation, acceptance, and cleanup.
+  Shadow jobs remain advisory and cannot change or cancel required CI. Measure first; set the
+  feedback-time adoption threshold before activation, after real pilot observations.
 - Keep `branch check` installed-only and require an explicit versioned policy plus exact short
   branch name. Never inspect Git, infer checkout or event state, discover policy, normalize full
   refs/remotes, or read environment in the domain layer. Schema v1 is a bounded ordered list of

{yaga_cli-0.2.1 → yaga_cli-0.3.0}/CONTRIBUTING.md

@@ -45,11 +45,52 @@ fallback because the locked PyYAML release does not publish Python 3.15 wheels.
 ## CLI and commit policy contract
 
 The public installed command groups are `branch`, `change`, `commit`, `config`, `github`, `mode`,
-`path`, `repo`, `self`, `size`, `tree`, `workflow`, and `gate`.
+`path`, `repo`, `self`, `size`, `test`, `tree`, `workflow`, and `gate`.
 Keep Typer declarations in `src/yaga/commands/`; keep commit parsing, policy, Git selection,
 configuration, GitHub event adaptation, and reporting in focused dependency-light modules under
 `src/yaga/commits/`. Domain behavior must remain directly testable without invoking Typer.
 
+Test planning lives under `src/yaga/test_planning/`; see the [command guide](docs/test-planning.md)
+and [design](docs/designs/test-planning.md). Keep explicit policy parsing separate from pure
+selection, reuse the neutral bounded matcher in `src/yaga/path_patterns.py`, and keep both examples
+executable in tests. `test policy check` requires one explicit file and no Git access; `test plan`
+requires policy, profile, and exactly one explicit range or revision. A revision-only plan requires
+a full profile. Keep Git collection in the source adapter, using `src/yaga/git/changes.py` and the
+shared bounded runtime; the pure planner must not discover Git or environment state. Range plans
+require complete history and exact endpoint/comparison/execution identities; revision plans need
+their selected commit and tree only. Both reject graft overlays and never fetch. Preserve exact
+policy-byte identity, optional binding SHA-256, canonical version-one plan digests, complete JSON
+within 4 MiB, and at most 256 human reasons with exact omitted counts. Emit successful output on
+stdout and bounded error envelopes on stderr, with exits 0/2 only. Planning never executes bindings
+or claims tests passed. Keep both commands outside repository plans and both Action runtimes.
+
+Keep executor handoff pure and installed-only. `ExecutorRegistry` must map the complete catalog
+exactly once to fixed dispatch IDs, preserve every variant, satisfy declared capabilities, and
+bind immutable executor-definition hashes. `create_handoff` requires a non-preview plan plus
+independent expected policy/commit/tree identities; keep the version-one manifest/handoff shapes
+and 4 MiB complete-output limit. No binding may become a command or credential source. Consumer
+adapters own real capability checks, execution, cancellation, custom acceptance, and cleanup.
+Keep shadow comparisons advisory and full shadow jobs isolated from required CI cancellation.
+Do not claim measured savings or enable skips before actual observations, a documented adoption
+threshold, and complete-result gating. See the [handoff guide](docs/test-planning-handoff.md).
+
+Keep selection diagnostics pure and separate from the frozen plan/handoff/comparison documents.
+Retain exact source and policy/registry/plan identities, distinguish selection breadth from the
+reason for full mode, and expose paths bypassed by early full decisions. A missing baseline is
+different from an explicitly empty selection. Strict offline decoding checks closed version-one
+plan semantics and canonical digests; callers still own bounded JSON reads and duplicate-key
+rejection. Complete diagnostic reports must fit within 4 MiB including the final newline.
+Recorded reasons are not proof of dependency coverage, trusted origin, or runtime savings.
+
+Keep version-one normalized test results and evaluation separate from frozen plan/handoff formats.
+`test evaluate` requires explicit bounded plan/results files plus independent expected policy,
+manifest, source, run, and aggregate-attempt identities. Keep the evaluator pure and validate every
+selected variant and prerequisite; missing or non-passed work returns 1, malformed or mismatched
+inputs return 2, and only complete passed obligations return 0. Bound complete JSON to 4 MiB and
+diagnostics to 256 with exact omitted counts. Adapters own provenance, custom acceptance, cleanup,
+and retry lineage; an artifact hash or green job alone cannot prove these. No execution, discovery,
+Git access, provider API, required-CI changes, or selective activation belongs in evaluation.
+
 All revision-bound providers use the dependency-free runtime under `src/yaga/git/`. Keep repository
 and executable discovery, metadata and alternate-object-store boundaries, process execution,
 environment isolation, time and output limits, object identity parsing, and complete-history checks
@@ -90,9 +131,22 @@ opt-in alternative. Apply it only in the event-aware `github pull-request check`
 read-only commit Action. Identify Dependabot from one strictly parsed PR author record with exact
 `dependabot[bot]` login, `Bot` type, and a bounded positive ID; never from Git author/committer
 metadata, a title, message, branch, actor, or footer. Complete event/context/checkout/config/range
-validation before returning skipped title and commit results with the stable reason `Dependabot
-pull request`. Ordinary `commit check` and repository plans keep checking, and every non-commit
-provider remains independent.
+validation before applying the stable `Dependabot pull request` skip reason. Narrow this already
+eligible quality exemption per commit with bounded exact author/committer metadata compatibility.
+`dependabot-require-github-signature` is a strict schema-v1 boolean defaulting to `true`; it affects
+only this opt-in exemption. Require offline verification of each candidate's exact object bytes
+against the pinned GitHub key using a trusted bounded `gpgv` process and private keyring. Missing
+or failed verification, unsupported signatures, and resource exhaustion run normal checks.
+An explicit `false` retains only the forgeable metadata filter. Check ordinary human additions
+and human rebases, and check titles/proposed messages in mixed PRs. Require metadata for exactly
+the previously selected SHA set, rejecting missing/duplicate records. Preserve that complete set
+in reports. The shared GitHub key does not prove exclusive Dependabot identity. Do not fetch keys,
+query live badges/revocation state, import REST/token code, or treat Signed-off-by as proof.
+The explicit `skip-pull-request-authors` list remains a broad independent exemption, including for
+human additions; do not generalize this option into Renovate/custom bot identity configuration.
+Never use these exemptions to skip tests/security checks. Ordinary `commit check` and repository
+plans keep checking, and every non-commit provider remains independent. Preserve frozen starter
+bytes: omitted signature settings inherit the new default without rewriting existing starters.
 `breaking-markers` is a schema-v1 enum with `either` as its default. `either` accepts a header `!`,
 a recognized final `BREAKING CHANGE:` or `BREAKING-CHANGE:` footer, or both; `paired` requires both
 markers or neither and reports `breaking.marker-pair` for exactly one. Apply marker pairing only to

{yaga_cli-0.2.1 → yaga_cli-0.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: yaga-cli
-Version: 0.2.1
+Version: 0.3.0
 Summary: Configurable developer workflow checks for local use and GitHub Actions
 Project-URL: Documentation, https://dariuszpanas.github.io/yaga/
 Project-URL: Changelog, https://dariuszpanas.github.io/yaga/changelog.html
@@ -49,6 +49,7 @@ become another review conversation. Start with one check and adopt more as your
 | Unwanted files, oversized blobs, or incompatible paths enter the repository | [Committed-file checks](https://dariuszpanas.github.io/yaga/repository-checks.html) for contents, sizes, names, and entry modes |
 | GitHub Actions workflows drift from your security and maintenance rules | [Workflow checks](https://dariuszpanas.github.io/yaga/workflow-checks.html) for immutable references, permission and checkout rules, and syntax |
 | Local checks and CI enforce different policies | An explicit [repository plan](https://dariuszpanas.github.io/yaga/repository-plans.html) used in both places |
+| A small change needs a clear test and qualification plan | [Test planning](https://dariuszpanas.github.io/yaga/test-planning.html) selects suites and required variants from explicit changed paths |
 
 Checks produce actionable findings and reports for automation. You choose the policies and checks;
 YAGA does not require adopting the entire CLI at once.

{yaga_cli-0.2.1 → yaga_cli-0.3.0}/README.md

@@ -17,6 +17,7 @@ become another review conversation. Start with one check and adopt more as your
 | Unwanted files, oversized blobs, or incompatible paths enter the repository | [Committed-file checks](https://dariuszpanas.github.io/yaga/repository-checks.html) for contents, sizes, names, and entry modes |
 | GitHub Actions workflows drift from your security and maintenance rules | [Workflow checks](https://dariuszpanas.github.io/yaga/workflow-checks.html) for immutable references, permission and checkout rules, and syntax |
 | Local checks and CI enforce different policies | An explicit [repository plan](https://dariuszpanas.github.io/yaga/repository-plans.html) used in both places |
+| A small change needs a clear test and qualification plan | [Test planning](https://dariuszpanas.github.io/yaga/test-planning.html) selects suites and required variants from explicit changed paths |
 
 Checks produce actionable findings and reports for automation. You choose the policies and checks;
 YAGA does not require adopting the entire CLI at once.

yaga_cli-0.3.0/_typos.toml

@@ -0,0 +1,3 @@
+[default]
+# The vendored public key is exact cryptographic data; prose remains checked.
+extend-ignore-re = ['(?s)\b_KEYRING_BASE64 = \(\s*(?:"[A-Za-z0-9+/=]+"\s*)+\)']

{yaga_cli-0.2.1 → yaga_cli-0.3.0}/docs/changelog.md

@@ -2,6 +2,57 @@
 
 ## [Unreleased]
 
+## [0.3.0] - 2026-10-18
+
+### Added
+
+- Add the internal version-one test qualification policy and pure selection planner, with
+  strict bounded validation, additive path/tag rules, full-suite fallback, complete variants,
+  prerequisite ordering, and tested polyglot and django-ray examples.
+
+- Add installed `test policy check` and `test plan` commands, with explicit policy/profile and
+  Git range or full-profile revision inputs. Plans bind exact commit/tree and policy identities,
+  carry deterministic version-one JSON digests, and explain selected suites and variants.
+  Git collection remains bounded and never fetches. Planning does not run tests or enable skips;
+  normalized receipt evaluation is available separately.
+
+- Add a pure version-one executor registry and handoff API with complete fixed job mappings,
+  binding/source/policy identity checks, exact variant preservation, capability preflight,
+  and bounded dispatch/cell output. Add runnable polyglot and django-ray examples, installed-wheel
+  smoke, and a django-ray shadow-pilot guide. Existing required CI stays enabled. Historical
+  selection replay and one full shadow observation are recorded; measured selective feedback
+  savings, an adoption threshold, and selective activation remain pending.
+
+- Add pure version-one selection diagnostics and strict offline plan decoding, preserving
+  source/policy identities, fallback causes, selection breadth, unclassified paths, and explicit
+  baseline comparisons. Add optional separate replay diagnostics without changing existing plan
+  or comparison formats. Complete reports stay within 4 MiB and make no execution claims.
+
+- Add version-one normalized test results and pure evaluation, plus installed `test evaluate`
+  with explicit plan/results files and independent policy, manifest, source, run, and attempt
+  identities. Missing prerequisites or variants and non-passed outcomes block success; malformed,
+  stale, duplicate, or extra results fail validation. Preserve bounded reports, offline operation,
+  both Action import boundaries, and existing required CI. Selective activation remains pending.
+
+- Add the schema-v1 boolean `dependabot-require-github-signature`, defaulting to `true`.
+  Each otherwise eligible Dependabot-skipped commit must verify offline against the pinned
+  GitHub signing key. Missing or failed verification runs normal checks. An explicit `false`
+  retains the per-commit metadata filter; explicit PR-author exemptions remain independent.
+
+### Fixed
+
+- Map eight exact application-test files to application qualification in the django-ray example,
+  include latency for changes to the shared Docker scenario helper, and preserve the shared lease
+  dependencies added by the coordinated django-ray release work. Add complete historical
+  path, unknown-path, lockfile, rename/deletion, and variant regressions. Required CI and the
+  conservative full/unknown fallback behavior remain enabled.
+
+- Narrow the opt-in Dependabot commit-message exemption per commit, so ordinary human additions
+  and human rebases are checked even inside a Dependabot PR. Mixed PR titles and proposed
+  messages are checked too. Signature verification requires an available trusted `gpgv` and
+  adds no API or token access. The shared GitHub key does not prove exclusive bot authorship,
+  and this quality exemption does not authorize skipping other checks.
+
 ## [0.2.1] - 2026-10-10
 
 ### Added

{yaga_cli-0.2.1 → yaga_cli-0.3.0}/docs/commands.md

@@ -29,6 +29,9 @@ or `yaga self update --dry-run` to verify a uv tool installation without updatin
 | `yaga workflow security` | Versioned permission and checkout policies | [Workflow checks](workflow-checks.md) |
 | `yaga workflow lint` | Syntax checks through Docker actionlint | [Workflow checks](workflow-checks.md) |
 | `yaga github pull-request check` | Exact event-bound title and commit validation | [GitHub Actions](github-actions.md) |
+| `yaga test policy check` | Validate an explicit test-suite catalog and selection policy | [Test planning](test-planning.md) |
+| `yaga test plan` | Select suites and variants for an explicit Git source and profile | [Test planning](test-planning.md) |
+| `yaga test evaluate` | Check normalized cell results against a trusted plan and explicit execution identities | [Test evaluation](test-planning.md#evaluate-normalized-results) |
 
 Evaluating YAGA for another repository? Start with [Assess and adopt in CI](ci-adoption.md).
 

{yaga_cli-0.2.1 → yaga_cli-0.3.0}/docs/commit-policy.md

@@ -63,6 +63,7 @@ body-min-words = 8
 # Omit body-max-line-length unless this repository wants a wrapping limit.
 # Set body-paragraph-splitting = "check" to catch sentence-like prose split by blank lines.
 dependabot-pull-requests = "skip" # check or skip in event-aware PR checks
+dependabot-require-github-signature = true # default; applies only to the Dependabot skip
 merge-commits = "reject"         # ignore, check, or reject
 ignored-headers = ['Revert "*"'] # bounded, case-sensitive glob patterns
 max-commits = 64
@@ -78,10 +79,38 @@ policy evaluation only in `yaga github pull-request check` and the read-only com
 and only when the event's pull-request author is exactly the GitHub `dependabot[bot]` Bot account,
 following [GitHub's event-author guidance for Dependabot
 automation](https://docs.github.com/en/code-security/tutorials/secure-your-dependencies/automate-dependabot-with-actions?learn=dependency_version_updates).
-The adapter still validates the complete event and runner context, verifies the checked-out head,
-loads configuration, and enumerates the bounded exact commit range before returning a visible
-`Dependabot pull request` skip. It does not skip change, mode, path, size, tree, workflow, test, or
-review-gate checks.
+After validating the complete event, runner context, checkout, configuration, and exact commit
+range, the adapter filters each selected commit independently. An exemption requires exact
+`dependabot[bot]` author metadata with either `49699333+dependabot[bot]@users.noreply.github.com`
+or `dependabot[bot]@users.noreply.github.com`, plus a committer with that bot name/email or
+`GitHub <noreply@github.com>`. The default `dependabot-require-github-signature = true` additionally
+requires a valid signature over the exact selected commit object using the pinned GitHub signing
+key with full fingerprint `968479A1AFF927E37D1A566BB5690EEEBB952194`. YAGA verifies this offline
+with an available trusted `gpgv` executable and a private keyring containing
+[GitHub's published public key](https://github.com/web-flow.gpg). It does not call the GitHub API,
+accept a token, download keys during a check, or use the user's keyring.
+
+Missing signatures, unavailable verification tools, unsupported or invalid signatures, verification
+errors, and exhausted verification limits all run normal checks for the affected commits.
+Ordinary human additions and bot-authored commits rebased by a human are also checked. If any
+commit is ineligible for the exemption, the title and optional proposed message are checked too.
+Otherwise their exemption is retained. Skipped results retain the `Dependabot pull request`
+reason, and every selected commit remains in the report.
+
+This option is a strict schema-v1 boolean and affects only `dependabot-pull-requests = "skip"`.
+Explicitly setting `dependabot-require-github-signature = false` retains only the per-commit
+metadata filter. Those metadata fields are forgeable, so this opt-out permits a human who forges
+both identities inside an eligible Dependabot PR to evade the filter. `Signed-off-by` footers are
+never consulted as proof. With the default requirement, the signature proves that the payload
+was signed by the pinned GitHub key; that shared key alone does not establish exclusive Dependabot
+authorship. This offline check does not query GitHub's live verification badge or refresh key
+revocation information. Keep `dependabot-pull-requests = "check"` to check every commit message.
+The exemption never skips change, mode, path, size, tree, workflow, test, or review-gate checks.
+
+The separate [`skip-pull-request-authors`](configuration.md#explicit-pr-author-exemptions) list
+remains a broader explicit exemption for the entire PR and does not require this signature check.
+Adding Dependabot to that list therefore bypasses the narrower per-commit policy. Signature-based
+identity policies for Renovate or custom bots are not part of this option.
 
 Ordinary `commit check` and the `commit` provider inside `repo check` never infer Dependabot from a
 Git author name, email, message, or branch because those values are author-controlled. They keep
@@ -263,7 +292,7 @@ Typos configuration is used; direct message and Git-backed sources follow the sa
 
 With the commit Action's `trusted-config` mode, `typos = "check"` applies to both the
 PR title and every selected full commit message. Structural title checks remain header-only.
-Authentic Dependabot skips and existing skipped commit types also skip spelling checks.
+Eligible Dependabot commit exemptions and existing skipped commit types also skip spelling checks.
 Findings fail with exit `1`; a missing or broken tool fails with exit `2`.
 
 Install a pinned Typos executable outside the checkout before invoking the Action.

{yaga_cli-0.2.1 → yaga_cli-0.3.0}/docs/configuration.md

@@ -128,7 +128,8 @@ version. Pin the installation separately when CI must always use one exact relea
 | `body-max-line-length` | Optional maximum body-line length; omitted means unlimited. |
 | `body-paragraph-splitting` | `skip` (default) or `check` for likely sentence splits across blank lines. |
 | `skip-pull-request-authors` | Empty-default list of up to 128 explicit GitHub PR author logins exempt from title and commit checks. |
-| `dependabot-pull-requests` | `check` (default) or `skip` in event-aware PR checks only. |
+| `dependabot-pull-requests` | `check` (default) or a per-commit metadata/signature-filtered `skip` in eligible event-aware PR checks only. |
+| `dependabot-require-github-signature` | Boolean, default `true`. Requires offline verification against the pinned GitHub signing key for each Dependabot-skipped commit. Missing or failed verification runs normal checks. Only affects `dependabot-pull-requests = "skip"`; `false` retains the metadata filter alone. |
 | `typos` | `skip` (default) or `check` with an installed Typos CLI. |
 | `typos-config` | `repository` (default) discovers Typos settings; `isolated` disables discovery. Trusted Actions always isolate. |
 | `quality` | Nested non-secret defaults for `commit quality`; provider, task, model, revision, threshold, region, max-tokens, max-input-tokens, and input-mode. |
@@ -378,7 +379,15 @@ checkout, policy, and commit-range validation. Reports use `Configured pull requ
 It does not exempt ordinary `commit check`, repository checks, or other providers.
 Unlike the narrower `dependabot-pull-requests = "skip"` option in trusted mode, this explicit
 list applies regardless of head repository or branch. Listing an account opts into that scope.
-The existing Dependabot option retains its identity and trusted same-repository/branch checks.
+The Dependabot option retains its identity and trusted same-repository/branch checks, then narrows
+the exemption per commit with the [metadata and signature checks](commit-policy.md).
+`dependabot-require-github-signature` defaults to `true`; an unavailable `gpgv`, missing signature,
+or failed verification runs normal checks. Setting it to `false` retains a forgeable metadata
+filter. The pinned GitHub key is shared, and verification does not prove exclusive bot authorship
+or query live revocation state. Explicit author exemptions remain broader and intentionally skip
+the entire PR even when it contains human-added commits. They bypass the Dependabot signature
+requirement, including when `dependabot[bot]` itself appears in this list. This does not add a
+generic signature or identity policy for Renovate or custom bots.
 
 Use `trusted-config` when the exemption must come from the default-branch policy. Default
 PR-head mode intentionally reads PR policy, including this list; it is not trusted merge authority.