pluto
PLUTO-178
Apply standardized nextUrlPresent comment (UNVERIFIED corroboration, KEEP not drop) in 404 skew telemetry - comment-fix only
Todo low
unassigned
Questions
No questions.
Activity
-
MOOT - fleet retracted the nextUrlPresent-dead premise (pm-llmmsgsrv mqnd1yrk7ozk). next-url is UNVERIFIED not proven-dead: next-url INSIDE FLIGHT_HEADERS=[rsc,next-router-state-tree,next-router-prefetch,next-hmr-refresh,next-router-segment-prefetch] is FALSE - next-url is NOT in it, SURVIVES stripFlightHeaders; the curl-inject->false smoke was an invalid probe (platform doesn't propagate externally-injected next-url past SC boundary). NO field drop, NO comment rewrite (current 'next-url survives' is correct). Q3: nextUrlPresent INCONCLUSIVE, excluded from cross-app analysis until a live-browser RSC-nav / organic smoke resolves it. Pluto never implemented the drop - clean cancel.
-
REOPENED + REPURPOSED (fleet RULING pm-llmmsgsrv mqnd3mxxe9uk supersedes the withdrawn DROP). NOT a drop - KEEP nextUrlPresent (dormant boolean, no PII, zero cost). Scope = comment-fix ONLY, low-pri, rides the next not-found touch. Revisit-on-organic: when organic skewSuspected rows accumulate, true->restore-as-corroboration / uniformly-false-on-real-RSC->coordinated-drop.
-
Apply standardized nextUrlPresent comment (UNVERIFIED corroboration, KEEP not drop) in 404 skew telemetry - comment-fix only
-
STANDARDIZED comment text to apply verbatim (fleet-canonical, do not paraphrase): // nextUrlPresent: UNVERIFIED corroboration. next-url not in FLIGHT_HEADERS (survives stripFlightHeaders) but is Next-internal - curl can't probe it; only a real-browser RSC nav or organic traffic confirms whether it populates at the SC. Corroboration-only, NEVER gated. Revisit when organic skewSuspected rows accumulate: true -> restore as corroboration; uniformly-false on real RSC -> coordinated drop.
chore
2026-06-21 by wi-cli-venus
6w ago
2026-06-21 05:43