Carry the PDrive release skills in-repo for the laboratory era #7
Loading…
Reference in a new issue
No description provided.
Delete branch "oss-oo/skills-z-era-rt20261008"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Carries the two general PDrive release skills in-repo —
.zcode/skills/pdrive-releaseand.zcode/skills/pdrive-release-matrix(withreferences/) — and modernizes them for the laboratory publication era.Why
These skills previously lived only as station-local imports from an earlier agent era and had drifted: GitHub-release wording in sections that have published through the laboratory since v0.9.1/v0.9.2, removed-tool log conventions, and dependency-publication steps predating the laboratory-hosted pinned rclone build. The repository is the durable home for project workflow knowledge; every checkout now carries the skills through the normal review path.
Notable changes
--latestswitch).GET /repos/{o}/{r}/actions/tasksfiltered byhead_sha(statussuccess/failureis the completion signal;donestays false; the classic commit-status endpoint never mirrors Actions runs).-T+ explicit Content-Type — a bare-Tanswers 405 and--data-binarystores a 0-byte asset — plus size verify and byte-exact download round-trip).gh release upload); wording sanitized for a public repo (no private deployment or maintainer-host details; the station-local live-sync runbook deliberately stays out of the repository).Validation
make checkgreen;git diff --checkclean.