audit-multizone

Multi-zone Audit: $ARGUMENTS

READ-ONLY MODE: This command audits an existing PolicyEngine Next.js tool for multi-zone compliance and reports findings. It does NOT make code changes.

Use this to verify that a zone will work correctly behind policyengine.org, in its own Vercel preview, and in next dev.

Migration-era command. This exists to retrofit existing PolicyEngine Next.js tools (built before the multi-zone architecture was standardized) and to verify tools built outside the /create-dashboard flow. Once all PolicyEngine Next.js apps conform to the multi-zone architecture, this command can be removed — new apps created via /create-dashboard are already validated by the dashboard validators at scaffold time.

Scope

This command audits Next.js zone apps — tools that deploy as a zone behind policyengine-app-v2/website/. It does not apply to:

• policyengine-app-v2 itself (the host — different rules)
• Legacy iframe-embedded tools (not yet migrated to multi-zone)
• Non-Next.js tools (Python/Modal dashboards, static GitHub Pages sites)

The underlying agent (multizone-validator) detects these cases and stops with a clear message.

Options

• --repo OWNER/NAME — Audit a specific GitHub repo (clones it to /tmp)
• --path ABSOLUTE_PATH — Audit a local path (e.g., a worktree or sibling clone)
• No arguments — Audit the current working directory

Examples

/audit-multizone                                        # Audit current working directory
/audit-multizone --repo PolicyEngine/keep-your-pay-act  # Clone and audit a GitHub repo
/audit-multizone --path /Users/me/Work/household-api-docs

Phase 0: Parse arguments

Parse $ARGUMENTS:
- REPO_ARG: value after --repo if present
- PATH_ARG: value after --path if present
- If neither: use current working directory

Phase 1: Resolve target path

If --repo OWNER/NAME is provided:

TARGET_PATH=/tmp/audit-multizone-REPO_NAME
if [ ! -d "$TARGET_PATH" ]; then
  gh repo clone OWNER/NAME "$TARGET_PATH"
else
  (cd "$TARGET_PATH" && git pull)
fi