docs: plan single coven distribution#278
Merged
Merged
Conversation
Documents the path for making coven the user-facing command for daemon, CLI, and Coven Code workflows while preserving the adapter boundary. Verification: git diff --check. Co-authored-by: Nova <nova@opencoven.ai>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds an implementation plan documenting how to converge on coven as the single user-facing command for the daemon, CLI/TUI, and Coven Code workflows, while keeping Coven Code as a managed adapter boundary until the contract stabilizes.
Changes:
- Add a phased rollout plan covering compatibility floors/visibility, a
coven codealias, capability reporting, and a later packaging decision. - Define expected Cave UX for compatibility warnings vs optional updates.
- Outline verification steps for both Cave and Coven changes during rollout.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| 1. **User-facing command stays `coven`.** Users should not need to remember whether a workflow belongs to `@opencoven/cli` or `coven-code`. | ||
| 2. **Coven Code becomes an adapter first.** `coven code` should launch the code workflow through an adapter boundary before any repo/package merge. | ||
| 3. **The daemon remains the source of runtime truth.** Cave and other clients keep handshaking through `/api/v1/health` and capability discovery. | ||
| 4. **Release compatibility is explicit.** Cave should warn when installed `coven` or `coven-code` versions are below the app's minimum compatible version, and show ordinary update notices separately. |
|
|
||
| ## Phase 1 — Compatibility and Release Visibility | ||
|
|
||
| **Outcome:** Cave can tell users when Cave itself, `coven`, or `coven-code` has an update, and it can distinguish ordinary updates from versions too old for the current Cave build. |
Comment on lines
+108
to
+115
| ```json | ||
| { | ||
| "id": "coven-code", | ||
| "installed": true, | ||
| "version": "0.0.22", | ||
| "command": "coven code" | ||
| } | ||
| ``` |
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
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.
Summary
coventhe single user-facing command for daemon, CLI/TUI, and Coven Code workflowscoven code, adapter capability reporting, and the later packaging decisionVerification
git diff --check