devstuff 2.11.0__tar.gz → 2.13.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 (223) hide show
  1. {devstuff-2.11.0 → devstuff-2.13.0}/CHANGELOG.md +20 -0
  2. {devstuff-2.11.0 → devstuff-2.13.0}/CLAUDE.md +71 -1
  3. {devstuff-2.11.0 → devstuff-2.13.0}/PKG-INFO +168 -1
  4. {devstuff-2.11.0 → devstuff-2.13.0}/README.md +167 -0
  5. {devstuff-2.11.0 → devstuff-2.13.0}/dev/Makefile +9 -1
  6. {devstuff-2.11.0 → devstuff-2.13.0}/docs/ROADMAP.md +40 -25
  7. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/README.md +2 -0
  8. devstuff-2.13.0/docs/specs/profile/development-plan.md +127 -0
  9. devstuff-2.13.0/docs/specs/profile/specifications.md +211 -0
  10. devstuff-2.13.0/docs/specs/profile/stack-decisions.md +134 -0
  11. devstuff-2.13.0/docs/specs/profile-apply/development-plan.md +92 -0
  12. devstuff-2.13.0/docs/specs/profile-apply/specifications.md +206 -0
  13. devstuff-2.13.0/docs/specs/profile-apply/stack-decisions.md +134 -0
  14. {devstuff-2.11.0 → devstuff-2.13.0}/pyproject.toml +1 -1
  15. devstuff-2.13.0/src/dev_setup/apply_exec.py +156 -0
  16. devstuff-2.13.0/src/dev_setup/apply_plan.py +218 -0
  17. devstuff-2.13.0/src/dev_setup/bundles/ai-agents.yaml +10 -0
  18. devstuff-2.13.0/src/dev_setup/bundles/ai-local.yaml +10 -0
  19. devstuff-2.13.0/src/dev_setup/bundles/devops.yaml +12 -0
  20. devstuff-2.13.0/src/dev_setup/bundles/essentials.yaml +14 -0
  21. devstuff-2.13.0/src/dev_setup/bundles/languages.yaml +11 -0
  22. devstuff-2.13.0/src/dev_setup/bundles/python.yaml +10 -0
  23. devstuff-2.13.0/src/dev_setup/bundles.py +62 -0
  24. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/cli.py +2 -0
  25. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/commands/help_cmd.py +1 -0
  26. devstuff-2.13.0/src/dev_setup/commands/profile_cmd.py +458 -0
  27. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/generic.py +97 -8
  28. devstuff-2.13.0/src/dev_setup/profile.py +353 -0
  29. devstuff-2.13.0/src/dev_setup/snapshot.py +131 -0
  30. devstuff-2.13.0/tests/integration/test_profile_apply.py +111 -0
  31. devstuff-2.13.0/tests/test_apply_exec.py +243 -0
  32. devstuff-2.13.0/tests/test_apply_plan.py +386 -0
  33. devstuff-2.13.0/tests/test_apply_run.py +339 -0
  34. devstuff-2.13.0/tests/test_bundles.py +194 -0
  35. devstuff-2.13.0/tests/test_installed_version.py +213 -0
  36. devstuff-2.13.0/tests/test_pin_support.py +120 -0
  37. devstuff-2.13.0/tests/test_profile.py +340 -0
  38. devstuff-2.13.0/tests/test_profile_apply_cmd.py +646 -0
  39. devstuff-2.13.0/tests/test_profile_diff.py +333 -0
  40. devstuff-2.13.0/tests/test_profile_diff_cmd.py +521 -0
  41. devstuff-2.13.0/tests/test_profile_snapshot_cmd.py +294 -0
  42. devstuff-2.13.0/tests/test_snapshot.py +188 -0
  43. devstuff-2.13.0/tests/test_update_checker_parity.py +120 -0
  44. {devstuff-2.11.0 → devstuff-2.13.0}/uv.lock +1 -1
  45. {devstuff-2.11.0 → devstuff-2.13.0}/.claude/skills/run-stuff/SKILL.md +0 -0
  46. {devstuff-2.11.0 → devstuff-2.13.0}/.claude/skills/run-stuff/smoke.sh +0 -0
  47. {devstuff-2.11.0 → devstuff-2.13.0}/.github/codex/review.md +0 -0
  48. {devstuff-2.11.0 → devstuff-2.13.0}/.github/workflows/agent.yml +0 -0
  49. {devstuff-2.11.0 → devstuff-2.13.0}/.github/workflows/bump.yml +0 -0
  50. {devstuff-2.11.0 → devstuff-2.13.0}/.github/workflows/ci.yml +0 -0
  51. {devstuff-2.11.0 → devstuff-2.13.0}/.github/workflows/publish.yml +0 -0
  52. {devstuff-2.11.0 → devstuff-2.13.0}/.github/workflows/test-installs.yml +0 -0
  53. {devstuff-2.11.0 → devstuff-2.13.0}/.gitignore +0 -0
  54. {devstuff-2.11.0 → devstuff-2.13.0}/dev/Dockerfile +0 -0
  55. {devstuff-2.11.0 → devstuff-2.13.0}/dev/Dockerfile.ci +0 -0
  56. {devstuff-2.11.0 → devstuff-2.13.0}/dev/docker-compose.yml +0 -0
  57. {devstuff-2.11.0 → devstuff-2.13.0}/devstuff +0 -0
  58. {devstuff-2.11.0 → devstuff-2.13.0}/docs/github-agent.md +0 -0
  59. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/agent/development-plan.md +0 -0
  60. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/agent/specifications.md +0 -0
  61. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/agent/stack-decisions.md +0 -0
  62. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/ansible-config/development-plan.md +0 -0
  63. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/ansible-config/specifications.md +0 -0
  64. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/ansible-config/stack-decisions.md +0 -0
  65. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/bat-config/development-plan.md +0 -0
  66. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/bat-config/specifications.md +0 -0
  67. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/bat-config/stack-decisions.md +0 -0
  68. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/commitizen-config/development-plan.md +0 -0
  69. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/commitizen-config/specifications.md +0 -0
  70. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/commitizen-config/stack-decisions.md +0 -0
  71. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/docker-config/development-plan.md +0 -0
  72. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/docker-config/specifications.md +0 -0
  73. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/docker-config/stack-decisions.md +0 -0
  74. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/lazygit-config/development-plan.md +0 -0
  75. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/lazygit-config/specifications.md +0 -0
  76. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/lazygit-config/stack-decisions.md +0 -0
  77. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/outdated/development-plan.md +0 -0
  78. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/outdated/specifications.md +0 -0
  79. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/outdated/stack-decisions.md +0 -0
  80. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/precommit-config/development-plan.md +0 -0
  81. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/precommit-config/specifications.md +0 -0
  82. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/precommit-config/stack-decisions.md +0 -0
  83. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/starship-config/development-plan.md +0 -0
  84. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/starship-config/specifications.md +0 -0
  85. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/starship-config/stack-decisions.md +0 -0
  86. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/uv-backbone/development-plan.md +0 -0
  87. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/uv-backbone/specifications.md +0 -0
  88. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/uv-backbone/stack-decisions.md +0 -0
  89. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/verbose-mode/development-plan.md +0 -0
  90. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/verbose-mode/specifications.md +0 -0
  91. {devstuff-2.11.0 → devstuff-2.13.0}/docs/specs/verbose-mode/stack-decisions.md +0 -0
  92. {devstuff-2.11.0 → devstuff-2.13.0}/install.sh +0 -0
  93. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/__init__.py +0 -0
  94. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/__main__.py +0 -0
  95. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/agent/__init__.py +0 -0
  96. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/agent/approval.py +0 -0
  97. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/agent/bridges.py +0 -0
  98. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/agent/catalog.py +0 -0
  99. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/agent/completion.py +0 -0
  100. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/agent/config.py +0 -0
  101. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/agent/loop.py +0 -0
  102. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/agent/ollama.py +0 -0
  103. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/agent/preflight.py +0 -0
  104. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/agent/primitives.py +0 -0
  105. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/agent/registry.py +0 -0
  106. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/agent/sandbox.py +0 -0
  107. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/agent/session.py +0 -0
  108. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/agent/transcript.py +0 -0
  109. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/agent/wizard.py +0 -0
  110. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/agent_tools.schema.json +0 -0
  111. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/agent_tools.yaml +0 -0
  112. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/base.py +0 -0
  113. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/catalog.py +0 -0
  114. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/commands/__init__.py +0 -0
  115. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/commands/add_cmd.py +0 -0
  116. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/commands/agent_cmd.py +0 -0
  117. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/commands/catalog_cmd.py +0 -0
  118. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/commands/configure_cmd.py +0 -0
  119. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/commands/delete_cmd.py +0 -0
  120. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/commands/docs_cmd.py +0 -0
  121. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/commands/doctor_cmd.py +0 -0
  122. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/commands/functions_cmd.py +0 -0
  123. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/commands/install_cmd.py +0 -0
  124. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/commands/links_cmd.py +0 -0
  125. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/commands/list_cmd.py +0 -0
  126. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/commands/outdated_cmd.py +0 -0
  127. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/commands/remove_cmd.py +0 -0
  128. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/commands/run_cmd.py +0 -0
  129. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/commands/skills_cmd.py +0 -0
  130. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/commands/update_cmd.py +0 -0
  131. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/__init__.py +0 -0
  132. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/ansible/__init__.py +0 -0
  133. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/ansible/detect.py +0 -0
  134. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/ansible/model.py +0 -0
  135. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/ansible/render.py +0 -0
  136. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/ansible/validate.py +0 -0
  137. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/ansible/wizard.py +0 -0
  138. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/bat/__init__.py +0 -0
  139. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/bat/detect.py +0 -0
  140. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/bat/model.py +0 -0
  141. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/bat/preview.py +0 -0
  142. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/bat/render.py +0 -0
  143. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/bat/wizard.py +0 -0
  144. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/commitizen/__init__.py +0 -0
  145. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/commitizen/detect.py +0 -0
  146. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/commitizen/model.py +0 -0
  147. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/commitizen/render.py +0 -0
  148. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/commitizen/validate.py +0 -0
  149. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/commitizen/wizard.py +0 -0
  150. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/docker/__init__.py +0 -0
  151. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/docker/detect.py +0 -0
  152. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/docker/model.py +0 -0
  153. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/docker/render.py +0 -0
  154. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/docker/validate.py +0 -0
  155. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/docker/wizard.py +0 -0
  156. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/lazygit/__init__.py +0 -0
  157. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/lazygit/detect.py +0 -0
  158. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/lazygit/model.py +0 -0
  159. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/lazygit/render.py +0 -0
  160. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/lazygit/validate.py +0 -0
  161. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/lazygit/wizard.py +0 -0
  162. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/precommit/__init__.py +0 -0
  163. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/precommit/detect.py +0 -0
  164. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/precommit/model.py +0 -0
  165. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/precommit/render.py +0 -0
  166. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/precommit/validate.py +0 -0
  167. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/precommit/wizard.py +0 -0
  168. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/reptyr/__init__.py +0 -0
  169. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/reptyr/wizard.py +0 -0
  170. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/starship/__init__.py +0 -0
  171. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/starship/fonts.py +0 -0
  172. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/starship/icons.py +0 -0
  173. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/starship/model.py +0 -0
  174. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/starship/preview.py +0 -0
  175. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/starship/render.py +0 -0
  176. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/configure/starship/wizard.py +0 -0
  177. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/doctor.py +0 -0
  178. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/function_runner.py +0 -0
  179. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/functions.schema.json +0 -0
  180. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/functions.yaml +0 -0
  181. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/functions_catalog.py +0 -0
  182. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/functions_registry.py +0 -0
  183. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/links.schema.json +0 -0
  184. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/links.yaml +0 -0
  185. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/links_catalog.py +0 -0
  186. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/links_registry.py +0 -0
  187. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/registry.py +0 -0
  188. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/tools.yaml +0 -0
  189. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/ui.py +0 -0
  190. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/updates.py +0 -0
  191. {devstuff-2.11.0 → devstuff-2.13.0}/src/dev_setup/verbose.py +0 -0
  192. {devstuff-2.11.0 → devstuff-2.13.0}/tests/__init__.py +0 -0
  193. {devstuff-2.11.0 → devstuff-2.13.0}/tests/integration/__init__.py +0 -0
  194. {devstuff-2.11.0 → devstuff-2.13.0}/tests/integration/conftest.py +0 -0
  195. {devstuff-2.11.0 → devstuff-2.13.0}/tests/integration/test_agent_smoke.py +0 -0
  196. {devstuff-2.11.0 → devstuff-2.13.0}/tests/integration/test_agent_tui.py +0 -0
  197. {devstuff-2.11.0 → devstuff-2.13.0}/tests/integration/test_commitizen_config.py +0 -0
  198. {devstuff-2.11.0 → devstuff-2.13.0}/tests/integration/test_tools.py +0 -0
  199. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_agent.py +0 -0
  200. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_agent_completion.py +0 -0
  201. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_agent_loop.py +0 -0
  202. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_agent_sandbox.py +0 -0
  203. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_agent_tools.py +0 -0
  204. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_agent_wizard.py +0 -0
  205. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_catalog.py +0 -0
  206. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_configure_ansible.py +0 -0
  207. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_configure_bat.py +0 -0
  208. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_configure_commitizen.py +0 -0
  209. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_configure_docker.py +0 -0
  210. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_configure_lazygit.py +0 -0
  211. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_configure_precommit.py +0 -0
  212. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_configure_reptyr.py +0 -0
  213. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_configure_starship.py +0 -0
  214. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_doctor.py +0 -0
  215. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_functions.py +0 -0
  216. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_generic.py +0 -0
  217. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_links.py +0 -0
  218. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_outdated_cmd.py +0 -0
  219. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_registry.py +0 -0
  220. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_update_notes.py +0 -0
  221. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_updates.py +0 -0
  222. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_uv_probes.py +0 -0
  223. {devstuff-2.11.0 → devstuff-2.13.0}/tests/test_verbose.py +0 -0
@@ -1,3 +1,23 @@
1
+ ## v2.13.0 (2026-10-11)
2
+
3
+ ### Features
4
+
5
+ - **profile**: add bundled profiles, `@name`, to apply and diff
6
+ - **profile**: add `devstuff profile apply`
7
+ - **profile**: add the apply executor
8
+ - **profile**: add the apply step runner and forget_probes
9
+ - **profile**: add the apply planner
10
+
11
+ ## v2.12.0 (2026-10-10)
12
+
13
+ ### Features
14
+
15
+ - **profile**: add `devstuff profile diff`
16
+ - **profile**: add the diff classifier
17
+ - **profile**: add `devstuff profile snapshot`
18
+ - **generic**: add installed_version() and supports_pin() for profiles
19
+ - **profile**: add the profile file model, strict loader and dumper
20
+
1
21
  ## v2.11.0 (2026-10-10)
2
22
 
3
23
  ### Features
@@ -65,8 +65,13 @@ src/dev_setup/
65
65
  ├── ui.py # Rich console + questionary wrappers (spinners, prompts, styled output)
66
66
  ├── verbose.py # Process-wide -v/-vv level + the stderr logger built on it
67
67
  ├── updates.py # Update probing + the five-state classifier, shared by `update` and `outdated`
68
+ ├── profile.py # Profile file format (strict load, deterministic dump) + the seven-state diff classifier — pure
69
+ ├── snapshot.py # Asks the machine: builds a Profile / the facts `profile.compare` needs
70
+ ├── apply_plan.py # `profile apply`'s planner: diff rows -> ordered steps + skips. Pure, no I/O
71
+ ├── apply_exec.py # `profile apply`'s step runner and serial executor (failure policy, Ctrl-C)
72
+ ├── bundles.py # `@name` profiles shipped in the package (bundles/*.yaml), looked up by name
68
73
  ├── configure/ # Per-tool setup wizards (see "Configurators" below)
69
- └── commands/ # One Click command per file: list, install, remove, update, outdated, add, delete, docs, catalog
74
+ └── commands/ # One Click command per file: list, install, remove, update, outdated, profile, add, delete, docs, catalog
70
75
  ```
71
76
 
72
77
  **Catalog precedence** (`catalog.load_effective_catalog`): bundled `tools.yaml` loads first →
@@ -155,6 +160,71 @@ and `devstuff outdated` share one collector and one classifier. Things that are
155
160
  - **Exit status is "did the lookup run", not the answer** (the same rule as `run_cmd`), and `--json`
156
161
  writes only the array to stdout, even at `-vv`.
157
162
 
163
+ **Profiles** (`profile.py`, `snapshot.py`, `commands/profile_cmd.py`; spec in `docs/specs/profile/`):
164
+ `devstuff profile snapshot` / `diff` describe and compare a machine; `apply` (below) changes one. Things that are
165
+ load-bearing:
166
+ - **`profile.py` is pure and `snapshot.py` asks the machine.** `compare()` takes *facts* (`MachineTool`), not tool
167
+ objects, so the whole decision table is testable without a registry — and is, exhaustively, one case per
168
+ combination of its six inputs.
169
+ - **Loading refuses what YAML silently corrupts**: `version: 1.10` → float `1.1`, `0.40` → `0.4`, `1:30` → int 90
170
+ (sexagesimal), a date → a date object, a duplicate key → the first dropped, a tool key `on`/`yes` → `True`. The
171
+ original text is gone by the time Python sees it, so the loader rejects instead of coercing. `Entry` enforces the
172
+ same rule at construction, so a version `snapshot` builds can always be read back. Emission is safe only because
173
+ `yaml.safe_dump` quotes numeric-looking strings; don't hand-roll it.
174
+ - **Versions come from `GenericTool.installed_version()`** — per-type, local-only readers for the types that can be
175
+ pinned (`npm`, `pip`/`uvx`, single-package `apt`). Never from `get_version()`, which is free text (`'bat 0.26.1
176
+ (979ba22)'`), and never from `check_for_update()`, which also hits the network. A regex over `get_version()` was
177
+ measured at 12 of 13 correct on today's catalog and rejected anyway: its failure is a *wrong pin written silently*.
178
+ - **`supports_pin()` is an explicit set tied to the updaters by a test** (`tests/test_pin_support.py`): a pin must
179
+ actually reach a command, and a refusal must be a refusal *of the pin*, not some other failure that happens to
180
+ raise. Add an updater and that test forces you to say whether it can pin.
181
+ - **Three states mean "could not compare" and are never `ok`**: `unverifiable`, `unpinnable`, `unknown-key`.
182
+ `unpinnable` is decided *before* the version is looked at, so a `bash` tool whose text version equals the pin
183
+ can't read as a match. Same rule as `outdated`'s `unknown`/`unsupported`; it is the point of both commands.
184
+ - **A profile names keys, never definitions or scripts** — otherwise applying one would be arbitrary code execution
185
+ past the catalog's validation. A custom tool is reported as `unknown-key` and moved with `catalog export`/`import`.
186
+ - **Exit status: `2` is a bad profile, `1` is "differs"** (`--exit-code` only). Don't merge them: a CI gate has to
187
+ tell a drifted machine from a typo. Output to stdout is the data and nothing else, at every `-v`.
188
+ - **Tests must be able to reach the guard they claim to test.** CliRunner's stdout is not a TTY, so a "no banner
189
+ under `--json`" test passes whatever the code does unless `isatty()` is forced true (and a counter-test shows the
190
+ banner *does* appear for a person). Likewise defensive `except` around a reader that never raises needs a fake
191
+ reader that does.
192
+
193
+ **`profile apply` and bundles** (`apply_plan.py`, `apply_exec.py`, `bundles.py`; spec in `docs/specs/profile-apply/`):
194
+ - **The plan comes from `profile.compare`'s rows, never a second comparison.** Two definitions of "missing" would let
195
+ `diff` say a machine matches while `apply` changes it. `build_plan` is pure — the one outside fact it needs, a tool's
196
+ missing `requires` closure, is passed in as a function — so ordering and skip rules are tested without installing.
197
+ - **The verdict is a re-measurement, not the installers' return values.** After the run `apply` calls `compare` again and
198
+ exits from that. `pip_name: ansible` "succeeds" and installs one unusable binary; an installer that returns proves
199
+ nothing. Don't replace the final `compare` with "every step returned".
200
+ - **A pinned install is ONE `tool.update(version=pin)` call**, never `install()` then `update()`: measured to work on a
201
+ tool that isn't installed, it never installs a "latest" nobody asked for, and the installers need no version
202
+ parameter. `perform` refuses a pinned step with no version rather than run it as "latest".
203
+ - **`generic.forget_probes()` runs after every step, on every exit path.** `_once` memoises probes for the process, so
204
+ `installed_version()` read `''` before an install, `''` *again after it succeeded*, and was right only once the memo
205
+ was cleared — a correct pin would have read unverifiable. A new `_once` probe is registered automatically.
206
+ - **A failure doesn't stop the run; its dependents are skipped, never attempted.** Exit `0` means every profile entry
207
+ matches after re-measuring; `1` anything else (declined and interrupted included); `2` a bad profile, or a run that
208
+ needs confirming with no terminal and no `--yes`. `1` and `2` are not interchangeable for the same reason as `diff`'s.
209
+ - **`--json` output is one document and nothing else**, which needs more than a redirect: streamed installer output
210
+ bypasses `sys.stdout`, so `_json_safe()` also sets verbosity to quiet and restores it. A `--json` test needs a chatty
211
+ fake installer, or it passes whatever the code does.
212
+ - **`apply` never removes** (no `--prune`: a trimmed profile would delete the rest of the machine), runs serially
213
+ (apt's lock, shared prefixes, a sudo prompt a worker can't answer) and doesn't prime sudo; the plan marks steps that
214
+ may ask for a password. `apt` pins older than the candidate fail on version-locked dependencies even with
215
+ `--allow-downgrades`, so they are attempted and reported, never forced. A uv tool installed into a bin directory not on
216
+ `PATH` reads `missing` (`is_installed()` is `which`); the summary says so rather than `apply` second-guessing a check
217
+ `diff` also uses.
218
+ - **`install_cmd` is deliberately untouched**: the shared part was one `try`/`except`, against a file with no tests to
219
+ refactor against (SD-10). If the two ever need to share more, add `install`'s own tests first.
220
+ - **Bundles are plain profiles** in `src/dev_setup/bundles/*.yaml` (a new bundle is one file; hatch ships it, measured).
221
+ `@name` is looked up by *listing the directory*, never by building a path from the argument, so `@../x` has nothing
222
+ to traverse. They pin nothing (a shipped version is stale on release day), and two tests guard them in both
223
+ directions: every key exists in the bundled catalog, and every file in the directory is a reachable bundle.
224
+ - **`tests/integration/test_profile_apply.py` is the only test where `apply` meets real installers** (`make run-apply-tests`
225
+ in `dev/`, empty container, sudo + network). It skips on a machine that already has the tools: ordering and
226
+ idempotence assertions mean nothing there.
227
+
158
228
  **Two ways a tool gets defined**: built-in (an entry added directly to `src/dev_setup/tools.yaml`,
159
229
  `builtin=True`) or custom (created via the `devstuff add` wizard, `devstuff catalog import`,
160
230
  or hand-edited YAML, landing in the user catalog). Both use the identical schema — the only
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: devstuff
3
- Version: 2.11.0
3
+ Version: 2.13.0
4
4
  Summary: Development environment setup CLI for Linux
5
5
  Project-URL: Repository, https://github.com/thesawdawg/dev-setup-py
6
6
  Author-email: Sawyer <sawyerksu@gmail.com>
@@ -372,6 +372,173 @@ includes the `unsupported` rows; `--updates-only` applies to it too.
372
372
 
373
373
  ---
374
374
 
375
+ ### `profile`
376
+
377
+ Describe which tools a machine should have as a small file, compare a machine against one, and make
378
+ a machine match one. `snapshot` and `diff` are **read-only** and **local** — they ask the machine,
379
+ never the network — so they work offline; `apply` installs, so it needs the network for that.
380
+
381
+ ```bash
382
+ devstuff profile snapshot > work.yaml # the tools installed here, as a file
383
+ devstuff profile snapshot --versions -o work.yaml # ...and the versions of the ones that can be pinned
384
+ devstuff profile diff work.yaml # how this machine differs from the file
385
+ devstuff profile diff work.yaml --exit-code # exit 1 if it differs: a gate for CI
386
+ devstuff profile apply work.yaml # install what's missing, then check it worked
387
+ devstuff profile apply @devops --dry-run # a profile that ships with devstuff
388
+ ```
389
+
390
+ > The file format is `version: 1`; a later breaking change will bump that number.
391
+
392
+ A profile names catalog **keys**, and optionally a version. It never contains an install script or
393
+ a tool definition, so a profile from somewhere else can't run anything your own catalog doesn't
394
+ already define.
395
+
396
+ ```yaml
397
+ version: 1
398
+ tools:
399
+ uv: {} # present, any version
400
+ ipython:
401
+ version: 9.17.1 # present, at exactly this version
402
+ ```
403
+
404
+ **Quote any version that looks like a number.** YAML reads `version: 1.10` as the number 1.1 and
405
+ `0.40` as 0.4, and the original text can't be recovered — so devstuff refuses it and says to quote
406
+ it (`version: '1.10'`). It also refuses a duplicate key, which YAML would otherwise resolve by
407
+ silently dropping the first, an unknown field, and a tool key that YAML reads as something other
408
+ than text (`on`, `yes`, `123`). `snapshot` always writes versions correctly quoted.
409
+
410
+ #### `snapshot`
411
+
412
+ Writes a profile of every installed tool, to stdout or to `-o FILE`. By default it records **keys
413
+ only**: a profile that pins versions goes stale the day a tool updates, and then reports drift
414
+ nobody intended. `--versions` adds the installed version for the tools that can be pinned — `npm`,
415
+ `pip`/`uvx`, and single-package `apt`; `git`, `script` and `bash` tools can't be installed at a
416
+ chosen version, so a version recorded for them could never be acted on and is left out.
417
+
418
+ - If a pinnable tool's version can't be read (say it is on your `PATH` but isn't a `uv tool`), it is
419
+ written without one and a warning on stderr names it and says why — it is never dropped silently.
420
+ - Tools defined in your own catalog are included, with one stderr note that another machine won't
421
+ know them: move their definitions with `devstuff catalog export` / `import`.
422
+ - Output is **deterministic** — sorted, with a fixed header and no timestamp, hostname or path — so
423
+ a profile kept in git shows only real changes.
424
+ - `-o` refuses to overwrite an existing file (exit 2) unless you pass `--force`.
425
+ - With no `-o`, stdout is exactly the YAML; warnings and notes go to stderr.
426
+
427
+ #### `diff`
428
+
429
+ ```
430
+ ╭──────────────────────────────────────────────────────────────────────────────╮
431
+ │ Package Type Profile Installed Status │
432
+ ├──────────────────────────────────────────────────────────────────────────────┤
433
+ │ reptyr apt ✘ missing │
434
+ │ ipython uvx 9.0.0 9.17.1 ≠ drift │
435
+ │ commitizen uvx 4.16.4 ? unverifiable │
436
+ │ uv doesn't list it as a tool │
437
+ │ (is it installed another │
438
+ │ way?) │
439
+ │ starship bash 1.0.0 – unpinnable │
440
+ │ a bash install can't be │
441
+ │ pinned, so the pin is ignored │
442
+ │ not-a-real-tool ? unknown-key │
443
+ │ not in this machine's catalog │
444
+ │ — if it is a custom tool, │
445
+ │ bring its definition over │
446
+ │ with `devstuff catalog │
447
+ │ import` │
448
+ ╰──────────────────────────────────────────────────────────────────────────────╯
449
+ 1 installed tool isn't in the profile: gh (--all lists them)
450
+ 1 missing · 1 drift · 1 unverifiable · 1 unpinnable · 1 unknown-key · 1 extra · 9 ok
451
+ ```
452
+
453
+ | State | Meaning |
454
+ |-------|---------|
455
+ | `ok` | In the profile and installed; and, if pinned, at the pinned version. |
456
+ | `missing` | In the profile and the catalog, but not installed. |
457
+ | `drift` | Pinned and installed, but at a different version. |
458
+ | `unverifiable` | Pinned and installed, but the installed version can't be read. |
459
+ | `unpinnable` | Pinned, but this tool's install type can't honour a pin — the pin is ignored. |
460
+ | `unknown-key` | In the profile but not in this machine's catalog. |
461
+ | `extra` | Installed, but not in the profile. |
462
+
463
+ `unverifiable`, `unpinnable` and `unknown-key` are three different reasons the comparison couldn't
464
+ be made, each with a different remedy, and **none of them is ever reported as `ok`**. Versions are
465
+ compared as text: `0.45` is not `0.45.0`, and a *newer* installed version is as much drift as an
466
+ older one.
467
+
468
+ By default only differences are listed; the matching tools are counted in the last line, and
469
+ `--all` lists them (and the extras) as rows. `--json` writes one array — every state, always — of
470
+ `{"key", "state", "type", "pinned", "installed", "note"}` objects and nothing else, even at `-vv`.
471
+
472
+ **Exit status.** `0` whenever the comparison ran, whatever it found. With `--exit-code` it is `1`
473
+ if the machine differs; an installed tool that isn't in the profile counts as a difference unless
474
+ you also pass `--ignore-extras`, which affects only this exit status and never hides a real
475
+ difference. A profile that is missing, unreadable or invalid is always `2`, so `1` can only ever
476
+ mean "differs".
477
+
478
+ #### `apply`
479
+
480
+ Makes this machine match a profile: installs what is missing (with whatever it needs, in order)
481
+ and moves pinned tools to the pinned version. **It never removes anything**, and it never touches a
482
+ tool the profile doesn't pin.
483
+
484
+ ```bash
485
+ devstuff profile apply work.yaml --dry-run # show the plan; change nothing, ask nothing
486
+ devstuff profile apply work.yaml # show the plan, ask, then run it
487
+ devstuff profile apply work.yaml --yes # no question (needed with no terminal)
488
+ devstuff profile apply work.yaml --missing-only # install what's missing; leave version drift alone
489
+ devstuff profile apply work.yaml --yes --json # one JSON document on stdout, nothing else
490
+ ```
491
+
492
+ The plan is worked out from the same comparison `diff` makes, so the two can't disagree about what
493
+ "missing" means. A pinned tool that isn't installed is installed **at the pin in one step**, not
494
+ installed at latest and then moved. A pin the tool's install type can't honour (`bash`, `script`,
495
+ `git`) is **skipped with a reason**, never installed at latest in its place.
496
+
497
+ - **A failure doesn't stop the run.** What needed the failed tool is skipped, with the reason, and
498
+ never attempted; everything else carries on.
499
+ - **The result is a re-reading of the machine**, not a tally of installers that didn't raise. An
500
+ installer that "succeeds" without installing anything is reported as the failure it is.
501
+ - **Run it again to resume.** A second `apply` finds nothing to do once the machine matches, so an
502
+ interrupted (`Ctrl-C`) or partly failed run is finished by running the same command.
503
+ - **`apt` pins older than the available version usually fail** — the package's libraries are
504
+ version-locked to it. `apply` tries it and shows apt's own error rather than forcing the install.
505
+ - If a tool installed fine but still reads `missing`, check that its bin directory (usually
506
+ `~/.local/bin`) is on `PATH` in the shell that ran `apply`; `apply` says so under the summary.
507
+
508
+ | Exit | Meaning |
509
+ |------|---------|
510
+ | `0` | Every entry in the profile now matches. |
511
+ | `1` | Something doesn't: a step failed or was skipped, an entry couldn't be acted on, drift is left by `--missing-only`, or you declined or interrupted. |
512
+ | `2` | The profile is unreadable or invalid, or the run needs confirming and there is no terminal (add `--yes`). |
513
+
514
+ With `--json` the document is `{"plan", "run", "rows"}` (`run` is `null` for `--dry-run` or when
515
+ there was nothing to do), `--yes` or `--dry-run` is required, and `-v` has no effect.
516
+
517
+ #### Bundled profiles
518
+
519
+ `PROFILE` can be `@name` for a profile that ships with devstuff, for both `apply` and `diff`:
520
+
521
+ ```bash
522
+ devstuff profile apply @devops --dry-run
523
+ devstuff profile diff @essentials
524
+ ```
525
+
526
+ | Bundle | Tools |
527
+ |--------|-------|
528
+ | `@essentials` | gh, git-lfs, lazygit, bat, htop, yq, starship, nerd-font |
529
+ | `@python` | uv, python, ipython, pre-commit, commitizen |
530
+ | `@devops` | docker, ansible, ansible-vault, aws, saml2aws, mkcert |
531
+ | `@languages` | go, java, php, python, ruby |
532
+ | `@ai-agents` | claude-code, codex, devin, hey-dave, pi |
533
+ | `@ai-local` | ollama, lmstudio, llm-checker, llamactl |
534
+
535
+ Bundles pin nothing, so each installs the latest. `docker`, `java`, `php` and `ruby` ask for sudo.
536
+ Only a leading `@` marks a bundle; a file whose name starts with `@` is `./@name`. An unknown name
537
+ is exit 2 and lists these. The files are plain profiles in `src/dev_setup/bundles/` — copy one out
538
+ and edit it to make your own.
539
+
540
+ ---
541
+
375
542
  ### `configure`
376
543
 
377
544
  Set up an installed tool through a guided wizard, previewing the result before anything is
@@ -345,6 +345,173 @@ includes the `unsupported` rows; `--updates-only` applies to it too.
345
345
 
346
346
  ---
347
347
 
348
+ ### `profile`
349
+
350
+ Describe which tools a machine should have as a small file, compare a machine against one, and make
351
+ a machine match one. `snapshot` and `diff` are **read-only** and **local** — they ask the machine,
352
+ never the network — so they work offline; `apply` installs, so it needs the network for that.
353
+
354
+ ```bash
355
+ devstuff profile snapshot > work.yaml # the tools installed here, as a file
356
+ devstuff profile snapshot --versions -o work.yaml # ...and the versions of the ones that can be pinned
357
+ devstuff profile diff work.yaml # how this machine differs from the file
358
+ devstuff profile diff work.yaml --exit-code # exit 1 if it differs: a gate for CI
359
+ devstuff profile apply work.yaml # install what's missing, then check it worked
360
+ devstuff profile apply @devops --dry-run # a profile that ships with devstuff
361
+ ```
362
+
363
+ > The file format is `version: 1`; a later breaking change will bump that number.
364
+
365
+ A profile names catalog **keys**, and optionally a version. It never contains an install script or
366
+ a tool definition, so a profile from somewhere else can't run anything your own catalog doesn't
367
+ already define.
368
+
369
+ ```yaml
370
+ version: 1
371
+ tools:
372
+ uv: {} # present, any version
373
+ ipython:
374
+ version: 9.17.1 # present, at exactly this version
375
+ ```
376
+
377
+ **Quote any version that looks like a number.** YAML reads `version: 1.10` as the number 1.1 and
378
+ `0.40` as 0.4, and the original text can't be recovered — so devstuff refuses it and says to quote
379
+ it (`version: '1.10'`). It also refuses a duplicate key, which YAML would otherwise resolve by
380
+ silently dropping the first, an unknown field, and a tool key that YAML reads as something other
381
+ than text (`on`, `yes`, `123`). `snapshot` always writes versions correctly quoted.
382
+
383
+ #### `snapshot`
384
+
385
+ Writes a profile of every installed tool, to stdout or to `-o FILE`. By default it records **keys
386
+ only**: a profile that pins versions goes stale the day a tool updates, and then reports drift
387
+ nobody intended. `--versions` adds the installed version for the tools that can be pinned — `npm`,
388
+ `pip`/`uvx`, and single-package `apt`; `git`, `script` and `bash` tools can't be installed at a
389
+ chosen version, so a version recorded for them could never be acted on and is left out.
390
+
391
+ - If a pinnable tool's version can't be read (say it is on your `PATH` but isn't a `uv tool`), it is
392
+ written without one and a warning on stderr names it and says why — it is never dropped silently.
393
+ - Tools defined in your own catalog are included, with one stderr note that another machine won't
394
+ know them: move their definitions with `devstuff catalog export` / `import`.
395
+ - Output is **deterministic** — sorted, with a fixed header and no timestamp, hostname or path — so
396
+ a profile kept in git shows only real changes.
397
+ - `-o` refuses to overwrite an existing file (exit 2) unless you pass `--force`.
398
+ - With no `-o`, stdout is exactly the YAML; warnings and notes go to stderr.
399
+
400
+ #### `diff`
401
+
402
+ ```
403
+ ╭──────────────────────────────────────────────────────────────────────────────╮
404
+ │ Package Type Profile Installed Status │
405
+ ├──────────────────────────────────────────────────────────────────────────────┤
406
+ │ reptyr apt ✘ missing │
407
+ │ ipython uvx 9.0.0 9.17.1 ≠ drift │
408
+ │ commitizen uvx 4.16.4 ? unverifiable │
409
+ │ uv doesn't list it as a tool │
410
+ │ (is it installed another │
411
+ │ way?) │
412
+ │ starship bash 1.0.0 – unpinnable │
413
+ │ a bash install can't be │
414
+ │ pinned, so the pin is ignored │
415
+ │ not-a-real-tool ? unknown-key │
416
+ │ not in this machine's catalog │
417
+ │ — if it is a custom tool, │
418
+ │ bring its definition over │
419
+ │ with `devstuff catalog │
420
+ │ import` │
421
+ ╰──────────────────────────────────────────────────────────────────────────────╯
422
+ 1 installed tool isn't in the profile: gh (--all lists them)
423
+ 1 missing · 1 drift · 1 unverifiable · 1 unpinnable · 1 unknown-key · 1 extra · 9 ok
424
+ ```
425
+
426
+ | State | Meaning |
427
+ |-------|---------|
428
+ | `ok` | In the profile and installed; and, if pinned, at the pinned version. |
429
+ | `missing` | In the profile and the catalog, but not installed. |
430
+ | `drift` | Pinned and installed, but at a different version. |
431
+ | `unverifiable` | Pinned and installed, but the installed version can't be read. |
432
+ | `unpinnable` | Pinned, but this tool's install type can't honour a pin — the pin is ignored. |
433
+ | `unknown-key` | In the profile but not in this machine's catalog. |
434
+ | `extra` | Installed, but not in the profile. |
435
+
436
+ `unverifiable`, `unpinnable` and `unknown-key` are three different reasons the comparison couldn't
437
+ be made, each with a different remedy, and **none of them is ever reported as `ok`**. Versions are
438
+ compared as text: `0.45` is not `0.45.0`, and a *newer* installed version is as much drift as an
439
+ older one.
440
+
441
+ By default only differences are listed; the matching tools are counted in the last line, and
442
+ `--all` lists them (and the extras) as rows. `--json` writes one array — every state, always — of
443
+ `{"key", "state", "type", "pinned", "installed", "note"}` objects and nothing else, even at `-vv`.
444
+
445
+ **Exit status.** `0` whenever the comparison ran, whatever it found. With `--exit-code` it is `1`
446
+ if the machine differs; an installed tool that isn't in the profile counts as a difference unless
447
+ you also pass `--ignore-extras`, which affects only this exit status and never hides a real
448
+ difference. A profile that is missing, unreadable or invalid is always `2`, so `1` can only ever
449
+ mean "differs".
450
+
451
+ #### `apply`
452
+
453
+ Makes this machine match a profile: installs what is missing (with whatever it needs, in order)
454
+ and moves pinned tools to the pinned version. **It never removes anything**, and it never touches a
455
+ tool the profile doesn't pin.
456
+
457
+ ```bash
458
+ devstuff profile apply work.yaml --dry-run # show the plan; change nothing, ask nothing
459
+ devstuff profile apply work.yaml # show the plan, ask, then run it
460
+ devstuff profile apply work.yaml --yes # no question (needed with no terminal)
461
+ devstuff profile apply work.yaml --missing-only # install what's missing; leave version drift alone
462
+ devstuff profile apply work.yaml --yes --json # one JSON document on stdout, nothing else
463
+ ```
464
+
465
+ The plan is worked out from the same comparison `diff` makes, so the two can't disagree about what
466
+ "missing" means. A pinned tool that isn't installed is installed **at the pin in one step**, not
467
+ installed at latest and then moved. A pin the tool's install type can't honour (`bash`, `script`,
468
+ `git`) is **skipped with a reason**, never installed at latest in its place.
469
+
470
+ - **A failure doesn't stop the run.** What needed the failed tool is skipped, with the reason, and
471
+ never attempted; everything else carries on.
472
+ - **The result is a re-reading of the machine**, not a tally of installers that didn't raise. An
473
+ installer that "succeeds" without installing anything is reported as the failure it is.
474
+ - **Run it again to resume.** A second `apply` finds nothing to do once the machine matches, so an
475
+ interrupted (`Ctrl-C`) or partly failed run is finished by running the same command.
476
+ - **`apt` pins older than the available version usually fail** — the package's libraries are
477
+ version-locked to it. `apply` tries it and shows apt's own error rather than forcing the install.
478
+ - If a tool installed fine but still reads `missing`, check that its bin directory (usually
479
+ `~/.local/bin`) is on `PATH` in the shell that ran `apply`; `apply` says so under the summary.
480
+
481
+ | Exit | Meaning |
482
+ |------|---------|
483
+ | `0` | Every entry in the profile now matches. |
484
+ | `1` | Something doesn't: a step failed or was skipped, an entry couldn't be acted on, drift is left by `--missing-only`, or you declined or interrupted. |
485
+ | `2` | The profile is unreadable or invalid, or the run needs confirming and there is no terminal (add `--yes`). |
486
+
487
+ With `--json` the document is `{"plan", "run", "rows"}` (`run` is `null` for `--dry-run` or when
488
+ there was nothing to do), `--yes` or `--dry-run` is required, and `-v` has no effect.
489
+
490
+ #### Bundled profiles
491
+
492
+ `PROFILE` can be `@name` for a profile that ships with devstuff, for both `apply` and `diff`:
493
+
494
+ ```bash
495
+ devstuff profile apply @devops --dry-run
496
+ devstuff profile diff @essentials
497
+ ```
498
+
499
+ | Bundle | Tools |
500
+ |--------|-------|
501
+ | `@essentials` | gh, git-lfs, lazygit, bat, htop, yq, starship, nerd-font |
502
+ | `@python` | uv, python, ipython, pre-commit, commitizen |
503
+ | `@devops` | docker, ansible, ansible-vault, aws, saml2aws, mkcert |
504
+ | `@languages` | go, java, php, python, ruby |
505
+ | `@ai-agents` | claude-code, codex, devin, hey-dave, pi |
506
+ | `@ai-local` | ollama, lmstudio, llm-checker, llamactl |
507
+
508
+ Bundles pin nothing, so each installs the latest. `docker`, `java`, `php` and `ruby` ask for sudo.
509
+ Only a leading `@` marks a bundle; a file whose name starts with `@` is `./@name`. An unknown name
510
+ is exit 2 and lists these. The files are plain profiles in `src/dev_setup/bundles/` — copy one out
511
+ and edit it to make your own.
512
+
513
+ ---
514
+
348
515
  ### `configure`
349
516
 
350
517
  Set up an installed tool through a guided wizard, previewing the result before anything is
@@ -5,7 +5,7 @@ ROOT := ..
5
5
  TOOL ?=
6
6
  PYTEST_ARGS ?=
7
7
 
8
- .PHONY: build build-ci run shell run-tests smoke-agent tui-tests clean
8
+ .PHONY: build build-ci run shell run-tests run-apply-tests smoke-agent tui-tests clean
9
9
 
10
10
  # Build a fresh wheel from source, then build the Docker image.
11
11
  # Clean dist first so the glob in the Dockerfile matches exactly one file.
@@ -36,6 +36,14 @@ run-tests: build-ci
36
36
  docker run --rm devstuff-ci \
37
37
  pytest $(_NODESEL) -m integration -v --tb=short $(PYTEST_ARGS)
38
38
 
39
+ # Run `devstuff profile apply` against the empty CI container: apply a profile, diff clean, apply
40
+ # again and find nothing to do (docs/specs/profile-apply, NFR-4). Needs sudo and network, like
41
+ # run-tests; kept separate because it exercises the orchestration, not one tool's installer.
42
+ # make run-apply-tests
43
+ run-apply-tests: build-ci
44
+ docker run --rm devstuff-ci \
45
+ pytest tests/integration/test_profile_apply.py -m integration -v --tb=short $(PYTEST_ARGS)
46
+
39
47
  # Smoke-test `devstuff agent` against a live Ollama daemon.
40
48
  # Runs on the HOST, not in Docker -- the CI image has no daemon, and yours may be
41
49
  # on another machine. Skips cleanly if nothing is reachable.
@@ -5,7 +5,7 @@ gets a `docs/specs/<feature>/` directory (see [`specs/README.md`](specs/README.m
5
5
  implementation starts, and that spec — not this file — is where requirements are numbered and
6
6
  rejected alternatives are recorded.
7
7
 
8
- Last revised: 2026-10-10.
8
+ Last revised: 2026-10-11.
9
9
 
10
10
  ## Theme
11
11
 
@@ -19,7 +19,7 @@ M5 is independent polish that can be slotted in anywhere.
19
19
  |---|-----------|--------|------------|----------------|
20
20
  | M1 | `devstuff outdated` | Low | — | `outdated/` |
21
21
  | M2 | `devstuff profile snapshot` / `diff` | Medium | M1 | `profile/` |
22
- | M3 | `devstuff profile apply` + bundled bundles | Medium–high | M2 | `profile/` (same) |
22
+ | M3 | `devstuff profile apply` + bundled bundles | Medium–high | M2 | `profile-apply/` |
23
23
  | M4 | Agent tools for `doctor` / `outdated` | Low | M1 | `agent/` (amend) |
24
24
  | M5 | Shell completion | Low | — | `completion/` |
25
25
  | — | git / tmux configurator | Medium | — | `git-config/` (unscheduled) |
@@ -64,7 +64,10 @@ over an existing probe and an existing collector, not new probing.
64
64
 
65
65
  ## M2 — `devstuff profile snapshot` and `diff`
66
66
 
67
- A profile is a YAML file: catalog keys, optional pinned versions, optional configurator output.
67
+ **Spec:** [`specs/profile/`](specs/profile/) — **done** (v1, 2026-10-10): `snapshot` and `diff`. `apply` (M3) has its own spec, [`specs/profile-apply/`](specs/profile-apply/) (approved 2026-10-10).
68
+
69
+ A profile is a YAML file: catalog keys and optional pinned versions. Configurator output is **not** part of it
70
+ (several configurators don't round-trip); capturing it is a separate, later decision.
68
71
 
69
72
  ```yaml
70
73
  version: 1
@@ -74,38 +77,47 @@ tools:
74
77
  starship: {}
75
78
  ```
76
79
 
77
- **Design commitments (to be written up in the spec)**
78
- - **A snapshot is measured, not remembered.** It is built by probing `is_installed()` and
79
- `get_version()` now. There is no separate "installed state" file to drift out of sync — the
80
- same reason `doctor` and every configurator measure the real binary.
81
- - **Reuse `catalog.py`'s validation style**: unknown fields and unknown keys fail loudly at load
82
- time, consistent with "invalid catalogs fail loudly".
83
- - **`diff` reports four states**: missing, extra, version drift, and *unverifiable* (a pinned
84
- `script` tool whose version cannot be probed). The fourth state is the M1 lesson again.
85
- - A profile references catalog keys only. It never embeds install scripts, so a profile file
86
- cannot become a way to smuggle arbitrary commands past the catalog's validation.
80
+ **Built** (v1, 2026-10-10): `profile snapshot` and `profile diff` (spec milestones P1–P6). The format is **provisional**
81
+ until M3 exists. What the design turned into, where it differs from the first sketch:
82
+ - **Versions are read locally, per type** (`installed_version()`), never from `get_version()`'s free text and never
83
+ via the update checkers, which hit the network. Only types that can be pinned (`npm`, `pip`/`uvx`, single-package
84
+ `apt`) ever get a version. So `snapshot` works offline.
85
+ - **`diff` reports seven states**, not four: `ok`, `missing`, `drift`, `unverifiable`, `unpinnable`, `unknown-key`,
86
+ `extra`. The three "could not compare" ones are never `ok` — the M1 lesson, applied again.
87
+ - **Loading is strict beyond the catalog's own rules**: YAML silently turns `version: 1.10` into `1.1` and drops
88
+ duplicate keys, so both are errors rather than coerced.
89
+ - A profile references catalog keys only and never embeds install scripts, so a profile file can't smuggle commands
90
+ past the catalog's validation. A custom tool is `unknown-key` on a machine without it; `catalog export`/`import`
91
+ moves definitions.
92
+ - `--exit-code` shipped in v1 (`1` = differs, `2` = bad profile), unlike `outdated`'s, because drift-gating is this
93
+ feature's headline use.
87
94
 
88
95
  **Done when**
89
- - [ ] `profile snapshot` writes a valid profile; `profile diff` of a fresh snapshot against the
90
- same machine reports no differences (round-trip test).
91
- - [ ] Keys unknown to the effective catalog are reported, not silently dropped.
92
- - [ ] Spec records the rejected alternative of extending `catalog export` instead, with reasons.
96
+ - [x] `profile snapshot` writes a valid profile; `profile diff` of a fresh snapshot against the same machine reports
97
+ no differences — tested on a fake machine, and live on a real one (`13 ok`, exit 0).
98
+ - [x] Keys unknown to the effective catalog are reported, not silently dropped (`unknown-key`).
99
+ - [x] Spec records the rejected alternative of extending `catalog export` instead, with reasons (`stack-decisions.md` SD-1).
93
100
 
94
101
  ## M3 — `devstuff profile apply` and bundled bundles
95
102
 
103
+ **Spec:** [`specs/profile-apply/`](specs/profile-apply/) — **done** (v1, 2026-10-11): `apply` and six bundles (`@essentials`, `@python`, `@devops`, `@languages`, `@ai-agents`, `@ai-local`). The one open item is the first run of the container test, below.
104
+
96
105
  Turn a profile into an install plan and run it.
97
106
 
98
107
  - **Ordering** comes from the existing `requires` graph (including auto-inferred edges such as
99
108
  `npm` → `nvm`). Do not write a second dependency resolver; if the existing one is not exposed in
100
109
  a reusable form, factor it out first.
101
- - **Plan before action**: reuse the `_plan.py` preview and the task-view progress bar that
102
- `install`/`update` use, so `apply` shows what it will do and asks.
110
+ - **Plan before action**: `apply` shows what it will do and asks first. The plan-preview helper
111
+ `install`/`update` are gaining lives on the unmerged UI branch (`commands/_plan.py`); reuse it if it
112
+ has landed, rather than writing a second one.
103
113
  - **Failure policy** needs a decision in the spec: continue past a failed tool and summarise, or
104
114
  stop. Recommendation: continue, skip anything whose `requires` failed, and report at the end —
105
115
  a 40-tool apply that dies on tool 3 is worse than one that finishes 39.
106
- - **Pins on `script`/`bash` tools** can only be honoured by a full reinstall. `apply` should say so
107
- and confirm, matching `update`'s existing behaviour for those types.
108
- - **Bundled bundles** (`@backend`, `@devops`, …) are profile files shipped in the package. They are
116
+ - **Pins on `git`/`script`/`bash` tools cannot be honoured at all** — `update(version=…)` raises for them
117
+ (spec F-2) — and `diff` already reports them `unpinnable`. `apply` must say so rather than quietly
118
+ install latest.
119
+ - **A pinned install is one step, not install-then-update** (measured 2026-10-10, apply spec F-3): `update(version=…)` works on a tool that isn't installed yet, so the installers need no version parameter. `apt` is the exception that matters: an older-than-candidate pin fails on version-locked dependencies whatever flags are passed (F-2), and is reported as a failure rather than worked around.
120
+ - **Bundled bundles** (`@devops`, `@python`, …) are profile files shipped in the package. They are
109
121
  data, so they get a validation test and a CI check that every key they name exists in the
110
122
  bundled catalog — the same two-direction enforcement as the CI-matrix test.
111
123
  - **Configurator state**: restoring starship/lazygit/bat configuration is the differentiator over
@@ -115,9 +127,12 @@ Turn a profile into an install plan and run it.
115
127
 
116
128
  **Done when**
117
129
  - [ ] `apply` on an empty container (the existing Docker integration harness) reproduces a
118
- snapshot taken elsewhere.
119
- - [ ] A failing tool does not abort the run; dependents are skipped with a stated reason.
120
- - [ ] Every bundled bundle passes the key-exists test.
130
+ snapshot taken elsewhere. *Written (`tests/integration/test_profile_apply.py`, `make run-apply-tests`);
131
+ its `uv` + pinned-`commitizen` half was run against the real installers in an isolated `HOME`, and
132
+ the `yq` half (a `sudo` install to `/usr/local/bin`) is waiting for its first container run.*
133
+ - [x] A failing tool does not abort the run; dependents are skipped with a stated reason (unit-tested, and live
134
+ with an impossible pin).
135
+ - [x] Every bundled bundle passes the key-exists test.
121
136
 
122
137
  ## M4 — Agent tools for `doctor` and `outdated`
123
138
 
@@ -48,3 +48,5 @@ They are most useful when they capture:
48
48
  | [`lazygit-config/`](lazygit-config/) — `devstuff configure lazygit`, the icons/pager/panels wizard | Complete (v1) |
49
49
  | [`verbose-mode/`](verbose-mode/) — `-v`/`-vv`, the process-wide verbosity level | Complete (v1) |
50
50
  | [`outdated/`](outdated/) — `devstuff outdated`, the read-only installed-vs-latest report | Complete (v1) |
51
+ | [`profile/`](profile/) — `devstuff profile snapshot` / `diff`, a portable description of a machine's tools | Complete (v1: snapshot, diff; apply is its own spec) |
52
+ | [`profile-apply/`](profile-apply/) — `devstuff profile apply`, make a machine match a profile | Complete (v1: apply, six bundles; container test written, first run pending) |