Check actual resolved CI source coverage #8
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/lib-block!8
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/ci-resolved-source-contract"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The gateway can acquire sources for other nested-package policy checks without including them in the active Cargo metadata closure. Comparing all selected graph entries to the consumer descriptor therefore rejects legitimate preparation.
Require exact equality between the actual retained tree set and its checked original metadata resolutions, and require every actual revision to match the tracked graph. Keep original root and authored graph-byte checks. Missing, foreign, unlisted and mismatched actual trees still refuse.
Validation: positive nested-policy subset and refusal controls; all Markdown files passed. The same corrected comparison also passes genuine previously prepared Block and Time consumers. No source producer, native engine or Cargo gate changed; actual CI remains independent.
WIP: Check actual resolved CI source coverageto Check actual resolved CI source coverageThe remaining change is prepared at
8770a0a382e06f8a526a34a23f1a39f886ed844fon the current #5 branch: changes. It explicitly selects the main/feature provider policy. Actual source coverage stays in Integration’s shared verifier; no copied checker or guide is introduced. The prepared history preserves the journal companion profile, device changes and native gates. It needs fresh review; the original branch remains intact.A signed preparation is available at 55a2440f. It preserves the original runtime, tests and documentation, keeps the destination source-policy guards, and retains separate feature boundaries. All local component checks and the exact preview’s CI run 46679 passed, including native strict Clippy/build, optimized tests, documentation and Markdown.
This checkpoint keeps the explicit main-to-auto provider-policy change separate. Its rewritten history needs renewed approval of this exact head; predecessor image acceptance remains open.
View command line instructions
Manual merge helper
Use this merge commit message when completing the merge manually.
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.