Skip to content

Completion epic: final certification and production release checklist #155

Description

@dayflaree

Goal

Track the final work required to move Source Weaver from public preview with explicit limitations to a fully completed, externally certified project state.

This is the parent checklist for the completion milestone. Close this only after all dependent certification, prerequisite, and final-release issues are closed with evidence comments.

Existing certification issues

New prerequisite and release-gate issues

Dependency graph

#156 + #159 + #160 -> #141
#157 + #159 + #160 -> #142
#158 + #160       -> #143
#156 + #157 + #159 + #160 -> #145
#156 + #159 + #160 -> #146
#141 + #142 + #143 + #145 + #146 + #160 + #162 + #163 -> #161
#141 + #142 + #143 + #145 + #146 + #156 + #157 + #158 + #159 + #160 + #161 + #162 + #163 -> #155

Completion definition

The project is complete when:

  • every currently blocked external-tool claim has real evidence;
  • production signing has been configured and verified;
  • runtime map-load evidence shows a real successful map load;
  • Hammer/Hammer++ and HLMV/HLMV++ evidence uses real tools;
  • documentation, release notes, compatibility matrices, and claim guards match the verified scope;
  • a final completion release is published with signed artifacts, provenance, SBOM, and final evidence links;
  • no proprietary binaries, SDK tools, game content, private assets, signing credentials, private keys, or private paths are committed.

Evidence requirements

Every closing evidence comment must include:

  • commit hash;
  • exact commands;
  • local validation results;
  • CI URL/status/SHA/jobs;
  • external tool versions and paths with private paths sanitized;
  • artifact paths and SHA-256 hashes;
  • validated claims;
  • unvalidated claims;
  • redistribution/legal boundary.

System investigation snapshot

On 2026-08-08 the current Ubuntu system had Half-Life 2, Source SDK Base 2013 SP/MP, and Proton installed, but did not expose Hammer/Hammer++, HLMV/HLMV++, VBSP/VVIS/VRAD, Wine, SignTool, osslsigncode, or production signing secrets on PATH. This milestone therefore needs environment and credential setup before the final certification tickets can close.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:releaseVersioning, changelog, GitHub releasesarea:testingFixtures, real-map tests, E2E validationhelp wantedExtra attention is neededpriority:p1High priority after the MVP foundationstatus:blockedBlocked by external environment, credential, legal-tool, or release dependencytype:qualityReliability, correctness, validation, maintainability

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions