docs(sample): drop stale merged-issue references from screen comments

Author: l2hyunwoo

sample/shared/src/commonMain/kotlin/io/github/compose/jindong/sample/screens/PresetGalleryScreen.kt

@@ -95,8 +95,8 @@ fun PresetGalleryScreen(modifier: Modifier = Modifier) {
     }
   }
 
-  // VIBRATION PATH (stale pre-#84; see SingleHapticScreen for the rationale). Each preset's literal
-  // events are replayed serially via the Compose DSL; the timeline cards above are always live.
+  // Each preset's literal events are replayed serially via the Compose DSL; the timeline cards above
+  // are always live.
   val current = remember(playName) { presets.firstOrNull { it.name == playName } }
   if (current != null) {
     Jindong(playTrigger, playName) {

sample/shared/src/commonMain/kotlin/io/github/compose/jindong/sample/screens/ReactiveScreen.kt

@@ -64,13 +64,9 @@ import io.github.compose.jindong.sample.theme.JindongTheme
 import kotlin.math.roundToLong
 
 /**
- * Reactive / State-driven (handoff 07): the one differentiator — moving a control re-fires the
+ * Reactive / State-driven (handoff 07): the one differentiator, moving a control re-fires the
  * pattern with no Play button, and the pattern itself changes with state. This screen doubles as a
  * regression oracle: each card's Expected/Actual proves whether the live path tracks the controls.
- *
- * NOTE: pre-#84 the VIBRATION (the actual buzz from `Jindong`) is the bug surface — it replays the
- * first-compiled pattern. The TIMELINE here stays live (it never touches the buggy remember), so the
- * Expected/Actual comparison still reads true; once #84 lands the buzz matches with zero changes.
  */
 @Composable
 fun ReactiveScreen(modifier: Modifier = Modifier) {
@@ -143,7 +139,8 @@ private fun ThresholdCard() {
     },
   )
 
-  // VIBRATION PATH (stale pre-#84). The card's timeline is live; the buzz self-heals once #84 lands.
+  // State is a key, so the pattern recompiles and the buzz tracks the controls. The card's timeline
+  // is driven separately and is always live.
   Jindong(rxThresh) {
     Haptic(120.ms, HapticIntensity.Custom(intensity))
   }
@@ -183,7 +180,8 @@ private fun CountCard() {
     },
   )
 
-  // VIBRATION PATH (stale pre-#84). The card's timeline is live; the buzz self-heals once #84 lands.
+  // State is a key, so the pattern recompiles and the buzz tracks the controls. The card's timeline
+  // is driven separately and is always live.
   Jindong(rxCount) {
     Repeat(rxCount) {
       Haptic(60.ms, HapticIntensity.Custom(0.7f))
@@ -240,7 +238,8 @@ private fun MultiInputCard() {
     },
   )
 
-  // VIBRATION PATH (stale pre-#84). The card's timeline is live; the buzz self-heals once #84 lands.
+  // State is a key, so the pattern recompiles and the buzz tracks the controls. The card's timeline
+  // is driven separately and is always live.
   Jindong(rxDur, rxInt) {
     Haptic(rxDur.ms, HapticIntensity.Custom(rxInt))
   }

sample/shared/src/commonMain/kotlin/io/github/compose/jindong/sample/screens/RepeatScreen.kt

@@ -119,8 +119,8 @@ fun RepeatScreen(modifier: Modifier = Modifier) {
     PlayButton(onClick = { playTrigger++ })
   }
 
-  // VIBRATION PATH (stale pre-#84; see SingleHapticScreen for the rationale). The timeline above is
-  // always live; this executor call self-heals once #84 lands.
+  // Explicit-play: playTrigger and the pattern parameters are keys, so Play replays the current
+  // values. The timeline above is driven separately and is always live.
   Jindong(playTrigger, rpCount) {
     Repeat(rpCount) {
       Haptic(60.ms, HapticIntensity.Custom(UNIT_INTENSITY))

sample/shared/src/commonMain/kotlin/io/github/compose/jindong/sample/screens/RepeatWithIndexScreen.kt

@@ -151,8 +151,8 @@ fun RepeatWithIndexScreen(modifier: Modifier = Modifier) {
     PlayButton(onClick = { playTrigger++ })
   }
 
-  // VIBRATION PATH (stale pre-#84; see SingleHapticScreen for the rationale). The timeline above is
-  // always live; this executor call self-heals once #84 lands.
+  // Explicit-play: playTrigger and the pattern parameters are keys, so Play replays the current
+  // values. The timeline above is driven separately and is always live.
   Jindong(playTrigger, riCount, riDir) {
     RepeatWithIndex(riCount) { i ->
       Haptic(70.ms, HapticIntensity.Custom(ramp(i, riCount, riDir)))

sample/shared/src/commonMain/kotlin/io/github/compose/jindong/sample/screens/SingleHapticScreen.kt

@@ -179,9 +179,9 @@ fun SingleHapticScreen(modifier: Modifier = Modifier) {
     PlayButton(onClick = { playTrigger++ })
   }
 
-  // VIBRATION PATH: key only on playTrigger so this stays an explicit-play screen (Reactive is the
+  // Explicit-play: key only on playTrigger, so this stays an explicit-play screen (Reactive is the
   // auto-firing one). The block reads live sgDur/resolvedIntensity, so Play always uses the current
-  // values. The timeline above is driven separately from state and stays live regardless of #84.
+  // values. The timeline above is driven separately from state and stays live.
   Jindong(playTrigger) {
     Haptic(sgDur.ms, resolvedIntensity)
   }

sample/shared/src/commonMain/kotlin/io/github/compose/jindong/sample/screens/TimingScreen.kt

@@ -151,8 +151,8 @@ fun TimingScreen(modifier: Modifier = Modifier) {
     PlayButton(onClick = { playTrigger++ }, text = "Play sequence")
   }
 
-  // VIBRATION PATH (stale pre-#84; see SingleHapticScreen for the rationale). The timeline above is
-  // always live; this executor call self-heals once #84 lands.
+  // Explicit-play: playTrigger and the pattern parameters are keys, so Play replays the current
+  // values. The timeline above is driven separately and is always live.
   Jindong(playTrigger, nodes.toList()) {
     Sequence {
       nodes.toList().forEach { node ->