podverse-workers-patterns

Per-command environment validation uses separate validators to ensure only required env vars are read for each worker command. This command-first bootstrap approach determines the command from argv before loading full config to avoid side effects.

Command-first bootstrap determines the worker command from argv before loading the full application configuration. This prevents side effects by ensuring startup checks only validate environment variables relevant to the specific command being executed.

Apply per-job environment validation to new or updated worker commands using provided validators and startup checks. This ensures correct validation behavior and automatically updates environment variable documentation for the modified worker.

Standardize environment variable documentation using ENV.md and APPS-WORKERS.md files. These files capture required variables, per-command validation rules, and worker startup configuration to maintain accurate documentation when commands are added or updated.

No external dependencies are required. The validation patterns implement command-first bootstrap and per-command validators directly within the worker application, using argv parsing to determine which environment variables to validate before startup.

Startup validation fails when per-command validators detect missing required environment variables. Use the command-first bootstrap to ensure only the specific variables needed for the invoked command are validated, preventing unrelated env vars from blocking startup.