Make Pheon structural review results self-contained
Capture revision metadata, cell presence and attributes, and structured diagnostics in owned comparison results. Derive outcomes and render text, JSON, and hierarchy reports without retaining source documents. Keep derived descriptions and graph analysis in their renderers. Use pheon-structural-v1 and PHEON_LAYER_NAMES_V1 consistently, expose helpers through their defining modules, and remove obsolete re-exports. Update user guides and report fixtures without changing schema version 1. Cover dropped inputs, diagnostic ordering, absent and empty cells, offset independence, and CLI failures. All 92 Rust tests pass in debug and release; report and hierarchy goldens retain their behavior.
This commit is contained in:
parent
a723ba2265
commit
df62677f5c
1 changed files with 870 additions and 504 deletions
|
|
@ -23,7 +23,7 @@ byte. Input and annotation validation finish before the output is created.
|
|||
|
||||
## Annotation format
|
||||
|
||||
A text label whose exact string is `KLAMATH_LAYER_NAMES_V1` identifies a carrier
|
||||
A text label whose exact string is `PHEON_LAYER_NAMES_V1` identifies a carrier
|
||||
pair in its cell. Every other text label on that pair in the same cell is a
|
||||
mapping of the form:
|
||||
|
||||
|
|
@ -33,7 +33,7 @@ layer:datatype:name
|
|||
|
||||
For example, `1:0:WG` names pair `(1, 0)` as WG. Numbers are unsigned 16-bit
|
||||
decimals. The name must be nonempty UTF-8 and may contain colons; only the first
|
||||
two colons separate fields. The legacy marker remains part of the format.
|
||||
two colons separate fields.
|
||||
|
||||
Mappings are collected across the library. Identical duplicates are accepted;
|
||||
conflicting names for the same pair are errors. Recognized annotation labels
|
||||
|
|
|
|||
Loading…
Reference in a new issue