feat: jj-ryu ForgeGraph bridge (external stack sync)

gmackie commented

2026-07-01 11:20:00 +00:00

Owner

Rebased from the April jj-ryu-forgegraph-bridge branch (design doc: docs/plans/2026-04-15-jj-ryu-forgegraph-bridge-design.md, status: approved). One-way jj-ryu -> ForgeGraph stack sync: create/update/close stack nodes, reparent edges, workspace-membership authorization, stale-topology guards.

Adds 5 nullable columns + 2 unique indexes to changesets (external_source, external_source_id, external_parent_source_id, external_head_ref, last_external_sync_at) via db:push (this repo applies schema via push, not versioned migrations) — already applied to the dev DB and verified additive/safe (existing rows all NULL, no duplicate-key conflicts on the new unique indexes).

Note: the route.test.ts integration suite uses a blanket TRUNCATE ... CASCADE for cleanup between tests, which fails against the shared local dev DB's restricted grants (the forgegraph role lacks TRUNCATE on some newer tables reached via cascade, e.g. gcp_app_bindings) but should work fine against CI's own dedicated test DB where the role owns everything. Flagging this since I couldn't fully verify the test suite locally — please check CI's result on this file specifically.

Rebased from the April jj-ryu-forgegraph-bridge branch (design doc: docs/plans/2026-04-15-jj-ryu-forgegraph-bridge-design.md, status: approved). One-way jj-ryu -> ForgeGraph stack sync: create/update/close stack nodes, reparent edges, workspace-membership authorization, stale-topology guards. Adds 5 nullable columns + 2 unique indexes to changesets (external_source, external_source_id, external_parent_source_id, external_head_ref, last_external_sync_at) via db:push (this repo applies schema via push, not versioned migrations) — already applied to the dev DB and verified additive/safe (existing rows all NULL, no duplicate-key conflicts on the new unique indexes). Note: the route.test.ts integration suite uses a blanket TRUNCATE ... CASCADE for cleanup between tests, which fails against the shared local dev DB's restricted grants (the forgegraph role lacks TRUNCATE on some newer tables reached via cascade, e.g. gcp_app_bindings) but should work fine against CI's own dedicated test DB where the role owns everything. Flagging this since I couldn't fully verify the test suite locally — please check CI's result on this file specifically.

gmackie added 4 commits

2026-07-01 11:20:00 +00:00

feat(db): add external stack sync fields to changesets 355768f243

Adds nullable external_source/external_source_id/external_parent_source_id/
external_head_ref/last_external_sync_at columns plus unique indexes on
(repositoryId, jjChangeId) and (repositoryId, externalSourceId), for
jj-ryu -> ForgeGraph one-way stack sync (see
docs/plans/2026-04-15-jj-ryu-forgegraph-bridge-design.md).

Schema-only: this repo applies schema changes via `db:push`
(introspection), not versioned drizzle-kit generate migrations.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

feat(api): add jj-ryu stack sync endpoints 2251b12fb4

fix(api): guard stale jj-ryu topology sync 73e8f37803

fix(api): authorize stack sync by workspace membership

CI / ci (pull_request) Successful in 15m46s

Details

444adc3578

gmackie merged commit 24a3cfd3e1 into main

2026-07-01 12:01:16 +00:00

gmackie referenced this pull request from a commit

2026-07-01 12:01:17 +00:00

feat: jj-ryu ForgeGraph bridge (external stack sync) (#46)

gmackie referenced this pull request from a commit

2026-07-01 15:43:33 +00:00

fix(db): remove nodeDatabaseBindings schema alias, blocking every deploy

Rows
Columns

feat: jj-ryu ForgeGraph bridge (external stack sync) #46