Repository navigation
Cierra verificaciones reales de infraestructura y recorridos de navegador - #9
Merged
Merged
Conversation
gorvet
changed the title
gorvet
marked this pull request as ready for review
October 25, 2026 07:20
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cierra V-02 con MySQL/HTTP en PHP 8.4 y Redis 7 reales (36 pruebas/764 aserciones, sin omisiones), y routing Nginx/PHP-CGI (1/85). Chromium ejecuta los 99 casos de la suite sin fallos ni omisiones. Los jobs dedicados rechazan omisiones.
La prueba Nginx antigua enviaba recuperación sin CSRF: ahora comprueba el rechazo y después el POST válido con sesión/token reales. La prueba de autoguardado medía la recepción de eventos en Node: usa el reloj monótono del navegador conservando el umbral, con sonda de demora de 500 ms que acredita la diferencia. Sin cambios del core, temporizadores, mensajes de acceso o aplicaciones instaladas.
Los servicios y dependencias se crean solo en fixtures/contenedores/directorios temporales. No se vacía Redis ni se envía correo. Se conservan explícitos los límites de cobertura visual universal, SMTP, pie personalizado y hosting. Evidencia en maintenance/verificacion-infraestructura-20261025.md. No requiere release.