Document prompt-owned schemas and finalize migration
This commit is contained in:
@@ -86,7 +86,10 @@ returning and retains no source capability for public inspection.
|
||||
Prompt materialization shares a lazy metadata snapshot across root and collection
|
||||
resources during construction, avoiding a full metadata copy per collection.
|
||||
Input metadata, message content and templates, and output contracts are captured
|
||||
separately before the definition, inspection, and hash are assembled.
|
||||
separately before the definition, inspection, and hash are assembled. Schema
|
||||
root and source-relative file bindings capture the effective field context
|
||||
without opening schema files; capabilities are excluded from the hash. Inline
|
||||
schema values and file-reference strings participate in the definition hash.
|
||||
|
||||
Normalization and defaults are recorded at individual resolved field paths,
|
||||
including message roles and cache controls. List indexes identify fields for
|
||||
@@ -212,18 +215,20 @@ buffer-to-string copy. The
|
||||
|
||||
## Schemas And Output Validation
|
||||
|
||||
`internal/validate` provides validators backed by an operating-system
|
||||
filesystem or an `fs.FS`. Invalid generated content is returned as a validation
|
||||
`internal/validate` prepares a source-neutral input containing an output contract
|
||||
and an optional bound `fs.FS` file. Invalid generated content is returned as a validation
|
||||
result; inability to load, register, or compile a schema is an operational
|
||||
error. Basic validation checks body emptiness on the byte slice directly
|
||||
instead of first making a response-sized string copy.
|
||||
|
||||
Every preparation operation creates one operation-local validation plan. None,
|
||||
basic, and JSON modes retain the effective output contract without source
|
||||
access. JSON Schema mode loads the root document once, compiles its declared
|
||||
access. JSON Schema mode uses the captured inline document or loads the bound
|
||||
root document once, compiles its declared
|
||||
schema locations, and retains the compiled root validator. External resources
|
||||
are rejected without file or network loading; in-document references remain
|
||||
supported. Root resources use canonical escaped file or private-scheme URLs. The
|
||||
supported. Bound files use canonical escaped private-scheme URLs; inline values
|
||||
use a stable private retrieval URL. The
|
||||
provider-facing structured-output metadata uses the root document captured by
|
||||
the same plan. Its detached schema document is not revalidated against the
|
||||
runtime provider-value copier's traversal limits. Smoke inference uses a
|
||||
|
||||
Reference in New Issue
Block a user