sisters

To detect GitHub Actions version pin drift, this audit compares `uses: owner/action@version` pins across related repositories, reporting mismatched versions that cause flaky CI or divergent behaviors. It provides read-only visibility into cross-repo configuration inconsistencies before applying fixes.

Cross-repository configuration drift occurs when related repositories lose synchronized CI, tooling, and operational conventions. This audit identifies drift in GitHub Actions pins, merge policies, branch protection, and `pyproject.toml` toolchain settings to prevent hidden inconsistencies during releases.

Auditing branch protection rules and merge settings across related repositories detects divergence in merge configurations and validates that `main` is protected with required checks. This audit surfaces those protection and hygiene signals in a categorized findings report.

Yes, you can check toolchain pin consistency by surfacing drift in `requires-python`, Ruff target-version, and dev tool specs like `ruff`, `ty`, and `pytest` at the root `pyproject.toml` level. This audit compares those settings across related repositories to ensure synchronization.

Yes, authenticated `gh` and `git` access via allowed shell commands is required to run the cross-repo audit. The tool loads the active sister set from your `~/.claude/techne.toml` configuration and executes targeted read-only inspection checks.

Operational hygiene signals to monitor include rolling up open PRs, flagging stale branches, checking local `main` vs `origin/main` divergence, and looking for conventions like Codecov config and log-retention policies. This audit compiles these signals into a categorized findings report.