Release 0.16.0: complete reads, safe retries and fact freshness

[renezander030]

GitHub and Notion native search can silently stop at the first page, while source failures and repeated writes can leave agents with incomplete reads or duplicate changes. This release completes scoped reads, bounds HTTP calls, and binds retries and fact approval to the work being performed.

Changes

• Paginate GitHub and Notion native search, preserve configured source scope, and report server caps or incomplete cursors.
• Apply a 30-second HTTP deadline through requests, retry waits and body reads; honor caller cancellation.
• Retain healthy GitHub/Notion corpus records when another project fails and propagate source warnings without caching partial data.
• Add read-only kg stale and reviewed kg confirm to surface old facts and record fresh evidence.
• Retry mutations only after explicit rate-limit rejection; retain transient retries for reads and opt-in read-only POSTs.
• Verify fact approval digests, check conflicts under the fact-store lock, and deduplicate ratification by proposal.
• Bind create keys to the effective payload and source, with exclusive claims for direct and reviewed creates.
• Bind batch journal entries to their operations and source; refuse changed or uncertain resumes and leave dry-run journals untouched.
• Preserve validated source-valid and learned timestamps separately from ratification, including fact exports.

All 13 public npm workspace versions and the existing MCP manifest are aligned at 0.16.0. The MCP tool surface is unchanged. The release guide documents publication from the reviewed merged revision. The fact-store implementation is in packages/core/kg-store.js; kg.js preserves its existing entrypoint. This makes the full implementation reviewable as text despite a binary byte in the older file.

Compatibility

ATS_HTTP_TIMEOUT_MS sets the positive HTTP deadline (default 30000 ms). Old idempotency keys and batch journal entries without payload/source bindings cannot safely resume; inspect the previous outcome and use a fresh binding. In-flight and uncertain claims require backend inspection. These claims do not provide a distributed transaction with remote adapters. Legacy fact approvals without a payload digest require a fresh proposal and approval.

Validation

• npm test: 490 tests passed, plus lint, publication-data checks and all repository proof gates.
• Regression coverage includes pagination and source scope, partial reads, cancellation/deadlines, ambiguous mutation failures, reviewed-create replay, batch resume binding, concurrent fact ratification, late conflicts, source dates and freshness confirmation.
• npm run check:release and npm run check:publish passed.
• All 13 npm archives installed into an isolated directory. Packaged CLI version/find/doctor checks passed; packaged MCP stdio initialization, tool listing (32 tools) and find passed.
• server.json passed validation against its declared MCP registry JSON schema.

No registry publication is part of this PR or its CI. Publish npm packages, the existing MCP registry entry and a matching GitHub Release after review and merge.