docs(spec): add CHANGELOG entry for custom resource type YAML format fix (#5622)
CI / lint (pull_request) Successful in 41s
CI / quality (pull_request) Successful in 56s
CI / typecheck (pull_request) Successful in 1m10s
CI / security (pull_request) Successful in 1m12s
CI / build (pull_request) Successful in 36s
CI / helm (pull_request) Successful in 32s
CI / unit_tests (pull_request) Successful in 7m25s
CI / push-validation (pull_request) Successful in 24s
CI / docker (pull_request) Successful in 1m52s
CI / integration_tests (pull_request) Successful in 23m5s
CI / coverage (pull_request) Successful in 15m35s
CI / status-check (pull_request) Successful in 3s
CI / lint (pull_request) Successful in 41s
CI / quality (pull_request) Successful in 56s
CI / typecheck (pull_request) Successful in 1m10s
CI / security (pull_request) Successful in 1m12s
CI / build (pull_request) Successful in 36s
CI / helm (pull_request) Successful in 32s
CI / unit_tests (pull_request) Successful in 7m25s
CI / push-validation (pull_request) Successful in 24s
CI / docker (pull_request) Successful in 1m52s
CI / integration_tests (pull_request) Successful in 23m5s
CI / coverage (pull_request) Successful in 15m35s
CI / status-check (pull_request) Successful in 3s
This commit is contained in:
+8
-1
@@ -941,6 +941,13 @@ Documentation Report (Cycle N)` issues every 10 cycles (~3.3 hours). The manager
|
||||
|
||||
### Fixed
|
||||
|
||||
- **Custom resource type YAML format** (#5622): Corrected three inconsistent YAML format
|
||||
examples in `docs/specification.md` to match the canonical format defined in
|
||||
`docs/schema/resource_type.schema.yaml`. Field names updated: `resource_kind`,
|
||||
`cli_args`, `parent_types`, `capabilities.read/write/sandbox/checkpoint`,
|
||||
`handler: module:ClassName`, and `child_types` as flat string list. Added documentation
|
||||
explaining per-child-type auto-discovery configuration in the `auto_discovery` block.
|
||||
|
||||
- **Plan Concurrency Race Condition** (#7989): Fixed critical race condition in `execute_plan()` and
|
||||
`apply_plan()` where concurrent CLI/worker sessions could simultaneously modify the same plan,
|
||||
corrupting plan state. `LockService` is now wired into the plan lifecycle with plan-level advisory
|
||||
@@ -1092,4 +1099,4 @@ iteration` and data corruption under concurrent plan execution. All public
|
||||
- **TUI -- Permission Question Widget**: A new inline `PermissionQuestionWidget`
|
||||
renders permission requests directly in the conversation stream for single-file
|
||||
operations. Users can allow/reject with single-key shortcuts (`a`/`A`/`r`/`R`),
|
||||
navigate with arrow keys, confirm with `Enter`, or press `v` to open the full
|
||||
navigate with arrow keys, confirm with `Enter`, or press `v` to open the full
|
||||
Reference in New Issue
Block a user