devstuff 2.12.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.
- {devstuff-2.12.0 → devstuff-2.13.0}/CHANGELOG.md +10 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/CLAUDE.md +40 -2
- {devstuff-2.12.0 → devstuff-2.13.0}/PKG-INFO +69 -6
- {devstuff-2.12.0 → devstuff-2.13.0}/README.md +68 -5
- {devstuff-2.12.0 → devstuff-2.13.0}/dev/Makefile +9 -1
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/ROADMAP.md +13 -10
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/README.md +2 -1
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/profile/specifications.md +2 -4
- devstuff-2.13.0/docs/specs/profile-apply/development-plan.md +92 -0
- devstuff-2.13.0/docs/specs/profile-apply/specifications.md +206 -0
- devstuff-2.13.0/docs/specs/profile-apply/stack-decisions.md +134 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/pyproject.toml +1 -1
- devstuff-2.13.0/src/dev_setup/apply_exec.py +156 -0
- devstuff-2.13.0/src/dev_setup/apply_plan.py +218 -0
- devstuff-2.13.0/src/dev_setup/bundles/ai-agents.yaml +10 -0
- devstuff-2.13.0/src/dev_setup/bundles/ai-local.yaml +10 -0
- devstuff-2.13.0/src/dev_setup/bundles/devops.yaml +12 -0
- devstuff-2.13.0/src/dev_setup/bundles/essentials.yaml +14 -0
- devstuff-2.13.0/src/dev_setup/bundles/languages.yaml +11 -0
- devstuff-2.13.0/src/dev_setup/bundles/python.yaml +10 -0
- devstuff-2.13.0/src/dev_setup/bundles.py +62 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/commands/help_cmd.py +1 -1
- devstuff-2.13.0/src/dev_setup/commands/profile_cmd.py +458 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/generic.py +19 -2
- devstuff-2.13.0/tests/integration/test_profile_apply.py +111 -0
- devstuff-2.13.0/tests/test_apply_exec.py +243 -0
- devstuff-2.13.0/tests/test_apply_plan.py +386 -0
- devstuff-2.13.0/tests/test_apply_run.py +339 -0
- devstuff-2.13.0/tests/test_bundles.py +194 -0
- devstuff-2.13.0/tests/test_profile_apply_cmd.py +646 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/uv.lock +1 -1
- devstuff-2.12.0/src/dev_setup/commands/profile_cmd.py +0 -199
- {devstuff-2.12.0 → devstuff-2.13.0}/.claude/skills/run-stuff/SKILL.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/.claude/skills/run-stuff/smoke.sh +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/.github/codex/review.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/.github/workflows/agent.yml +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/.github/workflows/bump.yml +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/.github/workflows/ci.yml +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/.github/workflows/publish.yml +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/.github/workflows/test-installs.yml +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/.gitignore +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/dev/Dockerfile +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/dev/Dockerfile.ci +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/dev/docker-compose.yml +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/devstuff +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/github-agent.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/agent/development-plan.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/agent/specifications.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/agent/stack-decisions.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/ansible-config/development-plan.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/ansible-config/specifications.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/ansible-config/stack-decisions.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/bat-config/development-plan.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/bat-config/specifications.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/bat-config/stack-decisions.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/commitizen-config/development-plan.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/commitizen-config/specifications.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/commitizen-config/stack-decisions.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/docker-config/development-plan.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/docker-config/specifications.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/docker-config/stack-decisions.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/lazygit-config/development-plan.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/lazygit-config/specifications.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/lazygit-config/stack-decisions.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/outdated/development-plan.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/outdated/specifications.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/outdated/stack-decisions.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/precommit-config/development-plan.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/precommit-config/specifications.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/precommit-config/stack-decisions.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/profile/development-plan.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/profile/stack-decisions.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/starship-config/development-plan.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/starship-config/specifications.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/starship-config/stack-decisions.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/uv-backbone/development-plan.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/uv-backbone/specifications.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/uv-backbone/stack-decisions.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/verbose-mode/development-plan.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/verbose-mode/specifications.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/docs/specs/verbose-mode/stack-decisions.md +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/install.sh +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/__init__.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/__main__.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/agent/__init__.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/agent/approval.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/agent/bridges.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/agent/catalog.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/agent/completion.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/agent/config.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/agent/loop.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/agent/ollama.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/agent/preflight.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/agent/primitives.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/agent/registry.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/agent/sandbox.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/agent/session.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/agent/transcript.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/agent/wizard.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/agent_tools.schema.json +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/agent_tools.yaml +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/base.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/catalog.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/cli.py +0 -0
- {devstuff-2.12.0/tests/integration → devstuff-2.13.0/src/dev_setup/commands}/__init__.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/commands/add_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/commands/agent_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/commands/catalog_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/commands/configure_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/commands/delete_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/commands/docs_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/commands/doctor_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/commands/functions_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/commands/install_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/commands/links_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/commands/list_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/commands/outdated_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/commands/remove_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/commands/run_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/commands/skills_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/commands/update_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/__init__.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/ansible/__init__.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/ansible/detect.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/ansible/model.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/ansible/render.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/ansible/validate.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/ansible/wizard.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/bat/__init__.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/bat/detect.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/bat/model.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/bat/preview.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/bat/render.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/bat/wizard.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/commitizen/__init__.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/commitizen/detect.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/commitizen/model.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/commitizen/render.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/commitizen/validate.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/commitizen/wizard.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/docker/__init__.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/docker/detect.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/docker/model.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/docker/render.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/docker/validate.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/docker/wizard.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/lazygit/__init__.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/lazygit/detect.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/lazygit/model.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/lazygit/render.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/lazygit/validate.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/lazygit/wizard.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/precommit/__init__.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/precommit/detect.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/precommit/model.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/precommit/render.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/precommit/validate.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/precommit/wizard.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/reptyr/__init__.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/reptyr/wizard.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/starship/__init__.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/starship/fonts.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/starship/icons.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/starship/model.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/starship/preview.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/starship/render.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/configure/starship/wizard.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/doctor.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/function_runner.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/functions.schema.json +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/functions.yaml +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/functions_catalog.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/functions_registry.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/links.schema.json +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/links.yaml +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/links_catalog.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/links_registry.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/profile.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/registry.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/snapshot.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/tools.yaml +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/ui.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/updates.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/src/dev_setup/verbose.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/__init__.py +0 -0
- {devstuff-2.12.0/src/dev_setup/commands → devstuff-2.13.0/tests/integration}/__init__.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/integration/conftest.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/integration/test_agent_smoke.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/integration/test_agent_tui.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/integration/test_commitizen_config.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/integration/test_tools.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_agent.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_agent_completion.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_agent_loop.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_agent_sandbox.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_agent_tools.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_agent_wizard.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_catalog.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_configure_ansible.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_configure_bat.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_configure_commitizen.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_configure_docker.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_configure_lazygit.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_configure_precommit.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_configure_reptyr.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_configure_starship.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_doctor.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_functions.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_generic.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_installed_version.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_links.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_outdated_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_pin_support.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_profile.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_profile_diff.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_profile_diff_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_profile_snapshot_cmd.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_registry.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_snapshot.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_update_checker_parity.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_update_notes.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_updates.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_uv_probes.py +0 -0
- {devstuff-2.12.0 → devstuff-2.13.0}/tests/test_verbose.py +0 -0
|
@@ -1,3 +1,13 @@
|
|
|
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
|
+
|
|
1
11
|
## v2.12.0 (2026-10-10)
|
|
2
12
|
|
|
3
13
|
### Features
|
|
@@ -67,6 +67,9 @@ src/dev_setup/
|
|
|
67
67
|
├── updates.py # Update probing + the five-state classifier, shared by `update` and `outdated`
|
|
68
68
|
├── profile.py # Profile file format (strict load, deterministic dump) + the seven-state diff classifier — pure
|
|
69
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
|
|
70
73
|
├── configure/ # Per-tool setup wizards (see "Configurators" below)
|
|
71
74
|
└── commands/ # One Click command per file: list, install, remove, update, outdated, profile, add, delete, docs, catalog
|
|
72
75
|
```
|
|
@@ -158,8 +161,8 @@ and `devstuff outdated` share one collector and one classifier. Things that are
|
|
|
158
161
|
writes only the array to stdout, even at `-vv`.
|
|
159
162
|
|
|
160
163
|
**Profiles** (`profile.py`, `snapshot.py`, `commands/profile_cmd.py`; spec in `docs/specs/profile/`):
|
|
161
|
-
`devstuff profile snapshot` / `diff` describe and compare a machine; `apply`
|
|
162
|
-
|
|
164
|
+
`devstuff profile snapshot` / `diff` describe and compare a machine; `apply` (below) changes one. Things that are
|
|
165
|
+
load-bearing:
|
|
163
166
|
- **`profile.py` is pure and `snapshot.py` asks the machine.** `compare()` takes *facts* (`MachineTool`), not tool
|
|
164
167
|
objects, so the whole decision table is testable without a registry — and is, exhaustively, one case per
|
|
165
168
|
combination of its six inputs.
|
|
@@ -187,6 +190,41 @@ file format is provisional. Things that are load-bearing:
|
|
|
187
190
|
banner *does* appear for a person). Likewise defensive `except` around a reader that never raises needs a fake
|
|
188
191
|
reader that does.
|
|
189
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
|
+
|
|
190
228
|
**Two ways a tool gets defined**: built-in (an entry added directly to `src/dev_setup/tools.yaml`,
|
|
191
229
|
`builtin=True`) or custom (created via the `devstuff add` wizard, `devstuff catalog import`,
|
|
192
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.
|
|
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>
|
|
@@ -374,19 +374,20 @@ includes the `unsupported` rows; `--updates-only` applies to it too.
|
|
|
374
374
|
|
|
375
375
|
### `profile`
|
|
376
376
|
|
|
377
|
-
Describe which tools a machine should have as a small file,
|
|
378
|
-
|
|
379
|
-
they work offline.
|
|
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
380
|
|
|
381
381
|
```bash
|
|
382
382
|
devstuff profile snapshot > work.yaml # the tools installed here, as a file
|
|
383
383
|
devstuff profile snapshot --versions -o work.yaml # ...and the versions of the ones that can be pinned
|
|
384
384
|
devstuff profile diff work.yaml # how this machine differs from the file
|
|
385
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
|
|
386
388
|
```
|
|
387
389
|
|
|
388
|
-
>
|
|
389
|
-
> breaking change will bump that number. There is no `apply` yet — nothing here installs anything.
|
|
390
|
+
> The file format is `version: 1`; a later breaking change will bump that number.
|
|
390
391
|
|
|
391
392
|
A profile names catalog **keys**, and optionally a version. It never contains an install script or
|
|
392
393
|
a tool definition, so a profile from somewhere else can't run anything your own catalog doesn't
|
|
@@ -474,6 +475,68 @@ you also pass `--ignore-extras`, which affects only this exit status and never h
|
|
|
474
475
|
difference. A profile that is missing, unreadable or invalid is always `2`, so `1` can only ever
|
|
475
476
|
mean "differs".
|
|
476
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
|
+
|
|
477
540
|
---
|
|
478
541
|
|
|
479
542
|
### `configure`
|
|
@@ -347,19 +347,20 @@ includes the `unsupported` rows; `--updates-only` applies to it too.
|
|
|
347
347
|
|
|
348
348
|
### `profile`
|
|
349
349
|
|
|
350
|
-
Describe which tools a machine should have as a small file,
|
|
351
|
-
|
|
352
|
-
they work offline.
|
|
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
353
|
|
|
354
354
|
```bash
|
|
355
355
|
devstuff profile snapshot > work.yaml # the tools installed here, as a file
|
|
356
356
|
devstuff profile snapshot --versions -o work.yaml # ...and the versions of the ones that can be pinned
|
|
357
357
|
devstuff profile diff work.yaml # how this machine differs from the file
|
|
358
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
|
|
359
361
|
```
|
|
360
362
|
|
|
361
|
-
>
|
|
362
|
-
> breaking change will bump that number. There is no `apply` yet — nothing here installs anything.
|
|
363
|
+
> The file format is `version: 1`; a later breaking change will bump that number.
|
|
363
364
|
|
|
364
365
|
A profile names catalog **keys**, and optionally a version. It never contains an install script or
|
|
365
366
|
a tool definition, so a profile from somewhere else can't run anything your own catalog doesn't
|
|
@@ -447,6 +448,68 @@ you also pass `--ignore-extras`, which affects only this exit status and never h
|
|
|
447
448
|
difference. A profile that is missing, unreadable or invalid is always `2`, so `1` can only ever
|
|
448
449
|
mean "differs".
|
|
449
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
|
+
|
|
450
513
|
---
|
|
451
514
|
|
|
452
515
|
### `configure`
|
|
@@ -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-
|
|
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/`
|
|
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,7 @@ over an existing probe and an existing collector, not new probing.
|
|
|
64
64
|
|
|
65
65
|
## M2 — `devstuff profile snapshot` and `diff`
|
|
66
66
|
|
|
67
|
-
**Spec:** [`specs/profile/`](specs/profile/) — **done** (v1, 2026-10-10): `snapshot` and `diff`. `apply` (M3)
|
|
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
68
|
|
|
69
69
|
A profile is a YAML file: catalog keys and optional pinned versions. Configurator output is **not** part of it
|
|
70
70
|
(several configurators don't round-trip); capturing it is a separate, later decision.
|
|
@@ -100,6 +100,8 @@ until M3 exists. What the design turned into, where it differs from the first sk
|
|
|
100
100
|
|
|
101
101
|
## M3 — `devstuff profile apply` and bundled bundles
|
|
102
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
|
+
|
|
103
105
|
Turn a profile into an install plan and run it.
|
|
104
106
|
|
|
105
107
|
- **Ordering** comes from the existing `requires` graph (including auto-inferred edges such as
|
|
@@ -114,10 +116,8 @@ Turn a profile into an install plan and run it.
|
|
|
114
116
|
- **Pins on `git`/`script`/`bash` tools cannot be honoured at all** — `update(version=…)` raises for them
|
|
115
117
|
(spec F-2) — and `diff` already reports them `unpinnable`. `apply` must say so rather than quietly
|
|
116
118
|
install latest.
|
|
117
|
-
- **A pinned install is install-then-update
|
|
118
|
-
|
|
119
|
-
downgrade. Whether to teach the `npm`/`uvx`/`apt` installers a version instead is an M3 decision.
|
|
120
|
-
- **Bundled bundles** (`@backend`, `@devops`, …) are profile files shipped in the package. They are
|
|
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
|
|
121
121
|
data, so they get a validation test and a CI check that every key they name exists in the
|
|
122
122
|
bundled catalog — the same two-direction enforcement as the CI-matrix test.
|
|
123
123
|
- **Configurator state**: restoring starship/lazygit/bat configuration is the differentiator over
|
|
@@ -127,9 +127,12 @@ Turn a profile into an install plan and run it.
|
|
|
127
127
|
|
|
128
128
|
**Done when**
|
|
129
129
|
- [ ] `apply` on an empty container (the existing Docker integration harness) reproduces a
|
|
130
|
-
snapshot taken elsewhere.
|
|
131
|
-
|
|
132
|
-
|
|
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.
|
|
133
136
|
|
|
134
137
|
## M4 — Agent tools for `doctor` and `outdated`
|
|
135
138
|
|
|
@@ -48,4 +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
|
|
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) |
|
|
@@ -176,7 +176,7 @@ Per the project convention (*measure the tool, don't recall it*). Date: 2026-10-
|
|
|
176
176
|
| F-1 | `get_version()` is the first line of `--version` output, and nothing more structured: `'bat 0.26.1 (979ba22)'`, `'codex-cli 0.162.0'`, `'gh version 2.102.0 (2026-09-30)'`, `'devin 3000.11.3 (9c803229faa4)'`, `'uv 0.12.23 (x86_64-unknown-linux-gnu)'`, and `''` for `nerd-font`. Only 4 of 13 installed tools (`commitizen`, `ipython`, `nvm`, `pi`) return a bare version. | A snapshot cannot record these as pins (FR-11, SD-3). |
|
|
177
177
|
| F-2 | Only four install types can honour a pin on `update`: `npm` (`pkg@ver`), `pip`/`uvx` (`pkg==ver`), `apt` (`pkg=ver`, single package only). `git` (`pull`), `script` and `bash` raise "Version pinning is not supported". | FR-10, FR-26. A pin on a `git`/`script`/`bash` key is `unpinnable`. |
|
|
178
178
|
| F-3 | A clean installed version exists only inside the `_check_update_*` functions, fused with a network lookup of the latest. Run offline, `outdated` took ~11 s waiting on timeouts. | `snapshot` needs local-only readers, not the checkers (FR-11, FR-25). Two of the three local reads were already separate functions (`_npm_installed_version`, `_uv_tool_versions`); only the `dpkg-query` call was inline and was factored out in P2. **Measured in P2** over this machine's 13 installed tools: `installed_version()` 1.0 s serial, 0.7 s on an 8-worker pool (nearly all of it `npm list -g` sourcing nvm, ~0.5 s per npm tool), and identical results with the network blocked. |
|
|
179
|
-
| F-4 | `install()` takes **no version** (`Tool.install(self)`); `update(version=…)` requires the tool to already be installed. | Not an M2 concern
|
|
179
|
+
| F-4 | `install()` takes **no version** (`Tool.install(self)`); `update(version=…)` requires the tool to already be installed. | Not an M2 concern. It looked like it forced install-then-update for M3; measuring `apply` showed `update(version=…)` works on a missing tool, so it doesn't (§6, `profile-apply/` F-3). |
|
|
180
180
|
| F-5 | **YAML corrupts version-shaped scalars.** `version: 1.10` → float `1.1`; `0.40` → `0.4`; `2` → int; `2026-09-30` → a date object. A duplicate key under `tools` is silently dropped (last wins). `yaml.safe_dump` *does* quote a string that would otherwise reload as a number (`'1.10'`). Also measured while building P1: `1:30` → int 90 (YAML 1.1 sexagesimal), `0x1F` → 31, `1_000` → 1000, `~` → null; `0o17` stays a *string* (PyYAML is YAML 1.1, not 1.2). Tool **keys** are affected too: `on`/`no` → bool, `null` → None, `123` → int, while `y`/`n` stay strings. | FR-4 and FR-5 reject rather than coerce; the emit side is safe, so NFR-4's round trip holds. |
|
|
181
181
|
| F-6 | `registry.missing_requires(tool)` already returns the transitive missing-dependency closure, deepest first. | Reusable for M3 ordering; no second resolver (§6). |
|
|
182
182
|
|
|
@@ -200,9 +200,7 @@ Per the project convention (*measure the tool, don't recall it*). Date: 2026-10-
|
|
|
200
200
|
Recorded now because they were found now and will not be cheaper to rediscover. `apply` gets its
|
|
201
201
|
own numbered requirements, and a decision on each of these, before it starts.
|
|
202
202
|
|
|
203
|
-
- **Pinned apply
|
|
204
|
-
pin that is older than latest that is two installs, and for `apt` a downgrade. Alternatives —
|
|
205
|
-
teaching the `npm`/`uvx`/`apt` installers to take a version — are a decision for M3.
|
|
203
|
+
- **Pinned apply** — *resolved 2026-10-10 in [`profile-apply/`](../profile-apply/):* not install-then-update. `update(version=…)` on a missing tool is a one-step pinned install (measured), so the installers keep taking no version. Kept here for the history of why it was asked.
|
|
206
204
|
- **Ordering** comes from `registry.missing_requires` (F-6), not a second resolver.
|
|
207
205
|
- **Pins on `git`/`script`/`bash` keys cannot be honoured** and `apply` must say so rather than
|
|
208
206
|
silently installing latest.
|
|
@@ -0,0 +1,92 @@
|
|
|
1
|
+
# Development plan: `devstuff profile apply`
|
|
2
|
+
|
|
3
|
+
**Date:** 2026-10-10
|
|
4
|
+
**Status:** Complete — A1 done 2026-10-10, A2–A6 done 2026-10-11 (the container test's first run is the one open item)
|
|
5
|
+
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
## Milestones
|
|
9
|
+
|
|
10
|
+
One commit each, pure pieces first so the rules that matter are tested before anything can touch a
|
|
11
|
+
machine — the order that worked for `outdated` and `profile`.
|
|
12
|
+
|
|
13
|
+
| # | Milestone | Satisfies | State |
|
|
14
|
+
|---|-----------|-----------|-------|
|
|
15
|
+
| A1 | **Planner** — pure `build_plan(rows, tools)`: row → action table, dependency closure across the plan with de-duplication, ordering, the skip-because-dependency-failed propagation as a pure function over results | FR-2, 3, 9, 22 | **Done** 2026-10-10 |
|
|
16
|
+
| A2 | **Step runner** — `apply_exec.perform` (install / pinned install in one call, failure as a result, never a wizard offer); `generic.forget_probes()` that clears every memoised probe. `install_cmd` untouched (SD-10) | FR-6, 7, 10, NFR-5 | **Done** 2026-10-11 |
|
|
17
|
+
| A3 | **Executor** — runs a `Plan` serially under the failure policy, handles `^C` between steps, returns per-step results | FR-8, 9, 11, 19 | **Done** 2026-10-11 |
|
|
18
|
+
| A4 | **`devstuff profile apply`** — plan table, `--dry-run`, `--yes`, TTY refusal, `--missing-only`, final re-measurement, summary, exit status, `--json` | FR-4, 5, 12–18, 23, NFR-1–4 | **Done** 2026-10-11 |
|
|
19
|
+
| A5 | **Bundles** — `@name` resolution, the shipped files, the two data tests; also accepted by `diff` | FR-20, 21 | **Done** 2026-10-11 |
|
|
20
|
+
| A6 | **Docs + integration** — README, CLAUDE.md rules, roadmap, specs index; a Docker integration test that applies a profile to an empty container and diffs clean | NFR-4 | **Done** 2026-10-11 — docs written; the container test is written and its `uv` + pinned-`commitizen` half was run against the real installers (isolated `HOME`); the `yq` half and the first run in the CI image are pending |
|
|
21
|
+
|
|
22
|
+
Nothing in this plan changes `devstuff install`: A2 was first written as a refactor of `install_cmd`
|
|
23
|
+
and became a new module once measured (SD-10). The only edit to existing code is additive —
|
|
24
|
+
`forget_probes()` and a registry of memoised probes in `generic.py`, which changes no behaviour.
|
|
25
|
+
|
|
26
|
+
## Testing strategy
|
|
27
|
+
|
|
28
|
+
Unit tests use fake tools and a fake runner — no real installs, default suite. Real behaviour is
|
|
29
|
+
checked separately (live below), because a unit test that fakes success is exactly how the uv
|
|
30
|
+
probe's ignored exit code went unnoticed in `outdated`.
|
|
31
|
+
|
|
32
|
+
- **Planner decision table (A1).** Exhaustive, like `diff`'s 72-case grid: every `diff` state ×
|
|
33
|
+
pinned or not × pinnable or not × has-missing-dependency or not. Each asserts the action and the
|
|
34
|
+
reason text, and that no combination plans an action on a `unverifiable`/`unpinnable`/
|
|
35
|
+
`unknown-key`/`extra` row.
|
|
36
|
+
- **Ordering (A1).** Shared dependency across two requested tools appears once and before both; a
|
|
37
|
+
depth-3 chain comes out deepest-first; a dependency the profile names *and* another tool needs
|
|
38
|
+
appears once, not labelled as an extra. A property test over every tool in the bundled catalog:
|
|
39
|
+
for any subset requested, every step's `requires` precede it.
|
|
40
|
+
- **Failure propagation (A1/A3).** A fails ⇒ everything requiring A is skipped with "needs A, which
|
|
41
|
+
failed"; a *sibling* is still attempted; a dependency that was *skipped* (not failed) also skips
|
|
42
|
+
its dependents, transitively.
|
|
43
|
+
- **Pinned install is one call (A2).** A spy asserts `update(version=…)` is called exactly once and
|
|
44
|
+
`install()` never, for a missing pinned tool; and the reverse for an unpinned one.
|
|
45
|
+
- **Stale cache (A2/A4).** A fake whose `installed_version()` reads a `_once`-style memo: without
|
|
46
|
+
the reset the final comparison says `unverifiable`, with it `ok`. Written *first* and shown to
|
|
47
|
+
fail on the unfixed code.
|
|
48
|
+
- **No wizard prompt (A2).** The core never calls `offer_after_install`; `devstuff install` still
|
|
49
|
+
does. A trap that raises if invoked from `apply`.
|
|
50
|
+
- **Command (A4).** Non-TTY without `--yes` ⇒ exit 2 and *nothing run* (spy asserts zero installer
|
|
51
|
+
calls); `--dry-run` ⇒ exit 0 and zero calls; `--json` stdout parses and stderr carries the rest;
|
|
52
|
+
exit 1 when a step failed, when an entry is unactionable, and 0 only when the final diff is clean;
|
|
53
|
+
a bad profile ⇒ exit 2 before any probe.
|
|
54
|
+
- **Idempotence (A4, NFR-4).** Apply, then plan again against the fake machine the first run
|
|
55
|
+
mutated: the plan is empty.
|
|
56
|
+
- **Bundles (A5).** Every shipped bundle loads; every key it names is in the bundled catalog; and
|
|
57
|
+
the reverse direction — every file in the bundle directory is reachable by name — so a bundle can't
|
|
58
|
+
be added and forgotten.
|
|
59
|
+
|
|
60
|
+
### Mutation checking
|
|
61
|
+
|
|
62
|
+
As with the previous milestones: after the tests pass, break the code on purpose and confirm a test
|
|
63
|
+
fails. The mutations worth making here: apply to an `extra` row; drop the dependency de-duplication;
|
|
64
|
+
let a skipped dependency's dependents run; treat a return-without-raise as final success (skip the
|
|
65
|
+
re-measurement); forget the cache reset; remove the TTY refusal; call `install()` then `update()`.
|
|
66
|
+
A survivor means a test is missing, not that the mutation was unfair.
|
|
67
|
+
|
|
68
|
+
### Live verification (not in CI)
|
|
69
|
+
|
|
70
|
+
1. **Isolated uv end to end.** With `UV_TOOL_DIR`/`UV_TOOL_BIN_DIR` pointed at a scratch directory,
|
|
71
|
+
apply a profile pinning a small package at its *older* release (as measured in F-3), then run
|
|
72
|
+
`profile diff` on the same file: clean. Apply again: empty plan.
|
|
73
|
+
2. **A deliberate failure.** *(Run on 2026-10-11 through the command, in an isolated `HOME`, catalog and `UV_TOOL_DIR`: the real pinned install succeeded, an impossible pin failed with uv's message, its dependent was skipped unattempted, the unknown key was reported, and the exit status was 1. That run is also what found F-8.)* A profile naming a package version that doesn't exist: the step fails,
|
|
74
|
+
dependents are skipped, siblings proceed, exit status 1, and `diff` agrees with the summary.
|
|
75
|
+
3. **Network blocked.** Planning and `--dry-run` work offline; only the install steps fail, with
|
|
76
|
+
their own error.
|
|
77
|
+
4. **Docker (A6).** *(Written as `tests/integration/test_profile_apply.py` and `make run-apply-tests`. Docker isn't available where it was written, so it was validated by running its `uv` + pinned `commitizen` half with the real installers in an isolated `HOME` and a `PATH` with no `uv`: the plan ordered `uv` first, the pinned install landed at the pinned version (checked with `uv tool list`), `diff` agreed, and a second plan was empty. The `yq` half installs with `sudo` into `/usr/local/bin` and was deliberately not run on a workstation. First container run pending.)* The existing integration harness: apply a profile in an empty
|
|
78
|
+
container, `diff` clean, apply again and find nothing. This is the roadmap's headline "done when", and the only test that
|
|
79
|
+
exercises `bash`-type installers and `requires` ordering for real. It needs sudo and network and
|
|
80
|
+
is not run by default.
|
|
81
|
+
|
|
82
|
+
## Risks
|
|
83
|
+
|
|
84
|
+
| Risk | Mitigation |
|
|
85
|
+
|------|------------|
|
|
86
|
+
| A `bash` installer exits 0 having installed nothing | The re-measurement (FR-15) judges by `is_installed`, so it is reported rather than believed; the same hazard `devstuff install` already has, now visible |
|
|
87
|
+
| `apply`'s runner drifts from what `devstuff install` does | Accepted (SD-10); the shared part is a single call, and the differences (no wizard, no short-circuit) are tested as requirements |
|
|
88
|
+
| A long run is interrupted halfway | FR-19: clean stop, honest summary, and re-running `apply` is the resume — NFR-4 makes that safe |
|
|
89
|
+
| Applying a profile from someone else | It can only run what *this* machine's catalog defines (`profile` SD-2); the plan is shown and confirmed first, and `--dry-run` previews it without running |
|
|
90
|
+
| A sudo prompt mid-run in `--yes` mode | Marked in the plan (FR-5), documented; priming is rejected (OQ-8) |
|
|
91
|
+
| Downgrades and non-resolvable apt pins | Reported as failures with apt's own message (FR-8); a pin that can't be honoured is never replaced by "latest" |
|
|
92
|
+
| Bundle content is a judgement call, not a fact | Decided with the user at A5 (six bundles, sudo-heavy tools included, no catch-all `@everything`); the test guards only that keys exist, not that a bundle is a good idea |
|