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

Select report formats automatically from content and templates

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-06 20:05:24 +00:00
parent ffe568b6f0
commit e82101434f
2 changed files with 124 additions and 85 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/roadmap/future.md
View File

@@ -70,8 +70,8 @@ subcommands. The roadmap records the agreed explanation modes and help behavior;
[OD-6](promptkit-v0.19.0.md#od-6-failure-evidence-and-structured-diagnostic-delivery)
selects optional validation details, a concise default, and available evidence
on failure. OD-8 selects focused display, source selection, and report filters.
Initial report content, default preferences, and filter spellings are selected
in the roadmap; core owns universal format selection. The
Initial report content, text templates, and filter spellings are selected
in the roadmap; core owns universal and automatic format selection. The
remaining layout details will be evaluated through implementation and beta use.
It also includes focused effective display,
source-ID selection, metadata/diagnostic filters, independent comparison
@@ -164,11 +164,13 @@ 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,
universal format availability, and optional command defaults that otherwise
defer to core policy. Plain text, YAML, and JSON are the target formats;
representation, template, native-document, and delivery-staging details 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
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; representation, template, and
native-document details 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
existing commands without per-command adoption.
Error-conversion helpers such as `WarnError` remain deferred pending demonstrated