Skip to content

Prepare Syncables 0.26.0 and proxy 0.4.1 for Keep write-back - #714

Merged
michielbdejong merged 4 commits into
mainfrom
codex/syncd-keep-release-0-26
Oct 30, 2026
Merged

michielbdejong merged 4 commits into
mainfrom
codex/syncd-keep-release-0-26

Conversation

@michielbdejong

@michielbdejong michielbdejong commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

The merged SyncD write implementation was unavailable in published packages. This release publishes syncables 0.26.0 and atomic-integration-proxy 0.4.1, with version/lock updates and consolidated release notes. No runtime or dependency versions change in this PR.

Codex completed the required state-of-the-art-model release review on head e6a2a37; review evidence. All 25 checks on that head passed/skipped. Independent laptop validation passed all 1,858 tests in 105 files with PostgreSQL, build, lint, formatting and changelog checks. The reviewed merge b23ec68 passed every main check before the crate release tag.

Both publications succeeded: npm 0.26.0 gitHead and the registry crate’s source metadata identify b23ec68. The integration-proxy-v0.4.1 OIDC publication passed, and its checksum was verified before locking the wrapper.

Catalog PR #717 preserves the actual production selection of 15 platforms, replacing only Keep. Its PR checks and Pages/Overlays publication passed. All fourteen non-Keep public composed documents remained byte-for-byte unchanged after deployment.

Wrapper PR #85 passed local and hosted checks and deployed as Heroku v101, commit f98862b441fb4701cfaf2740cb37d8aa07ea41c4. Health, startup logs and proxy:write discovery verified.

The laptop live trial used the installed npm package, a separate local PostgreSQL database, fresh memory-only grants for the existing Keep connection and invented checklist text. Create/pull, replace/pull and delete/pull succeeded; both trial-created IDs are absent and baseline/final collection counts match. One initial checked-parent/unchecked-child replacement payload was rejected with HTTP 400, retaining the original and creating no recorded replacement; that failed intent was cancelled. A new intent unchecking both parent and child completed successfully. Private receipts/history remain local; no credential or private note content is included here. Existing Keychain sessions were not replaced.

See the rollout handoff for migration, replacement and downgrade constraints. Completion status is reported on #227.

Consolidate unreleased notes around the final PostgreSQL/CLI implementation and document the reviewed release, production catalog preservation, Heroku rollout and isolated scratch-note trial. Keep publication and deployment gated on the required Opus review; merging the npm version bump will publish automatically.

Claude-Session: https://github.com/ontola/atomic-plugins/blob/codex/syncd-keep-release-0-26/syncables/docs/ai-logs/sessions/2026-10-29-syncd-release-preparation.md

Codex-Session: https://github.com/ontola/atomic-plugins/blob/codex/syncd-keep-release-0-26/syncables/docs/ai-logs/sessions/2026-10-29-syncd-release-preparation.md

@michielbdejong michielbdejong left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Codex release review completed on e6a2a37 at Michiel's explicit request to take over release/deployment. No blocking findings.

Reviewed the #714 release diff and merged #713 write implementation, plus the proxy changes since 0.4.0 (owner transfer locking/retirement, pacing tiers and bounded webhook payload reads). Version/lock changes contain no dependency upgrades or runtime changes; release notes retain migration/API and downgrade constraints. Checked default-off collection writes, independent connection-scoped read/write grants and refresh scope preservation, strict writable schema projection including nested checklist defaults, path encoding, receipt persistence before DELETE, no automatic uncertain-create retries, fresh precondition reads, retained partial-replacement receipts, and credential/transport isolation.

Validation: all 25 current-head hosted checks succeeded or intentionally skipped, including CI/GitGuardian, Node 22/24/26 and proxy suite/package/wrapper. Independently ran all 1,858 tests in 105 files against a dedicated local PostgreSQL database, plus TypeScript build, lint, formatting and changelog validation; all passed.

Accepted documented experimental limits: Keep replacement changes identity and loses metadata unavailable via its API; ownership is explicitly attested; conditional DELETE is unavailable, leaving a documented last-GET/DELETE race. The live trial must use only its own newly created disposable note and a separate local database. Production currently has 15 platforms; deployment will preserve every non-Keep catalog entry and replace only Keep. This review does not claim package publication, deployment or live provider verification.

@michielbdejong
michielbdejong marked this pull request as ready for review October 30, 2026 10:37
@michielbdejong
michielbdejong merged commit b23ec68 into main Oct 30, 2026
25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant