lalph 0.1.2 → 0.1.4

package/dist/cli.mjs

@@ -132212,10 +132212,12 @@ var Worktree = class extends Service()("lalph/Worktree", { make: gen(function* (
 	const pathService = yield* Path$1;
 	const directory = yield* fs.makeTempDirectory();
 	yield* addFinalizer(fnUntraced(function* () {
-		yield* execIgnore(make$21`git worktree remove ${directory}`);
+		yield* execIgnore(make$21`git worktree remove --force ${directory}`);
 	}));
+	yield* execIgnore(make$21`git pull`);
 	yield* exec(make$21`git worktree add ${directory} -d HEAD`);
 	yield* fs.makeDirectory(pathService.join(directory, ".lalph"), { recursive: true });
+	yield* scoped$1(fs.open(pathService.join(directory, "PROGRESS.md"), { flag: "a+" }));
 	yield* forEach$1([
 		make$21({
 			cwd: directory,
@@ -132367,11 +132369,13 @@ var PromptGen = class extends Service()("lalph/PromptGen", { make: gen(function*
    - If there is an existing PR, checkout the branch for that PR.
    - If there is an existing PR, check if there are any new comments or requested
      changes, and address them as part of the task.
+   - New branches should be named using the format \`{task id}/description\`.
 4. Run any checks / feedback loops, such as type checks, unit tests, or linting.
 5. APPEND your progress to the PROGRESS.md file.
 6. Create or update the pull request with your changes once the task is complete. The title of
    the PR should include the task id. The PR description should include a
    summary of the changes made.
+   - None of the files in the \`.lalph\` directory should be committed.
 7. Update the prd.json file to reflect any changes in task states.
    - Add follow up tasks only if needed.
    - Append to the \`description\` field with any notes.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "lalph",
   "type": "module",
-  "version": "0.1.2",
+  "version": "0.1.4",
   "publishConfig": {
     "access": "public"
   },

package/src/PromptGen.ts

@@ -21,11 +21,13 @@ export class PromptGen extends ServiceMap.Service<PromptGen>()(
    - If there is an existing PR, checkout the branch for that PR.
    - If there is an existing PR, check if there are any new comments or requested
      changes, and address them as part of the task.
+   - New branches should be named using the format \`{task id}/description\`.
 4. Run any checks / feedback loops, such as type checks, unit tests, or linting.
 5. APPEND your progress to the PROGRESS.md file.
 6. Create or update the pull request with your changes once the task is complete. The title of
    the PR should include the task id. The PR description should include a
    summary of the changes made.
+   - None of the files in the \`.lalph\` directory should be committed.
 7. Update the prd.json file to reflect any changes in task states.
    - Add follow up tasks only if needed.
    - Append to the \`description\` field with any notes.

package/src/Worktree.ts

@@ -9,15 +9,23 @@ export class Worktree extends ServiceMap.Service<Worktree>()("lalph/Worktree", {
 
     yield* Effect.addFinalizer(
       Effect.fnUntraced(function* () {
-        yield* execIgnore(ChildProcess.make`git worktree remove ${directory}`)
+        yield* execIgnore(
+          ChildProcess.make`git worktree remove --force ${directory}`,
+        )
       }),
     )
 
+    yield* execIgnore(ChildProcess.make`git pull`)
     yield* exec(ChildProcess.make`git worktree add ${directory} -d HEAD`)
 
     yield* fs.makeDirectory(pathService.join(directory, ".lalph"), {
       recursive: true,
     })
+    yield* Effect.scoped(
+      fs.open(pathService.join(directory, "PROGRESS.md"), {
+        flag: "a+",
+      }),
+    )
 
     yield* Effect.forEach(
       [