WIP: Keep Cargo CI output outside original sources #240

Draft
erikinkinen wants to merge 5 commits from feature/explicit-ci-output-custody into feature/retained-cargo-ci-consumers
Owner

Select disjoint operation and metadata storage, retain captured untracked-entry identities, and load the selected Cargo operation in each executing caller. Canonical path checks precede effects; explicit metadata replacement keeps prior bytes.

Depends on #237.

  • Preserve tracked inputs and unrelated output bodies.
  • Connect selected outputs to shell and Python consumers.
  • Exercise the complete public source graph and native build.
Select disjoint operation and metadata storage, retain captured untracked-entry identities, and load the selected Cargo operation in each executing caller. Canonical path checks precede effects; explicit metadata replacement keeps prior bytes. Depends on [#237](https://git.erikinkinen.fi/erix/integration/pulls/237). - [x] Preserve tracked inputs and unrelated output bodies. - [x] Connect selected outputs to shell and Python consumers. - [ ] Exercise the complete public source graph and native build.
erikinkinen added this to the Alpha 1 milestone 2026-10-31 02:20:35 +01:00
Select disjoint operation and metadata storage without treating tracked source
or unrelated output names as owned slots. Keep captured exclusion identities
and load the selected retained Cargo operation in each executing caller.
fix: match explicit output anchors to the nofollow opener
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 4s
CI / rust (push) Failing after 26s
CI / integration (push) Failing after 1m17s
a2603221f6
Reject double-leading-slash aliases before creating operation or metadata
storage. Lexical source-containment checks must name the same root that the
original directory descriptor opener actually traverses.
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
f4ec33f19b
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
091e98ab6e
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 20s
CI / rust (push) Successful in 5m28s
CI / integration (push) Failing after 5m1s
41a5c6beec
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 20s
CI / rust (push) Successful in 5m28s
CI / integration (push) Failing after 5m1s
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/explicit-ci-output-custody:feature/explicit-ci-output-custody'
git switch 'feature/explicit-ci-output-custody'

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/retained-cargo-ci-consumers'
git merge --no-ff 'feature/explicit-ci-output-custody'
git switch 'feature/explicit-ci-output-custody'
git rebase 'feature/retained-cargo-ci-consumers'
git switch 'feature/retained-cargo-ci-consumers'
git merge --ff-only 'feature/explicit-ci-output-custody'
git switch 'feature/explicit-ci-output-custody'
git rebase 'feature/retained-cargo-ci-consumers'
git switch 'feature/retained-cargo-ci-consumers'
git merge --no-ff 'feature/explicit-ci-output-custody'
git switch 'feature/retained-cargo-ci-consumers'
git merge --squash 'feature/explicit-ci-output-custody'
git switch 'feature/retained-cargo-ci-consumers'
git merge --ff-only 'feature/explicit-ci-output-custody'
git switch 'feature/retained-cargo-ci-consumers'
git merge 'feature/explicit-ci-output-custody'
git push origin 'feature/retained-cargo-ci-consumers'
Sign in to join this conversation.
No description provided.