Conformance evidence policy - FAQ and troubleshooting

import SpecArticleChrome from '@beskid/beskid-ui/platform-spec/SpecArticleChrome.astro';

<SpecArticleChrome />

This article documents faq and troubleshooting for conformance evidence policy in the reference compiler.

What this covers

For newcomers, this page explains where the contract shows up in day-to-day compiler work and which code paths are most useful first reads.

Anchored code paths

• compiler/crates/beskid_tests/src/analysis/diagnostics.rs provides semantic conformance evidence.
• compiler/crates/beskid_tests/src/doc_tests.rs validates docs-facing conformance examples.
• compiler/crates/beskid_e2e_tests/src/tests/runtime_cases.rs provides executable behavior evidence.

Practical notes

• Prefer tracing from CLI/test entry points into analysis/codegen crates before changing internals.
• Treat diagnostics and tests as part of the contract, not optional implementation details.
• If behavior changes, update this article and add/adjust tests in compiler/crates/beskid_tests or compiler/crates/beskid_e2e_tests.