lemming-cli 0.10.0__tar.gz → 0.11.0__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.10.0 → lemming_cli-0.11.0}/PKG-INFO +29 -25
  2. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/README.md +28 -24
  3. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/SKILL.md +45 -15
  4. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/docs/HOOKS.md +22 -24
  5. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/pyproject.toml +1 -1
  6. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/hooks.py +6 -6
  7. lemming_cli-0.11.0/src/lemming/cli/progress.py +73 -0
  8. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/progress_test.py +36 -0
  9. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/tasks.py +32 -0
  10. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/tasks_test.py +33 -0
  11. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/hooks.py +1 -4
  12. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/models.py +1 -0
  13. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/orchestrator.py +22 -7
  14. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/orchestrator_test.py +141 -25
  15. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/prompts/hooks/90-roadmap.md +9 -6
  16. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/prompts/taskrunner.md +8 -2
  17. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/prompts.py +28 -7
  18. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/prompts_test.py +93 -3
  19. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/tasks/progress.py +2 -0
  20. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/tasks/progress_test.py +1 -0
  21. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/tasks/state_machine.py +17 -11
  22. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/web/index.html +1 -1
  23. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/uv.lock +1 -1
  24. lemming_cli-0.10.0/src/lemming/cli/progress.py +0 -47
  25. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/.dockerignore +0 -0
  26. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/.github/workflows/ci.yml +0 -0
  27. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/.github/workflows/publish.yml +0 -0
  28. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/.github/workflows/screenshots.yml +0 -0
  29. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/.gitignore +0 -0
  30. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/Dockerfile +0 -0
  31. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/LICENSE +0 -0
  32. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/biome.json +0 -0
  33. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/docker-compose.yml +0 -0
  34. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/docs/EVALS.md +0 -0
  35. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/docs/WORKSPACE.md +0 -0
  36. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/docs/screenshots/dashboard-desktop.png +0 -0
  37. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/docs/screenshots/dashboard-mobile.png +0 -0
  38. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/docs/screenshots/task-log-desktop.png +0 -0
  39. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/docs/screenshots/task-log-mobile.png +0 -0
  40. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/package-lock.json +0 -0
  41. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/package.json +0 -0
  42. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/playwright.config.js +0 -0
  43. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/__init__.py +0 -0
  44. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/__init__.py +0 -0
  45. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/auth.py +0 -0
  46. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/auth_test.py +0 -0
  47. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/config.py +0 -0
  48. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/config_test.py +0 -0
  49. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/conftest.py +0 -0
  50. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/context.py +0 -0
  51. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/context_test.py +0 -0
  52. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/directories.py +0 -0
  53. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/directories_test.py +0 -0
  54. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/files.py +0 -0
  55. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/files_test.py +0 -0
  56. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/hooks.py +0 -0
  57. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/hooks_test.py +0 -0
  58. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/logging.py +0 -0
  59. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/logging_test.py +0 -0
  60. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/loop.py +0 -0
  61. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/loop_test.py +0 -0
  62. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/main.py +0 -0
  63. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/main_test.py +0 -0
  64. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/tasks.py +0 -0
  65. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/api/tasks_test.py +0 -0
  66. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/artifact_test.py +0 -0
  67. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/brief_test.py +0 -0
  68. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/__init__.py +0 -0
  69. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/artifact.py +0 -0
  70. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/brief.py +0 -0
  71. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/config.py +0 -0
  72. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/config_test.py +0 -0
  73. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/exec_cli.py +0 -0
  74. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/exec_cli_test.py +0 -0
  75. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/goal.py +0 -0
  76. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/goal_test.py +0 -0
  77. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/hooks_test.py +0 -0
  78. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/machine_output_test.py +0 -0
  79. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/main.py +0 -0
  80. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/main_test.py +0 -0
  81. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/operations.py +0 -0
  82. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/operations_test.py +0 -0
  83. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/readability_cli.py +0 -0
  84. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/readability_cli_test.py +0 -0
  85. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/skill.py +0 -0
  86. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/skill_test.py +0 -0
  87. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/cli/stop_test.py +0 -0
  88. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/conftest.py +0 -0
  89. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/__init__.py +0 -0
  90. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/__main__.py +0 -0
  91. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/cli.py +0 -0
  92. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/cli_test.py +0 -0
  93. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/container.py +0 -0
  94. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/container_test.py +0 -0
  95. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/fixtures.py +0 -0
  96. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/fixtures_test.py +0 -0
  97. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/harness.py +0 -0
  98. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/harness_test.py +0 -0
  99. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/metrics.py +0 -0
  100. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/metrics_test.py +0 -0
  101. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/readability/base/README.md +0 -0
  102. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/readability/base/calc/__init__.py +0 -0
  103. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/readability/base/calc/legacy.py +0 -0
  104. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/readability/base/calc/ops.py +0 -0
  105. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/readability/base/calc/ops_test.py +0 -0
  106. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/readability/clean/calc/ops.py +0 -0
  107. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/readability/clean/calc/ops_test.py +0 -0
  108. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/readability/dead-code/calc/ops.py +0 -0
  109. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/readability/dead-code/calc/ops_test.py +0 -0
  110. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/readability/duplicated-behavior/calc/ops.py +0 -0
  111. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/readability/duplicated-behavior/calc/ops_test.py +0 -0
  112. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/readability/false-reuse/calc/limits.py +0 -0
  113. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/readability/false-reuse/calc/limits_test.py +0 -0
  114. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/readability/lint-debt/calc/ops.py +0 -0
  115. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/readability/lint-debt/calc/ops_test.py +0 -0
  116. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/roadmap/add-only/README.md +0 -0
  117. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/roadmap/add-only/calc/__init__.py +0 -0
  118. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/roadmap/add-only/calc/ops.py +0 -0
  119. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/roadmap/add-only/calc/ops_test.py +0 -0
  120. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/roadmap/buggy-subtract/README.md +0 -0
  121. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/roadmap/buggy-subtract/calc/__init__.py +0 -0
  122. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/roadmap/buggy-subtract/calc/ops.py +0 -0
  123. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/roadmap/buggy-subtract/calc/ops_test.py +0 -0
  124. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/roadmap/full-ops/README.md +0 -0
  125. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/roadmap/full-ops/calc/__init__.py +0 -0
  126. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/roadmap/full-ops/calc/ops.py +0 -0
  127. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/roadmap/full-ops/calc/ops_test.py +0 -0
  128. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/roadmap/unwired-cli/README.md +0 -0
  129. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/roadmap/unwired-cli/calc/__init__.py +0 -0
  130. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/roadmap/unwired-cli/calc/cli.py +0 -0
  131. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/roadmap/unwired-cli/calc/cli_test.py +0 -0
  132. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/roadmap/unwired-cli/calc/ops.py +0 -0
  133. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/roadmap/unwired-cli/calc/ops_test.py +0 -0
  134. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/task/hidden/stats/summary_hidden_test.py +0 -0
  135. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/task/summary/README.md +0 -0
  136. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/task/summary/stats/__init__.py +0 -0
  137. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/task/summary/stats/summary.py +0 -0
  138. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/projects/task/summary/stats/summary_test.py +0 -0
  139. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/readability.py +0 -0
  140. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/readability_test.py +0 -0
  141. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/report.py +0 -0
  142. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/report_test.py +0 -0
  143. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/roadmap.py +0 -0
  144. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/roadmap_test.py +0 -0
  145. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/scenarios.py +0 -0
  146. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/scenarios_test.py +0 -0
  147. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/suites.py +0 -0
  148. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/task.py +0 -0
  149. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/task_test.py +0 -0
  150. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/trial.py +0 -0
  151. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/evals/trial_test.py +0 -0
  152. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/hooks_test.py +0 -0
  153. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/integration_test.py +0 -0
  154. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/main.py +0 -0
  155. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/main_test.py +0 -0
  156. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/models_test.py +0 -0
  157. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/paths.py +0 -0
  158. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/paths_test.py +0 -0
  159. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/persistence.py +0 -0
  160. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/persistence_test.py +0 -0
  161. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/prompts/hooks/50-readability.md +0 -0
  162. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/prompts/hooks/60-testing.md +0 -0
  163. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/prompts/hooks/70-ux.md +0 -0
  164. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/providers.py +0 -0
  165. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/providers_test.py +0 -0
  166. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/runner.py +0 -0
  167. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/runner_test.py +0 -0
  168. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/scope.py +0 -0
  169. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/scope_test.py +0 -0
  170. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/shutdown.py +0 -0
  171. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/shutdown_integration_test.py +0 -0
  172. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/shutdown_test.py +0 -0
  173. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/snapshots.py +0 -0
  174. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/snapshots_test.py +0 -0
  175. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/tasks/__init__.py +0 -0
  176. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/tasks/lifecycle.py +0 -0
  177. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/tasks/lifecycle_test.py +0 -0
  178. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/tasks/limits.py +0 -0
  179. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/tasks/operations.py +0 -0
  180. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/tasks/operations_test.py +0 -0
  181. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/tasks/queries.py +0 -0
  182. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/tasks/queries_test.py +0 -0
  183. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/tasks/state_machine_test.py +0 -0
  184. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/web/dashboard.spec.js +0 -0
  185. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/web/dashboard.test.js +0 -0
  186. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/web/favicon.js +0 -0
  187. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/web/favicon.spec.js +0 -0
  188. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/web/files.html +0 -0
  189. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/web/files.spec.js +0 -0
  190. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/web/index.js +0 -0
  191. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/web/logs.html +0 -0
  192. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/web/logs.test.js +0 -0
  193. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/src/lemming/web/mancha.js +0 -0
  194. {lemming_cli-0.10.0 → lemming_cli-0.11.0}/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.10.0
3
+ Version: 0.11.0
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
@@ -65,10 +65,10 @@ Set the long-term goal and define the first tasks.
65
65
  # Set the long-term goal that every task works toward
66
66
  lemming goal "Build a habit-tracking web app with auth, offline support, and tests"
67
67
 
68
- # Add tasks to the queue
69
- lemming add "Initialize the project with Vite"
70
- lemming add "Create the Button component"
71
- lemming add "Implement the authentication flow"
68
+ # Add self-contained vertical slices to the queue
69
+ lemming add "Scaffold the Vite app, routing shell, and test setup"
70
+ lemming add "Add user sign-in and session persistence with auth tests"
71
+ lemming add "Add habit check-ins with offline IndexedDB sync and tests"
72
72
  ```
73
73
 
74
74
  The goal is the one piece of state every task sees, no matter how far into the
@@ -258,32 +258,35 @@ loops through each pending task:
258
258
  the discarded workspace diff as an `attempt-<N>.patch` artifact (a repeated
259
259
  number gets `-2`, `-3`, ... rather than overwriting), restores the working
260
260
  tree to the task's pre-run snapshot, and retries up to the configured limit
261
- with accumulated progress as context. On success, it moves to the next task.
262
- 5. **Orchestration**: After each task, Lemming can run one or more
263
- **Orchestrator Hooks** (like the built-in `roadmap` hook) to evaluate the
264
- results and adapt the roadmap if needed. Only `roadmap` runs by default;
265
- reviews are opt-in.
261
+ with accumulated progress as context. A timeout also keeps the tail of the
262
+ agent's output as `attempt-<N>-timeout.log`, so the retry starts from what
263
+ the killed attempt found. On success, it moves to the next task.
264
+ 5. **Orchestration**: Lemming runs enabled **Orchestrator Hooks** to review
265
+ completed work or recover from failures. Opt-in review hooks (`< 90`) run
266
+ after each completed task; failure hooks (`90+`, including the default
267
+ `roadmap` hook) run only when a task fails.
266
268
 
267
269
  ---
268
270
 
269
271
  ## Orchestrator Hooks ⚓️
270
272
 
271
273
  For longer, multi-stage projects, the initial task list often can't anticipate
272
- everything. Tasks may fail in ways that retrying won't fix, or completing all
273
- tasks may not fully achieve the stated goal. **Orchestrator Hooks** address this
274
- by running custom agents or scripts after each task execution to evaluate
275
- results and adapt the roadmap.
274
+ everything. Tasks may fail in ways that retrying won't fix, or completed changes
275
+ may benefit from an independent review pass. **Orchestrator Hooks** address this
276
+ by running custom agents or scripts to review completed work or repair the
277
+ roadmap on failure.
276
278
 
277
279
  Lemming runs the hooks enabled for the project, which by default is only the
278
280
  built-in `roadmap` hook; review hooks are opt-in. Hooks are plain Markdown
279
281
  files, and udev-style filename conventions control their behavior:
280
282
 
281
283
  - **Ordering**: A numeric prefix sets the execution order (e.g. `10-lint.md`
282
- runs before `90-roadmap.md`); files without a prefix default to priority 50.
283
- - **Failure hooks**: Hooks at priority 90 and above also run when a task fails;
284
- all others only run on success.
285
- - **Oneshot tasks**: A task added with `--oneshot` skips all hooks once it
286
- completes, so mechanical work (a typo fix, a version bump) does not pay for
284
+ runs before `50-readability.md`); files without a prefix default to priority 50.
285
+ - **Failure hooks**: Hooks at priority 90 and above (such as `90-roadmap.md`)
286
+ run only when a task fails; hooks below 90 are review hooks and run only on
287
+ success.
288
+ - **Oneshot tasks**: A task added with `--oneshot` skips all review hooks once
289
+ it completes, so mechanical work (a typo fix, a version bump) does not pay for
287
290
  the full review lifecycle. Failure hooks still run if it fails.
288
291
  - **Masking**: An empty file hides the hook of the same name from a
289
292
  lower-precedence layer, even where it is enabled.
@@ -300,10 +303,9 @@ lemming add "Redesign the settings page" --hooks ux,testing
300
303
 
301
304
  Lemming comes with several built-in hooks to help manage your project:
302
305
 
303
- - **`roadmap`**: The primary mechanism for autonomous project management. It
304
- analyzes the results of the finished task and decides if the remaining roadmap
305
- needs to be adjusted (e.g., adding a missing prerequisite, skipping obsolete
306
- tasks, or breaking down a broad task).
306
+ - **`roadmap`**: Failure-recovery orchestration. When a task exhausts retries or
307
+ fails, it diagnoses the failure and adapts the roadmap (e.g., rewriting the
308
+ approach, splitting into prerequisites, or superseding obsolete tasks).
307
309
  - **`readability`**: A code quality and simplification hook that challenges
308
310
  unnecessary complexity and duplicate implementations, then reviews changes for
309
311
  adherence to the Google Style Guide and general readability using the
@@ -397,6 +399,8 @@ These come before the subcommand and apply to all of them.
397
399
  `lemming run --detach` reclaims it. If its runner outlived the loop,
398
400
  `status` names the runner's pid to kill first, and `run` refuses to start a
399
401
  second runner until it is gone.
402
+ - A running task that has recorded no progress for a quarter of the time limit
403
+ is flagged as stale.
400
404
  - **`goal [<text>]`**: Set or view the long-term goal shared by all tasks.
401
405
  Supports `-f/--file`.
402
406
  - **`add <desc>`**: Append a new task. Supports `--index`, `--runner`,
@@ -430,8 +434,8 @@ These come before the subcommand and apply to all of them.
430
434
  model without touching the runner.
431
435
  - **`hooks`**: Manage orchestrator hooks.
432
436
  - `list`: View available hooks and the ones enabled for the project.
433
- - `enable <name>...`: Run one or more hooks after every task.
434
- - `disable <name>...`: Stop running one or more hooks by default.
437
+ - `enable <name>...`: Enable one or more hooks for the project.
438
+ - `disable <name>...`: Disable one or more hooks for the project.
435
439
  - **`readability`**: Code quality tool for style guide adherence, wrapping the
436
440
  [readability](https://github.com/owahltinez/readability) package. Ruff and
437
441
  Pyrefly run with bundled Google-style defaults unless the target project
@@ -45,10 +45,10 @@ Set the long-term goal and define the first tasks.
45
45
  # Set the long-term goal that every task works toward
46
46
  lemming goal "Build a habit-tracking web app with auth, offline support, and tests"
47
47
 
48
- # Add tasks to the queue
49
- lemming add "Initialize the project with Vite"
50
- lemming add "Create the Button component"
51
- lemming add "Implement the authentication flow"
48
+ # Add self-contained vertical slices to the queue
49
+ lemming add "Scaffold the Vite app, routing shell, and test setup"
50
+ lemming add "Add user sign-in and session persistence with auth tests"
51
+ lemming add "Add habit check-ins with offline IndexedDB sync and tests"
52
52
  ```
53
53
 
54
54
  The goal is the one piece of state every task sees, no matter how far into the
@@ -238,32 +238,35 @@ loops through each pending task:
238
238
  the discarded workspace diff as an `attempt-<N>.patch` artifact (a repeated
239
239
  number gets `-2`, `-3`, ... rather than overwriting), restores the working
240
240
  tree to the task's pre-run snapshot, and retries up to the configured limit
241
- with accumulated progress as context. On success, it moves to the next task.
242
- 5. **Orchestration**: After each task, Lemming can run one or more
243
- **Orchestrator Hooks** (like the built-in `roadmap` hook) to evaluate the
244
- results and adapt the roadmap if needed. Only `roadmap` runs by default;
245
- reviews are opt-in.
241
+ with accumulated progress as context. A timeout also keeps the tail of the
242
+ agent's output as `attempt-<N>-timeout.log`, so the retry starts from what
243
+ the killed attempt found. On success, it moves to the next task.
244
+ 5. **Orchestration**: Lemming runs enabled **Orchestrator Hooks** to review
245
+ completed work or recover from failures. Opt-in review hooks (`< 90`) run
246
+ after each completed task; failure hooks (`90+`, including the default
247
+ `roadmap` hook) run only when a task fails.
246
248
 
247
249
  ---
248
250
 
249
251
  ## Orchestrator Hooks ⚓️
250
252
 
251
253
  For longer, multi-stage projects, the initial task list often can't anticipate
252
- everything. Tasks may fail in ways that retrying won't fix, or completing all
253
- tasks may not fully achieve the stated goal. **Orchestrator Hooks** address this
254
- by running custom agents or scripts after each task execution to evaluate
255
- results and adapt the roadmap.
254
+ everything. Tasks may fail in ways that retrying won't fix, or completed changes
255
+ may benefit from an independent review pass. **Orchestrator Hooks** address this
256
+ by running custom agents or scripts to review completed work or repair the
257
+ roadmap on failure.
256
258
 
257
259
  Lemming runs the hooks enabled for the project, which by default is only the
258
260
  built-in `roadmap` hook; review hooks are opt-in. Hooks are plain Markdown
259
261
  files, and udev-style filename conventions control their behavior:
260
262
 
261
263
  - **Ordering**: A numeric prefix sets the execution order (e.g. `10-lint.md`
262
- runs before `90-roadmap.md`); files without a prefix default to priority 50.
263
- - **Failure hooks**: Hooks at priority 90 and above also run when a task fails;
264
- all others only run on success.
265
- - **Oneshot tasks**: A task added with `--oneshot` skips all hooks once it
266
- completes, so mechanical work (a typo fix, a version bump) does not pay for
264
+ runs before `50-readability.md`); files without a prefix default to priority 50.
265
+ - **Failure hooks**: Hooks at priority 90 and above (such as `90-roadmap.md`)
266
+ run only when a task fails; hooks below 90 are review hooks and run only on
267
+ success.
268
+ - **Oneshot tasks**: A task added with `--oneshot` skips all review hooks once
269
+ it completes, so mechanical work (a typo fix, a version bump) does not pay for
267
270
  the full review lifecycle. Failure hooks still run if it fails.
268
271
  - **Masking**: An empty file hides the hook of the same name from a
269
272
  lower-precedence layer, even where it is enabled.
@@ -280,10 +283,9 @@ lemming add "Redesign the settings page" --hooks ux,testing
280
283
 
281
284
  Lemming comes with several built-in hooks to help manage your project:
282
285
 
283
- - **`roadmap`**: The primary mechanism for autonomous project management. It
284
- analyzes the results of the finished task and decides if the remaining roadmap
285
- needs to be adjusted (e.g., adding a missing prerequisite, skipping obsolete
286
- tasks, or breaking down a broad task).
286
+ - **`roadmap`**: Failure-recovery orchestration. When a task exhausts retries or
287
+ fails, it diagnoses the failure and adapts the roadmap (e.g., rewriting the
288
+ approach, splitting into prerequisites, or superseding obsolete tasks).
287
289
  - **`readability`**: A code quality and simplification hook that challenges
288
290
  unnecessary complexity and duplicate implementations, then reviews changes for
289
291
  adherence to the Google Style Guide and general readability using the
@@ -377,6 +379,8 @@ These come before the subcommand and apply to all of them.
377
379
  `lemming run --detach` reclaims it. If its runner outlived the loop,
378
380
  `status` names the runner's pid to kill first, and `run` refuses to start a
379
381
  second runner until it is gone.
382
+ - A running task that has recorded no progress for a quarter of the time limit
383
+ is flagged as stale.
380
384
  - **`goal [<text>]`**: Set or view the long-term goal shared by all tasks.
381
385
  Supports `-f/--file`.
382
386
  - **`add <desc>`**: Append a new task. Supports `--index`, `--runner`,
@@ -410,8 +414,8 @@ These come before the subcommand and apply to all of them.
410
414
  model without touching the runner.
411
415
  - **`hooks`**: Manage orchestrator hooks.
412
416
  - `list`: View available hooks and the ones enabled for the project.
413
- - `enable <name>...`: Run one or more hooks after every task.
414
- - `disable <name>...`: Stop running one or more hooks by default.
417
+ - `enable <name>...`: Enable one or more hooks for the project.
418
+ - `disable <name>...`: Disable one or more hooks for the project.
415
419
  - **`readability`**: Code quality tool for style guide adherence, wrapping the
416
420
  [readability](https://github.com/owahltinez/readability) package. Ruff and
417
421
  Pyrefly run with bundled Google-style defaults unless the target project
@@ -19,6 +19,9 @@ One interface over several agent CLIs. You do not need to know how `agy`,
19
19
  Use `exec` for one unit of work, and a roadmap for anything larger than a single
20
20
  agent run can hold.
21
21
 
22
+ This guide is for `lemming` 0.11.0 or newer. If `lemming --version` is older,
23
+ run `uv tool upgrade lemming-cli` first; older versions lack flags used below.
24
+
22
25
  ## Delegate one task
23
26
 
24
27
  ```sh
@@ -152,14 +155,19 @@ copy and pass it with the global `-C` option, as in the example above.
152
155
  ## Drive a roadmap
153
156
 
154
157
  For work that outlasts one agent run — a migration, a multi-step feature — break
155
- it into tasks. Each runs with a fresh context seeded only by the goal and
156
- recorded progress, so the project survives context limits.
158
+ it into self-contained vertical slices that each fit comfortably in one run.
159
+ Bundle implementation, caller wiring, and warranted tests into one task rather
160
+ than splitting production code from tests or layers from callers; keep each
161
+ slice small enough to finish well within the time limit. Each task runs with a
162
+ fresh context seeded only by the goal and recorded progress, so the project
163
+ survives context limits.
157
164
 
158
165
  ```sh
159
166
  lemming goal "Add offline support with a service worker and a sync queue"
160
- lemming add "Register the service worker and cache the app shell"
161
- lemming add "Queue writes in IndexedDB while offline"
162
- lemming add "Bump the service worker cache version" --oneshot
167
+ lemming add "Ignore dist/ and coverage/ in .gitignore" --oneshot
168
+ lemming add "Add the service worker, register it on boot, and test shell caching"
169
+ lemming add "Queue offline writes in IndexedDB and replay on reconnect, with tests"
170
+ lemming add "Verify end-to-end offline caching and reconnect replay against every goal clause"
163
171
  lemming run --detach # runs until the queue drains
164
172
  lemming run --detach --until <task-id> # or stops once that task settles
165
173
  ```
@@ -171,11 +179,16 @@ without a `.gitignore`, create one (or queue it as the first `--oneshot` task)
171
179
  before tasks install dependencies or run builds so workspace snapshots skip
172
180
  `node_modules/`, `.venv/`, and build outputs.
173
181
 
174
- **Mark mechanical tasks `--oneshot`.** After every other task, a roadmap hook
175
- may revise the queue and any enabled reviews run; each hook is a full agent run,
176
- so a typo fix, rename, version bump, or cleanup without `--oneshot` takes
177
- several times longer than the work itself. Reviews are opt-in: pick them for one
178
- task with `lemming add ... --hooks testing,ux`, or for every task with
182
+ **End multi-task roadmaps with a verification task.** Because `roadmap` runs
183
+ only on failures, queue a final task that verifies every clause of the goal
184
+ end-to-end against the built workspace.
185
+
186
+ **Mark mechanical tasks `--oneshot`.** When review hooks are enabled, each hook
187
+ is a full agent run after every non-oneshot completion, so a typo fix, rename,
188
+ version bump, or cleanup without `--oneshot` takes several times longer than the
189
+ work itself. The default `roadmap` hook (`90+`) runs only on task failures;
190
+ reviews are opt-in: pick them for one task with
191
+ `lemming add ... --hooks testing,ux`, or for every task with
179
192
  `lemming hooks enable <name>`. `lemming hooks list` shows which are enabled.
180
193
 
181
194
  ### Supervise in milestones
@@ -221,16 +234,32 @@ lemming diff [<id>] --stat # diffstat for a task (or the full patch without --s
221
234
  lemming logs <id> | tail -n 30 # never the whole log
222
235
  ```
223
236
 
224
- A task is stuck when its run time approaches the limit with no new progress
225
- entries and the log tail shows the same step repeating. Otherwise leave it.
237
+ `status` marks a running task `Stale` once it has gone a quarter of the time
238
+ limit without a progress entry. A stale task whose log tail shows the same step
239
+ repeating is stuck. Otherwise leave it.
226
240
 
227
241
  Never hold a shell open on a foreground or backgrounded `lemming run`: the loop
228
242
  dies with the shell or harness that started it, leaving its task abandoned.
229
243
  `--detach` keeps it alive; if a loop died anyway, `lemming run --detach`
230
244
  reclaims the abandoned task. A detached loop hides a stuck task until it
231
- exhausts its retries, so schedule a wake-up near each task's time limit that
232
- runs the checks above; if the task is stuck, `lemming cancel <id>` and `add`
233
- smaller tasks in its place.
245
+ exhausts its retries, so wait on more than the queue. This waiter returns when
246
+ the overview changes (a task settles or turns stale, or the loop stops) or when
247
+ the timeout passes; set the timeout to the time limit from
248
+ `lemming config list`:
249
+
250
+ ```sh
251
+ before=$(lemming status --brief)
252
+ timeout 60m sh -c 'while [ "$(lemming status --brief)" = "$1" ]; do sleep 60; done' _ "$before"
253
+ ```
254
+
255
+ Fix a stuck task yourself; do not end your turn to ask the user:
256
+
257
+ - Amend it for the retry. `lemming brief <id>` and `lemming edit <id>` take
258
+ effect when the task's next attempt starts, so record what the last attempt
259
+ found and let the retry run. A timed-out attempt's output tail is kept as its
260
+ `attempt-N-timeout.log` artifact.
261
+ - Split it when it is too large: `lemming cancel <id>` and `add` smaller tasks
262
+ in its place. Cancelling one task does not stop the loop.
234
263
 
235
264
  Adjust the queue while it runs — new tasks are picked up automatically:
236
265
 
@@ -244,6 +273,7 @@ lemming stop --after-current-task # drain, then stop
244
273
  Your own words fill context faster than any tool. Whether reporting to a user or
245
274
  to a parent agent:
246
275
 
276
+ - Report once, when the milestone settles, not at every check-in.
247
277
  - Report one milestone in this shape and no other: outcome (`done`, `failed`,
248
278
  `blocked`), task IDs that settled, files changed, one line of guidance for the
249
279
  next milestone. Skip anything that can be re-read from `lemming status`.
@@ -1,8 +1,8 @@
1
1
  # Orchestrator Hooks ⚓️
2
2
 
3
3
  Orchestrator hooks are a powerful way to extend the Lemming workflow. They allow
4
- you to execute custom agents or scripts after each task, enabling automated
5
- roadmap revision, code quality checks, or any other post-task validation.
4
+ you to execute custom agents or scripts after task execution, enabling automated
5
+ failure recovery, code quality checks, or any other post-task validation.
6
6
 
7
7
  ## How it Works
8
8
 
@@ -31,14 +31,12 @@ conventions control their behavior:
31
31
  before `90-roadmap.md`. Files without a prefix default to priority 50. The
32
32
  prefix is **not** part of the hook's name: `90-roadmap.md` defines the hook
33
33
  `roadmap`.
34
- - **Failure hooks**: Hooks at priority 90 and above also run when a task fails.
35
- All other hooks only run after successful tasks. The built-in `roadmap` hook
36
- ships as `90-roadmap.md` so it can react to failures.
37
- - **Oneshot tasks**: No hook runs after a task marked `--oneshot` completes,
38
- keeping mechanical changes cheap. A oneshot task that fails still gets its
39
- failure hooks, so recovery is never skipped. Note that `roadmap` is skipped
40
- too: if a oneshot task is the last one in the queue, the run ends without a
41
- goal audit, so nothing is queued to carry the goal further.
34
+ - **Failure hooks**: Hooks at priority 90 and above (such as `90-roadmap.md`)
35
+ run only when a task fails. Hooks below priority 90 are review hooks and run
36
+ only after successful non-oneshot tasks.
37
+ - **Oneshot tasks**: No review hook runs after a task marked `--oneshot`
38
+ completes, keeping mechanical changes cheap. A oneshot task that fails still
39
+ gets its failure hooks, so recovery is never skipped.
42
40
  - **Masking**: An empty file hides the hook of the same name from a
43
41
  lower-precedence layer (see below), even where a project or task enables it.
44
42
  For example, an empty `.lemming/hooks/readability.md` hides the built-in
@@ -55,10 +53,10 @@ Only `roadmap` runs by default; the review hooks are opt-in per project or task
55
53
 
56
54
  ### `roadmap` (Default)
57
55
 
58
- The primary mechanism for autonomous project management. It analyzes the results
59
- of the finished task and decides if the remaining roadmap needs to be adjusted
60
- (e.g., adding a missing prerequisite, skipping obsolete tasks, or breaking down
61
- a broad task).
56
+ The built-in failure-recovery hook (`90-roadmap.md`). When a task fails or
57
+ exhausts retries, it diagnoses the failure and adapts the roadmap (e.g.,
58
+ rewriting the approach, splitting into smaller prerequisites, or superseding
59
+ obsolete tasks).
62
60
 
63
61
  ### `readability`
64
62
 
@@ -72,8 +70,8 @@ fixes in the working directory and records broader findings as task progress.
72
70
 
73
71
  Checks that changed behavior has focused test coverage and runs the relevant
74
72
  tests. It may repair small, targeted problems in production code or tests and
75
- may add, merge, or remove tests. It records larger testing gaps as task progress
76
- for the roadmap hook.
73
+ may add, merge, or remove tests. It records larger testing gaps as task
74
+ progress.
77
75
 
78
76
  ### `ux`
79
77
 
@@ -81,7 +79,7 @@ A lightweight journey-continuity review for user-visible changes. It considers
81
79
  at most one affected critical journey, reports only concrete and reproducible
82
80
  gaps, and exits immediately when the task did not change user-facing behavior.
83
81
  Its prompt instructs the agent to stay advisory, but this is not
84
- sandbox-enforced. It runs after `testing` and before `roadmap`.
82
+ sandbox-enforced. It runs after `testing`.
85
83
 
86
84
  ### Rejecting Completion
87
85
 
@@ -93,13 +91,13 @@ lemming --tasks-file <path> reject <taskid> '<reason>'
93
91
  ```
94
92
 
95
93
  A rejection only applies to a task that is finalizing as completed, and it does
96
- not change the task's status on the spot. The remaining hooks still run and see
97
- the task as `REJECTED` with the reason, so the roadmap hook can tell a rejected
98
- task from a finished one. Once every hook has run, Lemming saves the rejected
99
- attempt's diff as an `attempt-<N>.patch` artifact, restores the workspace to the
100
- task's `pre_tree`, and reverts the task to pending with its attempt count intact
101
- — just as it does when a hook process fails. The rejection reason stays in
102
- `progress` so the next attempt starts with the diagnosis.
94
+ not change the task's status on the spot. Any remaining review hooks (below
95
+ priority 90) still run and see the task as `REJECTED` with the reason, while
96
+ `90+` failure hooks do not run on completions. Once the hooks finish, Lemming
97
+ saves the rejected attempt's diff as an `attempt-<N>.patch` artifact, restores
98
+ the workspace to the task's `pre_tree`, and reverts the task to pending with its
99
+ attempt count intact — just as it does when a hook process fails. The rejection
100
+ reason stays in `progress` so the next attempt starts with the diagnosis.
103
101
 
104
102
  Each hook that runs is also bracketed by its own shadow Git snapshot pair in
105
103
  `hook_trees`. If an individual hook process crashes or exits non-zero, its own
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
4
4
 
5
5
  [project]
6
6
  name = "lemming-cli"
7
- version = "0.10.0"
7
+ version = "0.11.0"
8
8
  description = "An autonomous, iterative task runner for AI coding agents."
9
9
  readme = "README.md"
10
10
  authors = [
@@ -13,13 +13,13 @@ def hooks_group():
13
13
  Hooks are Markdown prompt files discovered from the project
14
14
  (.lemming/hooks/), global (~/.local/lemming/hooks/), and built-in
15
15
  layers, with the project layer taking precedence. A numeric filename
16
- prefix (e.g. 90-roadmap.md) sets the execution order; hooks at 90 and
17
- above also run when a task fails. An empty file masks the hook of the
18
- same name.
16
+ prefix (e.g. 90-roadmap.md) sets the execution order. Hooks below 90
17
+ review completed tasks; hooks at 90 and above run only when a task
18
+ fails. An empty file masks the hook of the same name.
19
19
 
20
- Only the hooks enabled for the project run after each task; by default
21
- that is just roadmap. A task can pick its own reviews with
22
- 'add --hooks' or 'edit --hooks'.
20
+ Only the hooks enabled for the project run by default (initially just
21
+ roadmap). A task can pick its own reviews with 'add --hooks' or
22
+ 'edit --hooks'.
23
23
  """
24
24
  pass
25
25
 
@@ -0,0 +1,73 @@
1
+ """CLI command for recording task progress entries."""
2
+
3
+ import time
4
+ import typing
5
+
6
+ import click
7
+
8
+ from .. import models, orchestrator, persistence
9
+ from ..tasks import progress as task_progress
10
+ from .main import TEXT_FILE, cli
11
+
12
+
13
+ def _format_budget_suffix(task: models.Task, time_limit: int) -> str:
14
+ """Formats elapsed and remaining time for an active bounded execution."""
15
+ component = task.active_execution_component
16
+ started_at = task.active_execution_started_at
17
+ if time_limit <= 0 or not component or started_at is None:
18
+ return ""
19
+ if component == "runner":
20
+ limit_min = time_limit
21
+ elif component.startswith("hook:"):
22
+ limit_min = min(time_limit, orchestrator.HOOK_TIME_LIMIT)
23
+ else:
24
+ return ""
25
+
26
+ elapsed_s = max(0, int(time.time() - started_at))
27
+ elapsed = "<1m" if elapsed_s < 60 else f"{elapsed_s // 60}m"
28
+ remaining_s = limit_min * 60 - elapsed_s
29
+ if remaining_s <= 0:
30
+ return f" ({elapsed}/{limit_min}m elapsed, time limit reached)"
31
+ remaining = "<1m" if remaining_s < 60 else f"{remaining_s // 60}m"
32
+ return f" ({elapsed}/{limit_min}m elapsed, {remaining} remaining)"
33
+
34
+
35
+ @cli.command(short_help="<taskid> [text] Add a progress entry")
36
+ @click.argument("task_id")
37
+ @click.argument("text", required=False)
38
+ @click.option(
39
+ "--file",
40
+ "-f",
41
+ type=TEXT_FILE,
42
+ help="Read progress text from a file (or - for stdin).",
43
+ )
44
+ @click.pass_context
45
+ def progress(
46
+ ctx: click.Context,
47
+ task_id: str,
48
+ text: str | None,
49
+ file: typing.TextIO | None,
50
+ ):
51
+ """Records a progress entry or finding for a specific task."""
52
+ tasks_file = ctx.obj["TASKS_FILE"]
53
+
54
+ if file:
55
+ if text:
56
+ click.echo("Error: Cannot provide both progress text and --file.")
57
+ ctx.exit(1)
58
+ text = file.read().strip()
59
+ elif text:
60
+ text = text.strip()
61
+
62
+ if not text:
63
+ click.echo("Error: Must provide either progress text or --file.")
64
+ ctx.exit(1)
65
+
66
+ try:
67
+ target_task = task_progress.add_progress(tasks_file, task_id, text)
68
+ time_limit = persistence.load_tasks(tasks_file).config.time_limit
69
+ suffix = _format_budget_suffix(target_task, time_limit)
70
+ click.echo(f"Progress added to task {target_task.id}{suffix}.")
71
+ except ValueError as e:
72
+ click.echo(f"Error: {e}")
73
+ ctx.exit(1)
@@ -1,3 +1,5 @@
1
+ import time
2
+
1
3
  import pytest
2
4
  from click.testing import CliRunner
3
5
 
@@ -59,3 +61,37 @@ def test_progress_reports_actionable_size_error(setup_env):
59
61
  assert "lemming artifact <id> <name> --file -" in result.output
60
62
  assert str(tasks_file.parent) not in result.output
61
63
  assert persistence.load_tasks(tasks_file).tasks[0].progress == []
64
+
65
+
66
+ @pytest.mark.parametrize(
67
+ ("component", "time_limit", "elapsed_s", "expected"),
68
+ [
69
+ ("runner", 30, 20, "(<1m/30m elapsed, 29m remaining)."),
70
+ ("runner", 30, 22 * 60, "(22m/30m elapsed, 8m remaining)."),
71
+ ("runner", 30, 29 * 60 + 30, "(29m/30m elapsed, <1m remaining)."),
72
+ ("runner", 30, 31 * 60, "(31m/30m elapsed, time limit reached)."),
73
+ ("hook:testing", 60, 5 * 60, "(5m/15m elapsed, 10m remaining)."),
74
+ ("hook:testing", 10, 5 * 60, "(5m/10m elapsed, 5m remaining)."),
75
+ ("runner", 0, 10 * 60, "Progress added to task 12345678."),
76
+ ],
77
+ )
78
+ def test_progress_reports_elapsed_time_budget(
79
+ setup_env, monkeypatch, component, time_limit, elapsed_s, expected
80
+ ):
81
+ runner, base_args, tasks_file = setup_env
82
+ now = 1_700_000_000.0
83
+ monkeypatch.setattr(time, "time", lambda: now)
84
+
85
+ data = persistence.load_tasks(tasks_file)
86
+ data.config.time_limit = time_limit
87
+ data.tasks[0].status = models.TaskStatus.RUNNING
88
+ data.tasks[0].active_execution_component = component
89
+ data.tasks[0].active_execution_started_at = now - elapsed_s
90
+ persistence.save_tasks(tasks_file, data)
91
+
92
+ result = runner.invoke(
93
+ cli.cli, base_args + ["progress", "12345678", "checkpoint"]
94
+ )
95
+
96
+ assert result.exit_code == 0
97
+ assert result.output.strip().endswith(expected)
@@ -411,6 +411,32 @@ def _abandoned_hint(task: models.Task, loop_running: bool) -> str | None:
411
411
  return "`lemming run --detach` reclaims it"
412
412
 
413
413
 
414
+ def _stale_hint(task: models.Task, time_limit: int) -> str | None:
415
+ """Returns how long a running task has gone without recording progress.
416
+
417
+ Runners are told to record progress often, so a quarter of the time
418
+ limit without an entry suggests the attempt is spinning.
419
+
420
+ Args:
421
+ task: The task to check.
422
+ time_limit: The roadmap's time limit in minutes; 0 means none.
423
+
424
+ Returns:
425
+ A description of the silence, or None if the task is not stale.
426
+ """
427
+ if (
428
+ task.status != models.TaskStatus.RUNNING
429
+ or not task.last_started_at
430
+ or time_limit <= 0
431
+ ):
432
+ return None
433
+ since = max(task.last_started_at, task.last_progress_at or 0)
434
+ if time.time() - since < time_limit * 60 / 4:
435
+ return None
436
+ # Fixed text, so the overview only changes when the task turns stale.
437
+ return f"no progress in the last {time_limit / 4:g}m"
438
+
439
+
414
440
  def _task_payload(task: models.Task, brief: bool) -> dict:
415
441
  """Serialises a task for machine consumption.
416
442
 
@@ -509,8 +535,11 @@ def status(ctx: click.Context, task_id: str | None, as_json: bool, brief: bool):
509
535
  for task in queue:
510
536
  _echo_task_summary(task, project_data.tasks, brief)
511
537
  hint = _abandoned_hint(task, project_data.loop_running)
538
+ stale = _stale_hint(task, project_data.config.time_limit)
512
539
  if hint:
513
540
  click.echo(f" Abandoned: {hint}.")
541
+ elif stale:
542
+ click.echo(f" Stale: {stale}.")
514
543
  else:
515
544
  click.echo("No active tasks.")
516
545
 
@@ -565,8 +594,11 @@ def status(ctx: click.Context, task_id: str | None, as_json: bool, brief: bool):
565
594
  click.secho(f"Task ID: {target.id}", bold=True)
566
595
  status_str = str(target.status)
567
596
  hint = _abandoned_hint(target, project_data.loop_running)
597
+ stale = _stale_hint(target, project_data.config.time_limit)
568
598
  if hint:
569
599
  status_str += f" (abandoned; {hint})"
600
+ elif stale:
601
+ status_str += f" (stale; {stale})"
570
602
  click.echo(f"Status: {status_str}")
571
603
  click.echo(f"Description: {target.description}")
572
604
  if target.parent: