1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
//! rkyv section payloads for the core graph provider.
//!
//! Section payload format: rkyv 0.8 archives over sorted `Vec<(K, Row)>`
//! intermediates per spec 04 §4.3 / decision D14. Per-row property bags
//! are postcard-encoded inside an `Arc<[u8]>` field on each archived row until
//! every stored `Value` variant has rkyv archivability.
//!
//! Compatibility note: per spec 04 §4.6, any format change to a CORE section
//! bumps the snapshot envelope version so older snapshots fail with
//! `PersistError::UnsupportedVersion` instead of being decoded as garbled
//! bytes. BRIEF-Item-4a STEP 9 exercises this: `CORE/NODE` / `CORE/EDGE` now
//! persist the explicit external `NodeId` / `EdgeId` per row (read from the
//! `row_to_id` column) instead of synthesizing `row + 1`, so a future
//! 4b-compacted snapshot whose ids != row+1 round-trips. That change bumped
//! `SNAPSHOT_VERSION_MINOR` 0 -> 1 (selene-persist); pre-STEP-9 (minor 0)
//! snapshots are cleanly rejected — a clean break, not a dual decoder
//! (deferred to 4c per the D14 amendment).
//! `CORE/VIDX` later added optional IVF construction config beside HNSW config,
//! which bumped `SNAPSHOT_VERSION_MINOR` 2 -> 3 for the same clean-break reason.
//! The typed-descriptor stream then added `decimal_type` /
//! `character_string_type` / `byte_string_type` fields to the `CORE/GTYP`
//! `PropertyTypeDef` archive (plus descriptor variants on
//! `PropertyElementType` / `RecordFieldType`), which bumped
//! `SNAPSHOT_VERSION_MINOR` 3 -> 4 and the section-internal `GTYP_VERSION`
//! 1 -> 2.
//! Edge-property index registrations then added an entity discriminator to
//! `CORE/SCMA`, which bumped `SNAPSHOT_VERSION_MINOR` 4 -> 5 and
//! `SCMA_VERSION` 2 -> 3.
//!
//! Schema rows are stored in canonical wire order by their string keys and are
//! decoded defensively before duplicate validation.
// Re-exported to `core_provider` so the cap-boundary unit test can reach it.
pub use ensure_section_within_cap;
pub use ;
pub use ;
pub use SCMA_VERSION;
pub use ;