Document Scriptorium as a Promptkit application

docs/operations.md

@@ -7,8 +7,11 @@ recovery for Scriptorium. It does not redefine invocation syntax, configuration
 fields, or HTTP wire behavior.
 
 - [CLI reference](cli.md): commands, output destinations, and exit codes.
-- [Configuration reference](config.md): configuration, prompt/profile/schema
-  formats, defaults, and credentials.
+- [Configuration reference](config.md): application settings, source
+  locations, defaults, and credential mapping.
+- [Promptkit framework formats](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.1.0/docs/formats.md):
+  prompt, profile, schema, execution-setting, and framework credential
+  contracts.
 - [HTTP API reference](api.md): route, request/response schema, status codes,
   limits, and HTTP artifact access.
 - [Consumer integration overview](consumers/api.md): caller responsibilities.
@@ -26,10 +29,10 @@ responsibilities.
 
 ## Deploy The Filesystem And Process
 
-Provide the process with readable prompt, profile, and schema sources. Keep
-prompt templates adjacent to the prompt definitions that reference them. For an
-HTTP deployment that accepts file artifacts, use a dedicated, narrow artifact
-directory rather than a general-purpose or sensitive filesystem tree.
+Provide the process with readable configured Promptkit prompt, profile, and
+schema sources that follow the tagged framework formats. For an HTTP deployment
+that accepts file artifacts, use a dedicated, narrow artifact directory rather
+than a general-purpose or sensitive filesystem tree.
 
 Run Scriptorium under an identity that can: