WIP: Export actual generated Cargo locks as offline inputs #228

Draft
erikinkinen wants to merge 4 commits from feature/generated-cargo-lock-inputs into feature/inventory-bound-source-delivery
Owner

Borrow actual registered Cargo completions to freeze exact workspace locks and export their original byte and native evidence beside tracked sources. Admit generated lock roots with explicit work budgets, exact namespace checks and source-ID closure.

Depends on #227. Original tracked locks and source trees stay immutable; serialized reports cannot recreate a completing producer.

  • Freeze locks from actual registered workspace completions.
  • Deliver and admit separate generated inputs with original evidence.
  • Cover real Cargo export/admission and existing source boundaries.
  • Connect portable dependency graphs and actual guest consumption.
Borrow actual registered Cargo completions to freeze exact workspace locks and export their original byte and native evidence beside tracked sources. Admit generated lock roots with explicit work budgets, exact namespace checks and source-ID closure. Depends on [#227](https://git.erikinkinen.fi/erix/integration/pulls/227). Original tracked locks and source trees stay immutable; serialized reports cannot recreate a completing producer. - [x] Freeze locks from actual registered workspace completions. - [x] Deliver and admit separate generated inputs with original evidence. - [x] Cover real Cargo export/admission and existing source boundaries. - [ ] Connect portable dependency graphs and actual guest consumption.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 22:44:16 +01:00
feat: Export actual generated Cargo locks as offline 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 / markdown (push) Successful in 18s
CI / rust (push) Failing after 2m52s
CI / integration (push) Failing after 44m55s
c3867302da
Freeze workspace locks from the original registered Cargo completion and export their exact bytes beside immutable tracked sources. Retain actual tool evidence, explicit work budgets and complete offline lock/source-ID checks without adopting host caches or recreating completion from reports.
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
fb7ab6dd9e
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
7da5bfd662
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 11s
CI / rust (push) Successful in 4m10s
CI / integration (push) Failing after 35m36s
acf10b3e96
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 11s
CI / rust (push) Successful in 4m10s
CI / integration (push) Failing after 35m36s
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/generated-cargo-lock-inputs:feature/generated-cargo-lock-inputs'
git switch 'feature/generated-cargo-lock-inputs'

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/inventory-bound-source-delivery'
git merge --no-ff 'feature/generated-cargo-lock-inputs'
git switch 'feature/generated-cargo-lock-inputs'
git rebase 'feature/inventory-bound-source-delivery'
git switch 'feature/inventory-bound-source-delivery'
git merge --ff-only 'feature/generated-cargo-lock-inputs'
git switch 'feature/generated-cargo-lock-inputs'
git rebase 'feature/inventory-bound-source-delivery'
git switch 'feature/inventory-bound-source-delivery'
git merge --no-ff 'feature/generated-cargo-lock-inputs'
git switch 'feature/inventory-bound-source-delivery'
git merge --squash 'feature/generated-cargo-lock-inputs'
git switch 'feature/inventory-bound-source-delivery'
git merge --ff-only 'feature/generated-cargo-lock-inputs'
git switch 'feature/inventory-bound-source-delivery'
git merge 'feature/generated-cargo-lock-inputs'
git push origin 'feature/inventory-bound-source-delivery'
Sign in to join this conversation.
No description provided.