WIP: Transport original Git objects for fresh offline preparation #230

Draft
erikinkinen wants to merge 4 commits from feature/original-object-transport into feature/portable-cargo-graphs
Owner

Preserve complete role-bound original object bytes and shallow boundaries beside source and Cargo inputs. Prepare fresh contexts through actual retained admissions, then compare genuine new source/Cargo completion without recovering custody from serialized reports.

Depends on #229. Object byte admission, actual Git validity and fresh Cargo correspondence stay distinct; partial output and uncertain cleanup remain with their original owners.

  • Transport exact object selections for every original source role.
  • Prepare fresh held contexts with original input and deadline custody.
  • Compare actual new source, lock and graph completion.
  • Connect the explicit offline preparation command and native guest build.
Preserve complete role-bound original object bytes and shallow boundaries beside source and Cargo inputs. Prepare fresh contexts through actual retained admissions, then compare genuine new source/Cargo completion without recovering custody from serialized reports. Depends on [#229](https://git.erikinkinen.fi/erix/integration/pulls/229). Object byte admission, actual Git validity and fresh Cargo correspondence stay distinct; partial output and uncertain cleanup remain with their original owners. - [x] Transport exact object selections for every original source role. - [x] Prepare fresh held contexts with original input and deadline custody. - [x] Compare actual new source, lock and graph completion. - [ ] Connect the explicit offline preparation command and native guest build.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 23:05:29 +01:00
feat: Transport original Git objects for fresh offline preparation
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 15s
CI / rust (push) Failing after 1m53s
CI / integration (push) Failing after 30m49s
55824f6d33
Keep role-bound original object bytes and shallow boundaries with the source and Cargo inventory. Prepare fresh held contexts and compare actual new source and Cargo completion under the original native limit, retaining partial outputs and uncertain cleanup instead of recreating custody 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
4f98e462da
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
e7cfaefca6
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 33s
CI / rust (push) Successful in 6m34s
CI / integration (push) Failing after 35m12s
688094e4a2
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 33s
CI / rust (push) Successful in 6m34s
CI / integration (push) Failing after 35m12s
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/original-object-transport:feature/original-object-transport'
git switch 'feature/original-object-transport'

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/portable-cargo-graphs'
git merge --no-ff 'feature/original-object-transport'
git switch 'feature/original-object-transport'
git rebase 'feature/portable-cargo-graphs'
git switch 'feature/portable-cargo-graphs'
git merge --ff-only 'feature/original-object-transport'
git switch 'feature/original-object-transport'
git rebase 'feature/portable-cargo-graphs'
git switch 'feature/portable-cargo-graphs'
git merge --no-ff 'feature/original-object-transport'
git switch 'feature/portable-cargo-graphs'
git merge --squash 'feature/original-object-transport'
git switch 'feature/portable-cargo-graphs'
git merge --ff-only 'feature/original-object-transport'
git switch 'feature/portable-cargo-graphs'
git merge 'feature/original-object-transport'
git push origin 'feature/portable-cargo-graphs'
Sign in to join this conversation.
No description provided.