preflight

/app-kit:preflight — verify auth and CLIs

Run all checks, collect failures, then print a single summary. Don't bail on the first failure — the user wants to fix everything in one pass.

Load config first

Before any check, read ~/.config/mesh44/config.json:

cat ~/.config/mesh44/config.json

If it doesn't exist, fail with this message and stop:

Missing ~/.config/mesh44/config.json. Copy <plugin>/config.json.example to that path and fill in your AWS management account ID, SSO start URL, GitHub org, and developer dir.

Extract these values for use throughout the checks:

• aws.mgt_account_id
• aws.sso_start_url
• aws.sso_region (default us-east-1)
• aws.sso_role_name (default AdministratorAccess)
• github.org
• developer_dir (and developer_dir_symlinks[])

Expected facts (from config)

Thing	Source
AWS mgt account ID	aws.mgt_account_id
AWS region	aws.default_region
SSO start URL	aws.sso_start_url
GitHub org	github.org
Node	24.14.0 (per mise.toml; any 22+ is workable)

Checks

Run these in parallel (one Bash call each) and capture exit codes + stdout/stderr.

0. Working directory — must be the Developer root

pwd

Pass if the resolved path matches developer_dir from config (after expanding $HOME / ~) or any entry in developer_dir_symlinks. Use readlink -f . if ambiguous.

The whole new-app flow assumes the new project goes into ./<app-name> from here. If pwd is anywhere else (e.g., inside an existing project, or under ~), fail with:

Run this from your Developer directory: cd <developer_dir> then re-run.

(substitute the actual configured path).

A. Local CLIs present

command -v aws  >/dev/null && aws --version
command -v gh   >/dev/null && gh --version | head -1
command -v mise >/dev/null && mise --version
command -v node >/dev/null && node --version
command -v npm  >/dev/null && npm --version
command -v git  >/dev/null && git --version
command -v npx  >/dev/null && npx --version