You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/CORE_2_ACTUAL_EXPECTED_COMPARISON_DESIGN.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ Current state
19
19
- The runner reads and parses `input.json`.
20
20
- Malformed input JSON is handled deterministically.
21
21
- Missing conformance case files are covered by tests.
22
-
- The official conformance pack reports total=10 passed=10 failed=0.
22
+
- The official conformance pack reports total=11 passed=11 failed=0.
23
23
- Full verify execution is not implemented yet.
24
24
25
25
Target state
@@ -101,7 +101,7 @@ Reason-code implications
101
101
- Exact `reason_code` comparison will make reason code semantics stricter.
102
102
-`INTERNAL_ERROR` boundaries may need refinement.
103
103
-`INVALID_SNAPSHOT_SCHEMA` may later split into `INVALID_JSON` if partner feedback requires it.
104
-
-`UNSUPPORTED_PROFILE` and `MISSING_REFERENCE` should become stronger candidates for representable execution cases.
104
+
-`UNSUPPORTED_CANONICALIZATION_PROFILE` is represented by an official conformance case; unsupported reconstruction profile and missing-reference cases remain candidates for future coverage.
105
105
106
106
Non-goals
107
107
---------
@@ -118,7 +118,7 @@ Recommended next PRs
118
118
119
119
- Expand observed-result comparison coverage where new observed results are introduced.
120
120
- Keep public JSON report shape unchanged.
121
-
- Add representable `UNSUPPORTED_PROFILE`and `MISSING_REFERENCE` cases after comparison helper exists.
121
+
- Add representable unsupported reconstruction profile and missing-reference cases after comparison helper exists.
0 commit comments