@@ -216,3 +216,37 @@ stopped during cleanup and recorded ABORTED; no suites ran. Six version
216216surfaces are aligned to v0.11.0 for the next shared-job full gate. Pinned
217217package versions/checksums and wrapper repository endpoints remain unchanged.
218218Push and PR thread resolution remain pending a passing shared-job result.
219+
220+ ### Linux publication readiness audit (2026-10-01)
221+
222+ Shared Jenkins #34 passed the full Linux gate at ` 37dd63ba ` and archived
223+ Linux amd64 bytes, checksums, version, and source revision. #35 passed focused
224+ ` daemon_runtime cli ` checks at ` 7e9005f8 ` ; this does not qualify that newer
225+ revision through the full gate. PR #12 is merged; PR #13 carries subsequent
226+ release-tooling fixes. Jenkins evidence publication formerly pushed directly
227+ to main. The release-tooling correction archives locally without GitHub writes;
228+ only after a passing gate may the orchestrator push release-tooling and post
229+ an exact-SHA status. A regression contract rejects remote writes in the script.
230+
231+ Live GitHub audit: Actions are enabled and all actions are allowed. The active
232+ main ruleset prevents deletion and non-fast-forward updates; it has no required
233+ status checks. This does not establish that a release workflow will pass.
234+ The repository secret names contain only CLAUDE_CODE_OAUTH_TOKEN. The maintainer
235+ confirmed the remaining credentials are not yet available.
236+
237+ Publication blockers in the existing all-platform ` release.yml ` :
238+
239+ - ` VIRUS_TOTAL_SCANNER_API_KEY ` is required for candidate scanning and verification.
240+ - ` NPM_TOKEN ` and ` PYPI_TOKEN ` are required for registry publication; public
241+ un-drafting depends on successful registry publication.
242+ - External Windows qualification is held by default. Setting the hold to false
243+ does not create a Linux-only release: all-platform build/smoke gates and registry
244+ publication still run. Keep the qualification hold until the applicable evidence
245+ is complete; do not bypass it to compensate for missing credentials.
246+ - Package wrappers still download upstream releases. Fork endpoints and real
247+ artifact checksums must be aligned before advertising those installation routes.
248+ - No public or draft fork GitHub releases exist at this audit boundary.
249+
250+ Obtain the service credentials through their providers and supply a local
251+ credential-file or secret-manager reference for secure GitHub secret setup.
252+ Do not commit token values or remove release checks to bypass missing secrets.
0 commit comments