base-layer/commandkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Define original-value text templates and YAML fallback

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-06 21:40:52 +00:00
parent 408383db60
commit c52034f3fe
2 changed files with 89 additions and 52 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/roadmap/future.md
View File

@@ -163,13 +163,15 @@ steps. No delivery date or final API is selected here.
The [shared core report output prerequisite](promptkit-v0.19.0.md#shared-core-report-output-prerequisite)
is now part of the working adoption roadmap. It records application-owned
content selection, core-owned rendering, a text fallback with optional templates,
content selection, core-owned rendering, text output with optional templates,
and universal format availability. Explicit operator selection wins; otherwise
core selects text for a supplied template or chooses from the logical report
shape. Command-specific format defaults are omitted from the initial API.
Plain text, YAML, and JSON land together. The roadmap selects standard Go JSON
serialization conventions for ordinary report values, with separate core
adaptation for native configuration YAML. Text-template and native-document
serialization conventions for core-serialized report values, with separate core
adaptation for native configuration YAML. Text templates use Go's `text/template`
with the original Go report value. Without a template, structured text output
reuses the YAML renderer; template errors never trigger fallback. Native-document
decisions remain there. XML is removed from current consideration.
Markdown and other potential formats are not selected for this adoption; new
core formats will work with