eric/audita
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 6 Wiki Activity

Plan ReleaseKit adoption and a major-release hard cutover

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-08 01:40:10 +00:00
parent 46765bd326
commit 259f728f20
3 changed files with 84 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
docs/roadmap/configkit.md
View File

@@ -91,21 +91,23 @@ locations and import defaults still need selection before changing operator
behavior. Preserve explicit-path error evidence and distinguish optional from
required imports using native semantics.
**Alternative:** configure the native API with today's two system locations and
imports disabled. This eases installation migration and remains supported, but
should be retained only if deployment requirements justify it; historical behavior
alone does not satisfy the suite-alignment objective. Conversely, enabling all
**Alternative:** configure the native API with two system locations and imports
disabled if deployment requirements justify that source-selection policy. This
limits discovery flexibility and must stand on its own merits; compatibility with
today's installations carries no weight. Conversely, enabling all
possible searches/imports without a selected convention can load unintended
sources and is not required for full API adoption.
### Application Schema Version
**Recommendation:** retain `version: 2` only if the resulting application fields
and meaning remain coherent after PromptKit ownership is settled. Do not confuse
it with the library version or PromptKit's source header. This avoids meaningless
schema churn while allowing deliberate field migration.
**Recommendation:** design the application schema around the target ownership
boundaries, then choose its version to describe that contract. Keeping `version: 2`
is reasonable only if its meaning remains coherent; compatibility with existing
files is not a selection criterion. Do not confuse the application schema version
with the library version or PromptKit's source header.
**Alternative:** introduce a new application schema version if backend or
credential ownership changes make existing files misleading. It provides a clear
migration boundary, at the cost of updating files and guidance. Decide from the
final schema, not from dependency version numbers alone.
migration boundary; the version alone does not explain the new contract, so
hard-cutover guidance still needs to describe it. Decide from the final schema,
not from dependency version numbers alone, and do not add legacy-schema support.