Skip to content
ROLLCALL

Register 1.2.0 part of the Wayne State app stack

Menu

Scripts on every OS#

This page lists every script Rollcall ships and how each OS runs it. Next: the contract its output keeps.

Every developer tool works on Windows, macOS and Linux. Where PHP fits, there is one PHP command and nothing to pair. Where a script drives Docker, it ships twice: a .ps1 for Windows (PowerShell 5.1 and 7, never bash or WSL) and a .sh for Linux and macOS (written for macOS's bash 3.2 and BSD tools). tests/ScriptPairsTest.php fails if a script ships without its twin, if a .sh uses a bash 4 feature or a GNU-only flag, or if a .ps1 calls a Unix shell on the host.

One PHP command, every OS#

Command What it does
php bin/rollcall (vendor/bin/rollcall in an install) The CLI: scan, report, digest, owners, drift, advisories, prune
php bin/docs-site.php (composer docs) Builds the docs site from docs/
php bin/agent-ready.php (composer site:agent-ready) Writes the Markdown twins, llms.txt and the sitemap
php tools/versions-table.php (composer site:versions) Regenerates the front page versions table from CREED's policy
php bin/quickstart-versions.php (composer site:versions) Regenerates the quick-start printout's policy values in site/index.html and site/index.md from CREED's policy, between the quickstart-versions markers
composer site:versions-check Fails when the front page versions table or the quick-start printout's policy values are stale; runs in composer ci
php tools/creed-copy-check.php (composer creed-copy:check) Proves the CREED copy has not drifted

A pair per OS#

Windows (PowerShell) Linux and macOS (bash) What they do
scripts/a11y.ps1 scripts/a11y.sh The front page accessibility gate: Preflight's a11y checker (vendored in tools/a11y/check.mjs, pinned by tests/A11yCheckerPinTest.php) in Docker, the same image and inputs as the a11y-site CI job
scripts/dashboard-a11y.ps1 scripts/dashboard-a11y.sh The dashboard accessibility gate: renders the public, internal and empty-state dashboard pages with PHPUnit, from Laravel and from the raw-PHP entry point (styled with the bundled WayneUI stylesheet), server-renders the Vue page and fails unless it matches the Laravel page (tools/vue-dashboard/parity.mjs), then runs the same axe-core check on all nine, in Docker
deploy/scripts/parity.ps1 deploy/scripts/parity.sh The kit's parity script, replaced by Parity (parity up); kept only until Parity lands everywhere

scripts/readme-art is a Node tool (npm run build), the same on every OS.

Inside Citadel's container only#

These run on Citadel's Linux container, never on a developer machine, so they have no Windows twin. Squire writes and owns them (deploy/.squire.json):

File When Citadel runs it
deploy/build.sh At image build time, as root, with /bin/sh
deploy/deployments/001-first-release.sh Once, when the first release starts
deploy/.squire/portable/squire-entrypoint.sh Each time the portable image starts (OpenShift, Coolify, raw Docker), as the container entrypoint
deploy/scripts/release.sh After every Quick Update (the post-script), and from the first-release hook

Inside GitLab CI only#

This runs in a GitLab CI job on the Linux composer image, never on a developer machine, so it has no Windows twin. It still keeps to POSIX sh and macOS-safe tools, like every .sh here.

File When GitLab runs it
tools/creed-copy-refresh.sh The weekly creed-copy-refresh job (or a web pipeline on main): re-exports the CREED copy from CREED main, rebuilds the versions table, docs and agent-ready files, runs composer creed-copy:check and composer ci, and pushes to main with the job token only when both pass

Before a release, a maintainer runs the smoke test on all three OSes; the checklist is in MAINTAINING.md, "Smoke test on every OS".