WIP: Export completed Cargo graphs as portable inputs #229

Draft
erikinkinen wants to merge 4 commits from feature/portable-cargo-graphs into feature/generated-cargo-lock-inputs
Owner

Freeze the actual completing Cargo metadata view with its original source and lock owners. Preserve opaque package references and feature/resolve edges while projecting only known path coordinates into the same portable build inventory.

Depends on #228. Offline graph admission uses the retained source/lock contract without replaying Cargo, copying host caches or treating a report as execution authority.

  • Register actual final metadata with the completing producer.
  • Preserve package, target, feature and resolve graph semantics.
  • Exercise genuine Cargo export/admission and graph refusal controls.
  • Connect original object transport and actual guest Cargo consumption.
Freeze the actual completing Cargo metadata view with its original source and lock owners. Preserve opaque package references and feature/resolve edges while projecting only known path coordinates into the same portable build inventory. Depends on [#228](https://git.erikinkinen.fi/erix/integration/pulls/228). Offline graph admission uses the retained source/lock contract without replaying Cargo, copying host caches or treating a report as execution authority. - [x] Register actual final metadata with the completing producer. - [x] Preserve package, target, feature and resolve graph semantics. - [x] Exercise genuine Cargo export/admission and graph refusal controls. - [ ] Connect original object transport and actual guest Cargo consumption.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 22:46:18 +01:00
feat: Export completed Cargo graphs as portable inputs
Some checks failed
CI / rust (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / rust (push) Failing after 2m7s
CI / markdown (push) Successful in 20s
CI / integration (push) Failing after 27m6s
6eae428d1a
Bind the actual completing metadata view to its original source and lock owners before projecting known coordinates into the build inventory. Preserve opaque package references, feature and resolve edges, and validate offline graph admission without replaying Cargo or adopting host caches.
ci: Use shared development dependency profiles
Some checks failed
CI / rust (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / rust (push) Has been cancelled
CI / integration (push) Has been cancelled
CI / markdown (push) Has been cancelled
e67467d0f8
Keep authored manifests on main and select coordinated providers through Integration. Resolve branches once per run, retain the frozen snapshot and helper identity as artifacts, and use shared source checks instead of copied tests and guides.
ci: Extract the complete host fixture sequence
Some checks failed
CI / rust (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / rust (push) Has been cancelled
CI / integration (push) Has been cancelled
CI / markdown (push) Has been cancelled
29f5584f91
Keep the existing fixture commands together in a component-owned script sourced by their original CI step. Retain the same shell options, environment, working directory and complete acceptance gates.
ci: Declare policy helper and output boundaries
Some checks failed
CI / rust (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 21s
CI / rust (push) Successful in 6m31s
CI / integration (push) Failing after 35m20s
42c1627ac1
Select a disjoint operation parent for policy evidence and explicitly identify the helper checkout excluded from original component input. Keep the complete dependency policy and existing acceptance commands.
Some checks failed
CI / rust (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 21s
CI / rust (push) Successful in 6m31s
CI / integration (push) Failing after 35m20s
This pull request has changes conflicting with the target branch.
  • scripts/check-integration-host-fixtures.sh
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.
git fetch -u origin 'feature/portable-cargo-graphs:feature/portable-cargo-graphs'
git switch 'feature/portable-cargo-graphs'

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.

git switch 'feature/generated-cargo-lock-inputs'
git merge --no-ff 'feature/portable-cargo-graphs'
git switch 'feature/portable-cargo-graphs'
git rebase 'feature/generated-cargo-lock-inputs'
git switch 'feature/generated-cargo-lock-inputs'
git merge --ff-only 'feature/portable-cargo-graphs'
git switch 'feature/portable-cargo-graphs'
git rebase 'feature/generated-cargo-lock-inputs'
git switch 'feature/generated-cargo-lock-inputs'
git merge --no-ff 'feature/portable-cargo-graphs'
git switch 'feature/generated-cargo-lock-inputs'
git merge --squash 'feature/portable-cargo-graphs'
git switch 'feature/generated-cargo-lock-inputs'
git merge --ff-only 'feature/portable-cargo-graphs'
git switch 'feature/generated-cargo-lock-inputs'
git merge 'feature/portable-cargo-graphs'
git push origin 'feature/generated-cargo-lock-inputs'
Sign in to join this conversation.
No description provided.