Complete relative import destination documentation audit
This commit is contained in:
@@ -4,8 +4,8 @@ Status:
|
||||
|
||||
- Input destinations are implemented on the ConfigKit development branch
|
||||
(placement baseline reviewed at `315f464`).
|
||||
- Relative import destinations have been accepted and implementation is in
|
||||
progress; the [roadmap](relative-import-destinations.md) owns delivery scope.
|
||||
- Relative import destinations have been accepted and implemented; the
|
||||
[roadmap](relative-import-destinations.md) records their completed delivery.
|
||||
- Source specification headers have been partially accepted in the shared
|
||||
application-version-policy form described below. This does not accept
|
||||
PromptKit's original independent collection-header semantics. Design and
|
||||
@@ -193,9 +193,10 @@ An input with imports enabled must be able to use its existing source-root
|
||||
destination. The directive remains structural configuration, not an application
|
||||
field below that destination.
|
||||
|
||||
Without an explicit relative destination, imports inherit their importing
|
||||
input's destination, including transitive imports. Import paths continue to
|
||||
resolve relative to their declaring source's filesystem context. A mounted document must not send
|
||||
When an import omits `destination` or supplies an empty list, it inherits its
|
||||
importing document's effective destination, including transitively. An explicit
|
||||
sequence appends to that destination. Import paths continue to resolve relative
|
||||
to their declaring source's filesystem context. A mounted document must not send
|
||||
its imported application fields back to the configuration root accidentally.
|
||||
|
||||
Existing opt-in, containment, missing-input, cycle, and repeated-source behavior
|
||||
@@ -351,7 +352,7 @@ new coercion, or per-collection checker should be inferred from partial acceptan
|
||||
|
||||
## Requested Addition: Relative Import Destinations
|
||||
|
||||
Disposition: accepted; implementation is in progress under the
|
||||
Disposition: accepted and implemented under the completed
|
||||
[relative import destinations roadmap](relative-import-destinations.md).
|
||||
The behavior below records the accepted capability; exact syntax and completion
|
||||
status follow that work, rather than implying a released feature.
|
||||
|
||||
Reference in New Issue
Block a user