Releases and contributions

A release needs an executable entry path: purpose, requirements, a program, expected output and an issue channel. Packages identify their edition, target, hashes and included runtime.

Development caches, local reports, temporary files and build outputs do not belong in the source distribution. Public export uses an explicit file selection and a hash manifest. Native kits are distributed as Release assets.

Bootstrap releases remain prereleases with explicit limits. Test badges require executed checks. Download links must resolve, and performance claims require reproducible measurements.

A technical contribution explains the problem, affected contract, before-and-after behavior and validation. Parser, AST, semantics and IR changes must preserve continuity. ABI and memory work needs boundary cases and rejection tests. Documentation changes require working links and accurate examples.

Technical references

• AGENTS.md and docs/syntax.md.
• crates/ncc-parser/src/lib.rs and crates/ncc-stage0-bridge/build.rs.
• docs/NCC_MODULES_V81_DOSSIER.md.
• docs/NCC_MODULES_V81_ABI_LAYOUT.md and docs/NCC_MODULES_V81_REPRO.md.
• docs/NCC_MODULES_V81_ATTEMPTS.md.
• bootstrap/frontend-v81-build.json and bootstrap/frontend-v81-contracts.json.

These references define this edition's scope. Subsequent work must update contracts, tests and public documentation together.