Martin Vogel c1425d2e27 ci: write the shard manifest before any suite runs; warn on absent upload ...

The manifest content (leg, slice, list hash) is fully determined at
slicing time, so write it up front: a red run's manifest is exactly as
load-bearing for the cross-shard union proof as a green one's.

With that, a missing manifest at upload time can only mean the job
died before the harness started (contract step / build failure) — that
failure is already the job's red, so the upload warns instead of
stacking a second error on top (the recurring 'No files were found
with the provided path: build/c/test-logs/shard-manifest.txt'
annotation). The shard-completeness job still gates the union.

Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>

2026-07-27 02:00:59 +02:00

..

ISSUE_TEMPLATE

feat(diag): persistent memory trajectory + query-leak CI soak for #581

2026-06-28 23:28:01 +02:00

workflows

ci: write the shard manifest before any suite runs; warn on absent upload

2026-07-27 02:00:59 +02:00

CODEOWNERS

docs: make maintainer policy project-oriented

2026-06-29 00:00:10 +02:00

dependabot.yml

Pin Actions to SHA + enforce via security audit + Dependabot

2026-03-21 16:57:17 +01:00

issue-labeler.yml

fix(ci): issue labeler no-oped on every issue — (?i) is invalid in JS RegExp

2026-07-10 00:03:43 +02:00

label-actions.yml

ci: add issue-triage bots (stale, label-actions, area-labeler)

2026-06-24 01:18:29 +02:00

pull_request_template.md

Adopt the Developer Certificate of Origin for all commits

2026-06-12 14:31:55 +02:00