docs(spec): align checkpoint trigger names and config key path with implementation #10837
@@ -47,6 +47,16 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
|
||||
strict `is True or == 1` instead of `bool()` to prevent truthy non-boolean
|
||||
YAML values (e.g. `unsafe: "no"`) from being treated as unsafe.
|
||||
|
||||
- **Checkpoint Trigger Names and Config Key Path** (#5163): Aligned
|
||||
`docs/specification.md` and `docs/reference/checkpointing.md` with the
|
||||
implementation. Trigger names `on_tool_write` and `on_tool_write_complete`
|
||||
are renamed to `before_tool_execute` and `after_tool_execute` to match
|
||||
`src/cleveragents/tool/runner.py` (`DEFAULT_AUTO_TRIGGERS`) and
|
||||
`src/cleveragents/application/services/config_service.py`. The configuration
|
||||
reference table entry is moved from `sandbox.checkpoint.auto-create-on` to
|
||||
`core.checkpoints.auto-create-on` to match the implementation's
|
||||
`_register("core", "checkpoints.auto_create_on", ...)` call.
|
||||
|
||||
- **UKO Runtime Layer 2 (Paradigm) Indexing** (#9351): Added missing `rdf:type
|
||||
uko-oo:Class` triple emission in `PythonAnalyzer._extract_class()` so that
|
||||
Python class definitions are now correctly classified at layer 2 (paradigm/OO)
|
||||
|
||||
Reference in New Issue
Block a user