🛠 ResQ Dev Setup

One command to bootstrap the entire ResQ development environment.

---

⚡ Onboarding in one curl

# Default clone target is ~/resq; override with RESQ_DIR=...
curl -fsSL https://get.resq.software | sh

This endpoint is not a redirect to main. It serves one pinned commit and SHA-256 verifies every byte before sending it; on mismatch it returns 502 with a shell snippet that exits non-zero, never installer bytes.

Merging to main does not by itself change what you get here. What you receive is decided by the pinned digests in worker/src/index.ts, so it changes only when a reviewed pin bump merges and deploys. Cutting a release does not move this endpoint either: the release publishes the artifacts, and a separate reviewed pull request repoints the pins at them.

You do not have to take that on faith. Verify against a single immutable release, so the installer and the digest list cannot describe different versions:

REL=https://get.resq.software/v0.4.3
curl -fsSL "$REL/SHA256SUMS"
curl -fsSL "$REL/install.sh"| sha256sum # must match the install.sh line# Or just read it before running it
curl -fsSL "$REL/install.sh" -o install.sh
less install.sh && sh install.sh

The unversioned paths work too, but a deploy landing between the two requests would leave you comparing an installer from one release against digests from another.

Pin to an exact release, which never changes:

curl -fsSL https://get.resq.software/v0.4.3/install.sh | sh

What happens, in order:

1. Installs gh (GitHub CLI) if missing
2. Authenticates with GitHub
3. Installs Nix via the Determinate Systems installer for reproducible toolchains
4. Lets you choose which repo to clone
5. Runs nix develop to build the dev environment
6. Installs the canonical git hooks (delegating to resq pre-commit)
7. Offers to scaffold a repo-type-specific local-pre-push (auto-detects Rust / Python / Node / .NET / C++ / Nix)

Run unattended (CI / provisioning):

REPO=npm YES=1 RESQ_DIR=/srv/work \
curl -fsSL https://get.resq.software | sh

For provisioning, prefer a version-pinned URL so a later release cannot change what your machines install without you deciding to:

REPO=npm YES=1 curl -fsSL https://get.resq.software/v0.4.3/install.sh | sh

---

📦 Repositories

Repo	What	Languages
programs	Solana on-chain programs	Rust (Anchor)
dotnet	Clean/Hexagonal building blocks — the frame, not the domain	C#
dotnet-sdk	.NET client libraries	C#
pypi	Python packages (MCP + DSA)	Python
crates	Rust workspace (CLI + DSA + resq binary)	Rust
npm	TypeScript packages (UI + DSA)	TypeScript
vcpkg	C++ libraries	C++
viz	3D visualization — Three.js/Cesium web + Unity	TypeScript / C#
docs	Documentation site	MDX
dev	This repo — install scripts and onboarding	Shell / PowerShell

Public repos sync to the monorepo automatically.

This table is the public, non-archived, non-fork set (excluding .github), and it is the same list the installers offer. landing used to appear here and in the installer menu; it is now private, so choosing it failed at clone time. The rule is mechanical on purpose — repo-drift.yml re-derives it from the GitHub API and fails when this list and reality disagree, so the next such change is caught by CI rather than by whoever runs the installer next.

---

🛠 Standalone scripts

Each script can be run on its own without going through the full onboarding flow.

Script	Use case	Bootstrap
install.sh / install.ps1	Full onboarding — installs prereqs, clones a repo, sets up dev env + hooks	curl -fsSL https://get.resq.software | sh
install-hooks.sh / install-hooks.ps1	Drop the canonical git hooks into any repo. Asks to scaffold local-pre-push if resq is on PATH	cd <repo> && curl -fsSL https://get.resq.software/hooks.sh | sh
install-resq.sh	Install the resq CLI binary from the latest GitHub Release (SHA256-verified). Falls back to cargo install --git --rev <pinned commit> when no release asset matches — today that fallback is the only path, since no resq-cli-v* release exists yet	curl -fsSL https://get.resq.software/resq.sh | sh

Every one of these is served pinned and hash-verified, and each has a version-locked form — https://get.resq.software/v0.4.3/hooks.sh and so on. https://get.resq.software/SHA256SUMS lists the digest of all of them, keyed by the route name you fetch, so it works directly with sha256sum -c:

curl -fsSLO https://get.resq.software/SHA256SUMS
curl -fsSLO https://get.resq.software/install.sh
curl -fsSLO https://get.resq.software/hooks.sh
sha256sum --ignore-missing -c SHA256SUMS

Be clear about what that check is worth, because it is easy to overstate.

SHA256SUMS and the artifacts both come from get.resq.software. Comparing them detects a truncated download or corruption in transit; it does not detect a compromised endpoint, because anything able to alter the artifact can serve a manifest that agrees with it. Two files from one origin are one source, not two, and this check has no independent trust anchor.

The pinning described above defends a different hop. The Worker verifies what GitHub returns against digests baked into its deploy, so a tampered raw.githubusercontent.com response — or anything altered between the Worker and GitHub — is refused before a byte reaches you. That is real, and it is not the same as protecting you from us.

Closing the remaining gap needs a signature verifiable offline against a public key rather than against our word. Tracked in #58; until it lands, treat these digests as an integrity check, not proof of origin.

Common env vars across all of them:

• YES=1 — skip prompts (CI / provisioning)
• GIT_HOOKS_SKIP=1 — disable installed hooks for a session
• RESQ_SKIP_LOCAL_SCAFFOLD=1 — opt out of the local-pre-push scaffold prompt

To pin a revision, use a version-locked URL rather than an environment variable. (This section previously documented RESQ_DEV_REF=<sha|tag>; no script has ever implemented it, so it silently did nothing.)

install.sh additionally honours REPO, RESQ_DIR, RESQ_BIN_DIR, SKIP_RESQ_CLI and NO_COLOR — run sh install.sh --help for the current list.

---

🚀 Quick Start per Repo

Repo	Language	Setup
programs	Rust / Anchor	anchor build
dotnet	C# / .NET 9	dotnet restore
dotnet-sdk	C# / .NET 9	dotnet restore
pypi	Python	uv sync
crates	Rust	cargo build
npm	TypeScript	bun install
vcpkg	C++	cmake --preset default
viz	TypeScript / C#	bun install · dotnet restore
docs	MDX / Mintlify	mintlify dev
dev	Shell / PowerShell / TypeScript	shellcheck install.sh · cd worker && npm ci && npm test

🏷 Releasing

One authored value, one action:

echo 0.4.4 > VERSION # whatever comes next; 0.4.3 is current
sh bin/stamp.sh # propagates VERSION + hook digests into both installers# open a PR, merge it — that is the release

Do not tag by hand. Merging a VERSION change to main is what releases: CI validates it, creates the tag itself, publishes the Release and SHA256SUMS, and opens a pin-bump PR. Merging that is what changes the bytes https://get.resq.software serves.

Two gates, both ordinary code review:

merging	changes
a VERSION bump	what is published as a release
the pin-bump PR	what users actually receive

Everything else is generated. bin/stamp.sh --check runs on every pull request and verifies by regeneration, so a stamped value cannot be forgotten — forgetting it is a diff. Values marked GENERATED should never be hand-edited.

No Cloudflare credential is stored in GitHub. Deployment is Cloudflare Workers Builds pulling from this repository, and worker-live afterwards checks that the endpoint serves exactly what main declares — hashing the bytes on the wire, not trusting the Worker's own claim about them.

AGENTS.md has the full reasoning, including why tagging is an output of the release rather than its trigger.

🔎 What CI actually verifies

Most of this repo is two shell scripts and a Worker. Most of the engineering is in refusing to take anything on trust — including its own claims. The first two groups run on pull requests; the last runs after a deploy.

The distribution chain

check	what would otherwise rot silently
hook digests re-fetched from the pinned crates commit	a stale pin makes every fresh onboard fail a checksum
pinned crates commits are ancestors of master	a rebased-away or mistyped SHA breaks cargo install --rev
install-resq.sh pins its cargo fallback	an unpinned build of a moving branch, reached from curl | sh
Nix and Bun installer digests re-checked against the live URLs	upstream changing what we execute
stamp.sh --check	a generated version or hook digest left unstamped
gen-pins missing-PINS guard is reachable	the guard itself regressing, which has happened

The code

shellcheck at warning severity, plus an explicit POSIX-dialect check on install.sh — every "In POSIX sh, X is undefined" rule is warning-severity, so gating at error cannot catch a bashism entering the curl-piped installer.

The Worker is TypeScript, typechecked under strict with noUncheckedIndexedAccess, linted by Biome, and covered by a suite that fetches from live GitHub — so a rotted digest surfaces as a failing test rather than a 502 in production. It ships zero runtime dependencies.

windows-smoke loads the PowerShell installers on a Windows runner under both Windows PowerShell 5.1 and pwsh 7. Parsing them on Linux, which is all that happened before, cannot catch a variable that only exists in PowerShell 6+.

After deploy

worker-live fetches from the real endpoint and hashes the bytes on the wire against what main declares — it does not trust the Worker's own headers about what it served.

repo-drift re-derives the repository list from the GitHub API and fails when this README, install.sh and install.ps1 disagree with reality.

Contributor guide

Every ResQ repo ships an AGENTS.md at the root — the canonical plain-text dev guide. That's where the build/test/lint commands, architecture notes, and standards for that specific repo live. Read it first.

Org-wide guidance (onboarding, hooks contract, commit format, PR process) lives in the .github org repo: CONTRIBUTING.md, SECURITY.md, CODE_OF_CONDUCT.md. Every public repo falls back to those automatically.

🔧 Toolchain

Everything is pinned via Nix flakes. No "works on my machine" issues.

Language	Tools
Rust	rustc, cargo, clippy, rustfmt, cargo-deny
TypeScript	bun, node, turbo
Python	python 3.12, uv, ruff, mypy
C#	dotnet 9
C++	gcc, cmake, clang-format
Protobuf	buf, protoc
Solana	solana-cli, anchor

✅ Quality gates — canonical git hooks

Six hook shims live in resq-software/crates — embedded in the resq binary and served at a stable raw URL. install-hooks.sh picks the best path automatically:

1. resq on PATH → calls resq hooks install, which scaffolds the 6 canonical hooks from the templates embedded in the binary. Offline, versioned with the installed resq.
2. No resq → fetches them over HTTPS from a pinned commit in resq-software/crates, and verifies each of the six against a digest baked into the installer before any of them is written.

That second path used to fetch from master — a mutable branch — with no verification at all, which meant six files that git executes on every commit and push came from wherever that branch happened to point. It is now a commit SHA, which cannot be repointed, plus a SHA-256 check that fails closed: on any mismatch nothing is installed.

Precisely what that buys, since it is easy to overclaim:

• A failed verification publishes nothing. All six are downloaded and checked in a temp directory first, so a mismatch on the last file cannot leave the first five installed and active.
• Each hook lands by atomic rename, so an interrupt during publication can never leave a truncated file that git would still execute.
• The set is not atomic. An interrupt between files can leave a mix of old and new hooks, each individually valid. Making the set atomic would mean swapping the whole directory, which would discard the local-<hook> customisations this design keeps there — a worse trade. Re-running the installer is the fix.

RESQ_CRATES_REF still exists for testing an unreleased hook change, but a pinned digest cannot describe an arbitrary ref, so using it requires RESQ_ALLOW_UNVERIFIED=1 and says so.

required.yml re-fetches all six from the pinned commit on every pull request and fails if the digests in either installer disagree — so a stale pin is a red check rather than a broken onboard.

The hooks delegate logic back to the resq binary (resq pre-commit, etc.), so updates roll out via install-resq.sh without editing every repo. That installer prefers a digest-verified release asset and otherwise builds from a pinned commit (cargo install --git --rev); an unpinned build of the default branch requires RESQ_ALLOW_UNVERIFIED=1.

Hook	What it gates
pre-commit	resq pre-commit — copyright, secrets, audit, polyglot format
commit-msg	Conventional Commits + ! marker; blocks WIP: / fixup! / squash! on main
prepare-commit-msg	Prepends [TICKET-123] from branch name
pre-push	Force-push guard, branch-naming convention (feat/, fix/, …, changeset-release/* allowed)
post-checkout / post-merge	Notifies on lock-file changes (Cargo, bun, uv, flake)

Each hook then dispatches to .git-hooks/local-<hook-name> (if executable) — the only place a repo commits hook customization. Generate one with the right language template:

resq hooks scaffold-local --kind auto # detects rust/python/node/dotnet/cpp/nix

resq hooks doctor reports drift, resq hooks update re-syncs from the embedded canonical, resq hooks status prints a one-line shell-friendly summary.

The canonical content lives in exactly one place: crates/resq-cli/templates/git-hooks/. The crates repo's own .git-hooks/ (for dog-fooding) is kept identical via hooks-sync.yml. The dev/ repo used to ship a third copy and was retired in Phase 4 — install-hooks.sh now fetches from the crates source (or lets resq hooks install do it offline). Bats + Rust integration tests cover the hook behavior end-to-end.

📄 License

Apache License 2.0