CaliLuke declares fork identity: Luke, a local-first job-search workbench

One commit reframes the entire repo - new name, new purpose, new stack, eight-milestone migration plan, and a working Rust FFI bridge to embedded SurrealDB. This fork is diverging hard from upstream.

infrastructurebranding

Commit 9470452d is the fork's thesis statement. The README is rewritten end-to-end, AGENTS.md is updated to describe a transitional architecture, and a 246-line LOCAL_JOB_WORKBENCH_MIGRATION_PLAN.md appears with eight milestones: M0 persistence spike through M7 Wails feasibility. The plan rips out Supabase Auth, Postgres, R2, and Express in favor of embedded SurrealDB/SurrealKV, Loom-generated Go services, Romancy durable workflows on SQLite, local file storage, Ollama as the default AI surface, and a Wails desktop shell targeting macOS arm64.

The M0 spike lands in the same commit. A new backend-go/ package contains a Go test that opens a file-backed SurrealKV database, writes a record, closes it, reopens the same path in-process, and reads the record back. The persistence path runs through CGO and a 134-line Rust static library (backend-go/internal/persistence/rustbridge/src/lib.rs) that links the surrealdb 3.0.5 crate with the kv-surrealkv feature. The spike document explains why: the official Go SDK is remote-only, and the C binding (surrealdb.c.go) failed the same-process reopen because the C wrapper drops its Rust runtime before SurrealKV releases the file lock. The Rust bridge works around an async-shutdown lag with a bounded retry. Cargo.lock adds ~5400 lines of transitive Rust dependencies.

One legal issue worth noting: the LICENSE file is deleted from the repository while the README retains a one-line AGPL-3.0-only reference. AGPL requires the license text to accompany distribution; a one-line mention doesn't satisfy that obligation. This appears to be an oversight rather than intent.

So what Skip for now. The Rust FFI bridge, migration plan, and README rewrite are scoped entirely to a fork that discards the multi-tenant cloud product. The `backend-go` tree requires Rust, CGO, and Apple Command Line Tools, and is verified only on macOS arm64. Watch later milestones - if the Loom Go backend ports successfully, individual pieces may become liftable, but nothing here is directly importable.

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from CaliLuke/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`9470452d`	Add Luke local-first migration plan and persistence spike	CaliLuke	2026-05-06	↗ GitHub
commit body Reframes the repo as Luke (a local-first single-user job-search workbench), adds the milestone plan for migrating off Supabase/Express to a Loom Go backend on embedded SurrealDB, and lands the Rust FFI persistence spike that the plan depends on. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

SHA

Subject

Author

Date

9470452d

Add Luke local-first migration plan and persistence spike

CaliLuke

2026-05-06

↗ GitHub

commit body

Reframes the repo as Luke (a local-first single-user job-search workbench),
adds the milestone plan for migrating off Supabase/Express to a Loom Go
backend on embedded SurrealDB, and lands the Rust FFI persistence spike
that the plan depends on.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-70.md from inside the repo you want the changes in.