lemming-cli 0.9.0__tar.gz → 0.9.1__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (194) hide show
  1. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/PKG-INFO +25 -9
  2. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/README.md +24 -8
  3. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/docs/HOOKS.md +11 -4
  4. lemming_cli-0.9.1/docs/WORKSPACE.md +145 -0
  5. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/pyproject.toml +1 -1
  6. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/tasks_test.py +1 -1
  7. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/snapshots.py +3 -0
  8. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/snapshots_test.py +17 -0
  9. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/uv.lock +1 -1
  10. lemming_cli-0.9.0/docs/WORKSPACE.md +0 -120
  11. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/.dockerignore +0 -0
  12. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/.github/workflows/ci.yml +0 -0
  13. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/.github/workflows/publish.yml +0 -0
  14. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/.github/workflows/screenshots.yml +0 -0
  15. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/.gitignore +0 -0
  16. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/.prettierignore +0 -0
  17. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/.prettierrc +0 -0
  18. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/Dockerfile +0 -0
  19. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/LICENSE +0 -0
  20. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/SKILL.md +0 -0
  21. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/biome.json +0 -0
  22. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/docker-compose.yml +0 -0
  23. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/docs/EVALS.md +0 -0
  24. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/docs/screenshots/dashboard-desktop.png +0 -0
  25. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/docs/screenshots/dashboard-mobile.png +0 -0
  26. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/docs/screenshots/task-log-desktop.png +0 -0
  27. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/docs/screenshots/task-log-mobile.png +0 -0
  28. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/package-lock.json +0 -0
  29. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/package.json +0 -0
  30. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/playwright.config.js +0 -0
  31. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/__init__.py +0 -0
  32. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/__init__.py +0 -0
  33. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/auth.py +0 -0
  34. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/auth_test.py +0 -0
  35. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/config.py +0 -0
  36. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/config_test.py +0 -0
  37. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/conftest.py +0 -0
  38. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/context.py +0 -0
  39. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/context_test.py +0 -0
  40. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/directories.py +0 -0
  41. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/directories_test.py +0 -0
  42. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/files.py +0 -0
  43. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/files_test.py +0 -0
  44. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/hooks.py +0 -0
  45. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/hooks_test.py +0 -0
  46. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/logging.py +0 -0
  47. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/logging_test.py +0 -0
  48. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/loop.py +0 -0
  49. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/loop_test.py +0 -0
  50. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/main.py +0 -0
  51. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/main_test.py +0 -0
  52. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/tasks.py +0 -0
  53. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/api/tasks_test.py +0 -0
  54. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/artifact_test.py +0 -0
  55. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/brief_test.py +0 -0
  56. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/__init__.py +0 -0
  57. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/artifact.py +0 -0
  58. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/brief.py +0 -0
  59. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/config.py +0 -0
  60. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/config_test.py +0 -0
  61. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/exec_cli.py +0 -0
  62. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/exec_cli_test.py +0 -0
  63. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/goal.py +0 -0
  64. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/goal_test.py +0 -0
  65. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/hooks.py +0 -0
  66. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/hooks_test.py +0 -0
  67. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/machine_output_test.py +0 -0
  68. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/main.py +0 -0
  69. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/main_test.py +0 -0
  70. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/operations.py +0 -0
  71. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/operations_test.py +0 -0
  72. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/progress.py +0 -0
  73. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/progress_test.py +0 -0
  74. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/readability_cli.py +0 -0
  75. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/readability_cli_test.py +0 -0
  76. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/skill.py +0 -0
  77. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/skill_test.py +0 -0
  78. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/stop_test.py +0 -0
  79. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/cli/tasks.py +0 -0
  80. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/conftest.py +0 -0
  81. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/__init__.py +0 -0
  82. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/__main__.py +0 -0
  83. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/cli.py +0 -0
  84. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/cli_test.py +0 -0
  85. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/container.py +0 -0
  86. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/container_test.py +0 -0
  87. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/fixtures.py +0 -0
  88. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/fixtures_test.py +0 -0
  89. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/harness.py +0 -0
  90. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/harness_test.py +0 -0
  91. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/metrics.py +0 -0
  92. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/metrics_test.py +0 -0
  93. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/readability/base/README.md +0 -0
  94. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/readability/base/calc/__init__.py +0 -0
  95. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/readability/base/calc/legacy.py +0 -0
  96. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/readability/base/calc/ops.py +0 -0
  97. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/readability/base/calc/ops_test.py +0 -0
  98. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/readability/clean/calc/ops.py +0 -0
  99. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/readability/clean/calc/ops_test.py +0 -0
  100. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/readability/dead-code/calc/ops.py +0 -0
  101. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/readability/dead-code/calc/ops_test.py +0 -0
  102. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/readability/duplicated-behavior/calc/ops.py +0 -0
  103. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/readability/duplicated-behavior/calc/ops_test.py +0 -0
  104. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/readability/false-reuse/calc/limits.py +0 -0
  105. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/readability/false-reuse/calc/limits_test.py +0 -0
  106. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/readability/lint-debt/calc/ops.py +0 -0
  107. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/readability/lint-debt/calc/ops_test.py +0 -0
  108. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/roadmap/add-only/README.md +0 -0
  109. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/roadmap/add-only/calc/__init__.py +0 -0
  110. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/roadmap/add-only/calc/ops.py +0 -0
  111. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/roadmap/add-only/calc/ops_test.py +0 -0
  112. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/roadmap/buggy-subtract/README.md +0 -0
  113. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/roadmap/buggy-subtract/calc/__init__.py +0 -0
  114. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/roadmap/buggy-subtract/calc/ops.py +0 -0
  115. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/roadmap/buggy-subtract/calc/ops_test.py +0 -0
  116. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/roadmap/full-ops/README.md +0 -0
  117. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/roadmap/full-ops/calc/__init__.py +0 -0
  118. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/roadmap/full-ops/calc/ops.py +0 -0
  119. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/roadmap/full-ops/calc/ops_test.py +0 -0
  120. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/roadmap/unwired-cli/README.md +0 -0
  121. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/roadmap/unwired-cli/calc/__init__.py +0 -0
  122. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/roadmap/unwired-cli/calc/cli.py +0 -0
  123. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/roadmap/unwired-cli/calc/cli_test.py +0 -0
  124. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/roadmap/unwired-cli/calc/ops.py +0 -0
  125. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/roadmap/unwired-cli/calc/ops_test.py +0 -0
  126. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/task/hidden/stats/summary_hidden_test.py +0 -0
  127. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/task/summary/README.md +0 -0
  128. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/task/summary/stats/__init__.py +0 -0
  129. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/task/summary/stats/summary.py +0 -0
  130. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/projects/task/summary/stats/summary_test.py +0 -0
  131. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/readability.py +0 -0
  132. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/readability_test.py +0 -0
  133. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/report.py +0 -0
  134. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/report_test.py +0 -0
  135. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/roadmap.py +0 -0
  136. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/roadmap_test.py +0 -0
  137. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/scenarios.py +0 -0
  138. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/scenarios_test.py +0 -0
  139. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/suites.py +0 -0
  140. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/task.py +0 -0
  141. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/task_test.py +0 -0
  142. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/trial.py +0 -0
  143. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/evals/trial_test.py +0 -0
  144. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/hooks.py +0 -0
  145. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/hooks_test.py +0 -0
  146. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/integration_test.py +0 -0
  147. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/main.py +0 -0
  148. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/main_test.py +0 -0
  149. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/models.py +0 -0
  150. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/models_test.py +0 -0
  151. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/orchestrator.py +0 -0
  152. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/orchestrator_test.py +0 -0
  153. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/paths.py +0 -0
  154. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/paths_test.py +0 -0
  155. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/persistence.py +0 -0
  156. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/persistence_test.py +0 -0
  157. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/prompts/hooks/50-readability.md +0 -0
  158. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/prompts/hooks/60-testing.md +0 -0
  159. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/prompts/hooks/70-ux.md +0 -0
  160. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/prompts/hooks/90-roadmap.md +0 -0
  161. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/prompts/taskrunner.md +0 -0
  162. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/prompts.py +0 -0
  163. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/prompts_test.py +0 -0
  164. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/providers.py +0 -0
  165. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/providers_test.py +0 -0
  166. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/runner.py +0 -0
  167. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/runner_test.py +0 -0
  168. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/scope.py +0 -0
  169. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/scope_test.py +0 -0
  170. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/shutdown.py +0 -0
  171. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/shutdown_integration_test.py +0 -0
  172. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/shutdown_test.py +0 -0
  173. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/tasks/__init__.py +0 -0
  174. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/tasks/lifecycle.py +0 -0
  175. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/tasks/lifecycle_test.py +0 -0
  176. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/tasks/limits.py +0 -0
  177. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/tasks/operations.py +0 -0
  178. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/tasks/operations_test.py +0 -0
  179. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/tasks/progress.py +0 -0
  180. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/tasks/progress_test.py +0 -0
  181. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/tasks/queries.py +0 -0
  182. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/tasks/queries_test.py +0 -0
  183. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/web/dashboard.spec.js +0 -0
  184. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/web/dashboard.test.js +0 -0
  185. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/web/favicon.js +0 -0
  186. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/web/favicon.spec.js +0 -0
  187. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/web/files.html +0 -0
  188. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/web/files.spec.js +0 -0
  189. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/web/index.html +0 -0
  190. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/web/index.js +0 -0
  191. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/web/logs.html +0 -0
  192. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/web/logs.test.js +0 -0
  193. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/web/mancha.js +0 -0
  194. {lemming_cli-0.9.0 → lemming_cli-0.9.1}/src/lemming/web/screenshots.spec.js +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: lemming-cli
3
- Version: 0.9.0
3
+ Version: 0.9.1
4
4
  Summary: An autonomous, iterative task runner for AI coding agents.
5
5
  Project-URL: Homepage, https://github.com/owahltinez/lemming
6
6
  Project-URL: Repository, https://github.com/owahltinez/lemming
@@ -99,10 +99,10 @@ lemming run
99
99
  lemming run -- --model claude-3-5-sonnet
100
100
  ```
101
101
 
102
- The loop runs every task in one shared workspace, and the orchestrator never
103
- branches or commits on your behalf. Give the whole run its own branch or
104
- worktree first if you want to be able to throw it away — see
105
- [docs/WORKSPACE.md](docs/WORKSPACE.md).
102
+ The loop runs every task in one shared workspace, snapshotting the working tree
103
+ in an isolated shadow Git repository before and after each task and hook without
104
+ touching your `.git` history. Give the whole run its own branch or worktree
105
+ first when working in parallel — see [docs/WORKSPACE.md](docs/WORKSPACE.md).
106
106
 
107
107
  ---
108
108
 
@@ -249,9 +249,11 @@ loops through each pending task:
249
249
  `lemming complete` or `lemming fail`. Agents can also schedule new tasks
250
250
  with `lemming add`, breaking down complex work into smaller steps that
251
251
  Lemming will pick up automatically.
252
- 4. **Retry or advance**: On failure, Lemming retries the task up to the
253
- configured roadmap limit, with accumulated progress as context so the agent
254
- learns from previous attempts. On success, it moves to the next task.
252
+ 4. **Retry or advance**: On failure, timeout, or cancellation, Lemming saves
253
+ the discarded workspace diff as an `attempt-<N>.patch` artifact, restores
254
+ the working tree to the task's pre-run snapshot, and retries up to the
255
+ configured limit with accumulated progress as context. On success, it moves
256
+ to the next task.
255
257
  5. **Orchestration**: After each task, Lemming can run one or more
256
258
  **Orchestrator Hooks** (like the built-in `roadmap` hook) to evaluate the
257
259
  results and adapt the roadmap if needed. Hooks are enabled by default but
@@ -434,8 +436,22 @@ These come before the subcommand and apply to all of them.
434
436
 
435
437
  - **`complete <id>`**: Mark a task as successful.
436
438
  - **`fail <id>`**: Mark a task as a terminal failure (will not be retried).
437
- - **`cancel <id>`**: Stop an in-progress task (kills the runner process).
439
+ - **`reject <id> <reason>`**: Reject a finalizing task's completion from a
440
+ review hook, sending it back for a retry.
441
+ - **`cancel <id>`**: Stop an in-progress task (kills the runner process and
442
+ restores its pre-run workspace snapshot).
438
443
  - **`reset <id>`**: Clear attempts and progress to start a task fresh.
444
+ - **`diff [<id>]`**: Print the workspace diff captured for a task (defaults to
445
+ the active or most recent snapshotted task).
446
+ - `--stat`: Show diffstat summary instead of the full patch.
447
+ - `--hook <name>`: Show only the diff introduced by a specific post-run hook.
448
+ - **`rollback <id>`**: Revert a completed task's workspace changes and reset
449
+ `<id>` and subsequent tasks to pending (requires an idle loop and a clean
450
+ workspace).
451
+ - `--only`: Revert only `<id>`'s patch in place (3-way reverse apply) and
452
+ reset only `<id>`.
453
+ - `--hook <name>`: Revert only the changes made by a specific post-run hook,
454
+ keeping the task completed.
439
455
  - Superseded tasks remain visible as non-failing history; replacement tasks link
440
456
  back through their parent task ID.
441
457
  - **`logs [<id>]`**: Print a task's execution log to stdout, including retained
@@ -79,10 +79,10 @@ lemming run
79
79
  lemming run -- --model claude-3-5-sonnet
80
80
  ```
81
81
 
82
- The loop runs every task in one shared workspace, and the orchestrator never
83
- branches or commits on your behalf. Give the whole run its own branch or
84
- worktree first if you want to be able to throw it away — see
85
- [docs/WORKSPACE.md](docs/WORKSPACE.md).
82
+ The loop runs every task in one shared workspace, snapshotting the working tree
83
+ in an isolated shadow Git repository before and after each task and hook without
84
+ touching your `.git` history. Give the whole run its own branch or worktree
85
+ first when working in parallel — see [docs/WORKSPACE.md](docs/WORKSPACE.md).
86
86
 
87
87
  ---
88
88
 
@@ -229,9 +229,11 @@ loops through each pending task:
229
229
  `lemming complete` or `lemming fail`. Agents can also schedule new tasks
230
230
  with `lemming add`, breaking down complex work into smaller steps that
231
231
  Lemming will pick up automatically.
232
- 4. **Retry or advance**: On failure, Lemming retries the task up to the
233
- configured roadmap limit, with accumulated progress as context so the agent
234
- learns from previous attempts. On success, it moves to the next task.
232
+ 4. **Retry or advance**: On failure, timeout, or cancellation, Lemming saves
233
+ the discarded workspace diff as an `attempt-<N>.patch` artifact, restores
234
+ the working tree to the task's pre-run snapshot, and retries up to the
235
+ configured limit with accumulated progress as context. On success, it moves
236
+ to the next task.
235
237
  5. **Orchestration**: After each task, Lemming can run one or more
236
238
  **Orchestrator Hooks** (like the built-in `roadmap` hook) to evaluate the
237
239
  results and adapt the roadmap if needed. Hooks are enabled by default but
@@ -414,8 +416,22 @@ These come before the subcommand and apply to all of them.
414
416
 
415
417
  - **`complete <id>`**: Mark a task as successful.
416
418
  - **`fail <id>`**: Mark a task as a terminal failure (will not be retried).
417
- - **`cancel <id>`**: Stop an in-progress task (kills the runner process).
419
+ - **`reject <id> <reason>`**: Reject a finalizing task's completion from a
420
+ review hook, sending it back for a retry.
421
+ - **`cancel <id>`**: Stop an in-progress task (kills the runner process and
422
+ restores its pre-run workspace snapshot).
418
423
  - **`reset <id>`**: Clear attempts and progress to start a task fresh.
424
+ - **`diff [<id>]`**: Print the workspace diff captured for a task (defaults to
425
+ the active or most recent snapshotted task).
426
+ - `--stat`: Show diffstat summary instead of the full patch.
427
+ - `--hook <name>`: Show only the diff introduced by a specific post-run hook.
428
+ - **`rollback <id>`**: Revert a completed task's workspace changes and reset
429
+ `<id>` and subsequent tasks to pending (requires an idle loop and a clean
430
+ workspace).
431
+ - `--only`: Revert only `<id>`'s patch in place (3-way reverse apply) and
432
+ reset only `<id>`.
433
+ - `--hook <name>`: Revert only the changes made by a specific post-run hook,
434
+ keeping the task completed.
419
435
  - Superseded tasks remain visible as non-failing history; replacement tasks link
420
436
  back through their parent task ID.
421
437
  - **`logs [<id>]`**: Print a task's execution log to stdout, including retained
@@ -95,10 +95,17 @@ lemming --tasks-file <path> reject <taskid> '<reason>'
95
95
  A rejection only applies to a task that is finalizing as completed, and it
96
96
  does not change the task's status on the spot. The remaining hooks still run
97
97
  and see the task as `REJECTED` with the reason, so the roadmap hook can tell
98
- a rejected task from a finished one. Once every hook has run, the task is
99
- reverted to pending with its attempt count intact, exactly as it is when a
100
- hook process fails, and the reason is left in its progress so the next
101
- attempt starts with the diagnosis.
98
+ a rejected task from a finished one. Once every hook has run, Lemming saves the
99
+ rejected attempt's diff as an `attempt-<N>.patch` artifact, restores the
100
+ workspace to the task's `pre_tree`, and reverts the task to pending with its
101
+ attempt count intact — just as it does when a hook process fails. The rejection
102
+ reason stays in `progress` so the next attempt starts with the diagnosis.
103
+
104
+ Each hook that runs is also bracketed by its own shadow Git snapshot pair in
105
+ `hook_trees`. If an individual hook process crashes or exits non-zero, its own
106
+ workspace edits are rolled back before the task attempt is reverted. On a
107
+ completed task, you can inspect or undo a single hook's edits with
108
+ `lemming diff <id> --hook <name>` and `lemming rollback <id> --hook <name>`.
102
109
 
103
110
  Under `lemming exec` there is no second attempt: the run ends on the first
104
111
  rejection, and under `lemming run` a rejection on the task's final attempt
@@ -0,0 +1,145 @@
1
+ # Workspace Isolation 🧰
2
+
3
+ ## Lemming is VCS-Agnostic
4
+
5
+ An agent run writes to a real directory on your disk. The orchestrator never
6
+ creates a branch, a commit, or a worktree in your project's repository: the
7
+ task-runner prompt allows the agent itself to commit when that is the project's
8
+ convention, but the orchestrator neither asks for that nor relies on it.
9
+
10
+ When `git` is installed on the host, Lemming maintains an isolated **shadow Git
11
+ repository** alongside `tasks.yml` that snapshots the working tree before and
12
+ after each task runner and orchestrator hook — without touching your `.git`
13
+ index, branches, or commit history. If an attempt fails, times out, crashes, or
14
+ is cancelled, Lemming saves its changes to an `attempt-<N>.patch` artifact and
15
+ restores the workspace (and host Git `HEAD`, if the runner committed) to the
16
+ task's pre-run snapshot.
17
+
18
+ Shadow snapshots work in a Git checkout, a Mercurial repository, or a plain
19
+ directory under no version control at all, as long as `git` is on `PATH`. Even
20
+ so, concurrent writing runs still need separate working copies, and an outer
21
+ branch or worktree remains the cleanest way to isolate an entire multi-task run
22
+ from work you are doing in parallel.
23
+
24
+ ## Isolating a One-Off `exec` Run
25
+
26
+ Concurrent writing runs must not share a checkout: two agents editing one
27
+ directory interleave their edits, and neither result is reviewable. Give each
28
+ writing run its own working copy and pass it with the global `-C` option
29
+ (`lemming -C <working-copy> -v exec ...`). The full Git worktree recipe is under
30
+ "Isolate concurrent writing runs" in [SKILL.md](../SKILL.md), summarized in the
31
+ [README](../README.md#one-off-tasks-without-a-roadmap).
32
+
33
+ ## Isolating a Roadmap Loop
34
+
35
+ `lemming run` executes its tasks **sequentially in one shared workspace**. Task
36
+ 2 starts in whatever state task 1 left behind — that is the point, since tasks
37
+ build on each other. So the unit of isolation is the whole run: **one branch or
38
+ worktree for the entire loop**, created once before `lemming run`.
39
+
40
+ **Never one branch per task.** Whichever branch the last runner left checked out
41
+ would silently become the next task's baseline, and the loop's history would
42
+ fragment across branches nobody asked for. This is why the task-runner prompt
43
+ says nothing about branching: a runner has no business changing what is checked
44
+ out under it.
45
+
46
+ The minimal Git shape, from a clean tree:
47
+
48
+ ```bash
49
+ repo=$(git rev-parse --show-toplevel) || exit 1
50
+ test -z "$(git -C "$repo" status --porcelain)" || exit 1
51
+
52
+ # One worktree for the whole run, from committed HEAD.
53
+ worktree=$(mktemp -d "${TMPDIR:-/tmp}/lemming-run.XXXXXX") || exit 1
54
+ branch="lemming/$(basename "$worktree")"
55
+ git -C "$repo" worktree add -b "$branch" "$worktree" HEAD || exit 1
56
+
57
+ # Drive the loop against it; -C is a global option, before the subcommand.
58
+ lemming -C "$worktree" goal "<the long-term goal>"
59
+ lemming -C "$worktree" add "<first task>"
60
+ lemming -C "$worktree" -v run
61
+ ```
62
+
63
+ A plain branch (`git switch -c lemming/<run>`) does just as well when nothing
64
+ else needs the checkout; the worktree only buys you the original directory to
65
+ keep working in meanwhile. Either way the roadmap travels with the workspace: a
66
+ tracked `tasks.yml` is copied into the worktree and the loop's edits stay there,
67
+ and without one Lemming keeps isolated state keyed on the worktree path.
68
+
69
+ ## Inspecting Diffs and Rolling Back Tasks
70
+
71
+ Every snapshotted task records its `pre_tree`, `runner_tree`, `post_tree`, and
72
+ per-hook tree pairs (`hook_trees`), so you can inspect or undo individual tasks
73
+ and hooks without relying on the runner having made Git commits:
74
+
75
+ ```bash
76
+ lemming -C "$worktree" status # queue, attempts, diff summaries
77
+ lemming -C "$worktree" diff <id> # full patch for one task
78
+ lemming -C "$worktree" diff <id> --stat # diffstat summary
79
+ lemming -C "$worktree" diff <id> --hook <name> # changes made by one hook
80
+ lemming -C "$worktree" logs <id> # full runner and hook log
81
+ ```
82
+
83
+ When the orchestrator loop is idle and the workspace has no uncommitted manual
84
+ edits outside the latest snapshot, `lemming rollback` can revert completed work
85
+ at three granularities:
86
+
87
+ ```bash
88
+ # Rewind to <id>'s pre_tree and reset <id> and later tasks to pending
89
+ lemming -C "$worktree" rollback <id>
90
+
91
+ # Revert only <id>'s patch in place (3-way reverse apply) and reset only <id>
92
+ lemming -C "$worktree" rollback <id> --only
93
+
94
+ # Revert only one hook's changes on <id>, keeping the task completed
95
+ lemming -C "$worktree" rollback <id> --hook testing
96
+ ```
97
+
98
+ If you also created a dedicated worktree or branch before the run, you still
99
+ have standard Git commands (`git status`, `git log HEAD`, `git diff`) to review
100
+ or discard the entire branch wholesale.
101
+
102
+ Runners are also told to write verbose evidence into Lemming's per-project
103
+ scratch directory rather than into the workspace, so a failed task's notes and
104
+ `attempt-<N>.patch` artifacts survive even after a task is rolled back or you
105
+ throw the branch away. It sits under `~/.local/lemming/` (or `$LEMMING_HOME`),
106
+ named for the first 12 hex digits of the SHA-256 of the resolved tasks-file path
107
+ — or of the workspace path, when Lemming is keeping the roadmap itself. Once the
108
+ worktree is gone `-C` can no longer resolve it, and
109
+ `lemming --tasks-file <that dir>/tasks.yml logs <id>` is the way back in.
110
+
111
+ Retain a worktree until its changes have been recovered, then clean up
112
+ non-forcibly, which refuses rather than destroying uncommitted work — including
113
+ a tracked `tasks.yml` the loop has edited, which must be committed or discarded
114
+ first:
115
+
116
+ ```bash
117
+ git -C "$repo" worktree remove "$worktree"
118
+ git -C "$repo" branch -d "$branch"
119
+ ```
120
+
121
+ ## What the Runner Prompt and Snapshots Guarantee
122
+
123
+ Runners are instructed to leave a coherent workspace, to back out their own
124
+ half-applied edits before failing, and never to restore files from version
125
+ control history; the rules live in the "Workspace Hygiene" directive of
126
+ `src/lemming/taskrunner.md`, not in a copy here. Shadow Git snapshots back that
127
+ guidance up mechanically: when an attempt fails, times out, crashes, or is
128
+ cancelled, or when a post-run hook fails, Lemming restores the workspace to the
129
+ pre-attempt or pre-hook tree automatically.
130
+
131
+ ## Workspaces Not Under Version Control
132
+
133
+ Shadow Git snapshots work in a plain directory that has no `.git` of its own, as
134
+ long as the `git` binary is installed on the machine. In a greenfield directory,
135
+ create a `.gitignore` before tasks install dependencies or run builds so
136
+ snapshots skip `node_modules/`, `.venv/`, and build outputs.
137
+
138
+ If `git` is not installed on the host, snapshots are disabled silently and there
139
+ is nothing to diff against or reset; **copy the directory before the run** if
140
+ you need a rollback baseline:
141
+
142
+ ```bash
143
+ cp -a project project.bak
144
+ lemming -C project run
145
+ ```
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
4
4
 
5
5
  [project]
6
6
  name = "lemming-cli"
7
- version = "0.9.0"
7
+ version = "0.9.1"
8
8
  description = "An autonomous, iterative task runner for AI coding agents."
9
9
  readme = "README.md"
10
10
  authors = [
@@ -379,7 +379,7 @@ class TestCLITasks(unittest.TestCase):
379
379
  )
380
380
  self.assertEqual(res.exit_code, 0)
381
381
  mock_cancel.assert_called_once_with(
382
- self.test_tasks_file,
382
+ self.test_tasks_file.resolve(),
383
383
  "12345678",
384
384
  working_dir=None,
385
385
  )
@@ -55,6 +55,9 @@ def _repo_lock(repo_dir: pathlib.Path) -> Iterator[None]:
55
55
  lock_path.parent.mkdir(parents=True, exist_ok=True)
56
56
  with lock_path.open("a+", encoding="utf-8") as lock_file:
57
57
  fcntl.flock(lock_file.fileno(), fcntl.LOCK_EX)
58
+ # The flock excludes live git writers; a leftover lock is from a kill.
59
+ with contextlib.suppress(OSError):
60
+ (repo_dir / "index.lock").unlink(missing_ok=True)
58
61
  held.add(lock_path)
59
62
  try:
60
63
  yield
@@ -493,3 +493,20 @@ def test_snapshot_tree_evicts_newly_ignored_files_from_index(
493
493
  t2 = snapshots.snapshot_tree(tasks_file, work)
494
494
  assert t2 is not None
495
495
  assert snapshots._tree_files(repo_dir, t2) == {".gitignore", "app.js"}
496
+
497
+
498
+ def test_snapshot_tree_recovers_from_stale_index_lock(tmp_path, monkeypatch):
499
+ monkeypatch.setenv("LEMMING_HOME", str(tmp_path / "home"))
500
+ work = tmp_path / "work"
501
+ work.mkdir()
502
+ tasks_file = work / "tasks.yml"
503
+ (work / "app.py").write_text("print('hi')\n", encoding="utf-8")
504
+ assert snapshots.snapshot_tree(tasks_file, work) is not None
505
+
506
+ # A git process killed mid-add (timeout, reboot) leaves its lock behind.
507
+ repo_dir = snapshots.get_snapshots_dir(tasks_file)
508
+ (repo_dir / "index.lock").write_text("", encoding="utf-8")
509
+ (work / "app.py").write_text("print('bye')\n", encoding="utf-8")
510
+
511
+ assert snapshots.snapshot_tree(tasks_file, work) is not None
512
+ assert not (repo_dir / "index.lock").exists()
@@ -154,7 +154,7 @@ wheels = [
154
154
 
155
155
  [[package]]
156
156
  name = "lemming-cli"
157
- version = "0.9.0"
157
+ version = "0.9.1"
158
158
  source = { editable = "." }
159
159
  dependencies = [
160
160
  { name = "click" },
@@ -1,120 +0,0 @@
1
- # Workspace Isolation 🧰
2
-
3
- ## Lemming is VCS-Agnostic
4
-
5
- An agent run writes to a real directory on your disk. The orchestrator never
6
- creates a branch, a commit, or a worktree, and never reverts anything: it runs
7
- the agent in a directory and gets out of the way, so whatever a run leaves
8
- behind — finished work, half-applied edits, scratch files — is what you get. The
9
- task-runner prompt does allow the agent itself to commit when that is the
10
- project's convention, but the orchestrator neither asks for that nor relies on
11
- it.
12
-
13
- This is deliberate: branching would tie the orchestrator to Git, and Lemming is
14
- expected to work in a Mercurial repository, a Perforce client, or a plain
15
- directory under no version control at all. No portable "undo the last run"
16
- primitive exists across those, so **isolation and recovery are the caller's
17
- job**. If you need to be able to throw a run away, set that up before it starts.
18
-
19
- ## Isolating a One-Off `exec` Run
20
-
21
- Concurrent writing runs must not share a checkout: two agents editing one
22
- directory interleave their edits, and neither result is reviewable. Give each
23
- writing run its own working copy and pass it with the global `-C` option
24
- (`lemming -C <working-copy> -v exec ...`). The full Git worktree recipe is under
25
- "Isolate concurrent writing runs" in [SKILL.md](../SKILL.md), summarized in the
26
- [README](../README.md#one-off-tasks-without-a-roadmap).
27
-
28
- ## Isolating a Roadmap Loop
29
-
30
- `lemming run` executes its tasks **sequentially in one shared workspace**. Task
31
- 2 starts in whatever state task 1 left behind — that is the point, since tasks
32
- build on each other. So the unit of isolation is the whole run: **one branch or
33
- worktree for the entire loop**, created once before `lemming run`.
34
-
35
- **Never one branch per task.** Whichever branch the last runner left checked out
36
- would silently become the next task's baseline, and the loop's history would
37
- fragment across branches nobody asked for. This is why the task-runner prompt
38
- says nothing about branching: a runner has no business changing what is checked
39
- out under it.
40
-
41
- The minimal Git shape, from a clean tree:
42
-
43
- ```bash
44
- repo=$(git rev-parse --show-toplevel) || exit 1
45
- test -z "$(git -C "$repo" status --porcelain)" || exit 1
46
-
47
- # One worktree for the whole run, from committed HEAD.
48
- worktree=$(mktemp -d "${TMPDIR:-/tmp}/lemming-run.XXXXXX") || exit 1
49
- branch="lemming/$(basename "$worktree")"
50
- git -C "$repo" worktree add -b "$branch" "$worktree" HEAD || exit 1
51
-
52
- # Drive the loop against it; -C is a global option, before the subcommand.
53
- lemming -C "$worktree" goal "<the long-term goal>"
54
- lemming -C "$worktree" add "<first task>"
55
- lemming -C "$worktree" -v run
56
- ```
57
-
58
- A plain branch (`git switch -c lemming/<run>`) does just as well when nothing
59
- else needs the checkout; the worktree only buys you the original directory to
60
- keep working in meanwhile. Either way the roadmap travels with the workspace: a
61
- tracked `tasks.yml` is copied into the worktree and the loop's edits stay there,
62
- and without one Lemming keeps isolated state keyed on the worktree path.
63
-
64
- ## Recovering After an Aborted Run
65
-
66
- With a pre-run baseline, recovery is ordinary version control, and `-C` reaches
67
- the run's own records without your having to know where they are stored:
68
-
69
- ```bash
70
- git -C "$worktree" status # what the run touched
71
- git -C "$worktree" log HEAD # commits, if the runners made any
72
- git -C "$worktree" diff # whatever is still uncommitted
73
-
74
- lemming -C "$worktree" status # queue, attempts, recorded progress
75
- lemming -C "$worktree" logs <id> # the full runner log for one task
76
- ```
77
-
78
- Keep the branch, or discard it wholesale. There is no partial rollback of one
79
- task inside a loop — the tasks share a workspace, so their edits are not
80
- separable unless the runners committed them separately.
81
-
82
- Runners are also told to write verbose evidence into Lemming's per-project
83
- scratch directory rather than into the workspace, so a failed task's notes
84
- survive even after you throw the branch away. It sits under `~/.local/lemming/`
85
- (or `$LEMMING_HOME`), named for the first 12 hex digits of the SHA-256 of the
86
- resolved tasks-file path — or of the workspace path, when Lemming is keeping the
87
- roadmap itself. Once the worktree is gone `-C` can no longer resolve it, and
88
- `lemming --tasks-file <that dir>/tasks.yml logs <id>` is the way back in.
89
-
90
- So retain the worktree until its changes have been recovered, then clean up
91
- non-forcibly, which refuses rather than destroying uncommitted work — including
92
- a tracked `tasks.yml` the loop has edited, which must be committed or discarded
93
- first:
94
-
95
- ```bash
96
- git -C "$repo" worktree remove "$worktree"
97
- git -C "$repo" branch -d "$branch"
98
- ```
99
-
100
- ## What the Runner Prompt Guarantees
101
-
102
- Runners are instructed to leave a coherent workspace, to back out their own
103
- half-applied edits before failing, and never to restore files from version
104
- control history; the rules live in the "Workspace Hygiene" directive of
105
- `src/lemming/prompts/taskrunner.md`, not in a copy here. Treat them as a strong
106
- prior, not a guarantee: runners are LLMs, a prompt is guidance rather than
107
- enforcement, and a run killed by a timeout never gets to clean up at all. The
108
- branch or worktree is what actually makes a bad run recoverable; the prompt only
109
- reduces how often you need it.
110
-
111
- ## Workspaces Not Under Version Control
112
-
113
- If the workspace is a plain directory, there is nothing to diff against and
114
- nothing to reset. **Copy the directory before the run**; that copy is the only
115
- rollback available.
116
-
117
- ```bash
118
- cp -a project project.bak
119
- lemming -C project run
120
- ```
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes