Restore MPL baseline and add TC axis consistency layer

[pt2710]

Summary

This PR restores the repository to a safer MPL-consistent baseline by branching from commit 3f0ecb65de19ff1a44282a5a671f022fae4c11ab, before the later hardcoded early schedule and wheel(30) replacements.

It then adds a separate TC/U-E-O axis layer instead of overwriting the MPL generator.

Why

The current master contains a wheel(30)-based generator, which is not consistent with the MPL/TC paper architecture. The paper requires a distinction between:

• MPL: regime/motif successor machinery
• TC: U/E/O structural axis coverage
• Bridge / Axis Law: first-hole successor over realized axes

Changes

• Added triadic_domains.py

  • Unity domain U
  • Even domain E via dyadic depth and odd face
  • Odd domain O with O1 as prime/free odd axis
  • O2/O3/O4/... as least-prime-factor composite strata
  • finite-prefix Axis Law helpers

• Added tests/test_triadic_domains.py

  • checks 31 is placed on O1
  • checks 9, 15, 21 are placed on O2
  • checks 25 and 35 are placed on O3
  • checks 49 is placed on O4
  • checks first-hole examples after realized prime axes

Notes

This PR intentionally does not force-push or rewrite master. It creates a repair branch for review. The next step should be to align the MPL runtime itself with the TC axis layer and remove any remaining active-gcd behavior or legacy wheel language from the main branch after review.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c1a7280281

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Add repo-root path setup before importing triadic_domains

This test module imports triadic_domains directly without first adding the repository root to sys.path, unlike tests/test_basic.py, so invoking tests via the pytest entrypoint can fail during collection with ModuleNotFoundError: No module named 'triadic_domains'. In this environment, pytest -q tests/test_triadic_domains.py reproduces the error immediately, which blocks the new test suite from running in common CI/test invocations.

Useful? React with 👍 / 👎.