CodeRabbit Generated Unit Tests: Add unit tests for PR changes

[coderabbitai]

Unit test generation was requested by @canstralian.

• Establish code-quality baseline #15 (comment)

The following files were modified:

• =8.0
• tests/test_contracts.py
• tests/test_import_vectors.py
• tests/test_scope_mapper.py

[coderabbitai]

Important

Review skipped

This PR was authored by the user configured for CodeRabbit reviews. CodeRabbit does not review PRs authored by this user. It's recommended to use a dedicated user account to post CodeRabbit review feedback.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 12c22ea0-272f-4c2a-9c02-05332cde03f6

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[canstralian]

Thanks for the contribution. I’m going to close this PR rather than merge it in its current form.

There are a few issues that make the generated test suite too brittle and noisy for the repository right now:

• The PR includes an unintended file (=8.0) containing pip warning output.
• Several tests hardcode implementation details (exact vector counts, IDs, states, contract names, etc.) instead of validating durable invariants.
• Some tests appear to assume base64-encoded YAML while other parts of the suite parse the same files directly as YAML, which suggests the generator may have misunderstood the repository structure.
• The signal-to-noise ratio is too low relative to the maintenance burden these tests would introduce.

There are still useful ideas here worth preserving:

• validating set -euo pipefail
• ensuring dry-run behavior is safe
• checking registry structure and required fields
• verifying subtree commands are not executed during dry-run flows

I’ll likely replace this with a smaller hand-written invariant-focused test set that aligns more closely with the repo’s actual control-plane and drift assumptions.

Appreciate the effort and automation experimentation regardless.