2 Commits

Include renames

Author	SHA1	Message	Date
yonluandClaude Opus 5	4471db3aef	feat(wails): move the Go side to v3 ... Phases 2 and 3 of plan 009, plus the parts of phase 1 that could not land before them. Nothing in the tree imports wails/v2 any more; all three lint and test configurations are green and `go build .` produces a running binary. The point of the migration is one file. backend/events/emit.go probed ctx.Value("events") — a v2-*private* context key — to decide whether emitting was safe, because runtime.EventsEmit called log.Fatalf on a context without the runtime and took the process down with it. v3's emit takes no context, so that is now application.Get() == nil. D1 held: events.Emit keeps its ctx as the WithSink test seam, and all 45 call sites and 7 test files are untouched. The bootstrap splits into application.New + Window.NewWithOptions + Run. Ten bound services implement ServiceStartup instead of being handed a context by hand from OnStartup, which also stops ten SetContext methods being exported as bindings. jobs.Registry and explore.SearchIndex keep theirs — neither is bound, so converting them would be churn for no binding removed. Four things differed from the plan and are written up in it: GPU policy moved to the per-window LinuxWindow options rather than surviving on LinuxOptions; there is no OnStartup/OnDomReady option, so app-level wiring hangs off ApplicationStarted; application.NewService is generic, so FEBindings []any could not survive (the binding generator is a static analyser and would have seen nothing); and the quit veto had to be restructured, because v3's dialog answers on a callback rather than returning the button, so ShouldQuit vetoes, asks, and quits again from the callback. Window state saving moves to a WindowClosing hook — the size has to be read while the window still exists, and v3's OnShutdown has neither context nor window. backend/logging is deleted rather than ported: v3 takes a *slog.Logger directly, so the v2 logger.Logger adapter had no caller left. Phase 1's tail rides along, now that it can: the Makefile's wails invocations, all 50 webkit2_41 sites, lefthook, both packaging recipes and ci.yml's apt lists. v3 builds against GTK4 + WebKitGTK 6.0, which Arch and ubuntu:24.04 both ship, so the tag is a deletion rather than a translation. Phase 4 is next and the branch is not usable until it lands: the app builds, but frontend/wailsjs/ is v2's tree and nothing regenerates it, so the frontend cannot reach the backend yet. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UDCbcCZQepnpSQYJ6SxxZm	2026-08-14 14:01:02 -04:00
logan	5ca6cad45a	feat(harness): agent-drivable dev harness and CI that gates ... A coding agent could develop this repo's Go packages and could not develop the application: every path to running YellowJacket ended in a blocking GTK window, so 265 bound methods, 46 events, 33 component directories and 13 stores had exactly one form of verification available — `tsc --noEmit`. The unlock is that `wails dev`'s dev server on :34115 serves the real frontend with the real generated bindings against the same Go backend a desktop window attaches to, so a plain Chromium under Xvfb gets a fully functional app. Four test tiers now exist, cheapest first: - `make ui-test` — 313 Vitest tests in a real browser in ~2 s, no app, no backend, no display. Works because `frontend/wailsjs/` is a pure passthrough to `window.go`/`window.runtime`, so faking just those two globals runs the real bindings and the real store code. - `make test` — services in-process, asserting on the payload the frontend would receive, via a new `events.Emit` wrapper. - `make dev-headless` + `playwright-cli` — the real app, driven interactively, with an event bridge on `window.__yjEvents` and a dev-only control surface at `/__test/`. - `make e2e` — 19 of those flows frozen as Playwright specs. `events.Emit(ctx, …)` replaces all 35 direct `runtime.EventsEmit` call sites: wails' `getEvents` `log.Fatalf`s on any context without its runtime, so those paths could not run under test and a background worker could take the app down. Four packages had each hand-rolled the same guard; nine more guarded on `ctx != nil`, which does not help. `TestNoDirectRuntimeEmits` fails the build on a new one. Fixtures are generated, not committed (`make testdata`), and seeds are built by *running the app* — never by hand-writing config and DB rows, which would be a second description of a valid YJ_HOME. `.gitea/workflows/ci.yml` is the first workflow here that tests anything; the other three only package, so `gitea_ci` reported only packaging jobs and misled anyone asking whether a push was healthy. Both jobs were prototyped to green in a bare ubuntu:24.04 container before the YAML was written, which immediately caught `make lint` linting three configurations that nothing builds: all three passes omitted `webkit2_41`, so wails resolved webkit2gtk-4.0 — which Arch still ships and Ubuntu 24.04 dropped. Operational instructions live in `.pi/skills/yellowjacket-dev/`, measured discoveries in `.planning/NOTES.md`, and architecture in `CLAUDE.md` — split by tense, not by topic, because a topical split gives every new fact two plausible homes. `make skill-check` fails a commit if the skill cites a make target that does not exist.	2026-08-10 23:20:42 -04:00