@goodtek/vibeops 0.4.0 → 1.0.0

package/README.md

@@ -1,445 +1,105 @@
 # VibeOps
 
-> Workflow rails for Cursor-based vibe coding projects.
+> Minimal CLI rails for Cursor-based TASK-driven vibe coding.
 
 [![npm version](https://img.shields.io/npm/v/@goodtek/vibeops.svg)](https://www.npmjs.com/package/@goodtek/vibeops)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
 
-VibeOps is a local CLI that installs and operates the project structure needed to run Cursor-based vibe coding as reproducible TASKs: `AGENTS.md`, Cursor rules, project docs, TASK files, agents/prompts/workflows, Git lifecycle helpers, and optional Notion dashboard sync.
+VibeOps bootstraps a **Cursor-friendly repo**, starts numbered **TASK** files on Git branches, and closes them while updating **project memory** in Git. Cursor plans and implements; the CLI handles files, Git, and short LLM assists.
 
-VibeOps does not write product code for you. Cursor is the builder. VibeOps keeps the workflow on rails.
+## Four commands
 
-## What Is VibeOps?
+| Command | Purpose |
+|---------|---------|
+| `vibeops init` | Install AGENTS.md, Cursor rules/skills, docs layout, `.vibeops.json` |
+| `vibeops task add` | New `TASK-NNN` file + task branch (blocks if another TASK is In Progress) |
+| `vibeops task done` | LLM fills Result/Test + updates project docs; commit + merge |
+| `vibeops status` | Briefing: active TASK, branch, doc health, next hint |
 
-VibeOps is a **local CLI** for turning an idea into a repository that Cursor agents can work on safely and repeatably.
-
-It gives a project:
-
-- `docs/project/*` for product and architecture context.
-- `docs/tasks/TASK-*.md` as the AI execution source of truth.
-- `.cursor/rules/*` and `AGENTS.md` so Cursor knows how to behave.
-- `.vibeops/agents`, `.vibeops/prompts`, `.vibeops/workflows` for reusable agent instructions.
-- Git task lifecycle commands for start/check/done/rollback.
-- Notion metadata sync for a human dashboard.
-
-## Why It Exists
-
-Vibe coding is fast, but chat history is a weak source of truth. Without a durable workflow, agents repeat work, drift outside scope, lose decision history, and leave teammates without a dashboard. VibeOps moves the durable context into Git files and uses CLI commands to keep each TASK bounded.
-
-## Core Philosophy
-
-- **VibeOps = workflow rail**: it structures the work, validates state, and prints prompts.
-- **Cursor = builder**: Cursor reads the docs/TASKs and writes application code.
-- **Git `docs/tasks` = AI execution source of truth**: TASK markdown beats chat memory.
-- **Notion = human dashboard**: Notion shows metadata and progress, not canonical task bodies.
-
-| What | Source of truth |
-| --- | --- |
-| AI execution input | Git `docs/tasks/*.md` |
-| Project design/status | Git `docs/project/*.md` |
-| Change and rollback evidence | Git commits/branches |
-| Human dashboard | Notion Projects/Tasks DB |
-| Not a source of truth | Cursor chat, Slack, memory |
-
-## Installation
-
-VibeOps requires Node.js 20+.
+## Workflow
 
 ```bash
-npm install -g @goodtek/vibeops
-vibeops --help
-```
-
-The published package is `@goodtek/vibeops`. The installed CLI command is `vibeops`.
+vibeops init --git --initial-commit   # once per repo
 
-For local development from this repository:
+vibeops task add                      # interactive: idea → TASK file + branch
+# Plan in Cursor Ask:  @docs/tasks/TASK-NNN-….md
+# Build in Cursor Agent: same file + Scope / Acceptance Criteria
 
-```bash
-pnpm install
-pnpm build
-node dist/cli.js --help
-```
-
-## Quick Start
-
-```bash
-# 1. Install VibeOps workflow files into the current project.
-# Interactive mode can also initialize Git and create the first commit.
-vibeops init
-
-# Non-interactive Git bootstrap:
-vibeops init --git --initial-commit
-
-# 2. LLM planning session (OpenAI API key, Codex `codex login` / ~/.codex/auth.json, or Cursor `agent` CLI) → brief + planning prompt.
-#    Use `vibeops plan --legacy-wizard` for the original 20-question flow.
-vibeops plan
-
-# 3. Generate a TASK prompt or scaffold TASK markdown.
-vibeops task generate --dry-run
-
-# 4. Start one TASK at a time.
-vibeops task start TASK-001
-vibeops task prompt TASK-001 --agent builder
-
-# 5. Review and move to human review.
-vibeops task check TASK-001
-vibeops task done TASK-001
-
-# 6. Optional Notion dashboard sync.
-vibeops notion init
-vibeops notion test
-vibeops notion sync --dry-run
+vibeops task done                     # close TASK, update memory, merge branch
+vibeops status                        # anytime snapshot
 ```
 
-## Quick Tutorial: Acme Automator
-
-Suppose the idea is: “Build **Acme Automator**, a SaaS that schedules and runs browser automation jobs for marketing teams.”
-
-```bash
-mkdir acme-automator
-cd acme-automator
-
-vibeops init --name "Acme Automator" --git --initial-commit
-vibeops plan --idea "Acme Automator: schedule and run browser automation jobs for marketing teams"
-vibeops task generate --dry-run
-
-vibeops task start TASK-001
-vibeops task prompt TASK-001 --agent builder
-# Paste the prompt into Cursor and let Cursor implement the TASK.
-vibeops task check TASK-001
-vibeops task done TASK-001
-```
-
-If a Notion dashboard is enabled:
-
-```bash
-vibeops notion init
-vibeops notion test
-vibeops notion sync --dry-run
-vibeops notion sync
-```
-
-## Full Command Flow
-
-```text
-vibeops
-├─ init [--dry-run] [--force] [--cwd <path>] [--name <projectName>]
-│       [--git|--no-git] [--initial-commit|--no-initial-commit]
-│       [--default-branch <name>] [--commit-message <message>]
-├─ status [--json] [--cwd <path>]
-├─ plan [--idea <text>] [--from <path>] [--output <path>] [--non-interactive] [--legacy-wizard] [--provider <id>] [--cwd <path>]
-├─ agent
-│  ├─ list [--json] [--cwd <path>]
-│  ├─ show <name> [--raw] [--cwd <path>]
-│  └─ prompt <name> <taskId> [--context <path...>] [--cwd <path>]
-├─ task
-│  ├─ generate [--from <path>] [--output <path>] [--count <n>] [--phase <name>] [--scaffold] [--dry-run] [--cwd <path>]
-│  ├─ start <taskId> [--dry-run] [--allow-dirty] [--agent <name>] [--cwd <path>]
-│  ├─ prompt <taskId> --agent <name> [--context <path...>] [--cwd <path>]
-│  ├─ check <taskId> [--strict] [--agent <name>] [--cwd <path>]
-│  ├─ done <taskId> [--dry-run] [--finalize] [--cwd <path>]
-│  ├─ rollback <taskId> [--confirm | --confirm-destructive] [--strategy <name>] [--keep-branch] [--dry-run] [--cwd <path>]
-│  └─ pull [--dry-run] [--json] [--status <list>] [--limit <n>] [--cwd <path>] [--verbose]
-├─ notion
-│  ├─ init [--dry-run] [--enable] [--projects-db <id>] [--tasks-db <id>] [--non-interactive] [--cwd <path>]
-│  ├─ test [--json] [--debug-shape] [--cwd <path>]
-│  └─ sync [--dry-run] [--json] [--only-tasks] [--only-project] [--cwd <path>]
-└─ github
-   ├─ status [--json] [--cwd <path>]
-   └─ init [--dry-run] [--yes] [--owner <user>] [--repo <name>] [--public|--private]
-           [--remote <name>] [--connect <owner/repo or url>] [--no-package-update] [--cwd <path>]
-```
-
-Run any command with `--help` for the option details.
-
-## Features
-
-### Project Bootstrapper
-
-`vibeops init` installs a project operating system: `AGENTS.md`, `.cursor/rules`, `docs/project`, `docs/tasks`, `.vibeops/agents`, `.vibeops/prompts`, `.vibeops/workflows`, `.vibeops.json`, and `.vibeops.env.example`. It is idempotent by default and only overwrites when `--force` is used.
-
-### Interactive Planner
-
-`vibeops plan` runs only inside a **VibeOps project** (expects **`.vibeops.json`** from `vibeops init`). It writes `.vibeops/brief/project-brief.md` and `.vibeops/generated/plan-prompt.md`; with **`--apply-planner`** it also writes `docs/project/*` and `docs/tasks/*` via the LLM. The command uses **OpenAI** (`OPENAI_API_KEY`), **Codex (ChatGPT OAuth)** via tokens from `codex login` (`~/.codex/auth.json`, same OAuth client as Hermes/OpenClaw `openai-codex`), or the **Cursor Agent CLI** (`agent login`). With a TTY you **always pick** among those three (each line shows ✓ or “needs setup”; Codex can start browser OAuth from that menu). Pass `--provider` to skip the menu when that path is already ready. Then pick a **model** from the provider catalog (or `--model`). Next you pick the **planning dialogue language** (preset list + Other); the LLM asks **one question per turn** in that language. Each question header shows a **rough ASCII progress line** and **ETA hint** (assumes up to ~14 steps; not a guarantee). **Multi**-choice suggestions use **checkboxes** (Space, Other, **Wrap up — draft summary now** when allowed, then **Go back** last when you can undo); **single**-choice uses **arrow select** with **Other**, wrap-up, and **Go back** last (no extra Continue step). **Text** answers: type `back` alone to go back when allowed, or `wrap` / `enough` to stop questions and ask for a draft summary from the thread so far. When the model is ready, it shows a **readable markdown summary**; you must **confirm** before the `ProjectBrief` is written. After that, **`--apply-planner`** runs the planner pass via the same provider: fills `docs/project/*` and initial `docs/tasks/*`. With a **TTY** and without **`--non-interactive`**, you are then asked **in order**: create a **git commit** (default Yes; if Git is not initialized yet, you can run **`git init`** + branch **`main`** from the same prompts), **git push** (default No; use **`--push`** to skip the question and push after a successful commit; after you choose push, you can run **`vibeops github init`** to connect or create a GitHub repo / set **`origin`**, same as the standalone command), and **Notion sync** when the brief enables it (default Yes; **`--no-notion-sync`** skips; if Notion is not configured, you can run **`vibeops notion init`** from the same flow, then sync retries once ready). In **`--non-interactive`** mode, commit runs automatically (unless **`--no-git-commit`**), push only with **`--push`**, and Notion runs when the brief enables it (unless **`--no-notion-sync`**). **`--apply-dry-run`** asks the model which files it would emit without writing. Codex defaults to ChatGPT-account models (`gpt-5.4`; override with `VIBEOPS_CODEX_MODEL`). Use `--legacy-wizard` for the fixed 20-question flow. `--non-interactive` and `--from` never call an LLM for the brief unless you add `--apply-planner` with `--provider` (and optional `--model`) for the apply step.
-
-### Task Generator
-
-`vibeops task generate` builds a Cursor prompt for generating TASK files. With `--scaffold`, it creates placeholder TASK markdown directly. It does not call an LLM.
-
-### Git Task Lifecycle
-
-`task start`, `task prompt`, `task check`, and `task done` keep one TASK moving through `Planned → In Progress → Review → Done`. `task done` defaults to `Review`; use `--finalize` only after human review. `task start` still expects a clean tree for application code, but if the only uncommitted changes live under `docs/tasks/`, `docs/project/`, `docs/logs/`, or `.vibeops/state/`, it warns and continues so a prior doc-only finalize does not block the next TASK.
-
-### Rollback Safety
-
-`task rollback` prints recovery options by default. Destructive Git actions require explicit confirmation (`--confirm` or `--confirm-destructive`) and should be reviewed before use.
-
-### Notion Dashboard Sync
-
-`notion init/test/sync` and `task pull` keep Notion as a metadata dashboard. VibeOps syncs project/task metadata only and never updates Notion page bodies.
-
-## Runner Modes
-
-- **Prompt mode (default)**: VibeOps prints Cursor-ready prompts. Cursor executes the code changes.
-- VibeOps does not call LLM APIs and does not invoke Cursor CLI directly today; it works as a workflow rail around the human + Cursor loop.
-
-## Notion Setup
-
-Notion is optional. If enabled:
-
-- `NOTION_TOKEN` is the **only** environment variable VibeOps reads. It lives in `.vibeops.env` (gitignored) or in `process.env`.
-- Target IDs live in `.vibeops.json`, not in `.vibeops.env`.
-- `projectsTargetId` / `tasksTargetId` are preferred resolved **data_source** IDs.
-- `projectsDatabaseId` / `tasksDatabaseId` remain legacy/container fallbacks.
-- `notion init` uses data_source-first discovery. If no data sources are found, it can search accessible pages, scan 1-depth inline database blocks, then resolve child databases to data source IDs.
-- Legacy `NOTION_API_KEY` / `NOTION_PROJECT_DB` / `NOTION_TASK_DB` environment variables are no longer used. The `.vibeops.env.example` that `vibeops init` writes contains only `NOTION_TOKEN=`.
+If a TASK is already **In Progress**, `task add` prints a guide and exits with code 1 — it does **not** auto-run `task done`.
 
-Required Projects DB properties:
+## What `init` creates
 
-| Property | Type |
-| --- | --- |
-| `Name` | `title` |
-| `Project ID` | `rich_text` |
-| `Status` | `status` |
-| `Local Path` | `rich_text` |
-| `Git Repo` | `rich_text` or `url` |
-| `Current Phase` | `select` |
-| `Docs Path` | `rich_text` |
-| `Summary` | `rich_text` |
+| Path | Role |
+|------|------|
+| `AGENTS.md` | Source of truth, read order, four CLI commands |
+| `.cursor/rules/` | Task source of truth, Git safety, docs on done |
+| `.cursor/skills/` | Optional `plan-task` and `implement-task` skills |
+| `docs/tasks/TASK-000-template.md` | Section template for new TASKs |
+| `docs/project/05-current-state.md` | Facts: stage, active TASK, next step |
+| `docs/project/06-decisions.md` | Append-only decision log |
+| `docs/project/03-architecture.md` | Living architecture |
+| `docs/logs/README.md` | Daily log convention |
+| `.vibeops.json` | Project metadata (no Notion) |
 
-Required Tasks DB properties:
+## Source of truth
 
-| Property | Type |
-| --- | --- |
-| `Name` | `title` |
-| `Task ID` | `rich_text` |
-| `Project ID` | `rich_text` |
-| `Status` | `status` |
-| `Priority` | `select` |
-| `MVP Phase` | `select` |
-| `Git Branch` | `rich_text` |
-| `Docs Path` | `rich_text` |
-| `Summary` | `rich_text` |
-| `Result Summary` | `rich_text` |
+| What | Where |
+|------|--------|
+| Current work | `docs/tasks/TASK-NNN-*.md` |
+| Project memory | `docs/project/05-current-state.md`, `03-architecture.md`, `06-decisions.md` |
+| Change history | Git commits on task branches |
+| **Not** trusted | Cursor chat, Slack |
 
-> `MVP Phase` here is a Notion property name kept for compatibility with existing dashboards. It is a free-form label column and is not an internal release-phase tag.
+## LLM (optional)
 
-Required Status options:
+Used only for **`task add`** (scaffold title/slug/sections) and **`task done`** (Result, Test Result, project doc patches).
 
-- Projects DB: `Building`, `Planning`, `Paused`, `Done`, `Archived`
-- Tasks DB: `Planned`, `In Progress`, `Review`, `Done`, `Blocked`
+Providers (first match wins): Codex OAuth (`~/.codex/auth.json`), Cursor Agent CLI, `OPENAI_API_KEY` in `.vibeops.env`.
 
-VibeOps validates these options in `notion test` and `notion sync --dry-run`, but it never creates or mutates Notion schema.
+Without LLM, `task add` falls back to a minimal template; `task done` uses a git-diff fallback for Result sections.
 
-## GitHub Setup
-
-GitHub integration runs on top of the GitHub CLI (`gh`). VibeOps never stores `GITHUB_TOKEN` — authentication is owned by `gh auth login`.
-
-1. Install `gh`:
-
-   ```bash
-   brew install gh
-   # or follow https://cli.github.com/
-   ```
-
-2. Authenticate:
-
-   ```bash
-   gh auth login
-   ```
-
-3. Probe state:
-
-   ```bash
-   vibeops github status
-   ```
-
-4. Connect or create a repo interactively:
-
-   ```bash
-   # plan only — no gh / git / file mutation
-   vibeops github init --dry-run
-
-   # plan a new public repo
-   vibeops github init --dry-run --owner <user> --repo <name> --public
-
-   # connect to an existing repo by slug or URL
-   vibeops github init --dry-run --connect <owner>/<repo>
-   vibeops github init --dry-run --connect https://github.com/<owner>/<repo>.git
-   vibeops github init --dry-run --connect git@github.com:<owner>/<repo>.git
-   ```
-
-`vibeops github init` applies four things in sequence:
-
-- (optional) `gh repo create <owner>/<repo> --public|--private --source=. --remote=origin` for new repos.
-- `git remote add origin <url>` (or `git remote set-url`) for the `--connect` path. Existing remotes are never silently overwritten — VibeOps asks first and defaults to No.
-- Updates `package.json` `repository.url`, `homepage`, `bugs.url` (skip with `--no-package-update`).
-- Writes the `github` section of `.vibeops.json`: `enabled`, `mode = "gh-cli"`, `owner`, `repo`, `remote`, `visibility`, `url`.
-
-VibeOps never runs `git push`. Push your branch manually with `git push -u <remote> <branch>`.
-
-## Init Git Bootstrap
-
-`vibeops init` can optionally do the first local Git setup while installing the workflow files. In interactive mode it asks:
-
-- Initialize Git repository?
-- Use `main` as default branch?
-- Create initial commit?
-- Initial commit message
-
-For non-interactive setup:
-
-```bash
-vibeops init --git --initial-commit
-vibeops init --git --no-initial-commit
-vibeops init --git --default-branch main --commit-message "chore: initialize vibeops project"
-```
-
-Safety rules:
-
-- Existing Git repositories skip `git init`.
-- Existing repositories with commits skip the initial commit path.
-- `--dry-run` runs no Git commands.
-- VibeOps never pushes and never changes remotes during `init`.
-- Before the initial commit, VibeOps prints how many files will be included.
-
-Before the first commit, `vibeops status` distinguishes an unborn branch from a detached HEAD:
-
-```text
-Git
-  branch  main (unborn, no commits yet)
-  status  dirty
-  hint    create the first commit or run `vibeops init --git --initial-commit`
-```
-
-## Status Output
-
-`vibeops status` summarizes the local project surface only. It never calls the Notion API and never spawns `gh`. The Notion section reads from `.vibeops.env` / `process.env` (for `NOTION_TOKEN` presence) and `.vibeops.json` (for target IDs). The GitHub section reads from `.vibeops.json`. The Package section reads from `package.json`.
-
-Example output for a fully-configured project:
-
-```text
-Git
-  branch  main
-  status  clean
-
-Notion
-  enabled          yes
-  token            configured (.vibeops.env)
-  projects target  configured
-  tasks target     configured
-  hint             run `vibeops notion test`
-
-GitHub
-  enabled     yes
-  mode        gh-cli
-  owner/repo  goodtekxyz/vibeops
-  remote      origin
-  url         https://github.com/goodtekxyz/vibeops
-
-Package
-  name     @goodtek/vibeops
-  version  0.2.0
-  bin      vibeops
-```
-
-For a fresh project that has not been wired to Notion or GitHub yet:
-
-```text
-Notion
-  enabled          no
-  token            missing
-  projects target  missing
-  tasks target     missing
-  hint             run `vibeops notion init`
-
-GitHub
-  enabled  no
-  hint     run `vibeops github init`
-```
-
-If the project has no `package.json`, the Package section degrades gracefully:
-
-```text
-Package
-  package.json missing
-```
-
-`vibeops status --json` exposes the same surface programmatically, including `notion.tokenSource`, `notion.hasProjectsTarget`, `notion.hasTasksTarget`, the entire `github` object, and the entire `package` object. Legacy environment variables (`NOTION_API_KEY`, `NOTION_PROJECT_DB`, `NOTION_TASK_DB`) are no longer surfaced — VibeOps only uses `NOTION_TOKEN`.
-
-## Git Rollback Safety
-
-- `task start` records base branch, base commit, and task branch in task state.
-- `task check` is read-only and reports working tree + committed changes.
-- `task done` validates TASK Result/Test Result and moves to Review by default.
-- `task rollback` is advisory unless explicit confirmation flags are supplied.
-
-## Agent Workflow
+## Installation
 
-Agents are Markdown files under `.vibeops/agents`. Use:
+Node.js 20+ required.
 
 ```bash
-vibeops agent list
-vibeops agent show builder
-vibeops task prompt TASK-001 --agent builder
-```
-
-The default project template includes agents such as `orchestrator`, `planner`, `architect`, `builder`, `reviewer`, `tester`, `docs`, and `recovery`.
-
-## Packaging / npm Usage
-
-This package exposes the `vibeops` binary:
-
-```json
-{
-  "bin": {
-    "vibeops": "dist/cli.js"
-  }
-}
+npm install -g @goodtek/vibeops
+vibeops --help
 ```
 
-Package contents are limited by `package.json#files` to built output, templates, and top-level docs/license files. `dist/` is generated by `pnpm build` / `prepack` and is not committed.
-
-Useful maintainer commands:
+Local development:
 
 ```bash
-pnpm typecheck
+pnpm install
 pnpm build
-pnpm smoke
-pnpm pack
-pnpm publish --dry-run --access public --no-git-checks
+pnpm smoke          # typecheck + build + smoke cases
+node dist/cli.js --help
 ```
 
-Actual `npm publish` is a manual release action and is not performed by this repository workflow.
+## Flags (common)
 
-## Security Notes
+- **`init`**: `--dry-run`, `--cwd`, `--name`, `--git`, `--no-git`, `--initial-commit`, `--force`
+- **`task add`**: `--dry-run`, `--non-interactive --idea "…"` (CI/smoke)
+- **`task done`**: `--dry-run`, `--no-merge`, `--allow-dirty`, `--yes`, `--cwd`
+- **`status`**: `--json`, `--cwd`
 
-- `.vibeops.env` is gitignored and must contain secrets such as `NOTION_TOKEN`.
-- VibeOps masks tokens in CLI output.
-- Notion test/debug output is token-safe.
-- `notion sync --dry-run` performs no mutation.
-- `task pull --dry-run` performs no file or Notion mutation.
-- Notion page bodies are never synced.
-- Git destructive rollback paths require explicit confirmation.
-- `github init` uses `gh` CLI auth — VibeOps never stores `GITHUB_TOKEN`.
-- `github init --dry-run` runs zero `gh` / `git remote` / file mutations and produces only a plan.
+## Git conventions
 
-## Support
+- Task branch: `task/<slug>` from current HEAD
+- Commit message: `feat(task-nnn): <short title>`
+- Merge via `task done` (confirm in TTY; `--yes` to skip prompt)
+- No force-push
 
-- Bugs, setup issues, and usage questions: [support@goodtek.xyz](mailto:support@goodtek.xyz)
-- Collaboration and feedback: [hello@goodtek.xyz](mailto:hello@goodtek.xyz)
-- Issue tracker: [github.com/goodtekxyz/vibeops/issues](https://github.com/goodtekxyz/vibeops/issues)
+## Breaking change: 1.0.0
 
-## Documentation
+v1.0 removes `plan`, `start`, `next`, `rollback`, `notion`, `github`, and legacy task subcommands. Pin `@goodtek/vibeops@0.7` if you still need them.
 
-- [`AGENTS.md`](AGENTS.md) — agent operating guide.
-- [`docs/project/00-overview.md`](docs/project/00-overview.md) — vision and scope.
-- [`docs/project/01-architecture.md`](docs/project/01-architecture.md) — CLI / config / data flow.
-- [`docs/project/03-current-state.md`](docs/project/03-current-state.md) — current implementation state.
-- [`docs/project/04-decisions.md`](docs/project/04-decisions.md) — decisions already made.
-- [`docs/project/05-backlog.md`](docs/project/05-backlog.md) — task order.
-- [`docs/tasks/`](docs/tasks/) — TASK files used by Cursor.
+See [CHANGELOG.md](CHANGELOG.md) and [docs/project/v3-scope.md](docs/project/v3-scope.md).
 
 ## License
 
-MIT © VibeOps contributors
+MIT

package/dist/bootstrap/installer.js

@@ -6,24 +6,12 @@ import { loadManifest, resolveDestination } from "./manifest.js";
 import { applySubstitutions, buildSubstitutions, isTextPath, } from "./substitute.js";
 import { configToJson } from "../lib/config.js";
 function envExampleContents() {
-    // Modern VibeOps reads exactly one Notion secret: NOTION_TOKEN.
-    // Notion Projects / Tasks target IDs live in `.vibeops.json` under
-    // `notion.projectsTargetId` / `notion.tasksTargetId` (configured by
-    // `vibeops notion init`), so they are NOT environment variables.
-    //
-    // We intentionally do NOT seed GITHUB_TOKEN / OPENAI_* here:
-    //   - GitHub integration uses `gh` CLI auth.
-    //   - VibeOps' default runner is prompt mode and does not call LLM APIs.
     return [
-        "# VibeOps · environment example",
-        "# Copy this file to .vibeops.env and fill in the value.",
-        "# Never commit .vibeops.env — it is added to .gitignore by `vibeops init`.",
+        "# VibeOps · optional environment",
+        "# Copy to .vibeops.env (gitignored). Never commit secrets.",
         "#",
-        "# NOTION_TOKEN is the only secret VibeOps reads. Get it from",
-        "# https://www.notion.so/profile/integrations after creating an internal",
-        "# integration and sharing the target databases with it.",
-        "",
-        "NOTION_TOKEN=",
+        "# LLM for task add / task done (optional — Codex OAuth and Cursor Agent CLI also work):",
+        "# OPENAI_API_KEY=",
         "",
     ].join("\n");
 }