pytest-selective 1.3.0__tar.gz → 1.5.0__tar.gz

pytest_selective-1.3.0/.github/test-lanes.json → pytest_selective-1.5.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.5.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.3.0 → pytest_selective-1.5.0}/.github/workflows/ci.yml

@@ -13,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:
@@ -31,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 }}
@@ -49,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
@@ -82,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') &&
@@ -93,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:
@@ -119,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.3.0 → pytest_selective-1.5.0}/.github/workflows/public-actions.yml

@@ -15,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
@@ -35,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: ./
@@ -57,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: ''
@@ -68,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.5.0/.release-please-manifest.json

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

{pytest_selective-1.3.0 → pytest_selective-1.5.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.3.0 → pytest_selective-1.5.0}/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## [1.5.0](https://github.com/gigaverse-app/pytest-selective/compare/v1.4.0...v1.5.0) (2026-11-09)
+
+
+### Features
+
+* **declarations:** share reader-relative dependency rules ([#139](https://github.com/gigaverse-app/pytest-selective/issues/139)) ([7eea4ba](https://github.com/gigaverse-app/pytest-selective/commit/7eea4ba3ec3fd4607acf1e52b171e6eabd0c96fc))
+
+## [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)
 
 

{pytest_selective-1.3.0 → pytest_selective-1.5.0}/CONTRIBUTING.md

@@ -65,6 +65,7 @@ uv run --group quint pytest-quint-connect report '**/.artifacts/quint-connect/re
 | Private working-tree snapshots, staged inputs and index timestamp preservation | `working_tree.py` |
 | Python module names, Unicode matching and dotted import relationships | `ast_imports.py` |
 | Test-file discovery and cache exclusions | `test_inventory.py` |
+| Reader-owned declaration grammar, path expansion and dependency kinds | `impact_declarations.py`, with the canonical models in `impact_models.py` |
 | Repository-relative path containment, including the dot root | `impact_graph.within` |
 
 The expansion guard imports the first three owners directly when run as a script;
@@ -98,24 +99,47 @@ 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
+`# gv:test-dependency: PATH` comment for simple inputs, or a directory
+`.gv-dependencies.yaml` with `relative_to: reader` for repeated local layouts).
+Keep per-reader sidecars for exceptions needing separate declarations. Review
+`pytest-selective audit --write-declarations` output for shared conventions before
+retaining its individual sidecars; preserve `content` versus `import` semantics.
+`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)

{pytest_selective-1.3.0 → pytest_selective-1.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: pytest-selective
-Version: 1.3.0
+Version: 1.5.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.5.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.5.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.3.0 → pytest_selective-1.5.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.3.0 → pytest_selective-1.5.0}/docs/ci.md

@@ -285,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.3.0 → pytest_selective-1.5.0}/docs/configuration.md

@@ -89,6 +89,12 @@ root. `content` follows the file's bytes; `import` also follows its dependencies
 The default is `import`. Inputs must match tracked files. Invalid patterns,
 missing matches, duplicate YAML keys, and aliases are errors to repair.
 
+For repeated conventions, a directory `.gv-dependencies.yaml` can match `readers`
+and set `relative_to: reader`: each unanchored input then resolves beside each
+matched reader. The default remains `relative_to: manifest`, and `//` always
+anchors at the repository root. This keeps sibling readers' inputs separate;
+see [shared conventions](tutorials/sidecar-dependencies.md#share-a-convention-without-sharing-every-input).
+
 Declare lock files, environment manifests, and other suite-wide inputs explicitly:
 
 ```json

{pytest_selective-1.3.0 → pytest_selective-1.5.0}/docs/selection-health.md

@@ -29,8 +29,11 @@ uv run pytest-selective audit --config .github/test-impact.json --records impact
 
 The recorder observes real file reads in the tests you execute. The audit can
 expose a JSON fixture, template or schema that the graph did not declare. Add an
-edge at the reader using a dependency comment or YAML sidecar, then recheck the
-route. `audit --write-declarations` writes those sidecars for you; see
+edge at the reader using a dependency comment, shared directory manifest or YAML
+sidecar, then recheck the route. Prefer a shared `relative_to: reader` convention
+for repeated layouts, preserving each reader's own input scope and dependency kind.
+`audit --write-declarations` writes individual sidecars as a starting point;
+review repeated patterns before keeping them. Existing shared rules satisfy the audit. See
 [write the missing declarations](configuration.md#write-the-missing-declarations). [Work through the sidecar tutorial](tutorials/sidecar-dependencies.md), or consult
 [declaration syntax](configuration.md#declare-inputs-that-imports-cannot-describe).
 The audit covers observed paths; keep representative full runs for paths it has

{pytest_selective-1.3.0 → pytest_selective-1.5.0}/docs/tutorials/adoption-checklist.md

@@ -100,6 +100,9 @@ dependencies:
 - [ ] Use `content` for bytes read as data, and `import` when the reader executes
   Python and needs that module's transitive dependencies.
 - [ ] Keep declarations beside readers; use central rules for actual shared policy.
+- [ ] Replace repeated per-reader layouts with directory manifest rules using
+  `relative_to: reader`; compare affected readers and lanes before and after,
+  including sibling inputs, new matching files and deletions.
 - [ ] Review locks, environment configuration, external checkout pins and plugin startup.
 - [ ] Retain default global inputs until a narrower environment contract is verified.
 - [ ] Review nested/custom pytest configuration before refreshing fingerprints.

{pytest_selective-1.3.0 → pytest_selective-1.5.0}/docs/tutorials/sidecar-dependencies.md

@@ -20,7 +20,7 @@ cd selective-sidecar-demo
 git init
 python -m venv .venv
 source .venv/bin/activate
-python -m pip install "pytest-selective>=0.3,<0.4"
+python -m pip install "pytest-selective>=1,<2"
 mkdir -p tests/data
 ```
 
@@ -142,7 +142,7 @@ change should select its reader. There is no universal documentation exemption.
 | --- | --- | --- |
 | Dependency comment | In the reading Python file | One or two inputs fit naturally beside the code |
 | File sidecar | `reader.py.gv-dependency.yaml` | You need an explicit dependency kind or want declarations outside Python |
-| Directory manifest | `.gv-dependencies.yaml` | Several related readers share inputs |
+| Directory manifest | `.gv-dependencies.yaml` | Several related readers share inputs or a per-reader layout convention |
 
 Instead of the sidecar above, a comment in `tests/test_prices.py` can declare:
 
@@ -172,6 +172,46 @@ are relative to its directory. `//` anchors either pattern at the repository
 root, for example `//schemas/receipt.json`. Do not use `../` to reach another
 directory.
 
+### Share a convention without sharing every input
+
+When each reader consumes files beside itself, use `relative_to: reader` in a
+directory manifest. For example, `contracts/.gv-dependencies.yaml` can replace
+one sidecar per contract:
+
+```yaml
+dependencies:
+  - readers: ["**/test_*_contract.py"]
+    relative_to: reader
+    inputs: ["model.qnt", "quint-connect.json", "history/**", "//contracts/quint.ini"]
+    kind: content
+    reason: Each contract reads its own model, manifest and history under the shared pytest configuration.
+```
+
+The `readers` pattern is still relative to the manifest. Each unanchored input
+is resolved separately beside each matched reader; `//` still means the repository
+root. Changing one contract's model selects its readers, without connecting sibling
+contracts to that model. New matching readers inherit the same convention. Every
+input pattern must match for **each** reader; a missing history directory in one
+contract is an error even if a sibling has one. Omit inputs your convention does
+not require, or put distinct conventions in separate rules.
+
+The default, `relative_to: manifest`, preserves existing behavior. Both modes
+support `content` and `import`; a file sidecar has the same directory as its reader,
+so either mode means the same thing there. Expansion is reused for readers in the
+same directory within a rule and rebuilt against each Git tree, including added
+files and deleted inputs. Editing the shared manifest selects all its readers;
+keep unrelated conventions in separate manifests.
+
+For a source scanner, the same mechanism can declare `readers: ["*/test_inventory.py"]`
+with `inputs: ["**/*.py"]`, `relative_to: reader` and `kind: content`. Each inventory
+then follows only the Python source under its own directory. Prefer this to a broad
+rule joining every scanner to every project's source.
+
+Keep the convention where its readers live. A project-specific layout belongs in
+its manifest; it does not need a framework-specific plugin in the selector. Review
+`audit --write-declarations` output for repeated layouts before retaining individual
+sidecars. An existing shared rule already satisfies the audit for covered reads.
+
 ### Reading content versus executing Python
 
 | Input use | Kind | What changes can select the reader |