You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Vocabulary: runtime names, conformance facts and CI target sets from the catalog #112
Generated constants for the runtime's names: contract/names.rs (FORMAT_*, FRAMING_*, HANDSHAKE_*).
Conformance: Fact::name() in conformance/src/profile.rs, the fact domains in specs/profile.cue, and the feature ids in features.json.
CI: the fuzz target matrix and the Observatory expect: list in fuzz.yml, and the bench target lists, generated from vocabulary sets. Today packed_canonical is written in Cargo.toml, twice in fuzz.yml, in the README and in seed_corpus.rs.
A CI check that the generated files are current, the way comline.h is checked.
Update (2026-11-09): the catalog is leaning towards a spec repository (ComlineProject/core#220). The conformance specs (specs/, features.json) and the vectors would move there from runtime/conformance. The Rust engine, the reference and vectors_are_current stay here, reading the spec at a pinned revision.
Done by runtime#114 (vendor the specification with its catalog: profile facts and features.json derived from it), runtime#116 (names held to the catalog: Fact::name returns catalog ids, facts_are_the_catalogs, tests/catalog.rs checks the contract/names.rs constants) and runtime#117 (one list of fuzz targets: the fuzz crate's [[bin]]s feed the fuzz.yml matrix and the report's expect via .github/scripts/fuzz-targets.py, held against the README table). Bench targets are one TARGETS list in .github/scripts/bench-report.py, and the vendored spec is checked in CI by vendor-spec.sh --check. One difference from the issue text: the wire-name constants stay literal and are held to the catalog by a test rather than generated. Removed the stale blocked label (core#220 is done: the specification repo exists).
Activity
Kinflou commentedon Nov 15, 2026
Done by runtime#114 (vendor the specification with its catalog: profile facts and features.json derived from it), runtime#116 (names held to the catalog: Fact::name returns catalog ids, facts_are_the_catalogs, tests/catalog.rs checks the contract/names.rs constants) and runtime#117 (one list of fuzz targets: the fuzz crate's [[bin]]s feed the fuzz.yml matrix and the report's expect via .github/scripts/fuzz-targets.py, held against the README table). Bench targets are one TARGETS list in .github/scripts/bench-report.py, and the vendored spec is checked in CI by vendor-spec.sh --check. One difference from the issue text: the wire-name constants stay literal and are held to the catalog by a test rather than generated. Removed the stale blocked label (core#220 is done: the specification repo exists).