omena-semantic 0.1.7

Semantic boundary crate for Omena style analysis
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
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79

# `omena-semantic`

Internal Rust crate for the style semantic boundary.

This crate is intentionally small: it consumes the parser boundary from
`engine-style-parser` and exposes semantic-facing summaries without moving the
parser implementation or changing existing parser consumers.

Current public products:

- `omena-semantic.style-semantic-graph` — combined parser boundary,
  selector-identity, selector-reference, source-input evidence, promotion
  evidence, and lossless CST contract for semantic graph consumers.
- `omena-semantic.selector-identity` — canonical selector ids, BEM suffix
  identity, and rewrite-safety blockers.
- `omena-semantic.selector-references` — selector-scoped reference summaries
  and identity-preserving reference sites derived from `EngineInputV2`.
- `omena-semantic.design-token-semantics` — CSS custom property resolver
  readiness surface that exposes same-file and occurrence-level resolution
  counts, source-order facts, same-file cascade ranking signals,
  selector/wrapper context signals, and the remaining cross-file/package/theme
  gaps.
- `omena-semantic.promotion-evidence` — explicit readiness/gap checklist for
  promotion beyond output parity, including parser-backed design-token seed
  evidence from CSS custom properties.
- `omena-semantic.source-input-evidence` — `EngineInputV2`-backed reference
  site identity, binding origin, style module edge, value-domain explanation,
  value-domain derivation, and selector certainty reason evidence.
- `omena-semantic.lossless-cst-contract` — byte-span invariants used by precise
  rename, formatter, and recovery-oriented consumers.
- `omena-semantic.theory-observation-harness` — observation-only readiness
  summary for selector rewrite safety, source evidence explainability, semantic
  graph downstream readiness, and generic-vs-CME coupling boundaries.

Primary check:

- `cargo test --manifest-path rust/Cargo.toml -p omena-semantic`

CLI smoke:

```sh
printf '.button { &__icon {} }' \
  | cargo run --manifest-path rust/Cargo.toml -p omena-semantic --bin omena-semantic-boundary -- Component.module.scss
```

For `EngineInputV2` source-side evidence:

```sh
cat engine-input-v2.json \
  | cargo run --manifest-path rust/Cargo.toml -p omena-semantic --bin omena-semantic-source-evidence
```

For the combined style semantic graph product:

```sh
cat style-semantic-graph-input.json \
  | cargo run --manifest-path rust/Cargo.toml -p omena-semantic --bin omena-semantic-graph
```

For the theory observation harness:

```sh
cat style-semantic-graph-input.json \
  | cargo run --manifest-path rust/Cargo.toml -p omena-semantic --bin omena-semantic-observation
```

For the compact observation contract:

```sh
cat style-semantic-graph-input.json \
  | cargo run --manifest-path rust/Cargo.toml -p omena-semantic --bin omena-semantic-observation-contract
```

Downstream consumers can use either the free function or the
`TheoryObservationHarnessInput` trait. The trait is the dogfooding surface for
consumers that should depend on an observation contract instead of a concrete
builder entry point. Consumers that only need stable readiness state can call
`summarize_theory_observation_contract` or the trait method
`summarize_theory_observation_contract`.