[soulteary]

Real client coverage currently runs APT and CentOS Docker jobs on every PR/main push, while other common Linux package managers lack repository-cache end-to-end tests. This change moves the expensive suite to manual execution and makes all 18 clients a prerequisite for version publication.

• Test Debian/Ubuntu APT, CentOS/Fedora/Rocky/Alma DNF and DNF5, Alpine APK2/APK3, Arch pacman, and openSUSE zypper in their real Docker images using the current proxy binary and disposable signed native repositories.
• Require metadata refresh, installation, byte-verified payloads, integrity rejection, and reinstall after clearing the client's cache with unchanged origin package GET counts. APK separately tests embedded package signatures and identities protected by the original signed index; its mutation helper preserves valid archive framing and transfer size.
• Add a manual family selector and reusable workflow. The Release workflow calls the full matrix before tag/manual release builds. Branch dispatches validate without publishing; ordinary PR/main CI keeps fast harness regressions and existing Go/integration checks.
• Preserve failure logs and per-client machine-readable evidence. Pin jobs to the planned source commit, reject missing/stale/invalid reports, retain successful artifacts across failed-job reruns, and require the current matrix job itself to succeed.
• Document local commands, trigger behavior, routing requirements, and coverage limits. These local signed fixtures verify Linux client repository caching; they do not certify every public mirror or operating system.

Validation on final commit 6a8f683ba7cb5d470329d84676ac5351da5f182f:

• Full native AMD64 run: all 18 Docker clients, evidence verification, and release preflight passed. All clients retained origin package GET counts of 1 → 1 after clearing client caches. Registry logins and GoReleaser were skipped on the feature branch.
• Ordinary PR CI and security checks passed, including race/coverage, cross-compilation, container build, and existing integration tests.
• 52 planner/evidence, entrypoint, and APK archive regressions passed without Docker. Changed workflows passed actionlint; shell/Python syntax and diff checks passed.
• Requested @codex review after every commit and waited for each result. The final-head review reported no major issues.

Manual usage and verified scope: client compatibility guide.

[soulteary]

@codex review

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-13T10:37:33.340618Z	6a8f683	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Already looking forward to the next diff.

Reviewed commit: 82096352e3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[soulteary]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 👍

Reviewed commit: dbb5df5cb8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[soulteary]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Delightful!

Reviewed commit: 6a8f683ba7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".