# Future Work The completed CommandKit adoption, implementation plan, Narratio request, and earlier adoption/policy roadmaps remain available in [Git history](https://forge.maximumdirect.net/eric/scriptorium/src/commit/f5573f7c8f2ddf0d69414a05c978c8d6cfe291e7/docs/roadmap). Current behavior belongs to the [CLI](../cli.md), [configuration](../config.md), [HTTP API](../api.md), and other canonical contracts. ## Deferred Directions - **HTTP design review:** separate work before v1.0; CommandKit adoption retained the existing HTTP interface and execution-report representation. - **Embedded framework configuration:** deferred pending upstream support for a native handoff preserving resource context and inspection evidence. The current application settings select a separate PromptKit entry file. - **Dynamic resource completion:** possible enhancement beyond native command, flag, static-value, and path completion. - **Configurable namespace defaults and automatic report collection:** possible enhancements if concrete operator needs arise. Current callers select explicit namespaces and report paths and own retention. - **Selected-format accessor:** optional upstream CommandKit capability; not a prerequisite for the completed stdout-based generation/report interface. These directions do not select additional APIs, command syntax, implementation order, or delivery dates. Independently versioned report envelopes and programmatic invocation-failure categories remain potential upstream discussions if a concrete consumer need emerges, not missing migration requirements.