WIP: Supply the production artifact tool roles #57

Draft
erikinkinen wants to merge 9 commits from feature/ci-artifact-tool-roles into feature/owned-ci-source-graph
Owner

Pass Python, nm, strings and tee explicitly to the production boundary checker and install binutils in CI. The checker continues to reject absent tool roles before artifact work.

  • Exercise the production boundary through the selected original-source Cargo route.
  • Complete the remaining CI workflow gates.
Pass Python, nm, strings and tee explicitly to the production boundary checker and install binutils in CI. The checker continues to reject absent tool roles before artifact work. - [x] Exercise the production boundary through the selected original-source Cargo route. - [ ] Complete the remaining CI workflow gates.
erikinkinen added this to the Alpha 1 milestone 2026-11-06 13:42:18 +01:00
ci: Supply explicit production artifact tools
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 2s
CI / test (push) Failing after 3m55s
8cba815767
Pass the required installed tool roles to the production boundary checker and install their package in CI. Preserve the checker refusal when a role is absent rather than relying on ambient tool discovery.
ci: Use shared development dependency profiles
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Failing after 9s
CI / test (push) Failing after 33s
de1a5f83a4
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.
Refresh source and linked artifact measurements from the actual CI build after the retained physical serial-control and terminal-break changes. Preserve every compiler, authority, message, syscall, dependency, source inventory and phase contract field.
Keep the source selection explanation readable within the Markdown line limit while retaining its complete public reference.
Use the same complete reference definition in the architecture introduction so all three repository overviews obey the Markdown line limit.
ci: Select the provider policy explicitly
All checks were successful
CI / markdown (push) Successful in 3s
CI / test (push) Successful in 4m39s
c44ed789bc
Adopt the shared main/release and feature source contract. Actual CI reference metadata selects main providers for main and release builds, while feature builds retain their explicitly declared companions.
feat: Merge record current production bootstrap measurements
All checks were successful
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 4s
CI / test (push) Successful in 4m47s
184c3c0ff8
Integrate the reviewed prepared history into feature/ci-artifact-tool-roles. The feature tree and
original source branch remain unchanged. Upstream work retains its own
completion requirements.

#58
feat: Select boot objects by validated catalog index
All checks were successful
CI / markdown (push) Successful in 2s
CI / test (push) Successful in 3m35s
ee84dacd0b
Carry the original signed-store ordinal through pre-Procd and delegated staged mapping, checking returned identities before relocation and sealing. Preserve final payload framing, cleanup and authority controls with the counted mapping provider cohort. Retain completed production measurements and their signed prerequisite boundary without duplicating shared CI history.
feat: Merge feat: Select boot objects by validated catalog index
All checks were successful
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 3s
CI / test (push) Successful in 4m18s
9228ce9716
Integrate the reviewed prepared history into feature/ci-artifact-tool-roles. The feature tree and
original source branch remain unchanged. Upstream work retains its own
completion requirements.

#59
All checks were successful
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 3s
CI / test (push) Successful in 4m18s
This pull request has changes conflicting with the target branch.
  • .github/workflows/ci.yml
  • ARCHITECTURE.md
  • README.md
  • ROADMAP.md
  • audit/bootstrap-baseline.json
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/ci-artifact-tool-roles:feature/ci-artifact-tool-roles'
git switch 'feature/ci-artifact-tool-roles'

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/owned-ci-source-graph'
git merge --no-ff 'feature/ci-artifact-tool-roles'
git switch 'feature/ci-artifact-tool-roles'
git rebase 'feature/owned-ci-source-graph'
git switch 'feature/owned-ci-source-graph'
git merge --ff-only 'feature/ci-artifact-tool-roles'
git switch 'feature/ci-artifact-tool-roles'
git rebase 'feature/owned-ci-source-graph'
git switch 'feature/owned-ci-source-graph'
git merge --no-ff 'feature/ci-artifact-tool-roles'
git switch 'feature/owned-ci-source-graph'
git merge --squash 'feature/ci-artifact-tool-roles'
git switch 'feature/owned-ci-source-graph'
git merge --ff-only 'feature/ci-artifact-tool-roles'
git switch 'feature/owned-ci-source-graph'
git merge 'feature/ci-artifact-tool-roles'
git push origin 'feature/owned-ci-source-graph'
Sign in to join this conversation.
No description provided.