Seasonal Climate-Operations Field Calendar

Build a high-fidelity responsive offer page for FIELDWINDOW, an independent climate-operations consultant serving botanical gardens, small farms, and outdoor cultural programs. The visitor is an operations lead planning a seasonal change under crew, access, and weather constraints. They need to see whether the engagement fits the operating season they actually have, what work is included, and when the consultant is honestly available. The first viewport must turn one season choice into a concrete, bounded engagement.

Compose the offer as a seasonal field calendar connected to a scope ledger, not a personal-brand sales page. Use a compact identity header, a plain-language audience and job statement, a dominant four-season operating calendar, one engagement ledger, and a bottom availability rail. Avoid a portrait hero, discovery-call funnel, package-card grid, testimonial, guarantee, urgency timer, client logo wall, lead-magnet form, nature photograph, decorative weather animation, or generic earthy gradient.

Use this exact demonstrated content: FIELDWINDOW; Plan change inside the season you actually have.; Spring thaw; Summer heat; Autumn shift; Winter shutdown; Scope autumn readiness; 5-week field review; Window: Aug 31–Oct 2; Field walk; Crew workshop; Decision memo; Constraints; No live forecast; 2 site days; One opening; Scenario schedule. Treat the dates and opening as fictional scenario availability, not a live calendar or held booking. Do not add climate predictions, guaranteed resilience, yield claims, safety certification, client outcomes, revenue impact, endorsements, or invented credentials.

Art-direct the calendar with fog #eef0ea, forest #173d32, field orange #df673d, sky #5d8fa3, straw #d8bd68, graphite #252923, and line #aeb6ad. Pair a sturdy humanist grotesk with condensed operational labels and mono dates. Use square rule-led surfaces, month ticks, seasonal bands, a visibly bounded operating window, and restrained paper grain achieved through color and typography rather than a decorative image. All calendar dates, scope rows, constraints, availability, and controls must be semantic HTML; do not use a stock scene, SVG illustration, or decorative CSS landscape.

Start with Spring thaw selected and make Scope autumn readiness the deterministic five-second preview action. During 0–1.0 seconds Autumn shift becomes selected and the calendar announces that the scenario window is being checked. During 1.0–2.6 seconds the active operating band travels from spring to Aug 31–Oct 2 without bounce. During 2.6–4.1 seconds 5-week field review, Field walk, Crew workshop, and Decision memo typeset into the scope ledger. During 4.1–5.0 seconds No live forecast, 2 site days, and One opening settle, then the scenario schedule holds. The action must be repeatable and must not send, reserve, or store anything.

Support season-selected, checking-window, scoped, constraint-focused, no-opening, schedule-open, visible-focus, reduced-motion, and Save-Data states. Season controls must use real buttons with clear selected text and arrow-key navigation. Opening the scenario schedule reveals a closable local dialog that repeats the dates and explains that no booking was made. Announce material changes politely, keep focus visible, and never use color alone for season or availability. Put one data-preview-ready marker on the settled root, exactly one data-preview-action marker on Scope autumn readiness, and set data-preview-action-complete only after the stable final state.

At 960×600, keep the audience statement, four-season calendar, full scope/constraints ledger, and availability rail in the first 16:10 composition. Below 720px, order the content as purpose, season controls, active window, action, engagement scope, constraints, and scenario schedule; ensure every month/date remains understandable at 320px without horizontal scrolling. With prefers-reduced-motion or Save-Data, render the completed Autumn shift scope immediately, skip the moving window and typesetting, and preserve season and dialog controls.

Return one complete standalone responsive HTML document with internal CSS and JavaScript. Use no framework, external runtime, network request, live forecast, booking integration, stock imagery, placeholder box, handmade SVG/CSS illustration, lorem ipsum, copyrighted mark, or explanatory prose outside the product. Include one quiet source-prompt link.