zenno: update full charge info with new knowledge

zenno/src/routes/doc/frbm/+page.svelte

@@ -224,10 +224,10 @@
 				},
 	]);
 	const fcSeries: ComputedSeries[] = $derived([
-		{ label: 'Front Runner', y: (x) => conservePowerAccel(distance(raceLen), RunningStyle.FrontRunner, x) },
-		{ label: 'Pace Chaser', y: (x) => conservePowerAccel(distance(raceLen), RunningStyle.PaceChaser, x) },
-		{ label: 'Late Surger', y: (x) => conservePowerAccel(distance(raceLen), RunningStyle.LateSurger, x) },
-		{ label: 'End Closer', y: (x) => conservePowerAccel(distance(raceLen), RunningStyle.EndCloser, x) },
+		{ label: 'Front Runner', y: (x, raw) => conservePowerAccel(distance(raceLen), RunningStyle.FrontRunner, raw, x) },
+		{ label: 'Pace Chaser', y: (x, raw) => conservePowerAccel(distance(raceLen), RunningStyle.PaceChaser, raw, x) },
+		{ label: 'Late Surger', y: (x, raw) => conservePowerAccel(distance(raceLen), RunningStyle.LateSurger, raw, x) },
+		{ label: 'End Closer', y: (x, raw) => conservePowerAccel(distance(raceLen), RunningStyle.EndCloser, raw, x) },
 	]);
 </script>
 
@@ -528,9 +528,8 @@
 		</div>
 	</div>
 	<p>
-		The exact mechanics of conserving power are unclear at this time. What has been confirmed is that rushed and <a
-			href="#spot-struggle">spot struggle</a
-		> both reduce the chance for it to fire.
+		Rushed and <a href="#spot-struggle">spot struggle</a> reduce both the duration and effectiveness of full charge, potentially to
+		zero. In practice, this appears to be a concern primarily on sprints, which already have a -55% penalty to full charge duration.
 	</p>
 
 	<Sec h={3} id="lane-combo">Lane Combo</Sec>