# Outdoor Work Forecast Standalone Node 22+ local app and CLI. No packages or other purchases required. Run `node app.mjs`, open the complete printed session URL, load the sample, then get the forecast. Download JSON or CSV. Stop with Ctrl+C. Alternatively run `node cli.mjs examples/input.json new-report.json` (optional final `csv`). Existing files are refused. The sample is offline, historical demonstration data. For real weather use: `{"mode":"live","latitude":39.7392,"longitude":-104.9903,"userAgent":"MyOutdoorPlanner/1.0 (contact@example.com)"}`. Replace the identifier/contact with your own. Live mode sends coordinates and this identifier to api.weather.gov. No API key required. US land coverage only; outside coverage and network errors are reported as unavailable. No silent stale fallback. Output includes source URL, update time, query time, timezone, daily values and first matching flag: storm, snow, rain >=60%, sustained wind >=25mph, heat >=100F, cold <=32F. Missing measurements remain null and produce unknown if no other flag matches. Forecast older than 18 hours is explicitly stale. Daytime values take precedence; a remaining night-only period cannot certify daytime conditions. These are configurable-workflow defaults in source, not occupational exposure limits. No hourly timing, gusts, heat index or official alerts are included. Consult current official weather warnings and site conditions before work; no configured flag does not mean safe weather. Samples never claim to be live. One-hour in-process forecast cache, max 100 coordinates, four concurrent lookups. Two HTTPS requests per uncached location; each has 12-second timeout and 2MiB streamed response bound. Redirects and foreign response URLs refused. Restarting clears cache. Input 1MiB; sample max 100 periods; seven calendar-day window. No background polling, bookings, uploads or weather subscriptions. Research: https://www.weather.gov/documentation/services-web-api (checked 2026-10-30). The source documents identifying User-Agent, point lookup and periodically changing grid mappings. Every uncached request repeats point discovery. Contact is optional in the API documentation; app identification is required. Tests: `node --test tests/product.test.mjs`. Browser visual acceptance and actual operational scheduling acceptance are separate from automated tests.