[soulteary]

Problem

Several maintained guides and validation inventories still described native receive timestamps, explicit classic-on-FD frames and receive-own options as missing. Other text treated all timestamps as steady-clock values, omitted the per-device ownership path, or described configurable Session limits as absent.

Changes

Update both documentation editions, backend guides, API comments and the baseline inventory to match the current implementation. Clarify standard/extended-ID route keys versus the TX classic/FD override, timestamp provenance, opt-in echo, independent DeviceSession lifetimes, resource limits and the five-database analysis scope. Add missing navigation and distinguish Unreleased source APIs from published SDKs.

Retain fixed-version release, benchmark and hardware evidence unchanged. Production Python bindings, actual SDK Runtime sharing and deployment-specific native hardware acceptance remain unverified.

There are no runtime or API changes. All seven modified C++ files have identical non-comment tokens. The Python change is a module description; the JSON change updates descriptive capability/provenance text.

Validation

• Checked all 55 tracked Markdown documents, 377 relative file links and 12 local heading anchors; no missing targets.
• Clang-format 18 passed on the changed C++ files.
• 26 deployment-evidence tests and three analysis-database tests passed.
• git diff --check passed; signed commit verified.
• All 44 CI checks passed for c8a4a1183d0211dbde017e29bed5e70d19f0e582. Complete full-mode quality analysis passed with A+, 100/100: formatting 80/80 files and Cppcheck/Clang-Tidy 62/62 units each, no findings. There are no unresolved review threads.

Merged by the repository. This documents current source capabilities; it does not claim that Python integration or native hardware acceptance is complete.