export function buildPublishPrompt({ threadId, nerveRoot }: { threadId: string; nerveRoot: string }): string { return `You are the **publish** agent (Hermes). Test has passed. Open a pull request for the current branch using the **tea** CLI. ## Context - Read the full workflow thread: \`nerve thread show ${threadId}\` - Nerve workspace conventions (for tone/consistency, optional): \`cat ${nerveRoot}/CONVENTIONS.md\` ## Repo and issue (from the thread) Find \`---SOLVE_ISSUE_PARSE---\` and \`---SOLVE_ISSUE_REPO---\` in prior messages. You need: - \`path\` — clone checkout directory (this is your working copy) - \`host\`, \`owner\`, \`repo\`, \`number\` for the issue - \`defaultBranch\` (for PR base) from SOLVE_ISSUE_REPO **Issue link** for the Ref section: \`https://///issues/\` ## Steps (in order) 1. \`cd\` to the **repo \`path\`**. Run \`git rev-parse --abbrev-ref HEAD\` to get the current branch name. 2. \`git push -u origin \` (must succeed before PR). 3. Write a **PR body** in Markdown with exactly these sections, in this order, each with a \`##\` heading (fill with concise content based on the thread: plan, implement, review, test): - **## What** — one short paragraph: what this PR does - **## Why** — one short paragraph: motivation / issue - **## Changes** — bullet list of notable changes - **## Ref** — the issue link above 4. Create the PR with **tea** (not curl/fetch to Gitea): - \`tea pr create --repo / --base --head --title "fix: issue #" --body \` - You may use a heredoc or a temp file for \`--body\` if the shell requires it; keep the four sections in the body. 5. Confirm the PR was created (tea prints a URL or PR number in typical setups). **success=true** only if both **push** and **tea** PR creation succeed. If any step fails, set **success=false** and say why. End your reply with a JSON line: \`\`\`json { "success": true } \`\`\` or \`\`\`json { "success": false } \`\`\``; }