Relaxed CLI requirements when defaults are specified in the profile or application defaults

architecture.md

@@ -527,33 +527,30 @@ The response should include:
 - artifact
 - validation
 - metadata
-- raw_model_output, optionally controlled by request or config
+- raw_model_output
 - error details, if applicable
 
 The HTTP layer should not contain business logic.
 
 ## CLI
 
-The CLI should also be thin.
+The CLI should be thin and call the same core use case as HTTP.
 
-It should support local development and pipeline usage.
-
-Suggested commands:
+Current command surface:
 
 - scriptorium run
-- scriptorium profiles list
-- scriptorium profiles inspect
+- scriptorium serve
 
-The run command should accept:
+The `run` command should accept:
 
 - profile ID
 - input mappings
 - variable mappings
 - output path, optional
 - profile directory
-- config path
+- optional model/endpoint overrides
 
-The CLI should call the same use case used by the HTTP API.
+If model/endpoint overrides are omitted, profile model defaults should be used.
 
 ## Configuration