@clubnet/seedclub 0.2.29 → 0.2.30

package/README.md

@@ -28,14 +28,11 @@ seedclub
 
 ### First run
 
-On a fresh install, the normal setup flow is:
-
 1. Run `seedclub`
-2. Seed Club auth opens automatically
-3. `/login` to sign in to a model provider such as Anthropic, OpenAI, or Gemini
-4. `/model` to choose the model you want to use
-
-After that, run `/seedclub` to open the main Seed Club menu.
+2. Complete Seed Club sign-in when the browser opens
+3. Run `/login`
+4. Run `/model`
+5. Open `/seedclub`
 
 ### Alternative: curl | bash
 
@@ -45,17 +42,15 @@ curl -fsSL https://raw.githubusercontent.com/seedclub/seedclub-agent/main/instal
 
 ### Package access
 
-`@clubnet/seedclub` is a public npm package. Install access is open; runtime access is enforced by Seed Club auth inside the app.
+`@clubnet/seedclub` is a public npm package. Install access is open; runtime access is enforced inside the app.
 
 ## Core workflow
 
-The normal interactive flow is:
-
 1. Start the app with `seedclub`
-2. Complete Seed Club auth when the browser opens
+2. Complete Seed Club sign-in when the browser opens
 3. Complete `/login` and `/model` if this is your first run
 4. Open `/seedclub`
-5. Choose the CRM, meetings, media, recordings, or transcript workflow you need
+5. Choose the workflow you need
 
 ## Commands
 
@@ -70,233 +65,6 @@ The normal interactive flow is:
 
 Natural-language transcript retrieval is also supported (no slash command required). Examples: `download vibhu transcripts from 11am`, `i need transcripts for all guests on 11am last week`. Seed Club will run metadata-first export confirmation and then write VTT files.
 
-## Auth
-
-There are two separate auth layers in the product:
-
-1. Seed Club auth: auto-start on launch or `/connect`
-   This connects the CLI to your Seed Club account so Seed Club tools and commands can read and write account data.
-2. Model auth: `/login`
-   This signs you into the LLM provider you want the agent to use.
-3. Personal calendar connect: `/connect-calendar`
-   This connects a Google Calendar to your Seed Club account for booking and availability workflows. It is only needed if you want the agent to schedule using your personal calendar.
-
-Seed Club auth is the first gate. Until it succeeds, normal harness usage is blocked and only the setup commands are available.
-
-`/seedclub` is the main entry point for Seed Club actions. If you are not connected yet, it will start the Seed Club connect flow automatically.
-
-CLI auth now prefers an authorization-code exchange:
-- browser callback: `http://127.0.0.1:<port>/callback?code=...&state=...`
-- CLI exchange: `POST ${SEEDCLUB_API_URL}/auth/cli/exchange` with `{ code, state }`
-
-Power-user env overrides:
-
-```bash
-export SEEDCLUB_API_URL=http://localhost:3001
-export SEEDCLUB_AUTH_URL=http://localhost:3000
-export SEEDCLUB_ACCESS_TOKEN=<bearer-token>
-```
-
-Production defaults are already built into the auth extension:
-
-```bash
-SEEDCLUB_API_URL=https://api.seedclub.com
-SEEDCLUB_AUTH_URL=https://auth.seedclub.com
-```
-
-You do not need to export those for normal use. Only set env vars when you want to override them for local/dev.
-
-## How it works
-
-seedclub is an npm package (`@clubnet/seedclub`) that wraps [pi](https://github.com/badlogic/pi-mono) as a dependency. Installing the package globally gives you the `seedclub` command.
-
-The `seedclub` CLI wrapper does three things:
-1. Sets `PI_CODING_AGENT_DIR` to point pi at `~/.seedclub/agent/`
-2. Sets `PI_SKIP_VERSION_CHECK=1` so pi's update banner never shows
-3. Spawns the pi binary from the package's own `node_modules/`
-
-A `postinstall` script runs after every install/update and sets up:
-
-```
-~/.seedclub/
-  └── agent/
-        ├── extensions/
-        │     ├── seedclub/        ← core: auth, tools, commands
-        │     └── seedclub-ui/     ← UI: welcome screen, update check
-        ├── themes/
-        │     ├── dark.json
-        │     └── light.json
-        ├── settings.json
-        └── .seedclub-version
-```
-
-This means:
-- Running `seedclub` → uses `~/.seedclub/agent/` config, package-local pi binary
-- Running `pi` (if installed separately) → uses `~/.pi/agent/` config, totally independent
-- **seedclub never modifies pi's installation**
-
-## Version pinning
-
-seedclub pins versions in `package.json`:
-
-```json
-{
-  "version": "0.2.19",
-  "dependencies": {
-    "@mariozechner/pi-coding-agent": "0.65.2"
-  }
-}
-```
-
-Users never interact with pi's npm package directly. When they run `seedclub update`, it runs `npm install -g @clubnet/seedclub@latest`.
-
-## Theme
-
-Themes live under `assets/theme/` and are installed to `~/.seedclub/agent/themes/` (currently `dark.json` and `light.json`).
-
-It's a standard pi theme with 51 color tokens. Edit it to change any visual aspect of the app:
-
-| Section | What it controls |
-|---|---|
-| **Core UI** | `accent`, `border`, `success`, `error`, `warning`, `muted`, `text` |
-| **Backgrounds** | User messages, tool boxes (pending/success/error), selection highlight |
-| **Markdown** | Headings, links, code blocks, quotes, list bullets |
-| **Syntax** | Comments, keywords, functions, strings, numbers, types |
-| **Thinking borders** | Editor border color per thinking level (off → xhigh) |
-| **Diffs** | Added/removed/context lines in tool output |
-
-The `vars` block at the top defines reusable colors (e.g. `brand: "#00C853"`) that are referenced throughout `colors`. To change the brand color, just update `vars.brand`.
-
-Seed Club keeps product-level names in `vars` (`editorBg`, `messageBg`, `successBg`, `errorBg`) and maps pi's required tokens to those names (`selectedBg`, `userMessageBg`, `toolPendingBg`, etc.). The CLI probes the terminal background with OSC 11 and sets `COLORFGBG` before pi starts when no explicit theme is configured, so light/dark defaults track the actual terminal window instead of pi's fallback.
-
-**Hot reload:** Edit the theme file while seedclub is running and it reloads instantly.
-
-Colors can be hex (`"#00C853"`), 256-color palette index (`242`), a reference to a `vars` entry (`"brand"`), or empty string (`""`) for the terminal default.
-
-## Development
-
-### Setup
-
-```bash
-git clone https://github.com/seedclub/seedclub-agent.git
-cd seedclub-agent
-
-# Install deps, then install locally from the repo
-npm install
-npm install -g ./
-```
-
-For day-to-day work, run `seedclub version` after installing to confirm your shell is using this repo's wrapper build.
-
-### Repo structure
-
-```
-seedclub/
-  ├── package.json       ← npm package definition (@clubnet/seedclub)
-  ├── bin/cli.js         ← Node.js CLI wrapper (the `seedclub` command)
-  ├── postinstall.js     ← runs after npm install (sets up ~/.seedclub/agent/)
-  ├── install.sh         ← curl | bash installer (just runs npm install -g)
-  ├── README.md
-  └── assets/
-        ├── theme/
-        │     ├── dark.json
-        │     └── light.json
-        └── extensions/
-              ├── seedclub/        ← core extension source
-              └── seedclub-ui/     ← UI extension source
-```
-
-The `assets/` directory contains the canonical source for extensions and themes. The postinstall script copies these into `~/.seedclub/agent/`.
-
-### Updating pi
-
-When a new pi version comes out, upgrading it for Seed Club users means shipping a new `@clubnet/seedclub` package that depends on the newer pi release.
-
-Recommended flow:
-
-1. **Update and test locally:**
-   ```bash
-   npm install @mariozechner/pi-coding-agent@NEW_VERSION
-   npm install -g ./
-   seedclub version
-   seedclub
-   ```
-
-   Verify the wrapper still launches, the Seed Club UI loads, and the core flows you care about still work.
-
-2. **Commit the dependency change and bump the package version:**
-   The pi version is carried by this package, so users only receive it once the Seed Club package version is bumped and released.
-   ```json
-   {
-     "version": "0.3.0",
-     "dependencies": {
-       "@mariozechner/pi-coding-agent": "NEW_VERSION"
-     }
-   }
-   ```
-
-3. **Push the release:**
-   ```bash
-   git add -A
-   git commit -m "bump pi to NEW_VERSION"
-   npm version patch|minor|major
-   git push --follow-tags
-   ```
-
-4. **Users pull the update:**
-   Users get the newer pi runtime when they run:
-   ```bash
-   seedclub update
-   ```
-
-   A fresh `npm install -g @clubnet/seedclub` also installs the new packaged pi version.
-
-### Updating extensions
-
-Extensions live in `assets/extensions/`. Edit them there, then:
-
-```bash
-# Test locally
-npm install -g ./
-seedclub  # test
-
-# When ready, bump package version and publish
-git add -A
-git commit -m "update extensions"
-npm version patch|minor|major
-git push --follow-tags
-```
-
-For reproducible extension dependency installs, commit `assets/extensions/seedclub/package-lock.json` and keep it in sync when changing extension deps.
-
-### Release process
-
-Publishing is now handled by npm trusted publishing from GitHub Actions.
-
-Workflow:
-
-1. Create a branch and make changes
-2. Merge to `main`
-3. Pull `main`, run `npm install`, then `npm install -g ./`
-4. Smoke test with `seedclub version` and, if relevant, a quick interactive run
-5. Bump version: `npm version patch|minor|major`
-6. Push commits + tags: `git push --follow-tags`
-7. GitHub Actions publishes the tagged release to npm automatically via `.github/workflows/publish.yml`
-
-### Trusted publishing
-
-The npm package is configured to publish from GitHub Actions, not from long-lived local npm tokens.
-
-Trusted publisher settings for `@clubnet/seedclub`:
-
-- Provider: GitHub Actions
-- Organization or user: `seedclub`
-- Repository: `seedclub-agent`
-- Workflow filename: `publish.yml`
-- Environment name: blank
-
-Once trusted publishing is working, npm package publishing access should stay on the stricter setting that disallows token-based publishing.
-
 ## Update
 
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubnet/seedclub",
-  "version": "0.2.29",
+  "version": "0.2.30",
   "description": "A branded command-line agent wrapper around pi, with integrated Seed Club commands, tools, and app actions",
   "license": "MIT",
   "repository": {