Repository navigation
M2.14→M2.15 BCUGE: complete CFG/DAT/RIO bundles on verified MMS root without engine repin - #601
Conversation
…gine bundle without re-pin
…er and member summary
…er and member summary
…er and member summary
…ate/wrong-folder/partial transfers
…r catalog enrichment
|
Disposition: Integrated / superseded intermediate M2.14 COMTRADE-RIO compatibility milestone. This is PR tracking cleanup only; no merge to main or physical acceptance. Canonical replacement: #649 remains OPEN as a preserved integrated application lineage (head Unique delta — fully accounted for: All five changed files remain byte-identical in #649 (Git blob SHA verified individually): Safety: Original root FileDirectory authority, CFG/DAT/RIO exact-name/path matching, fail-closed ambiguous/orphan RIO, SHA-fenced transfer cache and no fabricated directory scans remain mandatory. No branches deleted and no mutation of ARIEC engine pins, main, stable v1.6.42 or CI/physical gates. Follow-up: #649 and RC qualification must still verify BCUGE/real-device FileDirectory, native download, COMTRADE bundle behavior and physical FAT before an R7/R10 mainline/source promotion. Closing this historical PR is not acceptance of subdirectory RIO or untested hardware. |
User acceptance: COMTRADE files named identically belong to one download
Supersedes blocked experimental consumer #600, whose engine pin replacement tripped physically anchored safety/interop CI guards. This safer branch is stacked on green #599, keeps exactly the validated ARIEC pin
036e2c00d83a0815b6160147b14ea05975057965, and does not bypass any engine guard..riofile from the same root MMS FileDirectory response with an already verified complete ARIEC CFG/DAT record and exactly matching directory and basename (ordinal). Reject alias duplicates, same-named other-folder files, or missing/mismatched server filename. No SCL or guessed paths.line_1, with per-selection membersCFG + DAT + RIOand exact count/bytes; orphan RIO remains browse-only.Informationkind is used strictly for transfer ordering; extension remains.rioand is never misrepresented as.inf. Future upstream ARIEC #170 can replace this compatibility seam after qualification.Coverage limitation: root FileDirectory RIO only; the historical engine does not reveal raw unknown extension entries from recursive subdirectory scans. Do not claim subdirectory RIO support without a new engine contract. No main merge or release until CI and BCUGE physical acceptance.