kevinveenbirkenbachandClaude Opus 4.7
356e3366be
Replace the seven separate deploy-* make targets with a single `make deploy` recipe that maps short Make variables to the canonical INFINITO_* environment variables and dispatches via the new scripts/tests/deploy/local/deploy/main.sh router. main.sh and all sub-scripts continue to read the long-form names, so Ansible passthrough and container forwarding stay unchanged. Short Make CLI now exposes apps, mode, purge, type, bundles, disabled, and full_cycle as aliases. The router picks the verb folder (initialize, reinstall, update) and scope (all, selection) based on the chosen mode plus the presence of INFINITO_APPS or INFINITO_BUNDLES. Also folds in the global INFINITO_TEST_DEPLOY_TYPE -> INFINITO_DEPLOY_TYPE rename across default.env, passthrough handler, dotenv test, CI deploy workflows, discovery scripts, and the server stage task. Active contributor and agent-iteration docs, role-level Administration and README files, the bundles README, and the deploy reset helper are all retargeted to the new short CLI. docs/requirements/ entries stay untouched as historical audit logs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Workflow Input Resolution 🔎
Shell helpers that derive structured inputs and outputs for GitHub Actions jobs from repository state.
Scope 📋
This directory contains pure resolvers that read repository state (git history, role metadata, version tags, input environment variables) and emit resolved values either via $GITHUB_OUTPUT or stdout. Resolvers MUST be idempotent and MUST NOT mutate repository or registry state beyond writing to $GITHUB_OUTPUT. The covered concerns are distro selection for push CI, diff-driven app whitelist resolution, release-tag parsing, app discovery for the deploy matrix, and change detection that gates the update pipeline.
For the workflow catalog that consumes these outputs see workflows.md. For the diff-driven whitelist contract see the "Diff-driven app selection" section in pipeline.md.