@goodtek/vibeops 0.2.0

package/CHANGELOG.md

@@ -0,0 +1,28 @@
+# Changelog
+
+All notable changes to VibeOps are documented here.
+
+## 0.2.0 - 2026-05-12
+
+Public release polish.
+
+- Rename the npm package to `@goodtek/vibeops`. The CLI command is still `vibeops`.
+- Publish as a public scoped package (`publishConfig.access = "public"`).
+- Rewrite the README for public release: replace the internal walkthrough example with `Acme Automator`, remove internal phase labels, add a Support section (`support@goodtek.xyz`, `hello@goodtek.xyz`), and update the install command to `npm install -g @goodtek/vibeops`.
+- Normalize CLI help, command descriptions, and program log/error messages to English so the output is consistent for international users.
+- Replace the leftover internal example reference inside `src/types/config.ts` and the planner agent template with a generic project name.
+
+No behavior changes — every command produces the same files and Git/Notion side effects as 0.1.0, only the user-facing text and packaging metadata changed.
+
+## 0.1.0 - 2026-05-11
+
+Initial release candidate.
+
+- Project Bootstrapper: `vibeops init` installs Cursor rules, `AGENTS.md`, agents/prompts/workflows, project docs, and a TASK template into a project; `vibeops status` summarizes installation, tasks, Git, Notion, GitHub, and package state.
+- Interactive Planner: `vibeops plan` runs 20 short questions and produces a normalized ProjectBrief plus a Cursor planning prompt.
+- Task Generator: `vibeops task generate` builds a Cursor prompt for generating TASK files or, with `--scaffold`, writes placeholder TASK markdown directly.
+- Git Task Lifecycle: `task start`, `task prompt`, `task check`, `task done`, and `task rollback` keep one TASK moving through `Planned → In Progress → Review → Done` with dry-run and read-only defaults and explicit rollback confirmation.
+- Notion Dashboard Sync: `notion init`, `notion test`, `notion sync`, and `task pull` provide data-source-first discovery and resolution, schema and status-option validation, metadata-only sync, and local TASK skeleton pull.
+- GitHub Integration: `github status` and `github init` use the `gh` CLI to connect or create a GitHub repository without storing `GITHUB_TOKEN` and without auto-pushing.
+- Init Git Bootstrap: `vibeops init --git --initial-commit` optionally initializes Git and creates the first commit, and `vibeops status` distinguishes unborn / detached / normal HEAD states.
+- Packaging: npm package metadata, MIT license, smoke checks, and publish dry-run workflow.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 VibeOps contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,444 @@
+# VibeOps
+
+> Workflow rails for Cursor-based vibe coding projects.
+
+[![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 does not write product code for you. Cursor is the builder. VibeOps keeps the workflow on rails.
+
+## What Is VibeOps?
+
+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+.
+
+```bash
+npm install -g @goodtek/vibeops
+vibeops --help
+```
+
+The published package is `@goodtek/vibeops`. The installed CLI command is `vibeops`.
+
+For local development from this repository:
+
+```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. Answer 20 short planning questions and generate a Cursor planning prompt.
+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
+```
+
+## 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] [--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` asks 20 short questions and produces a normalized brief plus a Cursor planning prompt. A non-interactive mode is available for safe placeholder output.
+
+### 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.
+
+### 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=`.
+
+Required Projects DB properties:
+
+| 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` |
+
+Required Tasks DB properties:
+
+| 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` |
+
+> `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.
+
+Required Status options:
+
+- Projects DB: `Building`, `Planning`, `Paused`, `Done`, `Archived`
+- Tasks DB: `Planned`, `In Progress`, `Review`, `Done`, `Blocked`
+
+VibeOps validates these options in `notion test` and `notion sync --dry-run`, but it never creates or mutates Notion schema.
+
+## 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
+
+Agents are Markdown files under `.vibeops/agents`. Use:
+
+```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"
+  }
+}
+```
+
+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:
+
+```bash
+pnpm typecheck
+pnpm build
+pnpm smoke
+pnpm pack
+pnpm publish --dry-run --access public --no-git-checks
+```
+
+Actual `npm publish` is a manual release action and is not performed by this repository workflow.
+
+## Security Notes
+
+- `.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.
+
+## Support
+
+- 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)
+
+## Documentation
+
+- [`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.
+
+## License
+
+MIT © VibeOps contributors

package/dist/agent/loader.js

@@ -0,0 +1,71 @@
+import { readdir } from "node:fs/promises";
+import { basename, extname, join } from "node:path";
+import matter from "gray-matter";
+import { isDirectory, readText } from "../lib/filesystem.js";
+function metaFromFile(filePath, data, body) {
+    const fallbackName = basename(filePath, extname(filePath));
+    const name = typeof data["name"] === "string" ? data["name"] : fallbackName;
+    const role = typeof data["role"] === "string" ? data["role"] : extractFirstHeading(body);
+    const description = typeof data["description"] === "string" ? data["description"] : undefined;
+    return { name, role, description, filePath };
+}
+function extractFirstHeading(body) {
+    for (const line of body.split("\n")) {
+        const m = /^#\s+(.*)$/.exec(line.trim());
+        if (m)
+            return m[1].trim();
+    }
+    return "(no role)";
+}
+function frontmatterSlice(raw) {
+    if (!raw.startsWith("---"))
+        return "";
+    const end = raw.indexOf("\n---", 3);
+    if (end < 0)
+        return "";
+    return raw.slice(0, end + 4);
+}
+export async function loadAgent(filePath) {
+    const raw = await readText(filePath);
+    const parsed = matter(raw);
+    const meta = metaFromFile(filePath, parsed.data, parsed.content);
+    return {
+        meta,
+        body: parsed.content.trimStart(),
+        rawFrontmatter: frontmatterSlice(raw),
+        raw,
+    };
+}
+export async function listAgents(agentsDir) {
+    if (!(await isDirectory(agentsDir)))
+        return [];
+    const entries = await readdir(agentsDir, { withFileTypes: true });
+    const files = entries
+        .filter((e) => e.isFile() && e.name.endsWith(".md"))
+        .map((e) => join(agentsDir, e.name))
+        .sort();
+    const records = [];
+    for (const f of files) {
+        try {
+            records.push(await loadAgent(f));
+        }
+        catch {
+            // skip malformed agent files
+        }
+    }
+    return records;
+}
+export async function findAgent(agentsDir, name) {
+    const all = await listAgents(agentsDir);
+    const target = name.toLowerCase();
+    for (const a of all) {
+        if (a.meta.name.toLowerCase() === target)
+            return a;
+    }
+    for (const a of all) {
+        const filenameKey = basename(a.meta.filePath, extname(a.meta.filePath)).toLowerCase();
+        if (filenameKey === target)
+            return a;
+    }
+    return null;
+}

package/dist/agent/prompt.js

@@ -0,0 +1,66 @@
+import { relative } from "node:path";
+import { readText } from "../lib/filesystem.js";
+function relOrAbs(root, p) {
+    const r = relative(root, p);
+    return r === "" ? "." : r.startsWith("..") ? p : r;
+}
+function header(inputs) {
+    const lines = [];
+    lines.push(`# Cursor prompt — agent: ${inputs.agent.meta.name}`);
+    lines.push("");
+    if (inputs.config) {
+        lines.push(`Project: \`${inputs.config.name}\``);
+        lines.push(`VibeOps: \`${inputs.config.vibeopsVersion}\``);
+    }
+    else {
+        lines.push("Project: (no .vibeops.json found — running outside a VibeOps project)");
+    }
+    if (inputs.task) {
+        lines.push(`TASK: \`${inputs.task.meta.id}\``);
+        lines.push(`TASK file: \`${relOrAbs(inputs.projectRoot, inputs.task.meta.filePath)}\``);
+    }
+    lines.push("");
+    return lines.join("\n");
+}
+function agentSection(agent) {
+    return `## Agent definition (${agent.meta.name})\n\n${agent.body.trim()}\n`;
+}
+function taskSection(task) {
+    return `## TASK file content\n\n${task.body.trim()}\n`;
+}
+async function contextSection(paths, projectRoot) {
+    if (paths.length === 0)
+        return "";
+    const parts = ["## Extra context\n"];
+    for (const p of paths) {
+        try {
+            const text = await readText(p);
+            parts.push(`### ${relOrAbs(projectRoot, p)}\n\n\`\`\`\n${text}\n\`\`\`\n`);
+        }
+        catch {
+            parts.push(`### ${relOrAbs(projectRoot, p)}\n\n_(could not read file)_\n`);
+        }
+    }
+    return parts.join("\n");
+}
+const FOOTER = `---
+
+Apply the **Role / Inputs / Output Format / Rules / Forbidden** sections of the agent definition above as-is.
+Your output must be a single markdown blob that pastes cleanly into the Cursor chat.
+
+When done, follow the "Completion report" format in \`AGENTS.md\`:
+TASK ID · summary · changed files · verification · doc updates (05-current-state / TASK / docs/logs).
+`;
+export async function buildPrompt(inputs) {
+    const parts = [
+        header(inputs),
+        agentSection(inputs.agent),
+    ];
+    if (inputs.task)
+        parts.push(taskSection(inputs.task));
+    const extra = await contextSection(inputs.contextPaths ?? [], inputs.projectRoot);
+    if (extra.length > 0)
+        parts.push(extra);
+    parts.push(FOOTER);
+    return parts.join("\n");
+}