Skip to content

Connect v3 CI, fuzz campaigns and guarded release publication - #381

Draft
etr wants to merge 4 commits into
v3from
task/FEATURE-ci-v3-integration
Draft

etr wants to merge 4 commits into
v3from
task/FEATURE-ci-v3-integration

Conversation

@etr

@etr etr commented Oct 16, 2026

Copy link
Copy Markdown
Owner

Connect v3 native, package and fuzz runners to CI, and require release publication to pass the existing complete readiness validator for one selected archive. Adds all eleven bounded sanitizer fuzz targets, persistent trusted corpora and nightly campaigns; the schedule activates when the workflow reaches master/default branch. Repairs observed compiler, documentation, output-directory, Git and port-443 prerequisites.

Release jobs prepare one archive, produce real platform evidence, import immutable provenance bundles, run all eighteen Linux gates and invoke actual tag-readiness validation before a separate publisher can use write permission. PR/manual validation paths disable publication; no tags or releases are created for verification.

Local validation: native TLS-off/on 239/270 checks with two documented nonlocal skips each; all eleven real sanitizer fuzz probes; GCC replay; real Doxygen/Graphviz; actionlint; 100 focused CI/release contracts, including execution from the relocated final archive. Clean committed selected-archive preparation passed. Focused installed public TLS passed all four linkage/execution cases with 82 checks each in an isolated network.

The earlier complete Linux installed-matrix attempt remains unsuccessful at the genuine unprivileged TCP443 prerequisite; its failure is retained separately from the passing focused proof. Actual GitHub platform execution and fresh complete release receipts are pending. Final Groundwork review follows this CI exercise.

etr added 4 commits October 15, 2026 20:58
…ease acceptance

Run TLS-off/on native suites and independent bounded fuzz shards, repair installed platform prerequisites, and route legacy CI by source capability. Bind one selected archive to fresh platform bundles and the existing complete readiness validator before an isolated inline publisher can release an existing tag.

Local verification: native 239/270 tests (two documented nonlocal skips each), eleven sanitizer fuzz targets, GCC QUIC replay, real Doxygen/Graphviz, 99 focused contracts, actionlint and workflow policy checks pass. A failed full Linux installed attempt remains unsuccessful at unprivileged TCP443; focused genuine isolated public TLS passes all four 82-check cells. Fresh full 18-gate and three nonlocal receipts plus actual GitHub PR verification remain CI/root-owned.
…mands

Exercise the actual FreeBSD staging step with a selected descriptor, preserving newlines so the VM receives the archive inputs. Behavioral RED/GREEN and actionlint pass; focused contract total is 100.
A real relocated archive exposed missing native and ChangeLog workflow inputs for the distributed CI contract script. Include all reviewed workflow dependencies; fresh distribution and relocated workflow/package contracts now pass.
The real PR artifact and run APIs report the branch head while GITHUB_SHA identifies the test merge checkout. Supply the trusted event head explicitly to download origin checks, retaining exact selected merge source, archive, run, attempt, repository and digest validation.

Reproduced the actual captured artifact failure twice before repair. Real ZIP replay now validates the branch-head origin and unchanged merge descriptor/archive; 15 release contracts and 10 workflow contracts pass, including negative source/origin/run/attempt/digest controls. Actionlint and Python compilation pass. Native/fuzz/docs/public443 evidence is reused unchanged; fresh actual CI remains root-owned.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant