AFI parity: generate the matrix from conformance probes, not prose
The per-adapter parity table was hand-maintained prose. An adapter that
never wired a capability (FastAPI SSR, Axum WebSocket) got its gap
relabelled "Django-only" or "out of scope — use native equivalents," and
nothing went red. The de-scope was crystallized in five mutually-ratifying
sites: the README §Stack-extensions table, the AFI fixture docstring
("channels/forms/shapes aren't AFI-common"), the core registry's
extension-hook framing, the mizan-fastapi __init__ docstring, and a
"CSRF is Django-only" comment in two adapters' session endpoints.
Replace prose-parity with conformance-generated parity:
- tests/afi/manifest.py declares the AFI-common surface as data — one list
of capabilities, one of adapters. Applicability ("—") is derived from
transport, never typed.
- tests/afi/probes.py independently inspects each backend's source for the
artifact a capability requires (comment-stripped, backend-scoped). Green
means wired; a cell can't be set by editing a word.
- tests/afi/test_capability_parity.py asserts every (capability × applicable
adapter) pair is wired. 35 unwired gaps are now loud red TFDD tests, each
naming an owed binding. No xfail/skip.
- tests/afi/parity_table.py generates the README table from the probes;
`make parity-check` fails CI on any hand-edit, like the codegen byte-parity.
Purge the five de-scope sites. The IR byte-parity gate is unchanged and green.
`make test-afi` is now intentionally red on the 35 gaps — that board is the
owed parity work, itemized; a gap turns green by being wired, never described.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
19
Makefile
19
Makefile
@@ -1,4 +1,4 @@
|
||||
.PHONY: install test test-core test-django test-fastapi test-react test-afi test-integration docker-up docker-down clean
|
||||
.PHONY: install test test-core test-django test-fastapi test-react test-afi parity-table parity-check test-integration docker-up docker-down clean
|
||||
|
||||
CORE = cores/mizan-python
|
||||
DJANGO = backends/mizan-django
|
||||
@@ -30,11 +30,24 @@ test-fastapi:
|
||||
test-react:
|
||||
cd $(REACT) && npm test
|
||||
|
||||
# AFI conformance — verifies mizan-django and mizan-fastapi emit equivalent
|
||||
# schemas for the same @client fixture. Substrate-level gate, not e2e.
|
||||
# AFI conformance — two gates, substrate-level, not e2e:
|
||||
# test_codegen_parity.py — Django/FastAPI/Rust emit byte-identical KDL IR.
|
||||
# test_capability_parity.py — every (capability, applicable adapter) pair is
|
||||
# probed for its wiring. RED on every unwired gap
|
||||
# by design: that board is the owed work, itemized.
|
||||
test-afi:
|
||||
cd $(AFI) && uv run pytest
|
||||
|
||||
# Regenerate the README parity table from the live conformance probes. The table
|
||||
# is generated output — never hand-edited.
|
||||
parity-table:
|
||||
cd $(AFI) && uv run python parity_table.py --write
|
||||
|
||||
# CI gate: the committed README parity table matches what the probes report.
|
||||
# Fails on any hand-edit, the same forcing function as the codegen byte-parity.
|
||||
parity-check:
|
||||
cd $(AFI) && uv run python parity_table.py --check
|
||||
|
||||
# ─── Integration Tests ──────────────────────────────────────────────────────
|
||||
|
||||
test-integration: docker-up
|
||||
|
||||
Reference in New Issue
Block a user