Files
computer-playbook/scripts/meta/resolve
kevinveenbirkenbachandClaude Opus 4.7 ba724c576d ci(deploy): skip make up for app discovery via host-mode runner
The four test-deploy workflows (server/universal/workstation/local)
each started the full compose stack just so scripts/meta/resolve/
apps.sh could call its meta-CLI inside the container. The stack
spin-up dwarfed the actual discovery query.

Introduce INFINITO_APP_DISCOVERY_RUNNER (host|docker, default
`docker` for local dev) alongside the existing INFINITO_TEST_RUNNER
/ INFINITO_LINT_RUNNER dispatch knobs. In host mode apps.sh runs
the meta-CLI through the venv python directly; docker mode keeps
the existing `docker compose --profile ci exec` path.

Workflows switch to host mode and replace `make up` with
actions/setup-python@v5 + `make install`. make install was already
a prereq of make up, so the install cost is unchanged -- only the
docker pull + container start time disappears.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-21 00:39:52 +02:00
..

Resolve Scripts

This directory contains scripts that resolve metadata and derived values used by the project.

  • 🧩 Derive runtime values from repository and workflow context
  • 🔍 Resolve identifiers, references, and computed inputs
  • 🗂️ Keep lookup and resolution logic grouped in one place

Examples in this folder and its subfolders:

  • repository/name.sh resolves the concrete repository name once for callers
  • repository/owner.sh resolves the concrete repository owner once for callers
  • distros.sh holds the canonical distro list used by workflows
  • See pr/README.md for the Pull Request-specific resolvers.

The scope of this folder is value resolution. Build, release, and wait-oriented behavior should stay in their dedicated script directories.