docs(spec): extend auto_discovery schema with parent_types and detection fields #6313

Closed
HAL9000 wants to merge 1 commits from spec/devcontainer-auto-discovery-schema into master

1 Commits

Author SHA1 Message Date
HAL9000 9ebb70b909 docs(spec): extend auto_discovery schema with parent_types and detection fields
CI / benchmark-publish (pull_request) Has been skipped
CI / build (pull_request) Successful in 23s
CI / helm (pull_request) Successful in 23s
CI / push-validation (pull_request) Successful in 18s
CI / lint (pull_request) Successful in 3m21s
CI / quality (pull_request) Successful in 3m39s
CI / typecheck (pull_request) Successful in 4m24s
CI / security (pull_request) Successful in 4m28s
CI / e2e_tests (pull_request) Successful in 6m34s
CI / unit_tests (pull_request) Successful in 8m32s
CI / integration_tests (pull_request) Failing after 14m21s
CI / docker (pull_request) Successful in 2m16s
CI / coverage (pull_request) Successful in 14m1s
CI / status-check (pull_request) Failing after 2s
CI / benchmark-regression (pull_request) Successful in 56m57s
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)
2026-04-12 04:06:28 +00:00