POST repetidos de lectura al detalle del vehiculo tras guardar, sin escrituras correlacionadas

Sub-tickets

Activity

• wi-cli-venus created · 5w ago
• wi-cli-venus assigned · 5w ago
  coder-mba-l-ca
• wi-cli-venus statusChanged · 5w ago
  Tracing existing proxy request window against SELECT-only DB evidence; no repeat save or credentials. Detail resolver already guarded by domain value (135/307); identifying individual read actions before calling this a loop.
• wi-cli-venus note · 5w ago
  Proxy fresh trace v5.5.66: save AA033TK click 2026-09-08T04:48:05.167Z, edit POST200 then edit/detail RSC GET503/503/200; five detail POST200 interleaved RSC GETs (first503, remainder200), settles on ficha. Tool lacks action IDs/bodies and individual timestamps. Original trace not persisted, unavailable after compaction. This does NOT establish repeated writes or recursion: source detail has domain-value resolver guard plus distinct mount read actions. Exact new window relayed db02 for audit/history and server error correlation. Requested no further saves. Older untimestamped503/login cascade is unverified causality, not deployment/session conclusion.
• wi-cli-venus titleChanged · 5w ago
  POST repetidos de lectura al detalle del vehiculo tras guardar, sin escrituras correlacionadas
• wi-cli-venus note · 5w ago
  db02 SELECT-only correlation for04:48:05Z: zero history rows04:40-05:00Z and zero audit_log04:45-04:55Z; logger last event04:27:41Z (670 total), AA033TK app rows80590/80592 unchanged. PM ruling: not write recursion; investigate client read sequence. Earlier untimestamped503/login cascade is excluded from this investigation; no causal claim. Proxy confirms headers/body unavailable via read_network_requests; trace recorded here in previous evidence event.
• wi-cli-venus note · 5w ago
  Source explains five base mount read actions; pending header evidence this may be expected mount traffic, not a defect. Proxy read-only authorized SPA search AA033TK to FB444EP captured6 POSTs,5 distinct Next-Action values, one40cd67135f9a2392492907089b9263cb480558d3f7 twice. No save/login or bodies/credentials. Search handler separately calls resolverVehiculoPorDominio before router.push, then destination effect resolves domain: candidate explanation for one duplicate, NOT confirmed until action mapping/order. Asked proxy existing ordered capture; no rerun requested. 503s unexplained and outside conclusion; do not close as all-unique yet.
• wi-cli-venus completed · 5w ago
  Resolved as expected read sequence, no duplicate-save defect or patch. db02 SELECT-only zero audit/history writes across04:48:05Z window; logger verified active. Proxy read-only authorized qa-editor SPA search AA033TK→FB444EP (no save/login; pathname/method/Next-Action only) captured index0 source POST AA033TK40cd67135f, then destination FB444EP indexes4/7/10/12/14 with five unique action IDs40cd67135f,40e3bc1688,402bc97410,403bc52d00,40329df846; zero repeated action within destination mount. Extra source call matches search resolver before navigation, destination resolver guarded by domain value. Source five mount reads resolver/comments/cadena/fechaAlta/history explain sequence; exact hash→export mapping unavailable (tool classifier blocked chunk scan; no bypass). Coverage: one read-only detail navigation plus DB correlation of earlier save; alta/baja only source-reviewed, not runtime exercised. Original historical trace unavailable;503s remain unexplained and outside this finding. Closed under coder02 ruling to close on unique destination actions. No app changes/deployment.
• wi-cli-venus note · 5w ago
  Proxy correction: /vehiculos/undefined in instrumentation was NOT a real endpoint. Wrapper used input.url for URL objects (which expose href), then resolved undefined against current location. Underlying RSC URLs not recovered; do not treat those captured paths as actual application requests. No rerun requested.