Repository navigation
Unify CI checks and verified development downloads - #4
Draft
lucidprogrammer wants to merge 2 commits into
Draft
lucidprogrammer wants to merge 2 commits into
lucidprogrammer wants to merge 2 commits into
Conversation
lucidprogrammer-svc
force-pushed
the
ci-shared-profile
branch
from
October 15, 2026 03:55
43ee976 to
7e66b39
Compare
lucidprogrammer
changed the title
lucidprogrammer-svc
force-pushed
the
ci-shared-profile
branch
3 times, most recently
from
October 15, 2026 06:59
4d6ef63 to
ca719ce
Compare
lucidprogrammer-svc
force-pushed
the
ci-shared-profile
branch
from
October 15, 2026 14:31
e2e7192 to
e0adea3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contributors now have separate paths for required PR checks, extended integration, manual performance measurement, stable publication, and verified development downloads. Required correctness coverage is preserved while test binaries run in isolated shards, with one stable PR checks aggregate.
Trusted pushes to dev can build and smoke the exact packaged binaries, then publish checksum-verified development assets behind permanent download links. Publication uses write-once run-specific fallback files and replaces the latest receipt last. Performance measurement remains manual; the dormant workflow cannot report a successful measurement without running one. Contributor and agent guides explain the shared layout and repository-specific commands.
Validation: 73 offline delivery controls and 9 required-check controls passed at the final commit. Earlier unchanged-profile checks covered inventory, shell syntax and ShellCheck. A fresh independent review cleared the guard-only delta and verified 39 adversarial cases across ContextDB and Vigil; this does not establish hosted or native qualification. The final change is one commit with a clean worktree. Hosted correctness, native package smoke and GitHub publication behavior still need their own runs; actionlint 1.7.12 rejects the documented queue key, whose exact shape is checked by the offline controls.
No database runtime, dependency manifest, dependency pin, dev/main history or branch-protection setting is changed.
Hosted validation: run 38678752105 is not passing. At the recorded checkpoint, 8 jobs had passed, 7 failed, 2 were cancelled and 9 remained running/queued. Strict build, integration, installed smoke and Linux cross-build stop on the unused expansion_cap field. Default engine/vector tests expose test-seam configuration errors. The server test-seams purge scenario reaches a pre-purge graph-count assertion (1,000 observed, 1,001 expected); its cause is not established. These runtime source and test files are unchanged by this PR. Resolve the failures on the integration source and requalify before merging.