Adopt the Coherent system

[jaraco]

No description provided.

[jaraco]

The tests are failing upstream, but pass fine for me locally. With e5e418b, tests pass in CI but fail locally. My guess is CI has a stale ruff.

[jaraco]

PyPy is failing with an indication that PyPy 3.10 may not be supported.

creating virtual environment...
installing coherent-test from spec 'coherent-test>=0.7.0'...
Fatal error from pip prevented installation. Full pip output in file:
    /opt/pipx/logs/cmd_2026-05-08_18.15.34_pip_errors.log

pip failed to build package:
    cryptography

Some possibly relevant errors from pip install:
        error: failed to run custom build command for `pyo3-ffi v0.28.3`
          error: the configured PyPy interpreter version (3.10) is lower than PyO3's minimum supported version (3.11)
        Error: command ['maturin', 'pep517', 'build-wheel', '-i', '/opt/pipx/.cache/3a066269010a8cb/bin/python', '--compatibility', 'off'] returned non-zero exit status 1
Error installing coherent-test from spec 'coherent-test>=0.7.0'.

[jaraco]

The tests are failing upstream, but pass fine for me locally. With e5e418b, tests pass in CI but fail locally. My guess is CI has a stale ruff.

I made an update to coherent.test so it now emits the packages installed, but I've found that the CI run and my local run both have the same ruff version (0.15.13), so the difference is not due to the version of ruff installed in the environment. Perhaps the issue is more nuanced - like maybe pytest-ruff isn't using the version of ruff installed in the environment. Or maybe it has nothing to do with the ruff version.

First, I need to confirm this disparity only affects the coherent build.

[jaraco]

The tests are failing upstream, but pass fine for me locally. With e5e418b, tests pass in CI but fail locally. My guess is CI has a stale ruff.

I made an update to coherent.test so it now emits the packages installed, but I've found that the CI run and my local run both have the same ruff version (0.15.13), so the difference is not due to the version of ruff installed in the environment. Perhaps the issue is more nuanced - like maybe pytest-ruff isn't using the version of ruff installed in the environment. Or maybe it has nothing to do with the ruff version.

First, I need to confirm this disparity only affects the coherent build.

I figured out the issue. On my local system, I'd previously checked out the project as a non-coherent project and run ruff there. When that happened, populated the ruff cache with "tempora" as a first-party import. When switching to coherent, ruff no longer detects "tempora" as a first party import, so demands a different syntax. So just a git clean -fdx makes the behavior consistent with CI. I do need to report the issue with first party detection upstream, however.

[jaraco]

Note that 0a1eabf needed to be added to remove the AGENTS.md unintentionally left in this PR.