Ground placed-structure side-buffer seam
This commit is contained in:
parent
ec4919fdbf
commit
a669edcaa8
4 changed files with 82 additions and 8 deletions
|
|
@ -23,8 +23,9 @@ Working rule:
|
|||
semantics of the now-grounded compact `0x55f3` footer dword/status lane and the newly exposed
|
||||
separate tagged side-buffer seam candidates, especially the exact `0x38a5/0x38a6/0x38a7`
|
||||
family whose compact `6`-byte header pattern and embedded placed-structure-style `0x55f1`
|
||||
name rows now make it the strongest current candidate for the separate placed-structure dynamic
|
||||
side-buffer owner.
|
||||
name rows now make it the grounded placed-structure dynamic side-buffer owner; the remaining
|
||||
blocker is semantic closure of the 6-byte prefix lane and its relation to the embedded
|
||||
`0x55f1/0x55f2/0x55f3` row subset.
|
||||
- Extend shellless clock advancement so more periodic-company service branches consume owned
|
||||
runtime time state directly instead of only the explicit periodic service command.
|
||||
- Keep widening selected-year world-owner state only when a full owning reader/rebuild family is
|
||||
|
|
@ -90,6 +91,12 @@ Working rule:
|
|||
`rrt-runtime`: its synthetic regression is grounded, its header shape is checked in, and the
|
||||
parser now expects a compact 6-byte prefix plus separator byte before an embedded
|
||||
placed-structure-style dual-name row rather than treating the family as anonymous residue.
|
||||
- That exact `0x38a5/0x38a6/0x38a7` parser is now also wired through a lightweight CLI inspector
|
||||
and the normal save company/chairman analysis output, and grounded real saves now prove the
|
||||
same seam directly:
|
||||
`q.gms` exposes `live_record_count=3865`, prefix `0x0005d368/0x0001/0xff`, and first embedded
|
||||
names `TrackCapST_Cap.3dp` / `Infrastructure`; `p.gms` exposes the same structure with
|
||||
`live_record_count=2467`.
|
||||
- The placed-structure tagged save stream now also exposes repeated `0x55f1/0x55f2/0x55f3`
|
||||
triplets with dual name stems, a fixed five-`f32` policy row, and a compact `0x5dc1...0x5dc2`
|
||||
footer carrying one raw `u32` payload lane plus one live `i32` status lane, so the remaining
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue