fix(native): advance anchor data sequence after SYN
This commit is contained in:
parent
93d1b7a948
commit
f74ade94db
4 changed files with 34 additions and 6 deletions
|
|
@ -5,11 +5,12 @@
|
|||
> Persona subject: `ICE-P-ZY001 EXISTS_100`.
|
||||
>
|
||||
> Protected native residency and recovery control are `PASS_100`. Production
|
||||
> cutover remains `0`: the 2026-08-07 physical anchor gate reached the native
|
||||
> runtime and completed heartbeat sequences 1-6, but a real JD Cloud TCP SYN
|
||||
> carried a 40-byte TCP header and exposed the fixed-header parser defect.
|
||||
> Linux remains the unattended default while the option-aware parser is
|
||||
> validated and the physical HTTP gate is rerun.
|
||||
> cutover remains `0`: the first 2026-08-07 physical anchor gate exposed a
|
||||
> fixed 20-byte TCP-header assumption. The option-aware retry completed the
|
||||
> real TCP handshake and transmitted the full anchor response, but reused the
|
||||
> SYN-ACK sequence number for data, so a standards-compliant client discarded
|
||||
> the first response byte. Linux remains the unattended default while the
|
||||
> corrected server sequence progression is validated and rerun physically.
|
||||
|
||||
This directory is the first executable handoff from the registered HLDP
|
||||
language world to a native Guanghu OS. It is not a claim that Guanghu OS has
|
||||
|
|
|
|||
Loading…
Reference in a new issue