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

{yaga_cli-0.2.1 → yaga_cli-0.4.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@07a047e608db84b3d8c06cd9a7c7dcc9c355c18e # v10.3.2
         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@07a047e608db84b3d8c06cd9a7c7dcc9c355c18e # v10.3.2
         with:
           enable-cache: true
           version: "0.13.0"

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

@@ -15,12 +15,12 @@ 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:
           persist-credentials: false
-      - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+      - uses: actions/setup-python@6d4fd22b20465ccc0f7354476588e8df7c9ca0e0 # v7.1.0
         with:
           python-version: "3.12"
       - name: Install pinned Typos for spelling controls

{yaga_cli-0.2.1 → yaga_cli-0.4.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@07a047e608db84b3d8c06cd9a7c7dcc9c355c18e # v10.3.2
         with:
           enable-cache: true
           version: "0.12.7"

{yaga_cli-0.2.1 → yaga_cli-0.4.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@07a047e608db84b3d8c06cd9a7c7dcc9c355c18e # v10.3.2
         with:
           version: "0.12.7"
       - run: uv sync --frozen --group dev --python 3.12

{yaga_cli-0.2.1 → yaga_cli-0.4.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@07a047e608db84b3d8c06cd9a7c7dcc9c355c18e # v10.3.2
         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,11 +77,11 @@ 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/
-      - uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2
+      - uses: pypa/gh-action-pypi-publish@7245906fb61fa33a13554f9d5fb856fe61758086 # v1.14.3
 
   github-release:
     name: Create GitHub Release
@@ -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.4.0}/AGENTS.md

@@ -13,6 +13,29 @@ Agent review gate is the public review contract. Its current provider adapter re
 
 ## Preserve the CLI contract
 
+- Keep pull-request description checks installed-only under `src/yaga/descriptions/`, with one
+  explicit versioned policy and file/stdin/event/PR source plus an optional explicit Markdown template.
+  Keep the checker pure, Markdown support deliberate, and Typos execution bounded and isolated.
+  Require meaningful content and unique ordered template headings; preserve schema-v1 reports,
+  exact finding counts, 256 stored diagnostics, 64 KiB policy/body/template and 1 MiB event limits.
+  Keep `heading-min-level` defaulted to 2 and `heading-max-length` to 120, with strict integer
+  ranges 1–6 and 1–256. Apply these rules to top-level ATX and Setext headings, reject raw HTML
+  heading tags outside comments/code/escaped literals, and reject conflicting templates.
+  Preserve the `description.heading-*` and `description.html-heading` diagnostic boundaries;
+  structural checks are neither a complete Markdown renderer nor an HTML sanitizer.
+  Keep text hygiene source-located and code/comment/escape-aware. Diagnose invisible format
+  controls, prose tabs, high-confidence literal newline escapes, and unmatched backticks without
+  rejecting ordinary Unicode joining/emoji sequences or guessing arbitrary emphasis. Reject
+  unsupported control characters and bare CR before normalization; preserve LF/CRLF input.
+  Keep file/stdin/event sources offline. Only explicit `--pr` may fetch the current body through
+  the installed authenticated `gh` CLI: require a canonical HTTPS URL or a positive number plus
+  `--repo [HOST/]OWNER/REPO`, reject mixed sources and URL/repository ambiguity, and never infer
+  checkout or environment selection. Use shell-free bounded process execution, verify returned
+  PR identity and strict JSON, preserve the 64 KiB decoded-body limit, and never expose raw process
+  output or credentials. Keep the 30-second, 512 KiB stdout, and 64 KiB stderr bounds. Fetches may
+  check open/closed/merged PRs, without retrieving historical descriptions or writing to GitHub.
+  Never discover templates or policy, access Git history, or inherit commit-author exemptions.
+  Keep this provider outside repository plans and both Action import graphs.
 - `commit check` accepts one explicit source or defaults to `HEAD`; never silently combine sources,
   fetch history, reduce a Git selection, or ignore a missing base.
 - Treat commit messages, Git output, revisions, paths, and displayed labels as untrusted. Bound
@@ -27,9 +50,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 +133,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.4.0}/CONTRIBUTING.md

@@ -42,14 +42,81 @@ with project and Python environment leakage removed.
 That strict build gate runs on Python 3.12. The Python 3.15 test jobs permit PyYAML's source-build
 fallback because the locked PyYAML release does not publish Python 3.15 wheels.
 
+The default `make ci` changed-path check covers only `HEAD^..HEAD`. To qualify a complete pull
+request, use exact base/head SHAs that are already available in complete local history, and run
+from the head checkout:
+
+```bash
+uv run yaga commit check --range '<base-sha>..<head-sha>'
+uv run make ci CHANGE_RANGE='<base-sha>...<head-sha>'
+```
+
+The independent two-dot commit check selects branch-only commits; the three-dot changed-path
+check compares the head against its unique merge base. Neither command fetches or infers a remote
+branch. The range override does not change workflow, formatting, or test inputs: those still use
+the current checkout. A final docs-only commit must not hide an earlier source change from the
+complete PR check.
+
+Minimum runtime compatibility has a separate optional check:
+
+```bash
+uv run --locked --python 3.12 python scripts/check_minimum_runtime.py --report minimum-runtime.json
+```
+
+It builds a fresh base wheel, resolves the lowest runtime dependency versions outside the checkout,
+checks installed provenance and dependency consistency, and exercises representative CLI/report
+paths. See [minimum runtime qualification](docs/minimum-runtime.md) for scope and retained evidence;
+this complements the frozen-lock `make ci` and strict package build gates.
+
 ## 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`, `pull-request`, `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 +157,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
@@ -126,6 +206,36 @@ diagnostics.
 must refuse to shadow any effective discovered configuration, never edit `pyproject.toml`, and keep
 its deterministic starter template round-trippable through the strict loader.
 
+Pull-request description policy lives under `src/yaga/descriptions/` and remains installed-only.
+Require one explicit versioned policy and description source, plus an optional explicit template.
+Keep the Markdown subset and checker pure; file/stdin/event loading, explicit current-PR fetching,
+and bounded isolated Typos execution belong in adapters. File/stdin/event sources remain offline.
+Only `--pr` invokes the installed authenticated `gh` CLI to read the current description. Require
+a canonical HTTPS PR URL or a positive number plus `--repo [HOST/]OWNER/REPO`; reject mixed sources,
+URL/repository ambiguity, and implicit checkout/environment selection. Use the shared shell-free
+bounded process runtime with a 30-second timeout, 512 KiB stdout, and 64 KiB stderr; strictly parse
+JSON and verify returned PR identity before checking its bounded body. Do not expose raw process
+output or credentials. Support open, closed, and merged PRs without historical-description reads.
+No Git history access, policy/template discovery, author exemptions, or writes belong in this
+provider. Schema v1 controls prose word minimum, total character maximum,
+heading level/length, whole-line placeholders, task completion, and optional spelling. Default
+`heading-min-level` to 2 (strict integer 1 through 6) and `heading-max-length` to 120 (strict integer
+1 through 256). Apply level/length/content checks to top-level ATX and Setext headings; Setext
+paragraphs do not contribute prose words. Reject raw HTML `h1` through `h6` tags outside comments,
+code, and escaped literal markup; this narrow rule does not sanitize or forbid other HTML.
+Template headings must occur once in order with meaningful section content; hidden comments and
+fenced code cannot satisfy it. Reject template/policy conflicts as configuration errors.
+Keep fixed text hygiene checks code/comment/escape-aware: suspicious invisible Unicode characters,
+prose tabs, high-confidence literal newline escapes, and unmatched backtick delimiters. Preserve
+ordinary Unicode joining/emoji behavior and source byte-column locations. Reject unsupported
+control characters and bare CR before normalization; accept LF and CRLF. Do not infer lost text,
+rewrite descriptions, or claim complete Markdown rendering or HTML sanitization.
+Preserve 64 KiB policy/body/template bounds, the 1 MiB event bound, 64 template headings, exact
+finding counts with 256 stored diagnostics, schema-v1 reports, and exits 0/1/2. The GitHub body
+adapter validates supported open-PR events without claiming authenticated identity or requiring
+commit metadata. Keep both commands outside repository plans and both Action import graphs.
+See [pull-request descriptions](docs/pull-request-descriptions.md) for the complete public contract.
+
 Branch-name policy lives under `src/yaga/branches/` and remains installed-only. `branch check`
 requires one explicit versioned policy and one explicit short name; never inspect Git, infer the
 current branch, discover policy, parse an event, normalize `refs/` or remote prefixes, or read an
@@ -345,7 +455,11 @@ gate. Its PR-head configuration is contributor-controlled and is only a quality
 ## Action contract
 
 The public inputs are exactly `gate`, `operation`, `github-token`, `prerequisite-workflow`,
-`lifecycle-workflow`, `owner-id`, `approval-marker`, `request-timeout`, and `job-timeout-minutes`.
+`lifecycle-workflow`, `owner-id`, `approval-marker`, `request-timeout`, `job-timeout-minutes`, and
+`agent-review-policy-file`. The last input defaults to empty; nonempty values are deliberately
+rejected before API access because this fixed GitHub adapter cannot execute named lenses or bind
+their outcomes to a policy digest. Provider-neutral `gate agent-review policy` commands remain
+available to external adapters.
 `operation` is closed to `invalidate`, `prepare`, `authorize`, `observe`, `request`, and `finalize`.
 Only `prepare` emits the closed `route` capability and `pull_request_number` used by the template;
 its routes are `skip`, `done`, `observe`, `owner`, `external`, and `approved`. Candidate identity

{yaga_cli-0.2.1 → yaga_cli-0.4.0}/Makefile

@@ -2,6 +2,7 @@
 
 DOCS_ADDR ?= localhost:9000
 BUILD_ARGS ?=
+CHANGE_RANGE ?= HEAD^..HEAD
 
 actionlint:
 	uv run yaga workflow lint .github/workflows examples
@@ -23,7 +24,7 @@ check:
 	uv run ty check
 	uv run pre-commit validate-manifest .pre-commit-hooks.yaml
 	uv run yaga repo check --plan .yaga/checks/ci.toml --commit HEAD --revision HEAD
-	uv run yaga change check --policy .yaga/change-policy.toml --range HEAD^..HEAD
+	uv run yaga change check --policy .yaga/change-policy.toml --range "$(CHANGE_RANGE)"
 	bash -n scripts/composite_smoke_python
 
 test:

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: yaga-cli
-Version: 0.2.1
+Version: 0.4.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
@@ -24,6 +24,7 @@ Requires-Python: >=3.12
 Requires-Dist: pyyaml<7,>=6.0.3
 Requires-Dist: typer<1,>=0.27.2
 Provides-Extra: quality
+Requires-Dist: certifi>=2026.10.19; extra == 'quality'
 Requires-Dist: torch<3,>=2.13; extra == 'quality'
 Requires-Dist: transformers<6,>=5.10; extra == 'quality'
 Provides-Extra: quality-bedrock
@@ -45,10 +46,12 @@ become another review conversation. Start with one check and adopt more as your
 | Problem | What YAGA checks |
 | --- | --- |
 | Commit messages and branch names follow inconsistent conventions | [Commit policy](https://dariuszpanas.github.io/yaga/commit-policy.html) and [branch naming](https://dariuszpanas.github.io/yaga/branch-policy.html) defined by your team |
+| Pull requests omit useful context or leave template sections unfinished | [Description checks](https://dariuszpanas.github.io/yaga/pull-request-descriptions.html) for required content, templates, and optional spelling |
 | A change lands without the related files your project expects | [Changed-path rules](https://dariuszpanas.github.io/yaga/change-policy.html), such as source changes accompanied by tests |
 | 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.4.0}/README.md

@@ -13,10 +13,12 @@ become another review conversation. Start with one check and adopt more as your
 | Problem | What YAGA checks |
 | --- | --- |
 | Commit messages and branch names follow inconsistent conventions | [Commit policy](https://dariuszpanas.github.io/yaga/commit-policy.html) and [branch naming](https://dariuszpanas.github.io/yaga/branch-policy.html) defined by your team |
+| Pull requests omit useful context or leave template sections unfinished | [Description checks](https://dariuszpanas.github.io/yaga/pull-request-descriptions.html) for required content, templates, and optional spelling |
 | A change lands without the related files your project expects | [Changed-path rules](https://dariuszpanas.github.io/yaga/change-policy.html), such as source changes accompanied by tests |
 | 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.4.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.4.0}/docs/changelog.md

@@ -2,6 +2,116 @@
 
 ## [Unreleased]
 
+## [0.4.0] - 2026-10-29
+
+### Added
+
+- Add installed `pull-request description check` and `github pull-request description check`
+  commands for explicit Markdown files, stdin, and GitHub event bodies. Version-one policies
+  check meaningful content, word and character limits, unfinished placeholders, optional task
+  completion, and isolated Typos spelling. Explicit templates require ordered, filled sections
+  and replacement of unchanged prompts. Reports support text, JSON, and GitHub annotations;
+  existing commit checks and composite Actions retain their separate contracts.
+
+- Check description heading structure even without a template. Default to H2 or deeper and at
+  most 120 heading-text characters; reject empty headings and raw HTML heading tags. Recognize
+  top-level Setext headings so a whole paragraph formatted as an H1 or H2 cannot count as prose.
+  Reject templates whose headings conflict with the selected policy.
+
+- Detect suspicious invisible characters, prose tabs, literal escaped line breaks, and unmatched
+  backticks outside code and comments. Reject bare carriage returns and identify unsupported
+  control characters without rendering them. Document literal UTF-8 file authoring to preserve
+  Markdown through shell commands.
+
+- Add `pull-request description check --pr` for the current body of an existing GitHub pull
+  request. Accept an explicit URL or a number with `--repo`, fetch through the installed
+  authenticated `gh` CLI with bounded process execution, and run the same policy/template checks
+  without a checkout or Actions. File, stdin, and event checks remain offline.
+
+- Add a separate minimum-runtime qualification helper that builds a fresh base wheel, installs
+  the lowest resolved runtime dependencies outside the checkout, checks installed imports, and
+  runs the shared CLI smoke checks. Its JSON receipt records actual versions and the wheel hash;
+  the frozen-lock matrix and strict package build gate remain required.
+
+- Make source types, prerequisites, network behavior, reports, repository-plan membership, and
+  Action availability discoverable from installed help and the command guide, with tested local
+  and complete-PR recipes.
+
+- Document the staged-check design assessment, including index semantics, report compatibility,
+  and implementation acceptance criteria. Staged execution is not included in this release.
+
+### Fixed
+
+- Reject Git object-path selectors in changed-path range endpoints before repository access, so
+  a crafted gitlink cannot redirect the selected comparison and hide policy findings.
+
+- Isolate installed-wheel smoke Git setup from ambient repository variables, user/system
+  configuration, and templates, preserving unrelated repositories during qualification.
+
+- Allow an explicit `CHANGE_RANGE` override for local `make ci` qualification. Document the
+  independent full commit range check and the default last-commit-only comparison.
+
+- Require `certifi>=2026.10.19` in the published `quality` extra, including wheel metadata, to
+  prevent supported model-download stacks retaining older affected certificate bundles. This
+  applies when installing/upgrading with the extra; base and Bedrock requirements are unchanged.
+
+- Reject inconsistent Typos success/finding responses instead of silently accepting unexpected
+  output as a clean spelling result.
+
+- Correct the documented repository-plan key, stdout/stderr capture, lifecycle exit codes,
+  quality-provider help, and the fixed GitHub Action's rejecting policy-file input.
+
+## [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