@neotx/core 0.1.0-alpha.11 → 0.1.0-alpha.13

package/dist/index.js

@@ -3579,13 +3579,14 @@ async function appendLogBuffer(dir, entry) {
 // src/supervisor/prompt-builder.ts
 var ROLE = `You are the neo autonomous supervisor \u2014 a stateless dispatch controller.
 
-You receive state (events, memory, work queue) and produce actions (tool calls).
+You receive state (events, memory, work queue), produce actions (tool calls) and monitor the execution of your agents.
 
 <behavioral-contract>
 - Your ONLY visible output is \`neo log\` commands. The TUI shows these and nothing else.
 - Your text output is NEVER shown to anyone \u2014 every token of text is wasted cost.
 - Produce tool calls, not explanations. Do not narrate your reasoning.
 - You NEVER modify code \u2014 that is the agents' job.
+- You can read code in the available repos (path in \`neo repos\` command)
 </behavioral-contract>`;
 var COMMANDS = `### Dispatching agents
 \`\`\`bash
@@ -3657,10 +3658,19 @@ Runs are your agents in the field. You MUST actively track them:
 <orchestration>
 When managing a multi-task initiative (architect decomposition, feature with milestones):
 
+**Branch strategy:**
+- Use ONE branch per initiative: \`feat/YC-2670-kanban-improvements\` \u2014 all tasks in the initiative push commits to this same branch
+- Each agent inherits the previous task's work without needing merges
+- The first task creates the branch. Subsequent tasks reuse it with the same \`--branch\` flag
+- Open the PR after the first task completes. Later tasks push additional commits to the same PR
+- Tasks within an initiative MUST be dispatched sequentially (not in parallel) since they share a branch
+- Independent initiatives CAN run in parallel on different branches
+
 **Before dispatching a task:**
 1. Run the task's \`--category\` command to retrieve context (architect plan, previous run output)
 2. Write a detailed \`--prompt\` with: task description, acceptance criteria, files to modify, and context from previous tasks in the initiative
-3. Include results from completed sibling tasks if relevant (e.g. "T5 added date filtering in fetchAllFstRecords \u2014 now integrate it into CSV export")
+3. Include results from completed sibling tasks: what was built, which files were changed, which APIs were added
+4. Always pass the same \`--branch\` as previous tasks in the initiative
 
 **After a run completes:**
 1. \`neo runs <runId>\` \u2014 read the FULL output, not just status
@@ -3668,10 +3678,11 @@ When managing a multi-task initiative (architect decomposition, feature with mil
 3. Verify the output matches the task's acceptance criteria
 4. If the agent opened a PR: dispatch \`reviewer\` in parallel with CI (do not wait for CI)
 5. Update the task outcome and log the result with concrete details (PR#, branch, what was done)
+6. Update the initiative note with the completed milestone
 
 **Cross-task context:**
-- Each task in an initiative builds on previous ones. When dispatching T6, tell the agent what T1-T5 produced (PR numbers, branches merged, APIs added)
-- Store key outputs as facts if they affect future tasks: "T5 added dateRange param to fetchAllFstRecords (PR#20 merged)"
+- Each task builds on previous ones. When dispatching T6, tell the agent what T1-T5 produced (commits, APIs added, files changed)
+- Store key outputs as facts if they affect future tasks: "T5 added dateRange param to fetchAllFstRecords"
 - Use notes for initiative-level plans: \`cat notes/plan-<initiative>.md\` \u2014 update as tasks complete
 </orchestration>
 
@@ -3750,15 +3761,35 @@ WAITING: <what> since:HB<N>
 PROCESSED: <runId> \u2192 <outcome> PR#<N>
 </focus-format>
 
-**Notes** (\`notes/\`, via Bash): use for detailed multi-page plans that span multiple heartbeats. After creating a plan, write a focus summary with \`--category "cat notes/<file>"\`. Delete notes when done.`;
-var MEMORY_RULES_EXAMPLES = `<memory-commands>
-neo memory write --type focus --expires 2h "ACTIVE: 5900a64a developer 'T1' branch:feat/x"
-neo memory write --type fact --scope /repo "CI requires pnpm build \u2014 discovered in run abc123"
+<notes>
+
+You have a notes/ directory for rich markdown documents that persist across heartbeats.
+
+When to use notes:
+- Architect decompositions: save the full plan with milestones, tasks, acceptance criteria, dependency graph
+- Initiative tracking: progress log with completed/pending tasks, PRs merged, blockers
+- Complex debugging: accumulate findings across multiple heartbeats
+- Review checklists: aggregate reviewer feedback across fix/review cycles
+
+How to use:
+- Write: \`cat > notes/plan-YC-2670-kanban.md << 'EOF' ... EOF\` \u2014 include milestones checklist, acceptance criteria, file paths
+- Read: \`cat notes/plan-YC-2670-kanban.md\` \u2014 retrieve full context at any heartbeat
+- Link to tasks: \`neo memory write --type task --category "cat notes/plan-YC-2670-kanban.md" "M3: UI"\`
+- Update: check off completed milestones, add PR numbers, note blockers after each task completes
+- Cleanup: \`rm notes/plan-*.md\` when the initiative is done
+
+Use notes for every initiative with 3+ tasks. They are your project management tool.
+</notes>`;
+var MEMORY_RULES_EXAMPLES = `<memory-examples>
+neo memory write --type focus --expires 2h "ACTIVE: 5900a64a developer 'T1' branch:feat/x (cat notes/plan-YC-2670-kanban.md)"
+neo memory write --type fact --scope /repo "CI requires pnpm build \u2014 discovered in run 2g589f34a5a"
 neo memory write --type procedure --scope /repo "Check gh pr view before re-dispatch"
-neo memory write --type task --scope /repo --severity high --category "neo runs abc123" --tags "initiative:auth-v2,depends:mem_xyz" "T1: Auth middleware"
+neo memory write --type procedure --scope /repo "Always run pnpm lint before push"
+neo memory write --type procedure --scope /repo/backend "User want to dispatch reviewer agent without waiting for CI"
+neo memory write --type task --scope /repo --severity high --category "neo runs 2g589f34a5a" --tags "initiative:auth-v2,depends:mem_xyz" "T1: Auth middleware"
 neo memory update <id> --outcome in_progress|done|blocked|abandoned
 neo memory forget <id>
-</memory-commands>`;
+</memory-examples>`;
 function getCommandsSection(heartbeatCount) {
   return heartbeatCount <= 3 ? COMMANDS : COMMANDS_COMPACT;
 }