Chart Prompts

Restyle my chart in the "Runway Movements" style described below. Keep my data, chart type, title meaning and units; change only the presentation. Use the charting library this project already uses (plain SVG if there is none). If the library can't express a detail, draw it in a custom layer instead of dropping it. Measurements assume a 960 x 600 chart; scale them proportionally.

Mood: a control tower display at night. Near-black glass, thin phosphor lines, monospaced readouts, an amber status strip and a faint radar scope glowing in the corner.

Colors (use these exact values):
- Background: #0A0C10.
- Series: #4ADE80 (green) for the first series, #22D3EE (cyan) for the second. They sit close in lightness, so always add secondary encoding: the second series is dashed (7 on, 3 off) with square markers; the first is solid with round markers; both are direct-labeled.
- Status amber: #FBBF24 for the configuration strip, its change markers, the eyebrow and its notes.
- Primary text #E6EDF3, secondary text #7D8896, gridlines #1A2029, baseline and ticks #3A4350.
- Radar rings #15261C, sweep edge #1E3A29. Hatched closed periods: #06070A base with #161B22 diagonal lines.

Typography (Google Fonts):
- Rajdhani for the title (700, 34px, #E6EDF3, stating the finding) and subtitle (500, 17px, #7D8896).
- B612 Mono for everything else: eyebrow 11px amber with 1px letter-spacing ("ADG TWR // MOVEMENT LOG // 24 H LOCAL"), strip labels 700 10.5px amber, axis labels 11px #7D8896, callouts and series labels 700 11px in the series color, legend 11px. Every time in B612 Mono is written ATC style as four digits with no colon ("0600", "1600").
- B612 Mono sits colons and periods at the left of a full-width cell, so they read as a gap ("16: 00", "82. 5"). Never put a colon, decimal point or other mid-text punctuation in B612 Mono: use four-digit times, and set any readout that needs punctuation (the source line "Source: illustrative data", decimals) in proportional B612 at the same size and color.

Layout:
- 56px margins. Eyebrow baseline 44px, title 82px, subtitle 108px.
- Radar motif anchored to the top-right corner: four 1px #15261C quarter-circles at radii 70, 140, 210 and 280px, a 45-degree sweep wedge filled with a radial gradient of #4ADE80 from 10% to 0% opacity with a 1px #1E3A29 leading edge, and two tiny green blips (r 2 to 2.5, 35 to 55% opacity). It sits behind everything and must stay faint.
- A configuration strip at y 150 spanning the plot width: 22px tall amber-outlined segments (1px, 2px radius, 14% amber fill) for each runway configuration, labeled in amber; closed periods get a dashed 35% outline and no fill. "RWY" in 700 amber at the left margin. At each change, a dotted amber line (2 on, 4 off, 45% opacity) drops through the plot, and one note under the strip names the cause ("WIND SHIFT 1600").
- Plot from x 92 to 880, top 214, baseline 504. The right gutter holds the direct labels. Legend and source share a footer line at 558px.

Axes and grid:
- Horizontal 1px #1A2029 gridlines every 10 units, the zero line in #3A4350. Y numbers right-aligned 12px left of the plot. Time ticks every 3 hours, 6px long.

Marks:
- Line chart: 2px straight-segment lines with points at hour centers; green line with r 2.4 dots, cyan dashed line with 4.6px square markers. Peak callout: a 14px open cyan square around the peak point and "DEP 36 0700" beside it.
- Bar chart: paired thin bars per hour (green then cyan), 2px apart, square ends; the cyan bars carry a 1px darker diagonal hatch so they remain distinct without color.
- Closed or curfew hours: full-height rectangles filled with a 45-degree hatch pattern (6px period, 1.5px #161B22 lines on #06070A) and a two-line label "NIGHT CURFEW / 2300 TO 0600" in 10.5px #7D8896 with 1.2px letter-spacing.

Avoid: glows and blur on the lines, gradients in the plot area, smoothing, thick strokes, bright radar rings that compete with data, and any color outside green, cyan and amber.

When you're done, render the chart and check that the radar rings stay behind and below the title in visual weight, every configuration change has its dotted marker, the peak value in the title matches the data, and the direct labels do not collide.