context loading, path resolution, form state, dynamic rules, and provider-neutral assessment runner/cache boundary
This commit is contained in:
parent
eccf1874fb
commit
8361f9ea45
29 changed files with 2809 additions and 65 deletions
25
examples/runtime/runtime-expected-diagnostics.md
Normal file
25
examples/runtime/runtime-expected-diagnostics.md
Normal file
|
|
@ -0,0 +1,25 @@
|
|||
# Runtime Expected Diagnostics
|
||||
|
||||
These examples are meant for manual inspection and future snapshot fixtures.
|
||||
|
||||
```text
|
||||
mkt contract check examples/runtime/workplan-done-missing-decision.md \
|
||||
--contract examples/runtime/workplan-dynamic.contract.md \
|
||||
--format text
|
||||
```
|
||||
|
||||
Expected diagnostic:
|
||||
|
||||
- `runtime.section.missing`: status `done` requires a `Decision Point` section.
|
||||
|
||||
```text
|
||||
mkt contract check examples/runtime/business-letter-prefill.md \
|
||||
--contract examples/contracts/business-letter.contract.md \
|
||||
--context examples/runtime/business-letter.context.yaml \
|
||||
--format text
|
||||
```
|
||||
|
||||
Expected runtime utility:
|
||||
|
||||
- `recipient_name` and `sender_name` are prefilled from context.
|
||||
- No field-missing diagnostic is emitted for those fields.
|
||||
Loading…
Add table
Add a link
Reference in a new issue