Build AI methods with your coding agent, then run them anywhere: as an MCP for chatbots, as a webapp for people, or via API for your software.
chore/Repoint-specs-path · L-260914-8d49e6 (#1373)
Louis Choquel64bee3924c5c
diff --git a/api/pipelex_api/schemas/models.py b/api/pipelex_api/schemas/models.pyindex a45c68312..12df7f4ed 100644--- a/api/pipelex_api/schemas/models.py+++ b/api/pipelex_api/schemas/models.py@@ -53,8 +53,9 @@ class RunRequest(BaseModel):deliberately open (`extra="allow"`): a caller may send extra requestproperties, and they are kept rather than silently dropped. Openness is nota waiver, though — an unknown key never satisfies the run-source- precondition. Under the layered extension policy (the Pipelex workspace- spec `docs/specs/pipelex-platform-api.md` → "Layered extension policy"), an+ precondition. Under the layered extension policy+ (`conformance/specs/pipelex-platform-api.md` → "Layered extension policy",+ in the `conformance` repo beside the tests that verify it), anextension-borne method selector is resolved by the layer that owns itBEFORE the request reaches this one, so a body arriving here with no sourcethis server understands is an error whatever else it carries.diff --git a/api/tests/unit/test_codegen_route.py b/api/tests/unit/test_codegen_route.pyindex f65ba4ac4..69aeff2a2 100644--- a/api/tests/unit/test_codegen_route.py+++ b/api/tests/unit/test_codegen_route.py@@ -1,9 +1,10 @@"""Envelope tests for `POST /v1/codegen` — the typed-artifact projection route.-Pins `docs/specs/pipelex-codegen.md#route-envelopes` (workspace root): the two explicit projection-axes (`kind`, `target`); a produced verdict is a 200 discriminated on `is_valid` with the stamped-artifacts + lock on the valid arm; an unknown `kind`/`target` is a request-shape 422 problem+json;-the artifacts a client writes verbatim pass the offline `codegen check` byte-for-byte.+Pins `conformance/specs/pipelex-codegen.md#route-envelopes`, in the `conformance` repo beside the tests+that verify it: the two explicit projection axes (`kind`, `target`); a produced verdict is a 200+discriminated on `is_valid` with the stamped artifacts + lock on the valid arm; an unknown+`kind`/`target` is a request-shape 422 problem+json; the artifacts a client writes verbatim pass the+offline `codegen check` byte-for-byte."""from pathlib import Pathdiff --git a/api/tests/unit/test_pipe_io_route.py b/api/tests/unit/test_pipe_io_route.pyindex ef3e25a7a..b4a035606 100644--- a/api/tests/unit/test_pipe_io_route.py+++ b/api/tests/unit/test_pipe_io_route.py@@ -1,11 +1,12 @@"""Tests for `POST /v1/pipe-io` — a method's three I/O artifacts off the resolved crate, with no dry run.-Pins `docs/specs/pipelex-codegen.md#the-pipe-io-route` (workspace root): the route resolves the-closure through the crate routes' static core, selects a pipe with the per-pipe routes' chain, and-returns `pipe_io_contracts`, `input_form` and `output_form` keyed by qualified `pipe_ref`, beside-`pipe_ref`, `default_pipe_ref`, `pending_signatures`, `is_runnable` and, on request, the closure's-files. The pinning cases hold each artifact equal to `/v1/validate`'s same-named view for the same-closure and pipe; the teardown cases hold the loaded-on-success contract on every exit.+Pins `conformance/specs/pipelex-codegen.md#the-pipe-io-route`, in the `conformance` repo beside the+tests that verify it: the route resolves the closure through the crate routes' static core, selects a+pipe with the per-pipe routes' chain, and returns `pipe_io_contracts`, `input_form` and `output_form`+keyed by qualified `pipe_ref`, beside `pipe_ref`, `default_pipe_ref`, `pending_signatures`,+`is_runnable` and, on request, the closure's files. The pinning cases hold each artifact equal to+`/v1/validate`'s same-named view for the same closure and pipe; the teardown cases hold the+loaded-on-success contract on every exit."""from collections.abc import Callablediff --git a/api/tests/unit/test_resolve_route.py b/api/tests/unit/test_resolve_route.pyindex f45de5b63..6b6d2136d 100644--- a/api/tests/unit/test_resolve_route.py+++ b/api/tests/unit/test_resolve_route.py@@ -1,10 +1,10 @@"""Envelope tests for `POST /v1/resolve` — the normalized-crate resolution route.-Pins `docs/specs/pipelex-codegen.md#route-envelopes` (workspace root): the request accepts inline-`files[]` XOR a `method_ref`; a produced verdict is a 200 discriminated on `is_valid` with the-crate on the valid arm; request-shape errors are 422 problem+json; an address-form `method_ref`-resolves the fetched package's `.mthds` files into the closure, while the registry form keeps its-honest 501 until the method registry exists.+Pins `conformance/specs/pipelex-codegen.md#route-envelopes`, in the `conformance` repo beside the tests+that verify it: the request accepts inline `files[]` XOR a `method_ref`; a produced verdict is a 200+discriminated on `is_valid` with the crate on the valid arm; request-shape errors are 422+problem+json; an address-form `method_ref` resolves the fetched package's `.mthds` files into the+closure, while the registry form keeps its honest 501 until the method registry exists."""from collections.abc import Callablediff --git a/api/tests/unit/test_run_source_precondition.py b/api/tests/unit/test_run_source_precondition.pyindex bc86adfd3..8706ec7c3 100644--- a/api/tests/unit/test_run_source_precondition.py+++ b/api/tests/unit/test_run_source_precondition.py@@ -1,7 +1,7 @@"""Route-level tests for the run-source precondition on /execute and /start.-Pins the layered extension policy's Rule 4 (the Pipelex workspace spec-`docs/specs/pipelex-platform-api.md` → "Layered extension policy"): an unknown+Pins the layered extension policy's Rule 4 (`conformance/specs/pipelex-platform-api.md` →+"Layered extension policy", in the `conformance` repo beside the tests that verify it): an unknownextension key never waives the requirement that a run request carry a sourcethis server understands, and a source-less body whose keys this deployment doesnot handle gets a message that NAMES them — so "a hosted client was pointed atdiff --git a/docs/contribute/mthds-test-corpus.md b/docs/contribute/mthds-test-corpus.mdindex 17a9af761..e20831557 100644--- a/docs/contribute/mthds-test-corpus.md+++ b/docs/contribute/mthds-test-corpus.md@@ -2,7 +2,7 @@The MTHDS Test Corpus is one canonical, tagged set of `.mthds` methods that every repository building on the MTHDS language — this runtime and the tools and services around it — draws its language-level fixtures from. It lives at `pipelex/test_extras/mthds_corpus/`, ships in the wheel, and is gated on both sides: the corpus must cover every feature the runtime registers, and each consumer must exercise every entry in the slice it declares.-This page is both the pipelex-side working guide — where things are, how to add an entry, and what each gate is telling you when it goes red — and the contract other repositories are written against: the entry layout, the `entry.toml` manifest, the closed tag vocabulary with its `fails_at` field, the conformance tiers, and the two ways a consumer reaches the corpus.+This page is both the pipelex-side working guide — where things are, how to add an entry, and what each gate is telling you when it goes red — and the public statement of the contract other repositories are written against: the entry layout, the `entry.toml` manifest, the closed tag vocabulary with its `fails_at` field, the conformance tiers, and the two ways a consumer reaches the corpus.!!! note "Why it exists"diff --git a/pipelex/cli/dev_cli/commands/generate_corpus_vocabulary_cmd.py b/pipelex/cli/dev_cli/commands/generate_corpus_vocabulary_cmd.pyindex 7731c7afe..63dfb56e6 100644--- a/pipelex/cli/dev_cli/commands/generate_corpus_vocabulary_cmd.py+++ b/pipelex/cli/dev_cli/commands/generate_corpus_vocabulary_cmd.py@@ -1,6 +1,7 @@"""Command to generate the MTHDS Test Corpus tag vocabulary.-Contract: ``docs/specs/mthds-test-corpus.md`` (workspace root), section "Tag vocabulary".+Contract: ``conformance/specs/mthds-test-corpus.md`` (the cross-repo spec, kept in the ``conformance``+repo), section "Tag vocabulary".The generator is unshipped dev tooling — the wheel excludes ``pipelex/cli/dev_cli`` — while the``vocabulary.toml`` it writes into the corpus tree is committed and ships. That split is the@@ -45,8 +46,8 @@ _HEADER = """# The MTHDS Test Corpus tag vocabulary — the closed set an entry'# expects a diagnostic on exactly the `schema` entries and none on the others.## This file ships in the pipelex wheel, so it names a document its readers can reach:-# https://docs.pipelex.com/contribute/mthds-test-corpus/ — which in turn points at the-# cross-repo contract, `docs/specs/mthds-test-corpus.md` in the Pipelex workspace repo.+# https://docs.pipelex.com/contribute/mthds-test-corpus/, which states the contract the corpus's+# consumers are written against."""_ADVISORY_HINT_LINT_EXCLUSION = (diff --git a/pipelex/pipeline/input_form.py b/pipelex/pipeline/input_form.pyindex 8855f22b2..956f4bcf9 100644--- a/pipelex/pipeline/input_form.py+++ b/pipelex/pipeline/input_form.py@@ -1,11 +1,11 @@"""Per-pipe input-form descriptors (`input_form`) for the validate surfaces.-This is the reference derivation of the MTHDS input-form descriptor (workspace spec-`docs/specs/mthds-input-form-descriptor.md`): for each loaded pipe, an ordered list of field-descriptors a renderer can turn into a fill-in form with no schema heuristics, no hardcoded-concept tables, and no description matching. It is keyed by the same namespaced `pipe_ref` set as-`pipe_io_contracts` — both are built from the same loaded pipes, so the key spaces are equal by-construction.+This is the reference derivation of the MTHDS input-form descriptor (spec:+`conformance/specs/mthds-input-form-descriptor.md`, in the `conformance` repo beside the tests that+verify it): for each loaded pipe, an ordered list of field descriptors a renderer can turn into a+fill-in form with no schema heuristics, no hardcoded concept tables, and no description matching.+It is keyed by the same namespaced `pipe_ref` set as `pipe_io_contracts` — both are built from the+same loaded pipes, so the key spaces are equal by construction.**The wire shapes belong to the standard, not to this engine.** `FieldKind`, the per-kind fieldmodels, their two unions and `PipeInputFormDescriptor` are the models ofdiff --git a/pipelex/test_extras/mthds_corpus/loader.py b/pipelex/test_extras/mthds_corpus/loader.pyindex a81eca707..347267bd3 100644--- a/pipelex/test_extras/mthds_corpus/loader.py+++ b/pipelex/test_extras/mthds_corpus/loader.py@@ -1,6 +1,7 @@"""The MTHDS Test Corpus loader — how a consumer takes a view of the corpus.-Contract: ``docs/specs/mthds-test-corpus.md`` (workspace root), section "Loader API".+Contract: ``conformance/specs/mthds-test-corpus.md`` (the cross-repo spec, kept in the ``conformance``+repo), section "Loader API".A consumer selects entries by the axes it declares rather than by path convention, soreorganizing storage never breaks it."""diff --git a/pipelex/test_extras/mthds_corpus/manifest.py b/pipelex/test_extras/mthds_corpus/manifest.pyindex e184f6f84..20d73446a 100644--- a/pipelex/test_extras/mthds_corpus/manifest.py+++ b/pipelex/test_extras/mthds_corpus/manifest.py@@ -1,6 +1,7 @@"""The MTHDS Test Corpus entry manifest — the strict model behind every ``entry.toml``.-Contract: ``docs/specs/mthds-test-corpus.md`` (workspace root), section "The entry manifest".+Contract: ``conformance/specs/mthds-test-corpus.md`` (the cross-repo spec, kept in the ``conformance``+repo), section "The entry manifest".The model is deliberately strict: an unknown key is an error rather than aforward-compatibility affordance, so a new field is a change to the spec and to thismodel in the same commit.diff --git a/pipelex/test_extras/mthds_corpus/vocabulary.py b/pipelex/test_extras/mthds_corpus/vocabulary.pyindex e17e5a75a..96664b2f8 100644--- a/pipelex/test_extras/mthds_corpus/vocabulary.py+++ b/pipelex/test_extras/mthds_corpus/vocabulary.py@@ -1,6 +1,7 @@"""The MTHDS Test Corpus tag vocabulary — the closed set an entry's ``covers`` draws from.-Contract: ``docs/specs/mthds-test-corpus.md`` (workspace root), section "Tag vocabulary".+Contract: ``conformance/specs/mthds-test-corpus.md`` (the cross-repo spec, kept in the ``conformance``+repo), section "Tag vocabulary".``vocabulary.toml`` is generated in full by ``pipelex-dev generate-corpus-vocabulary`` andcommitted, so a consumer reading it needs neither the generator nor a registry walk. Thismodule is the reader; the generator lives in the dev CLI, which the wheel excludes.diff --git a/pipelex/test_extras/mthds_corpus/vocabulary.toml b/pipelex/test_extras/mthds_corpus/vocabulary.tomlindex 562599db1..78a56b0e4 100644--- a/pipelex/test_extras/mthds_corpus/vocabulary.toml+++ b/pipelex/test_extras/mthds_corpus/vocabulary.toml@@ -11,8 +11,8 @@# expects a diagnostic on exactly the `schema` entries and none on the others.## This file ships in the pipelex wheel, so it names a document its readers can reach:-# https://docs.pipelex.com/contribute/mthds-test-corpus/ — which in turn points at the-# cross-repo contract, `docs/specs/mthds-test-corpus.md` in the Pipelex workspace repo.+# https://docs.pipelex.com/contribute/mthds-test-corpus/, which states the contract the corpus's+# consumers are written against.[native.dynamic]code = "Dynamic"diff --git a/tests/integration/pipelex/pipeline/test_input_form.py b/tests/integration/pipelex/pipeline/test_input_form.pyindex 6b71daf29..504de08cc 100644--- a/tests/integration/pipelex/pipeline/test_input_form.py+++ b/tests/integration/pipelex/pipeline/test_input_form.py@@ -1,9 +1,10 @@"""Pin the D2 `build_input_form` deriver: the per-pipe input-form descriptor from authored facts.-Contract: the workspace spec `docs/specs/mthds-input-form-descriptor.md`. The descriptor is derived-from the loaded pipes (slot facts: order, presence, multiplicity) plus the authored blueprints-(concept facts: descriptions, refinement chains, structure fields) — never from the emitted JSON-Schema, so the facts the schema projection destroys (S1 findings E1-E10) survive here:+Contract: `conformance/specs/mthds-input-form-descriptor.md`, in the `conformance` repo beside the+tests that verify it. The descriptor is derived from the loaded pipes (slot facts: order, presence,+multiplicity) plus the authored blueprints (concept facts: descriptions, refinement chains,+structure fields) — never from the emitted JSON Schema, so the facts the schema projection destroys+(S1 findings E1-E10) survive here:- concept identity on every concept-typed node (E1) and the refinement chain as a stated list (E2);- three-valued `presence` so `!` is not flattened (E5), and `gating` stated as its own fact;diff --git a/tests/integration/pipelex/test_extras/test_mthds_corpus_entries.py b/tests/integration/pipelex/test_extras/test_mthds_corpus_entries.pyindex 0017d78c7..d6dfd94e0 100644--- a/tests/integration/pipelex/test_extras/test_mthds_corpus_entries.py+++ b/tests/integration/pipelex/test_extras/test_mthds_corpus_entries.py@@ -1,7 +1,7 @@"""The MTHDS Test Corpus entry-validation gate: every entry means what its manifest claims.-Contract: ``docs/specs/mthds-test-corpus.md`` (workspace root), section "Gates" →-"Corpus-side: entry validation".+Contract: ``conformance/specs/mthds-test-corpus.md`` (the cross-repo spec, kept in the ``conformance``+repo), section "Gates" → "Corpus-side: entry validation".It drives the in-process validation engine — the one behind ``pipelex validate bundle`` — andnever a hosted API: the corpus is defined against the local runtime, and a deployed API lagsdiff --git a/tests/integration/pipelex/test_extras/test_mthds_corpus_packaging.py b/tests/integration/pipelex/test_extras/test_mthds_corpus_packaging.pyindex 8346fd8f9..06325418d 100644--- a/tests/integration/pipelex/test_extras/test_mthds_corpus_packaging.py+++ b/tests/integration/pipelex/test_extras/test_mthds_corpus_packaging.py@@ -1,6 +1,7 @@"""The corpus ships in the wheel — asserted against a wheel that is actually built.-Contract: ``docs/specs/mthds-test-corpus.md`` (workspace root), section "Distribution".+Contract: ``conformance/specs/mthds-test-corpus.md`` (the cross-repo spec, kept in the ``conformance``+repo), section "Distribution".Wheel consumers reach the corpus through ``importlib.resources``, so a corpus that stopped beingpackaged would be invisible in this repo and would break every consumer at once, on the release.diff --git a/tests/unit/pipelex/test_extras/test_mthds_corpus_exhaustivity.py b/tests/unit/pipelex/test_extras/test_mthds_corpus_exhaustivity.pyindex 17341093c..e3ac825bc 100644--- a/tests/unit/pipelex/test_extras/test_mthds_corpus_exhaustivity.py+++ b/tests/unit/pipelex/test_extras/test_mthds_corpus_exhaustivity.py@@ -1,7 +1,7 @@"""The corpus-side exhaustivity gate — the gate the whole corpus exists for.-Contract: ``docs/specs/mthds-test-corpus.md`` (workspace root), section "Gates" →-"Corpus-side: exhaustivity".+Contract: ``conformance/specs/mthds-test-corpus.md`` (the cross-repo spec, kept in the ``conformance``+repo), section "Gates" → "Corpus-side: exhaustivity".The moment a runtime registry grows a code, regeneration adds its tag and this gate stays reduntil a focused entry covers it. It is why "the `Time` native concept has no fixture anywhere"diff --git a/tests/unit/pipelex/test_extras/test_mthds_corpus_loader.py b/tests/unit/pipelex/test_extras/test_mthds_corpus_loader.pyindex f0718a102..4adaec211 100644--- a/tests/unit/pipelex/test_extras/test_mthds_corpus_loader.py+++ b/tests/unit/pipelex/test_extras/test_mthds_corpus_loader.py@@ -1,7 +1,7 @@"""Loading the corpus and taking a view of it.-Contract: ``docs/specs/mthds-test-corpus.md`` (workspace root), sections "Entry layout" and-"Loader API".+Contract: ``conformance/specs/mthds-test-corpus.md`` (the cross-repo spec, kept in the ``conformance``+repo), sections "Entry layout" and "Loader API".The bundles themselves are validated by the integration-tier entry gate; this module pins thelayout rules and the filter semantics a consumer selects on.diff --git a/tests/unit/pipelex/test_extras/test_mthds_corpus_manifest.py b/tests/unit/pipelex/test_extras/test_mthds_corpus_manifest.pyindex 937cb250b..439476207 100644--- a/tests/unit/pipelex/test_extras/test_mthds_corpus_manifest.py+++ b/tests/unit/pipelex/test_extras/test_mthds_corpus_manifest.py@@ -1,6 +1,7 @@"""The strict `entry.toml` model.-Contract: ``docs/specs/mthds-test-corpus.md`` (workspace root), section "The entry manifest".+Contract: ``conformance/specs/mthds-test-corpus.md`` (the cross-repo spec, kept in the ``conformance``+repo), section "The entry manifest".Strictness is the point: an unknown key is an error rather than a forward-compatibilityaffordance, so a new field is a change to the spec and to the model in the same commit.diff --git a/tests/unit/pipelex/test_extras/test_mthds_corpus_plxt_exclusions.py b/tests/unit/pipelex/test_extras/test_mthds_corpus_plxt_exclusions.pyindex 027cee3c1..f3b397194 100644--- a/tests/unit/pipelex/test_extras/test_mthds_corpus_plxt_exclusions.py+++ b/tests/unit/pipelex/test_extras/test_mthds_corpus_plxt_exclusions.py@@ -1,6 +1,7 @@"""This repo's own linter config, gated against the corpus's ``fails_at`` signal.-Contract: ``docs/specs/mthds-test-corpus.md`` (workspace root), section "Tag vocabulary".+Contract: ``conformance/specs/mthds-test-corpus.md`` (the cross-repo spec, kept in the ``conformance``+repo), section "Tag vocabulary".`pipelex` is the first consumer of its own signal, and `.pipelex/plxt.toml` is where it consumesit. Every deliberately invalid corpus entry used to be excluded from `plxt lint` by one blanketdiff --git a/tests/unit/pipelex/test_extras/test_mthds_corpus_vocabulary.py b/tests/unit/pipelex/test_extras/test_mthds_corpus_vocabulary.pyindex 2dfa0df2f..49de40851 100644--- a/tests/unit/pipelex/test_extras/test_mthds_corpus_vocabulary.py+++ b/tests/unit/pipelex/test_extras/test_mthds_corpus_vocabulary.py@@ -1,6 +1,7 @@"""The corpus tag vocabulary: normalization, generation drift, and the exclusion mechanism.-Contract: ``docs/specs/mthds-test-corpus.md`` (workspace root), section "Tag vocabulary".+Contract: ``conformance/specs/mthds-test-corpus.md`` (the cross-repo spec, kept in the ``conformance``+repo), section "Tag vocabulary".No `native.*` code is excluded today — every one of them turned out to support a meaningfulfocused entry — so the exclusion mechanism's semantics are pinned here rather than left to bediff --git a/tests/unit/repo/test_docs_cite_nothing_private.py b/tests/unit/repo/test_docs_cite_nothing_private.pyindex 3512e55cf..c125945df 100644--- a/tests/unit/repo/test_docs_cite_nothing_private.py+++ b/tests/unit/repo/test_docs_cite_nothing_private.py@@ -1,10 +1,10 @@"""Guards the published documentation against citations its readers cannot follow.`docs/` is the MkDocs `docs_dir` published at docs.pipelex.com. A workspace ledger id, a `wip/` path or a-document at the root of the private workspace (its `docs/specs/`, its ledger, its conventions) means-something to a contributor with the workspace checked out and nothing to anyone reading the site, so the-page states the fact in plain words, links a public page that states it, or leaves the pointer out. Ids and-paths stay welcome in code comments, commit messages and pull request bodies.+document in the private workspace (an interface spec in its internal `conformance` repo, its ledger, its+conventions) means something to a contributor with the workspace checked out and nothing to anyone reading+the site, so the page states the fact in plain words, links a public page that states it, or leaves the+pointer out. Ids and paths stay welcome in code comments, commit messages and pull request bodies."""from __future__ import annotations@@ -36,8 +36,12 @@ URL_PATTERN = re.compile(r"\b[a-z][a-z0-9+.-]*://\S+", re.IGNORECASE)#: ends a longer name (`mthds-wip/`).PRIVATE_PATH_PATTERNS: dict[str, re.Pattern[str]] = {"wip/ path": re.compile(r"(?<![\w-])wip/"),- # This repository has no docs/specs/, so the path can only name the workspace's.+ # This repository has no docs/specs/, so the path can only name the workspace's, which now holds nothing+ # but a pointer to the conformance repo."workspace spec path": re.compile(r"(?<![\w-])docs/specs/"),+ # Nor has it a conformance/ directory, so the path can only name the internal conformance repo, whose+ # specs/ holds the interface specs that moved out of the workspace's docs/specs/.+ "conformance repo path": re.compile(r"(?<![\w-])conformance/"),}TEXT_SUFFIXES = frozenset({".md", ".html", ".css", ".txt", ".yml", ".yaml"})@@ -64,7 +68,7 @@ def private_references(*, line: str) -> list[str]:class TestDocsCiteNothingPrivate:def test_published_docs_cite_nothing_in_the_private_workspace(self) -> None:- """Every published page reads without the private workspace: no ledger id, no `wip/` path, no workspace-root document."""+ """Every published page reads without the private workspace: no ledger id, no `wip/` path, no workspace or `conformance` spec."""doc_files = published_files()assert doc_files, f"no documentation files found under {DOCS_DIR}"offending_lines: list[str] = []@@ -81,7 +85,22 @@ class TestDocsCiteNothingPrivate:def test_private_path_patterns_catch_relative_links_and_skip_urls(self) -> None:"""A relative link out of docs/ is the likeliest way a page cites the workspace; another site's URL is not a citation."""- for cited in ("[d](../../wip/foo.md)", "./wip/x", "`wip/x`", "[s](../../../docs/specs/corpus.md)", "`docs/specs/x.md`"):+ for cited in (+ "[d](../../wip/foo.md)",+ "./wip/x",+ "`wip/x`",+ "[s](../../../docs/specs/corpus.md)",+ "`docs/specs/x.md`",+ "[s](../../../conformance/specs/mthds-test-corpus.md)",+ "`conformance/specs/x.md`",+ ):assert private_references(line=cited), cited- for clean in ("mthds-wip/x", "https://opentelemetry.io/docs/specs/semconv/", "https://example.com/wip/y"):+ for clean in (+ "mthds-wip/x",+ "mthds-conformance/x",+ "## Conformance tiers",+ "https://opentelemetry.io/docs/specs/semconv/",+ "https://example.com/wip/y",+ "https://example.com/conformance/specs/z",+ ):assert not private_references(line=clean), clean