Chart Prompts

Restyle my chart in the "Yield Ramp" 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 fab engineering ramp review. Clean white page, one deep blue measured line against a gray plan, and numbered event markers keyed to a short change log under the chart. Precise, sober and easy to present in a weekly yield meeting.

Colors (use these exact values):
- Page: #FFFFFF.
- Measured series (line, markers, end value, tag numbers and tag outlines): #1C3F7A (deep blue).
- Plan or target series: #8A9099 (gray), always dashed.
- Primary text, baseline, leader lines and event rules: #141A26 (event rules at 45% opacity).
- Secondary text and axis labels: #5F6673. Gridlines and the note list divider: #E6E8EC.
- Event tag fill: #EEF2F8.

Typography (Google Fonts): Epilogue throughout.
- Title 27px 700, -0.5px letter-spacing, #141A26, stating the finding (for example when the measure overtook the plan and where it ended).
- Subtitle 15px 400 #5F6673 with measure, unit and period.
- Legend items 13px 600. Axis labels 12px 400 #5F6673. End labels: measured 14px 700 blue, plan 12.5px 500 gray.
- Note list heading 11px 700 uppercase with 1.8px letter-spacing in #5F6673; note rows 13px (the week in 700, the description in 400).
- Source and footnote 11.5px #5F6673.

Layout:
- 56px side margins. Title baseline at y 58, subtitle at 86, a legend row at about y 116 (swatch line 28px long, then the label; items spaced about 110px apart; a thin vertical rule plus a sample tag labeled "Process change" closes the row).
- Plot area from x 88 to 880 and y 168 to 408. Event tags sit in a band just above the plot.
- A 1px #E6E8EC divider at y 452, then the note list: heading at y 476 and notes in two columns (x 56 and x 488), rows 28px apart.
- Footer at y 578: "Source: ..." left, a short measurement definition right.

Axes and grid:
- Y axis 0 to 100% with gridlines every 20 (1px #E6E8EC, running 8px past the plot on both sides); the zero line is the baseline in 1.2px #141A26. Labels right-aligned 16px left of the plot; only the top label carries the % sign.
- X axis: 5px tick marks below the baseline at every 5th period, labels 22px below it; the first label reads "Wk 1", the rest are bare numbers.
- No y-axis line, no plot border.

Marks:
- Line chart: the measured series is a 2.5px #1C3F7A straight-segment line with round joins and a small marker at every point (r 3.2 filled blue with a 1.5px white ring). The plan is a 2px #8A9099 line dashed 6 on, 4 off, no markers. End values sit 12px right of the last point: the measured value in bold blue, the plan value in gray just below. Mark the crossover point with a 7px open blue ring and a 0.8px elbow leader to a 12.5px 600 label ("Above plan from week 20").
- Bar chart: slender square-cornered #1C3F7A columns (about 55% of the band) with a 2px #8A9099 dashed plan tick across each column at its target, value labels 12px 600 blue above the columns, the same event rules and tags between columns.
- Events: a 1px #141A26 vertical rule at 45% opacity from 14px above the plot to the baseline, topped by a 20 x 20 px tag (2px radius, #EEF2F8 fill, 1px #1C3F7A outline) holding its number in 12px 700 blue. Each number keys to a row in the note list with the same tag drawn at 18px.

Avoid: color on anything but the measured series, area fills, smoothing that hides step changes after events, event text crammed into the plot, and heavy gridlines.

When you're done, render the chart and check that every tag number matches its note row, event rules sit exactly on their periods, the crossover claim in the title is true for the data, and the end labels do not collide.