HAL9000
e121663ae7
CI / benchmark-publish (pull_request) Has been skipped
CI / lint (pull_request) Successful in 25s
CI / build (pull_request) Successful in 28s
CI / push-validation (pull_request) Successful in 22s
CI / helm (pull_request) Successful in 23s
CI / quality (pull_request) Successful in 1m2s
CI / security (pull_request) Successful in 1m11s
CI / typecheck (pull_request) Successful in 1m32s
CI / e2e_tests (pull_request) Successful in 3m19s
CI / unit_tests (pull_request) Successful in 5m5s
CI / docker (pull_request) Successful in 10s
CI / integration_tests (pull_request) Successful in 6m28s
CI / coverage (pull_request) Successful in 11m58s
CI / status-check (pull_request) Successful in 1s
CI / benchmark-regression (pull_request) Successful in 58m13s
The formal JSON Schema for auto_discovery in the Resource Type schema (§34650-34676) was missing three fields used by the built-in devcontainer-instance type example (§35283-35294): - parent_types: list of resource types that trigger auto-discovery - detection.scan_paths: relative paths to check for child resource presence - detection.activation: eager|lazy activation mode (default: lazy) The devcontainer-instance built-in type uses all three fields to express that it should be auto-discovered when a git-checkout resource is registered and a .devcontainer/devcontainer.json file is found. Without these fields in the formal schema, implementers could not determine the correct auto_discovery schema from the spec alone, causing the auto_discover_children() helper to use an incompatible schema. Fixes: #6291 Refs: ADR-043 (Devcontainer Integration)