Repository navigation
docs: specify interactive migration roadmap - #1
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Users currently migrate by source ID/title and explicit CLI options. This defines the fork evolution for interactive selection/preview, target naming, lineage, handoff/update and an optional local dashboard.
The specification defines requirements R01–R14, source/target profiles, native capability proofs, versioned checkpoints, recovery, usage provenance and web access boundaries. The implementation plan was derived after the initial spec review and maps phases 2–6 to modules, tasks, acceptance gates and independent releases. Shared installation is outside both documents.
Same-ID updates remain a separate deliverable requiring a native concurrency/storage contract; creating a linked new session does not satisfy that requirement. Codex titles and usage estimates likewise require explicit proof/provenance. Frameworks are proposed as optional extras, not introduced by this documentation change.
Validation: independent integrated documentation review approved; local Markdown links, whitespace and no-index diff checks passed. Runtime tests are not applicable: no runtime, dependencies, migration or native session operation is changed. Implementation scope remains subject to operator approval. These documents are separate from the OpenCode adapter PR #17.