Skip to content

docs: add upgrade-coven guide (guides checkpoint 7)#42

Merged
BunsDev merged 2 commits into
mainfrom
docs/guides-upgrade
Jul 22, 2026
Merged

docs: add upgrade-coven guide (guides checkpoint 7)#42
BunsDev merged 2 commits into
mainfrom
docs/guides-upgrade

Conversation

@BunsDev

@BunsDev BunsDev commented Jul 22, 2026

Copy link
Copy Markdown
Member

Summary

Checkpoint 7 of the guides-section goal, stacked on #41: the Upgrade Coven guide — safe upgrade as a verified state transition, not just a reinstall.

Changes

  • content/docs/guides/upgrade-coven.mdx — 5 steps: capture live state (sessions --plain, daemon status, --version) → npm/source upgrade → daemon restart (supervisor caveat) → health + apiVersion + capabilities verification → session-survival check; troubleshooting footer incl. engine pin lag
  • content/docs/guides/index.mdx — catalog row linked
  • content/docs/guides/meta.json — page registered
  • scripts/check-guides-docs.mjs — pins for coven --version, /api/v1/capabilities, sessions --all --plain, and the recovery-upgrades cross-link

Sources

Step order mirrors the upgrade flow in daemon/recovery-upgrades.mdx (finish sessions → status → install → restart → health → apiVersion → capabilities); restart/stop output strings verified against run_daemon_command (../coven main.rs:2714+); ledger-survival and orphaned-session framing from daemon/lifecycle.mdx + recovery-upgrades.mdx.

Validation

  • check-guides-docs, english-only, no-leading-h1, mermaid-parse, validate-links (0 errors) ✅
  • npx fumadocs-mdx + npx tsc --noEmit + npx next build ✅ — all six guide pages prerendered

Sixth catalog entry: pre-upgrade state capture, npm/source upgrade,
daemon restart, health + apiVersion/capabilities verification, and
session-survival check. Flow mirrors daemon/recovery-upgrades.mdx;
restart output verified against run_daemon_command.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings July 22, 2026 00:13
@vercel

vercel Bot commented Jul 22, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
coven-docs Ready Ready Preview Jul 22, 2026 12:34am

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new Guides-section page that documents a safe Coven upgrade flow as a verified state transition (capture state → upgrade → restart → API/contract verification → session survival), and wires it into the guides nav and validation tooling.

Changes:

  • Added a new Upgrade Coven guide with an ordered, verification-driven upgrade procedure and troubleshooting footer.
  • Registered the new guide in the Guides catalog and meta.json navigation.
  • Extended the Guides docs check script to require the new page and pin key command/endpoint mentions and a required cross-link.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
scripts/check-guides-docs.mjs Adds upgrade-coven to required guide pages, pins new required mentions, and enforces a recovery-upgrades cross-link.
content/docs/guides/upgrade-coven.mdx New “Upgrade Coven” step-by-step guide covering pre-checks, upgrade paths, daemon restart, health/capabilities verification, and session survival checks.
content/docs/guides/meta.json Registers upgrade-coven in the Guides section page list.
content/docs/guides/index.mdx Adds the Upgrade Coven row as a live link in the guides catalog.

@BunsDev
BunsDev changed the base branch from docs/guides-failed-install to main July 22, 2026 00:39
@BunsDev
BunsDev merged commit 6172771 into main Jul 22, 2026
1 check passed
@BunsDev
BunsDev deleted the docs/guides-upgrade branch July 22, 2026 00:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants