Fix base-branch and composer-alias resolution

[mikelittle]

Following on from #1055, there were still a couple of edge cases in the module CI workflow worth tightening up before module repos start consuming the reusable workflow at scale: the branch-resolution regex was being tested against the wrong ref on PRs (so feature PRs targeting a v##-branch fell back to a master skeleton), and the new composer alias produced 9999.9.9 for dev-* installed versions, which doesn't satisfy a dev-master constraint from sibling packages. This PR fixes both, adds developer-side test scripts that mirror the inline shell logic, and flips the dev-tools self-CI caller to a relative-path reference so workflow changes are exercised by their own PRs.

Summary

• Branch resolution: test the v##-branch regex against the PR target ref (github.base_ref) instead of the source ref. Previously a feature PR against a v##-branch resolved BASE_BRANCH=master and the skeleton fallback installed master-version Altis.
• Composer alias regression (follow-up to Update branch name and version resolution #1055): for dev-* installed versions, alias to the installed version itself instead of 9999.9.9. The 9999.9.9 alias only satisfies numeric constraints and breaks sibling packages that require this package as dev-master. Travis handled this correctly via its /^dev/q sed short-circuit; this restores that behaviour while keeping Update branch name and version resolution #1055's packages-dev lookup and missing-package fallback.
• Self-CI: switch dev-tools' own caller (.github/workflows/ci.yml) to the relative-path form ./.github/workflows/module-ci.yml, so this repo always tests the workflow at the PR commit instead of master's copy. Without this, workflow changes here aren't exercised by their own PR.
• Test scripts under .github/workflows/tests/ mirroring both inline shell snippets, runnable locally.
• Refresh workflows/README.md to document the test scripts and correct the base-branch fallback description.

Why

Branch resolution

Travis derived BASE_BRANCH from $TRAVIS_BRANCH (the PR target on PRs); github.head_ref (used by BRANCH_NAME) is the source on PRs, so the GHA equivalent is github.base_ref.

Event	Before	After
push master	master	master
push v##-branch	v##-branch	v##-branch
PR feat/* -> master	master	master
PR feat/* -> v##-branch	master (BUG)	v##-branch

Composer alias

The dev-tools self-CI run on this PR initially failed with:

altis/cms is locked to version dev-master and an update of this package was not requested.
altis/cms dev-master requires altis/dev-tools dev-master -> found altis/dev-tools[dev-master] but it conflicts with your root composer.json require (dev-fix-base-branch-resolution as 9999.9.9).

PR #1055 changed the alias logic so any dev-* installed version produced 9999.9.9, but Travis emitted the literal version (e.g. dev-master). For dev-tools — which most altis modules require as dev-master — the 9999.9.9 alias doesn't satisfy that constraint and resolution fails. The fix:

INSTALLED_VERSION	Alias
empty / not in lock	9999.9.9 (sensible fallback)
dev-*	$INSTALLED_VERSION (e.g. dev-master)
concrete X.Y.Z	X.Y.Z9

Test scripts

Both live under .github/workflows/tests/ and ship as developer-side tools (not wired into CI for now). Each has a full matrix and an --eval mode for ad-hoc input. See .github/workflows/README.md for usage.

• ci-branch-resolution.sh — 9 cases covering pushes and PRs across master, v##-branch, slashy source names, and a non-matching target.
• ci-version-resolution.sh — 10 cases covering concrete versions in .packages / .packages-dev, missing packages, dev-* versions, prerelease suffixes, duplicates, and exact-name matching.

Test plan

• .github/workflows/tests/ci-branch-resolution.sh (9 passed, 0 failed)
• .github/workflows/tests/ci-version-resolution.sh (10 passed, 0 failed)
• dev-tools self-CI green on this PR (run 25568838894)
• Verify against a real PR from a module repo (e.g. altis-local-server) targeting a v##-branch once the SHA is bumped

🤖 Generated with Claude Code

[github-actions]

Backport failed for v12-branch, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin v12-branch
git worktree add -d .worktree/backport-1056-to-v12-branch origin/v12-branch
cd .worktree/backport-1056-to-v12-branch
git switch --create backport-1056-to-v12-branch
git cherry-pick -x 56ccfbf12b18709088e1e0f3890c0d21f0132e8c 55c1a717d75bfe08ef4c8a634ea526b538d25135

[github-actions]

Backport failed for v26-branch, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin v26-branch
git worktree add -d .worktree/backport-1056-to-v26-branch origin/v26-branch
cd .worktree/backport-1056-to-v26-branch
git switch --create backport-1056-to-v26-branch
git cherry-pick -x 56ccfbf12b18709088e1e0f3890c0d21f0132e8c 55c1a717d75bfe08ef4c8a634ea526b538d25135

[github-actions]

After resolving conflicts, continue with:

# Add the resolved files
git add .
# Continue the cherry-pick
git cherry-pick --continue
# Push the branch to GitHub
git push --set-upstream origin backport-1056-to-v12-branch
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktree/backport-1056-to-v12-branch

Then create a pull request using the GitHub CLI:

gh pr create --base v12-branch --head backport-1056-to-v12-branch --title "[Backport v12-branch] Fix base-branch and composer-alias resolution" --body "Backport of #1056 to \`v12-branch\`."

[github-actions]

Backport failed for v12-branch, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin v12-branch
git worktree add -d .worktree/backport-1056-to-v12-branch origin/v12-branch
cd .worktree/backport-1056-to-v12-branch
git switch --create backport-1056-to-v12-branch
git cherry-pick -x 56ccfbf12b18709088e1e0f3890c0d21f0132e8c 55c1a717d75bfe08ef4c8a634ea526b538d25135

[github-actions]

Backport failed for v26-branch, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin v26-branch
git worktree add -d .worktree/backport-1056-to-v26-branch origin/v26-branch
cd .worktree/backport-1056-to-v26-branch
git switch --create backport-1056-to-v26-branch
git cherry-pick -x 56ccfbf12b18709088e1e0f3890c0d21f0132e8c 55c1a717d75bfe08ef4c8a634ea526b538d25135

[github-actions]

After resolving conflicts, continue with:

# Add the resolved files
git add .
# Continue the cherry-pick
git cherry-pick --continue
# Push the branch to GitHub
git push --set-upstream origin backport-1056-to-v12-branch
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktree/backport-1056-to-v12-branch

Then create a pull request using the GitHub CLI:

gh pr create --base v12-branch --head backport-1056-to-v12-branch --title "[Backport v12-branch] Fix base-branch and composer-alias resolution" --body "Backport of #1056 to \`v12-branch\`."