Corrección de errores

lib/pantallas/pantalla_historial.dart

@@ -42,7 +42,8 @@ class PantallaHistorial extends StatelessWidget {
                 child: ListView.separated(
                   padding: const EdgeInsets.fromLTRB(16, 12, 16, 24),
                   itemCount: partidas.length + 1,
-                  separatorBuilder: (_, __) => const SizedBox(height: 12),
+                  separatorBuilder: (context, index) =>
+                      const SizedBox(height: 12),
                   itemBuilder: (context, index) {
                     if (index == 0) {
                       return const ArteGameplayFarolero.historial(height: 132);

lib/pantallas/pantalla_votacion_cliente.dart

@@ -41,7 +41,6 @@ class _PantallaVotacionClienteState extends State<PantallaVotacionCliente> {
   ServicioNearby? _nearby;
 
   List<JugadorInicioPartida> get _votantes => widget.jugadoresControlados;
-  bool get _modoMultiVotante => _votantes.length > 1;
   bool get _votacionCompleta {
     if (_votantes.isEmpty) return _votosPorVotante.containsKey('_legacy');
     return _votantes.every((votante) => _votosPorVotante[votante.jugadorId] != null);

skills/premium-game-ui/SKILL.md

@@ -6,7 +6,7 @@ description: >
 license: Apache-2.0
 metadata:
   author: gentleman-programming
-  version: "1.2"
+  version: "1.3"
 ---
 
 ## When to Use
@@ -40,6 +40,7 @@ metadata:
 15. **Localization is part of premium UI.** User-visible copy must go through the app localization system. For Spanish, use Spanish from Spain; avoid Rioplatense/Argentinian phrasing in app strings.
 16. **Do not bundle chroma-source images.** Chroma-key sources are temporary production files. Only the final transparent PNG/WebP and opaque backgrounds belong in registered Flutter asset folders; otherwise green-screen images can be shipped accidentally.
 17. **Use shared decorative art widgets for repeated phases.** Debate, word reveal, voting, host-management, notes, rules, and history screens should reuse generated gameplay art through shared components so layouts stay consistent and text/buttons remain real Flutter widgets.
+18. **Analyzer cleanliness is mandatory.** When editing Dart, do not introduce unused getters/fields or analyzer-only style issues. Avoid `(_, __)`/`(_, __, ___)` callback parameters because `unnecessary_underscores` is enabled; name unused callback parameters descriptively (`context`, `index`, `error`, `stackTrace`) or use only one `_` where valid.
 
 ## Mandatory Image Generation Rule