aion-context 1.0.0

Cryptographically-signed, versioned business-context file format
Documentation 
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

<!--
Thanks for the PR. Please fill in the sections below — they make the
review faster and the merge log readable later.
-->

## Summary

<!-- 1–3 bullets of what changed and why. Link related issue: "Closes #N". -->

-

## Test plan

<!-- How did you verify this works? Local commands you ran, output you checked. -->

- [ ] `cargo test` passes
- [ ] `cargo clippy --all-targets -- -D warnings` clean
- [ ] `cargo fmt --check` clean
- [ ]

## Breaking change

<!--
Yes / No. If yes, describe what breaks and what migration callers need.
Anything that touches the on-disk file format, public API surface, CLI
exit codes, or tracing event names is a breaking change.
-->

- [ ] No breaking change
- [ ] Yes — described below

## Related

<!-- Issues, RFCs, prior PRs. -->

- Closes #
- RFC:

## Reviewer checklist

- [ ] No `unwrap` / `expect` / `panic!` / `todo!` / `unreachable!` in library code
- [ ] No raw `==` on signature, hash, or key bytes (use `subtle::ConstantTimeEq`)
- [ ] If touching crypto / signature / audit chain: `crypto-auditor` agent has reviewed
- [ ] If adding a new `pub` item: doc comment + at least one example
- [ ] If changing on-disk format: an RFC exists, format version is bumped