add lane stuff (#1107)

Author: davidslater

.agents/skills/lane/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: lane
+description: Use lane in this repository when the user asks to create or work in an isolated worktree.
+---
+
+# lane
+
+## Create a worktree
+
+Create a worktree only when asked by the user. Otherwise, work in the current checkout.
+
+```bash
+lane new fix-login     # create a branch and worktree
+lane enter fix-login   # print or enter the lane's directory
+```
+
+Capture the worktree path printed by `lane new` or `lane enter`. Use that path as
+the working directory for every subsequent command; do not assume a `cd` persists
+between command invocations. Work there, not in the parent checkout.
+
+## Rules
+
+- Do not pass `--dirty` unless the lane should inherit the parent checkout's uncommitted work.
+
+## End gate
+
+When the user asks to publish the work, run `lane push`, then create a PR for the
+branch. Do not push or create a PR solely because the work in the lane is complete.

.lane/.gitkeep

@@ -312,3 +312,10 @@ docker compose down -v + rm /tmp/awf-<ts>/
 ## Exit Codes & Cleanup
 
 AWF propagates the agent container's exit code via `docker inspect`. Use `--keep-containers` to preserve `/tmp/awf-<ts>/` (squid.conf, docker-compose.yml, agent-logs/, squid-logs/) for debugging.
+
+## Lane worktrees
+
+- Create isolated worktrees only when asked by the user. Use `lane new <name>` and work in the printed path. Otherwise, work in the current checkout.
+- Do not pass `--dirty` unless the worktree should inherit the parent checkout's uncommitted work.
+- Run `lane push` as the end gate when the work is ready to publish.
+