lanekeeper 0.1.0 → 0.1.1

package/dist/land.js

@@ -101,8 +101,13 @@ export async function land() {
                 // Landing isn't "done" until the checkout that actually serves your
                 // dev server can see it — call sync in-process rather than shelling
                 // back out to the CLI, so this doesn't depend on `lanekeeper` being
-                // resolvable on PATH.
-                exitCode = await sync();
+                // resolvable on PATH. Pass this lane's own already-loaded cfg through
+                // rather than letting sync() reload from MAIN — MAIN hasn't been
+                // fast-forwarded yet at this exact moment (that's what sync is about
+                // to do), so if this push just introduced or changed
+                // lanekeeper.config.mjs itself, a fresh MAIN-side load would silently
+                // fall back to DEFAULTS instead of the real config.
+                exitCode = await sync(cfg);
                 // Housekeeping, never a reason to fail this landing: sweep sibling
                 // lanes whose OWN branch already made it upstream (nothing created
                 // ever tears a worktree down on the way out) so they don't

package/dist/sync.d.ts

@@ -1,2 +1,16 @@
-/** Fast-forwards the MAIN checkout. Returns a process exit code; never throws. */
-export declare function sync(): Promise<number>;
+import { type LaneKeeperConfig } from "./lib/config.js";
+/**
+ * Fast-forwards the MAIN checkout. Returns a process exit code; never throws.
+ *
+ * Accepts an already-loaded config, for `land` calling this immediately
+ * after a push that ITSELF introduced or changed lanekeeper.config.mjs: the
+ * MAIN checkout hasn't been fast-forwarded yet at that exact moment (that's
+ * this function's whole job), so loading fresh from MAIN would silently
+ * fall back to DEFAULTS and could reject a perfectly good sync — the same
+ * bootstrap gap createLane had to be fixed for. The lane's own config,
+ * which just successfully rebased onto and pushed to the real
+ * integrationBranch, is the more trustworthy answer at that moment. A bare
+ * `lanekeeper sync` (no caller-provided config) still loads fresh from
+ * MAIN, same as before.
+ */
+export declare function sync(providedCfg?: LaneKeeperConfig): Promise<number>;

package/dist/sync.js

@@ -40,8 +40,21 @@ function sleep(ms) {
         /* tiny synchronous backoff for index.lock */
     }
 }
-/** Fast-forwards the MAIN checkout. Returns a process exit code; never throws. */
-export async function sync() {
+/**
+ * Fast-forwards the MAIN checkout. Returns a process exit code; never throws.
+ *
+ * Accepts an already-loaded config, for `land` calling this immediately
+ * after a push that ITSELF introduced or changed lanekeeper.config.mjs: the
+ * MAIN checkout hasn't been fast-forwarded yet at that exact moment (that's
+ * this function's whole job), so loading fresh from MAIN would silently
+ * fall back to DEFAULTS and could reject a perfectly good sync — the same
+ * bootstrap gap createLane had to be fixed for. The lane's own config,
+ * which just successfully rebased onto and pushed to the real
+ * integrationBranch, is the more trustworthy answer at that moment. A bare
+ * `lanekeeper sync` (no caller-provided config) still loads fresh from
+ * MAIN, same as before.
+ */
+export async function sync(providedCfg) {
     let MAIN;
     try {
         MAIN = resolveMainCheckout(process.cwd());
@@ -50,7 +63,7 @@ export async function sync() {
         console.error("lanekeeper sync: not inside a git repo — nothing to do.");
         return 0;
     }
-    const cfg = await loadConfig(MAIN);
+    const cfg = providedCfg ?? (await loadConfig(MAIN));
     const regenerable = new Set(cfg.regenerableFiles);
     const branchRes = git(MAIN, ["rev-parse", "--abbrev-ref", "HEAD"], { allowFail: true });
     const branch = branchRes.out.trim();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lanekeeper",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "The local, zero-cost merge queue for parallel Claude Code agents. Plugs into Claude Code's native worktree isolation; one build at a time, one landing at a time, zero races.",
   "type": "module",
   "license": "MIT",
@@ -8,7 +8,7 @@
   "homepage": "https://github.com/funador/lanekeeper",
   "repository": {
     "type": "git",
-    "url": "https://github.com/funador/lanekeeper.git"
+    "url": "git+https://github.com/funador/lanekeeper.git"
   },
   "keywords": [
     "claude-code",
@@ -20,7 +20,7 @@
     "monorepo-tooling"
   ],
   "bin": {
-    "lanekeeper": "./dist/bin/lanekeeper.js"
+    "lanekeeper": "dist/bin/lanekeeper.js"
   },
   "files": [
     "dist",