pytest-selective 1.2.0__tar.gz → 1.4.0__tar.gz

pytest_selective-1.2.0/.github/test-lanes.json → pytest_selective-1.4.0/.github/plan-lanes.json

@@ -25,27 +25,6 @@
         "src/**",
         "tests/**"
       ]
-    },
-    "contracts": {
-      "roots": [
-        "contracts"
-      ],
-      "inputs": [
-        "src/**",
-        "contracts/**",
-        "tests/testing/git_repo.py"
-      ]
-    },
-    "package": {
-      "inputs": [
-        "src/**",
-        "pyproject.toml",
-        "uv.lock",
-        "README.md",
-        "LICENSE",
-        "scripts/check_metadata.py",
-        "scripts/smoke_distribution.py"
-      ]
     }
   },
   "global_inputs": [
@@ -56,6 +35,7 @@
     "pyproject.toml",
     "**/uv.lock",
     "uv.lock",
+    ".github/plan-lanes.json",
     ".github/test-lanes.json",
     ".github/workflows/ci.yml",
     ".github/workflows/release.yml",

pytest_selective-1.4.0/.github/test-lanes.json

@@ -0,0 +1,22 @@
+{
+  "extends": "workflow",
+  "lanes": {
+    "tests": {
+      "roots": ["tests"]
+    }
+  },
+  "rules": [
+    {
+      "name": "python-environment",
+      "when": ["pyproject.toml", "**/pyproject.toml", "uv.lock", "**/uv.lock", ".python-version"],
+      "select": ["all"],
+      "reason": "the locked test environment; documentation/requirements*.txt belongs to Read the Docs"
+    },
+    {
+      "name": "distribution-smoke",
+      "when": ["scripts/smoke_distribution.py"],
+      "select": ["lane:tests"],
+      "reason": "the distributions job runs the smoke only when the tests lane is planned"
+    }
+  ]
+}

{pytest_selective-1.2.0 → pytest_selective-1.4.0}/.github/workflows/ci.yml

@@ -6,8 +6,6 @@ on:
     types: [opened, synchronize, reopened]
   workflow_dispatch:
   workflow_call:
-  schedule:
-    - cron: '13 3 * * 1'
 permissions:
   contents: read
 concurrency:
@@ -15,6 +13,9 @@ concurrency:
   group: ci-${{ github.workflow }}-${{ github.event_name == 'pull_request' && github.run_attempt == 1 && github.event.pull_request.number || github.run_id }}
   cancel-in-progress: ${{ github.event_name == 'pull_request' && github.run_attempt == 1 }}
 jobs:
+  # Plans whole lanes before any runner starts: each lane is the name a job's condition reads, and a change selects it
+  # through the tests, scripts and actions that job runs. `ci-esta lanes` shows the lanes and why; .github/test-lanes.json
+  # holds only what the workflow cannot show.
   select-tests:
     runs-on: ubuntu-latest
     permissions:
@@ -33,7 +34,7 @@ jobs:
       CONTRACT_LANE_JOBS: '{"selection":"Selection contract (Quint)"}'
     outputs:
       # Planned lanes after reuse: a reusing lane is false only when every one of its jobs is proven by a receipt.
-      lanes: ${{ steps.admit.outputs.lanes }}
+      lanes: ${{ steps.contract-evidence.outputs.admitted-lanes || steps.plan.outputs.lanes }}
       # The plan before reuse, for steps that follow changed runtime inputs rather than test execution.
       planned: ${{ steps.plan.outputs.lanes }}
       mode: ${{ steps.files.outputs.mode }}
@@ -51,9 +52,10 @@ jobs:
         if: github.event_name == 'pull_request'
         run: 'true'
       - id: plan
-        uses: ./actions/plan-lanes
+        uses: gigaverse-app/ci-esta/actions/plan-work@v1
         with:
           config: .github/test-lanes.json
+      # File selection has no workflow graph, so it reads the complete lane file public-actions.yml plans with.
       - name: Share the repository graph and execution inputs with file selection
         env:
           PYTHONPATH: src
@@ -84,6 +86,8 @@ jobs:
           input-paths: ${{ steps.inputs.outputs.tests }}
           reuse-after-merge: 'true'
           reuse-version-only-release: 'true'
+          planned-lanes: ${{ steps.plan.outputs.lanes }}
+          lane-keys: '{"tests":["py311-ubuntu","py311-windows","py311-macos","py314-ubuntu","py314-windows","py314-macos","minimum"]}'
       - id: contract-evidence
         if: >-
           ${{ (github.event_name == 'pull_request' || github.event_name == 'push') &&
@@ -95,21 +99,9 @@ jobs:
           input-paths: ${{ steps.inputs.outputs.contracts }}
           reuse-after-merge: 'true'
           reuse-version-only-release: 'true'
-      - id: admit
-        name: Admit each reusing lane unless every job is proven
-        env:
-          PLANNED_LANES: ${{ steps.plan.outputs.lanes }}
-          REUSED: ${{ steps.evidence.outputs.reused || '{}' }}
-          CONTRACT_REUSED: ${{ steps.contract-evidence.outputs.reused || '{}' }}
-        run: |
-          admitted=$(jq -c \
-            --argjson tests "$TEST_LANE_JOBS" --argjson reused "$REUSED" \
-            --argjson contracts "$CONTRACT_LANE_JOBS" --argjson contract_reused "$CONTRACT_REUSED" '
-              def proven($jobs; $proof): [$jobs | keys[] | $proof[.] == true] | all;
-              (if proven($tests; $reused) then .tests = false else . end)
-              | (if proven($contracts; $contract_reused) then .contracts = false else . end)' <<<"$PLANNED_LANES")
-          echo "reused=$REUSED contracts=$CONTRACT_REUSED"
-          echo "lanes=$admitted" | tee -a "$GITHUB_OUTPUT"
+          # Chained: the tests step already admitted its lane; this step admits the contracts lane on top.
+          planned-lanes: ${{ steps.evidence.outputs.admitted-lanes }}
+          lane-keys: '{"contracts":["selection"]}'
   quality:
     runs-on: ubuntu-latest
     steps:
@@ -121,11 +113,18 @@ jobs:
       - run: uv run --locked pre-commit run --all-files
         env:
           SKIP: dry-lint
+      # Each lane-gated job's condition, the gate's lane-jobs and the lanes the workflow defines must agree.
       - name: Check aggregate gate against the execution lanes
         run: >-
           uv run --no-project --python 3.14
-          --with "ci-esta>=1.1.0,<2.0.0"
+          --with "ci-esta[selection]>=1.13.0,<2.0.0"
           ci-esta check-workflow --workflow .github/workflows/ci.yml --lanes .github/test-lanes.json
+      # Plans one-file changes with CI-esta against real commits and fails on any lane a change should not run.
+      - name: Check the lane routing
+        run: >-
+          uv run --no-project --python 3.14
+          --with "ci-esta[selection]>=1.13.0,<2.0.0"
+          python scripts/check_lane_routing.py
       - name: Validate GitHub Actions
         run: docker run --rm -v "$PWD:/repo" -w /repo rhysd/actionlint:1.7.7 -color
   tests:

{pytest_selective-1.2.0 → pytest_selective-1.4.0}/.github/workflows/pr-title.yml

@@ -2,7 +2,8 @@ name: PR title
 
 # Squash merges use this checked title as the Conventional Commit header.
 on:
-  pull_request_target:
+  # Metadata reads need no privileged target event or repository secrets.
+  pull_request:
     types: [opened, edited, synchronize, reopened, ready_for_review]
 
 permissions:

{pytest_selective-1.2.0 → pytest_selective-1.4.0}/.github/workflows/public-actions.yml

@@ -4,8 +4,6 @@ on:
   push:
     branches: [main]
   workflow_dispatch:
-  schedule:
-    - cron: '33 3 * * 1'
 permissions:
   contents: read
 jobs:
@@ -17,10 +15,12 @@ jobs:
       - uses: actions/checkout@v7
         with:
           fetch-depth: 0
+      # This workflow smokes the repository's own actions, so its planner is plan-lanes itself, run selectively on every
+      # change against .github/plan-lanes.json; CI's lanes come from CI-esta's plan-work.
       - id: select
         uses: ./actions/plan-lanes
         with:
-          config: .github/test-lanes.json
+          config: .github/plan-lanes.json
           artifact-name: public-action-selection
   public-actions:
     needs: select-tests
@@ -37,7 +37,7 @@ jobs:
           python - <<'PY'
           import json
           from pathlib import Path
-          graph = json.loads(Path('.github/test-lanes.json').read_text())['graph']
+          graph = json.loads(Path('.github/plan-lanes.json').read_text())['graph']
           Path('smoke-impact.json').write_text(json.dumps(graph))
           PY
       - uses: ./
@@ -59,7 +59,7 @@ jobs:
       - uses: ./actions/plan-lanes
         id: lanes
         with:
-          config: .github/test-lanes.json
+          config: .github/plan-lanes.json
           base: ${{ github.sha }}
           full: 'true'
           artifact-name: ''
@@ -70,7 +70,7 @@ jobs:
           python - <<'PY'
           import json, os
           # A full checkpoint admits every configured lane.
-          configured = json.load(open('.github/test-lanes.json', encoding='utf-8'))['lanes']
+          configured = json.load(open('.github/plan-lanes.json', encoding='utf-8'))['lanes']
           assert json.loads(os.environ['LANES']) == dict.fromkeys(configured, True)
           PY
       - name: Require successful planning after fallback execution

pytest_selective-1.4.0/.github/workflows/weekly-checkpoint.yml

@@ -0,0 +1,21 @@
+name: Weekly full checkpoint
+'on':
+  schedule:
+  - cron: 13 3 * * 1
+  workflow_dispatch: null
+permissions:
+  contents: read
+  actions: write
+concurrency:
+  group: weekly-full-checkpoint
+  cancel-in-progress: false
+jobs:
+  dispatch:
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    steps:
+    - uses: gigaverse-app/ci-esta/actions/weekly-checkpoint@v1
+      with:
+        workflows: '["ci.yml", "public-actions.yml"]'
+        ref: ''
+        workflow-inputs: '{}'

pytest_selective-1.4.0/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "1.4.0"
+}

{pytest_selective-1.2.0 → pytest_selective-1.4.0}/AGENTS.md

@@ -19,9 +19,10 @@ on pytest-selective itself.
 - Planning supports committed revisions and explicit working-tree snapshots. Preserve full execution on
   operational uncertainty and diagnostics for invalid declarations. An empty
   selection is not an empty pytest argument list.
-- Select consumer routing regressions by their declared execution/configuration inputs. Update
-  `.github/test-lanes.json` when adding execution inputs; preserve explicit full/manual
-  checkpoints and the `test:full` override.
+- Select consumer routing regressions by their declared execution/configuration inputs. Declare a
+  file a test or CI script reads by path next to its reader; `.github/test-lanes.json` holds only
+  what CI-esta cannot see in the workflow, and `scripts/check_lane_routing.py` pins the lanes. Preserve
+  explicit full/manual checkpoints and the `test:full` override.
 - The README's performance numbers are scenario-specific observations. Keep
   claims linked to [raw evidence](docs/benchmarks/2026-10-22-routing.md); distinguish
   runner-seconds, elapsed time and billing. Skill/example edits need usable links

{pytest_selective-1.2.0 → pytest_selective-1.4.0}/CHANGELOG.md

@@ -1,5 +1,26 @@
 # Changelog
 
+## [1.4.0](https://github.com/gigaverse-app/pytest-selective/compare/v1.3.0...v1.4.0) (2026-11-09)
+
+
+### Features
+
+* **lanes:** partition test roots by filename patterns ([27c10ec](https://github.com/gigaverse-app/pytest-selective/commit/27c10ec608f052a36f58d9b10730048ab9d38598))
+
+## [1.3.0](https://github.com/gigaverse-app/pytest-selective/compare/v1.2.0...v1.3.0) (2026-11-09)
+
+
+### Features
+
+* **audit:** show how many tests each written declaration selects ([#124](https://github.com/gigaverse-app/pytest-selective/issues/124)) ([b660301](https://github.com/gigaverse-app/pytest-selective/commit/b660301be82aefb04fdc79202dc83067c28d7eb1))
+
+
+### Bug fixes
+
+* agent setup round 3, from a third adoption trial ([#127](https://github.com/gigaverse-app/pytest-selective/issues/127)) ([a82bea9](https://github.com/gigaverse-app/pytest-selective/commit/a82bea9f607abcb3ed68009571202ad8b7726c7e))
+* **selection:** keep every module a pytest11 entry-point name maps to ([#122](https://github.com/gigaverse-app/pytest-selective/issues/122)) ([acb6649](https://github.com/gigaverse-app/pytest-selective/commit/acb66492c6440621387e0506c1d0071a5a48979c))
+* **selection:** plan a pull request against its merge commit's actual base ([#119](https://github.com/gigaverse-app/pytest-selective/issues/119)) ([276cec8](https://github.com/gigaverse-app/pytest-selective/commit/276cec84f65c889a1820fd5a001a3a4aca8b7e0d))
+
 ## [1.2.0](https://github.com/gigaverse-app/pytest-selective/compare/v1.1.2...v1.2.0) (2026-11-09)
 
 

{pytest_selective-1.2.0 → pytest_selective-1.4.0}/CONTRIBUTING.md

@@ -98,24 +98,44 @@ limitations. The pull request template provides a short checklist. See
 
 ## CI lane selection
 
-This repository uses its own `plan-lanes` action. Documentation-only PRs keep
+CI plans whole lanes with [CI-esta](https://github.com/gigaverse-app/ci-esta)'s
+`plan-work` before any runner starts: `tests` (the Python matrix and
+`pytest-minimum`), `contracts` (the Quint selection contract) and `package` (the
+distribution build), the names the jobs' conditions read. A change selects a lane
+through what its jobs run: the tests that import it, the files tests declare they
+read, and the scripts and actions each job executes. Documentation-only PRs keep
 quality checks (including Markdown links) and the documentation build, while
-skipping every test lane and the distribution build. A README or LICENSE change
-also runs the `package` lane, because both distributions embed them. Within an
-admitted lane, the repository's public file-selection action selects affected
-test files once; the platform matrix and minimum-pytest job execute that same
-plan. CI-esta receives both lane and file explanations, learns JUnit timings,
-and validates the aggregate gate. Source and test edits follow dependencies;
-scripts, dependency/pytest policy and execution workflow changes retain full
-validation. Manual/called/release runs and the `test:full` label run it in full; a
-failed planner also runs all tests. Installed-distribution smoke checks use the
-same runtime-input decision; README-only changes skip those checks while still
-verifying the README embedded in both release archives. Repository routing
-controls exercise the committed config against real Git trees, including full and missing-history
-controls. Add new non-import execution inputs to `.github/test-lanes.json`.
-
-File planning derives its graph from that same lane config and merges its declared
-global execution inputs with the graph's environment inputs. Declare subprocess
+skipping every lane. A README or LICENSE change runs the `package` lane, because
+both distributions embed them; a README change also runs `contracts`, whose job
+checks the README's contract report, and the one test whose metadata check reads it. `pyproject.toml` and `uv.lock` run every
+lane. `ci-esta lanes --base origin/main` shows what a change would run and why.
+[.github/test-lanes.json](.github/test-lanes.json) extends the workflow and holds
+only what it cannot show: the `tests` lane's roots (its jobs run `pytest-selective
+execute-plan`, which CI-esta does not read as a pytest command), a
+`python-environment` rule that leaves the documentation site's requirements out,
+and a rule that plans the tests lane when the installed-distribution smoke script
+changes, because `distributions` smokes only when that lane is planned. When a test
+or a script starts reading a file by path, declare it next to the reader (a
+`<test>.gv-dependency.yaml` sidecar, which `pytest-selective audit
+--write-declarations` writes, or a `# gv:test-dependency: PATH` comment).
+`quality` runs [scripts/check_lane_routing.py](scripts/check_lane_routing.py),
+which plans one-file changes with CI-esta against real Git commits, including a
+full checkpoint, and `ci-esta check-workflow`, which keeps the job conditions, the
+gate and the lane file in agreement. Manual/called/release runs and the
+`test:full` label run everything; a failed planner also runs all tests.
+Installed-distribution smoke checks follow the tests lane's plan; README-only
+changes skip them while still verifying the README embedded in both release
+archives.
+
+Within an admitted lane, the repository's public file-selection action selects
+affected test files once; the platform matrix and minimum-pytest job execute that
+same plan. CI-esta receives both lane and file explanations, learns JUnit timings,
+and validates the aggregate gate. File selection has no workflow graph, so it reads
+[.github/plan-lanes.json](.github/plan-lanes.json), a complete lane file: its graph
+plus the execution inputs that run every test file (scripts, workflows, actions,
+dependency and pytest policy). `public-actions.yml` plans with the same file through
+this repository's own `plan-lanes` action, selectively on every change, and smokes
+its full checkpoint. Declare subprocess
 and non-import dependencies at their readers. Full plans collect whole-suite
 coverage; scoped plans produce JUnit timing evidence without presenting partial
 coverage as a whole-suite result. The public [shared-plan executor](docs/shared-plan-execution.md)
@@ -199,14 +219,19 @@ history or failed planning must execute the full affected lanes and fail the
 required planning gate. Ordinary PRs and pushes use selection; manual/release/scheduled/full overrides
 remain complete checkpoints.
 
-CI and public-action smoke run full checkpoints every Monday. Ordinary runs keep
+The **Weekly full checkpoint** workflow dispatches CI and public-action smoke
+every Monday using [CI-esta's shared action](https://github.com/gigaverse-app/ci-esta/blob/main/docs/weekly-checkpoints.md).
+Its small wrapper is generated by `ci-esta checkpoint init`; the source guide
+documents schedule, workflow, ref and input overrides. Ordinary runs keep
 the shared affected-file plan across all six OS/Python combinations and minimum
 pytest. `tests/test_tutorial.py` owns the end-to-end tutorial execution and follows
 that plan; there is no second tutorial invocation in each matrix job. JUnit retains
 its test result and timing, and full plans also upload whole-suite coverage.
 
-To run a complete checkpoint after a CI change, select **CI** in GitHub Actions
-and choose **Run workflow**. Retrying an ordinary PR run preserves its selection;
+To run both complete checkpoints after a CI change, select **Weekly full checkpoint**
+in GitHub Actions and choose **Run workflow**, then inspect the dispatched CI and
+public-action results. A green dispatcher means both requests were accepted.
+You can also dispatch either target directly. Retrying an ordinary PR run preserves its selection;
 use the manual checkpoint when you need full-suite coverage evidence.
 
 ## Duplication

{pytest_selective-1.2.0 → pytest_selective-1.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: pytest-selective
-Version: 1.2.0
+Version: 1.4.0
 Summary: Explainable Python test impact analysis: select affected pytest files from Git changes
 Project-URL: Homepage, https://github.com/gigaverse-app/pytest-selective
 Project-URL: Documentation, https://pytest-selective.readthedocs.io/en/latest/

{pytest_selective-1.2.0 → pytest_selective-1.4.0}/action.yml

@@ -14,6 +14,11 @@ inputs:
   head:
     description: Exact checked-out commit.
     default: HEAD
+  pr-head:
+    description: The pull request's head. When the checkout is GitHub's merge of it (refs/pull/N/merge), changes are measured
+      from that merge's base-branch parent, so commits that landed on the base branch after `base` are not counted as the
+      PR's. Empty (any other event) keeps `base`.
+    default: ${{ github.event.pull_request.head.sha }}
   full-roots:
     description: Space-separated complete test roots used if planning cannot prove a narrower scope.
     required: true
@@ -100,6 +105,7 @@ runs:
       config: ${{ inputs.config }}
       base: ${{ inputs.base }}
       head: ${{ inputs.head }}
+      pr-head: ${{ inputs.pr-head }}
       full-roots: ${{ inputs.full-roots }}
       full: ${{ inputs.full }}
       extra-files: ${{ inputs.extra-files }}

{pytest_selective-1.2.0 → pytest_selective-1.4.0}/actions/plan-lanes/action.yml

@@ -7,6 +7,12 @@ inputs:
   base:
     description: Base commit containing the complete change set.
     default: ${{ github.event.pull_request.base.sha || github.event.before }}
+  pr-head:
+    description: >-
+      The pull request's head. When the checkout is GitHub's merge of it (refs/pull/N/merge), changes are measured from
+      that merge's base-branch parent, so commits that landed on the base branch after `base` are not counted as the PR's.
+      Empty (any other event) keeps `base`.
+    default: ${{ github.event.pull_request.head.sha }}
   full:
     description: 'auto preserves selection on PR/push reruns and runs full for manual/scheduled/release checkpoints or test:full. Override with true or false.'
     default: auto
@@ -40,10 +46,12 @@ runs:
         SELECTIVE_CONFIG: ${{ inputs.config }}
         SELECTIVE_BASE: ${{ inputs.base }}
         SELECTIVE_FULL: ${{ inputs.full }}
+        SELECTIVE_PR_HEAD: ${{ inputs.pr-head }}
       run: |
         export PYTHONPATH="$SELECTIVE_ACTION/../../src${PYTHONPATH:+:$PYTHONPATH}"
         args=(--config "$SELECTIVE_CONFIG" --base "$SELECTIVE_BASE" --github-output "$GITHUB_OUTPUT")
         args+=(--full "$SELECTIVE_FULL")
+        if [ -n "$SELECTIVE_PR_HEAD" ]; then args+=(--pr-head "$SELECTIVE_PR_HEAD"); fi
         uv run --no-project --python 3.14 --with pydantic==2.13.4 --with pyyaml==6.0.3 \
           python -m pytest_selective.ci "${args[@]}" | tee test-lanes.json
         {

{pytest_selective-1.2.0 → pytest_selective-1.4.0}/actions/test-impact/action.yml

@@ -13,6 +13,12 @@ inputs:
   head:
     description: Exact checked-out commit.
     default: HEAD
+  pr-head:
+    description: >-
+      The pull request's head. When the checkout is GitHub's merge of it (refs/pull/N/merge), changes are measured from
+      that merge's base-branch parent, so commits that landed on the base branch after `base` are not counted as the PR's.
+      Empty (any other event) keeps `base`.
+    default: ${{ github.event.pull_request.head.sha }}
   full-roots:
     description: Space-separated complete test roots used if planning cannot prove a narrower scope.
     required: true
@@ -114,6 +120,7 @@ runs:
         IMPACT_CONFIG: ${{ inputs.config }}
         IMPACT_BASE: ${{ inputs.base }}
         IMPACT_HEAD: ${{ inputs.head }}
+        IMPACT_PR_HEAD: ${{ inputs.pr-head }}
         IMPACT_FULL: ${{ inputs.full }}
         IMPACT_EXTRA: ${{ inputs.extra-files }}
         IMPACT_ALTERNATE_BASE: ${{ inputs.alternate-base }}
@@ -147,6 +154,7 @@ runs:
         # A reused workspace must not upload a previous plan's explanation.
         rm -f test-impact-explanation.json
         args+=(--full "$IMPACT_FULL")
+        if [ -n "${IMPACT_PR_HEAD:-}" ]; then args+=(--pr-head "$IMPACT_PR_HEAD"); fi
         if [ -n "$IMPACT_EXTRA" ]; then args+=(--extra-files "$IMPACT_EXTRA"); fi
         if [ -n "${IMPACT_GRAPH_BASE:-}" ]; then args+=(--graph-base "$IMPACT_GRAPH_BASE"); fi
         # Optional: an unfetchable alternate only forgoes a smaller selection.

pytest_selective-1.4.0/contracts/selection/conftest.py.gv-dependency.yaml

@@ -0,0 +1,5 @@
+dependencies:
+  - inputs:
+      - "//contracts/selection/runtime_deps.py"
+    kind: import
+    reason: "The runtime referee, run by path in a subprocess (python -I -B runtime_deps.py) for every history."

pytest_selective-1.4.0/contracts/selection/test_selection_contract.py.gv-dependency.yaml

@@ -0,0 +1,6 @@
+dependencies:
+  - inputs:
+      - "//contracts/selection/quint-connect.json"
+      - "//contracts/selection/selection.qnt"
+    kind: content
+    reason: "quint_contract() reads the contract file, which names the Quint model it runs."

{pytest_selective-1.2.0 → pytest_selective-1.4.0}/docs/ci-toolkit.md

@@ -36,7 +36,14 @@ PR, on a version-only release PR, and on a PR push that changes nothing the
 tests read. A `PR evidence #N head SHA` step ties each PR run to its pull
 request, because GitHub often leaves that link out. The distribution smoke test
 still follows the plan before reuse (`planned`), and partial proof runs the
-whole lane.
+whole lane. The contract lane works the same way with its own receipt and inputs
+(including `README.md`, which its README check reads).
+
+CI-esta decides admission: each evidence step gets the planned lanes and
+`lane-keys`, the keys of every job a lane gates, and reports `admitted-lanes`.
+The contract step chains on the tests step's result. `ci-esta check-workflow`
+then proves `lane-keys` name every job each lane gates, matrix cells included,
+so a newly added cell can never be skipped as proven.
 
 The unconditional CI job runs `ci-esta check-workflow` against this workflow and
 lane configuration, so renamed lanes or omitted metadata prerequisites cannot

{pytest_selective-1.2.0 → pytest_selective-1.4.0}/docs/ci.md

@@ -64,6 +64,14 @@ controls the test interpreter. `full-roots` must contain the complete roots, not
 the previous selection. `base` defaults to the PR base or the push's previous
 commit. Override it only when you have validated a different comparison base.
 
+On a pull request, GitHub checks out a merge of the PR head into the base
+branch's current tip, which can be newer than the PR's recorded base. Both
+actions pass the PR head (`pr-head`) so the planner measures changes from that
+merge's base-branch parent. Commits that landed on the base branch after the PR
+was opened, such as a release's version bump, are then not counted as the PR's
+own. A shallow checkout or any other event keeps `base`. Check out with
+`fetch-depth: 0` to get the narrower plan.
+
 Both file and lane actions default to `full: auto`:
 
 | Trigger | Default |
@@ -277,3 +285,27 @@ The action also uploads the report as the `test-lane-selection` artifact; set
 pull-request sticky's lane section: which lanes ran and why, and the runner time
 the skipped jobs took on the default branch's last full run. See
 [how the two fit together in a Python project](https://github.com/gigaverse-app/ci-esta/blob/main/docs/integrations.md#getting-the-most-from-both-in-a-python-project).
+
+## Split whole lanes by test filename
+
+Lanes sharing a directory can partition its tests with `test_patterns` and
+`exclude_patterns`. Both match repository-relative POSIX paths using the same
+globs as lane inputs; `*` also matches path separators. Roots still limit the
+search. The defaults include every test under the roots and exclude none.
+
+```json
+{
+  "unit": {"roots": ["tests"], "exclude_patterns": ["*_integration.py"]},
+  "integration": {"roots": ["tests"], "test_patterns": ["*_integration.py"]}
+}
+```
+
+Put these entries under `lanes` in the lane configuration. A source dependency
+still selects every lane containing an affected test. Deleted tests use their
+base-revision membership; an affected test claimed by no lane causes a full
+fallback. Explicit inputs and full checkpoints are unaffected by these filters.
+
+Same-named modules in independent module roots are unrelated unless an import
+connects them. An actual ambiguous bare import conservatively retains every
+possible target. Use qualified imports to make independent demo modules
+unambiguous; selection does not guess a runtime import order.

{pytest_selective-1.2.0 → pytest_selective-1.4.0}/docs/configuration.md

@@ -22,6 +22,11 @@ select. The default filenames are `test_*.py`, `*_test.py`, `*_tests.py`, and
 `tests.py`; configure
 `test_patterns` for a different collection policy.
 
+Every `--config` (`affected`, `explain`, `fingerprints`, `audit`, `run` and the rest) also accepts a
+[lane config](ci.md) such as `.github/test-lanes.json`: it uses the lane config's `graph`, with its
+top-level `global_inputs` when declared. Pass the lane config itself rather than a copy of its graph,
+so a later `graph.pytest_policy` refresh is always the one in use.
+
 ## Review and record collection policy
 
 If your repository has `pyproject.toml`, `pytest.ini`, a `tox.ini` with a `[pytest]`
@@ -61,6 +66,9 @@ fixture example, directory manifests, dependency comments, and dynamic Python in
 
 A read that names a tracked file by literal path, such as `open("data/prices.json")` or
 `(Path(__file__).parent / "prices.json").read_text()`, is followed automatically as a content read.
+A string that only names a tracked file, such as a routing test's `("bench.py", ...)` row, adds no
+edge: a dotted string is followed as a possible module name (a patch target, a plugin) only when it
+names no tracked file, from the repository root or beside its reader.
 For a path that is computed, or built from several parts, add a reader-owned comment:
 
 ```python