Skip to content

feat(engine): /doctor /maintain /bootstrap as first-class commands#34

Open
abdout wants to merge 1 commit into
feat/macos-scriptsfrom
feat/engine-integration
Open

feat(engine): /doctor /maintain /bootstrap as first-class commands#34
abdout wants to merge 1 commit into
feat/macos-scriptsfrom
feat/engine-integration

Conversation

@abdout
Copy link
Copy Markdown
Contributor

@abdout abdout commented May 16, 2026

Summary

Engine integration for the v2 scripts. The new doctor, maintain, and bootstrap commands now behave like every other Kun keyword: typed in chat, recognized by the keyword registry, surfaced as slash commands, and discoverable in c sessions.

What's in the PR

File What
.claude/commands/doctor.md New /doctor slash command (62 lines)
.claude/commands/maintain.md New /maintain slash command (44 lines)
.claude/commands/bootstrap.md New /bootstrap slash command (60 lines)
.claude/CLAUDE.md Adds 3 rows to Tier 2 keywords + 3 rows to slash command table
.claude/scripts/finish.ps1 One-line shim → bootstrap.ps1 (alias per spec)
.claude/scripts/finish.sh One-line shim → onboarding-mac.sh
next.config.ts Adds /install.sh, /finish.sh, /doctor.sh redirects (mirroring the Windows ones)

How the new keywords flow

User types in chat            Harness picks up           Action
─────────────────             ─────────────────          ─────────
"doctor"           →   c "/doctor"           →   runs ~/.claude/scripts/doctor.ps1 (or .sh)
"maintain install" →   c "/maintain install" →   runs maintain.ps1 -Install
"doctor fix"       →   c "/doctor fix"       →   doctor.ps1 -Fix
"bootstrap dry-run"→   c "/bootstrap dry-run"→   bootstrap.ps1 -DryRun

Auto-registered as skills — verified the harness picked up bootstrap, doctor, maintain immediately after the markdown files were committed:

- bootstrap: Bootstrap — Single-paste Cold Start
- doctor: Doctor — Health, Updates, Self-repair
- maintain: Maintain — Daily Heartbeat

Canonical pastes — now both OS forms work

# Windows
irm https://kun.databayt.org/install | iex
# macOS / Linux
curl -fsSL https://kun.databayt.org/install.sh | bash

Both redirect to the canonical scripts in databayt/kun/main/.claude/scripts/.

Test plan

  • Three slash commands auto-registered as skills (verified)
  • CLAUDE.md keyword table now includes the new keywords (visible to readers + Claude Code)
  • c "/doctor" from inside a session runs doctor.ps1 and renders the output
  • c "/maintain install" arms the scheduled task
  • curl -fsSL https://kun.databayt.org/install.sh | bash resolves to onboarding-mac.sh after Vercel deploy

Dependencies

This branch stacks on feat/macos-scripts (PR #33). Merge order:

#29 → #30 → #31 → #32 → #33 → this PR → #25

🤖 Generated with Claude Code

Wraps up engine integration of the v2 scripts. The new scripts now
behave like every other Kun keyword: typed in chat, recognized by
the keyword registry, surfaced as slash commands.

- Three new .claude/commands/*.md slash commands (doctor, maintain,
  bootstrap). Auto-registered as skills by the harness — verified
  the bootstrap/doctor/maintain entries appear in the available
  skills list immediately after the files were written.
- CLAUDE.md Tier 2 standalone tools table gains 3 keyword rows.
- CLAUDE.md slash command table gains 3 command rows.
- New finish.ps1 / finish.sh shims — alias for bootstrap.ps1 /
  onboarding-mac.sh respectively (the spec called this out as a
  one-line wrapper since every bootstrap step is already
  idempotent — no separate "resume" mode needed).
- next.config.ts adds 3 redirects for the macOS curl form:
    /install.sh → onboarding-mac.sh
    /finish.sh  → onboarding-mac.sh
    /doctor.sh  → doctor.sh
  Mirroring the 3 Windows redirects already in place.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented May 16, 2026

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

Project Deployment Actions Updated (UTC)
kun Ready Ready Preview, Comment May 16, 2026 4:28pm

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.

1 participant