AW10 — Finalize release build, versioning, packaging, reproducibility, and CI gates

[joris97jansen]

Description

Finalize release engineering for the static HTML/CSS engine.

This issue should ensure that the release can be built, tested, reproduced, tagged, and verified consistently.

The goal is to make AW a real release closeout, not just a documentation checkpoint.

Requirements

• Define release version/tag naming policy.

• Define release branch/tag process.

• Define release build profile.

• Define supported build targets.

• Ensure release builds are reproducible where feasible.

• Ensure lockfiles/toolchain versions are pinned where appropriate.

• Add release CI gate.

• Include:

  • formatting;

  • linting;

  • unit tests;

  • integration tests;

  • conformance baseline;

  • compatibility corpus subset;

  • snapshot tests;

  • guardrail tests;

  • benchmark smoke tests where feasible.

• Ensure debug-only code is not required for release behavior.

• Ensure release artifacts include docs/reports where scoped.

• Add build provenance/release manifest.

• Add release checklist.

• Add rollback/retry policy for failed release candidates.

• Document local release verification commands.

Exit Criteria

• Release build process is documented.

• Version/tag policy exists.

• CI release gate exists.

• Release artifacts are reproducible where feasible.

• Release manifest exists.

• Local verification commands are documented.

• Release checklist exists.

• The issue is closeable when a release candidate can be produced.