fix(mirror): carry the tests into the exec mirror, and drop a layout-bound assertion

[stranske]

Two regressions from #90, both found by running verify from the mirror rather than reasoning about it — which is what CLAUDE.md §1 requires, and exactly what it warns of: "cmp-clean is not agreement, since a path resolved relative to a module's own directory is right in one tree and wrong in the other."

1. The exec mirror lost its test suite

Before the move the modules and the 33 test files were all root-level .py, so orch-sync-mirror.sh's single cp "$SRC"/*.py carried both. Afterwards cp "$MODSRC"/*.py carries only the modules — a mirror run collected zero tests and reported floor 442 — NOT MET, which reads as a broken change rather than a broken sync.

The sync script (outside the repo, patched separately) now also copies $SRC/tests/*.py and fails loudly if either half is empty, so a hollow mirror can never be handed to launchd quietly.

In this repo: pyproject.toml gains pythonpath = ["src", "."]. Both entries are load-bearing, in different trees — a checkout resolves the modules through src, the flat mirror through .. pytest ignores a pythonpath entry that doesn't exist, so one list is correct in both shapes; same detect-don't-assume rule paths.py applies in Python and orchestrate.sh in shell.

The sync also now removes the file pyproject.toml replaced. Its delete step only clears *.py and *.sh, so the migrated-away .coveragerc lingered — and test_coverage_config_enables_parallel_mode correctly refuses that, because CI reads only pyproject.toml and the two would disagree with nothing to say so.

2. An assertion I added in #90 was true in one tree only

env_prereq's selftest asserted that a module name is absent from the checkout root. True under src/; false in the flat mirror, where the module dir and the checkout root are the same directory. It passed in the repo and failed in the mirror.

Removed rather than made conditional. The detector's real contract is layout-independent — present ⇒ None, absent ⇒ a reason naming it — and the surrounding assertions already check exactly that. A test that holds in only one layout is worse than none, because it makes the other layout look broken.

Verified in both trees, which is the point

tree	result
repo (src/)	442 passed, 0 failed, 0 skipped, 85/85 selftests, 5/5 gates
mirror (flat, what launchd runs)	419 passed, 0 failed, 23/26 skipped (the documented repo-config skips), 442 collected against floor 442, 85/85 selftests, 5/5 gates

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

Next included review available in 47 minutes.

View limit details

Limit details: You’ve used the included review currently available. Your 74 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 8bc93c8e-a698-488a-b212-90f412d732fa

📥 Commits

Reviewing files that changed from the base of the PR and between 6c6648d and 3ff49a7.

📒 Files selected for processing (2)

• pyproject.toml
• src/env_prereq.py

---

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

[agents-workflows-bot]

Workflow source needed

PR #92 needs either a linked GitHub issue or one valid non-issue Workflow Source before PR metadata automation can manage it safely.

Please do one of:

• Add <!-- meta:issue:123 --> or a normal Closes #123 / Related to #123 line.
• Check one Workflow Source option in the PR body.
• Add a hidden marker such as <!-- workflow-source:local_request -->, <!-- workflow-source:manual_remote -->, <!-- workflow-source:review_followup -->, <!-- workflow-source:sync_campaign -->, or <!-- workflow-source:dependabot -->.
• Add a workflow source label such as workflow:source-direct-pr, workflow:source-local-request, workflow:source-review-followup, workflow:source-sync, or workflow:no-automation.

Once a valid source is present, this warning will not be reposted.