Clean up roadmap and troubleshooting documentation
This commit is contained in:
@@ -247,7 +247,7 @@ The completed feature includes:
|
||||
of unbounded state growth;
|
||||
- an Accepted ADR documenting the architectural decision; and
|
||||
- updates to canonical architecture, CLI, operations, configuration,
|
||||
troubleshooting, integration, internal, testing, and release documentation
|
||||
integration, internal, testing, and release documentation
|
||||
where their contracts change.
|
||||
|
||||
## Non-Goals
|
||||
@@ -296,16 +296,11 @@ shares mutable filesystem state.
|
||||
|
||||
## Relationship To Domain-Specific Profiles
|
||||
|
||||
The domain-specific profile feature can be implemented before this refactor,
|
||||
but it should not add new historical compatibility or durable-provenance
|
||||
commitments. Profile inspection, selection, override precedence, and effective
|
||||
model resolution remain active-workflow behavior and survive the state change.
|
||||
|
||||
The domain-profile roadmap and implementation plan should acknowledge that
|
||||
prompt artifacts from version `1.0.1` need not remain readable after prompts
|
||||
advance to `1.1.0`. Existing state persistence may remain temporarily while
|
||||
the profile feature lands, but it should not be expanded or treated as the
|
||||
target architecture.
|
||||
The implemented domain-specific profiles do not add historical compatibility
|
||||
or durable-provenance commitments. Profile inspection, selection, override
|
||||
precedence, and effective model resolution remain active-workflow behavior and
|
||||
survive the state change. Existing prompt artifacts need not remain readable
|
||||
after this refactor and must not constrain the target architecture.
|
||||
|
||||
## Completion Criteria
|
||||
|
||||
|
||||
Reference in New Issue
Block a user