@xn-intenton-z2a/agentic-lib 7.1.22 → 7.1.23

package/bin/agentic-lib.js

@@ -786,6 +786,42 @@ function initReseed() {
 
 function initPurge(seedsDir) {
   console.log("\n--- Purge: Reset Source Files to Seed State ---");
+
+  // Read TOML to get source and tests paths (or use defaults)
+  let sourcePath = "src/lib/";
+  let testsPath = "tests/unit/";
+  const tomlTarget = resolve(target, "agentic-lib.toml");
+  if (existsSync(tomlTarget)) {
+    try {
+      const tomlContent = readFileSync(tomlTarget, "utf8");
+      const sourceMatch = tomlContent.match(/^source\s*=\s*"([^"]+)"/m);
+      const testsMatch = tomlContent.match(/^tests\s*=\s*"([^"]+)"/m);
+      if (sourceMatch) sourcePath = sourceMatch[1];
+      if (testsMatch) testsPath = testsMatch[1];
+    } catch (err) {
+      console.log(`  WARN: Could not read TOML for paths, using defaults: ${err.message}`);
+    }
+  }
+
+  // Clear source directory completely
+  const sourceDir = resolve(target, sourcePath);
+  if (existsSync(sourceDir)) {
+    console.log(`  CLEAR: ${sourcePath}`);
+    if (!dryRun) rmSync(sourceDir, { recursive: true });
+    initChanges++;
+  }
+  if (!dryRun) mkdirSync(sourceDir, { recursive: true });
+
+  // Clear tests directory completely
+  const testsDir = resolve(target, testsPath);
+  if (existsSync(testsDir)) {
+    console.log(`  CLEAR: ${testsPath}`);
+    if (!dryRun) rmSync(testsDir, { recursive: true });
+    initChanges++;
+  }
+  if (!dryRun) mkdirSync(testsDir, { recursive: true });
+
+  // Copy seed files
   const SEED_MAP = {
     "zero-main.js": "src/lib/main.js",
     "zero-main.test.js": "tests/unit/main.test.js",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xn-intenton-z2a/agentic-lib",
-  "version": "7.1.22",
+  "version": "7.1.23",
   "description": "Agentic-lib Agentic Coding Systems SDK powering automated GitHub workflows.",
   "type": "module",
   "scripts": {

package/src/actions/agentic-step/config-loader.js

@@ -117,6 +117,7 @@ export function loadConfig(configPath) {
 
   return {
     schedule: toml.schedule?.tier || "schedule-1",
+    supervisor: toml.schedule?.supervisor || "daily",
     paths,
     buildScript: execution.build || "npm run build",
     testScript: execution.test || "npm test",

package/src/actions/agentic-step/tasks/discussions.js

@@ -9,6 +9,8 @@ import * as core from "@actions/core";
 import { existsSync } from "fs";
 import { runCopilotTask, readOptionalFile, scanDirectory } from "../copilot.js";
 
+const BOT_LOGINS = ["github-actions[bot]", "github-actions"];
+
 /**
  * Respond to a GitHub Discussion using the Copilot SDK.
  *
@@ -64,6 +66,16 @@ export async function discussions(context) {
     core.warning(`Could not parse discussion URL: ${discussionUrl}`);
   }
 
+  // Separate human comments from bot's own replies
+  const humanComments = discussionComments.filter(
+    (c) => !BOT_LOGINS.includes(c.author?.login),
+  );
+  const botReplies = discussionComments.filter(
+    (c) => BOT_LOGINS.includes(c.author?.login),
+  );
+  const latestHumanComment = humanComments.length > 0 ? humanComments[humanComments.length - 1] : null;
+  const lastBotReply = botReplies.length > 0 ? botReplies[botReplies.length - 1] : null;
+
   const mission = readOptionalFile(config.paths.mission.path);
   const contributing = readOptionalFile(config.paths.contributing.path, 1000);
 
@@ -78,47 +90,68 @@ export async function discussions(context) {
 
   const agentInstructions = instructions || "Respond to the GitHub Discussion as the repository bot.";
 
-  const prompt = [
+  // Build thread-aware prompt
+  const promptParts = [
     "## Instructions",
     agentInstructions,
     "",
-    "## Discussion",
+    "## Discussion Thread",
     `URL: ${discussionUrl}`,
     discussionTitle ? `### ${discussionTitle}` : "",
     discussionBody || "(no body)",
-    discussionComments.length > 0 ? `### Comments (${discussionComments.length})` : "",
-    ...discussionComments.map((c) => `**${c.author?.login || "unknown"}** (${c.createdAt}):\n${c.body}`),
+  ];
+
+  // Show conversation history (human comments only, with timestamps)
+  if (humanComments.length > 0) {
+    promptParts.push("", "### Conversation History");
+    for (const c of humanComments) {
+      const isLatest = c === latestHumanComment;
+      const prefix = isLatest ? ">>> **[LATEST — RESPOND TO THIS]** " : "";
+      promptParts.push(`${prefix}**${c.author?.login || "unknown"}** (${c.createdAt}):\n${c.body}`);
+    }
+  }
+
+  // Show the bot's last reply so it knows what it already said
+  if (lastBotReply) {
+    promptParts.push(
+      "",
+      "### Your Last Reply (DO NOT REPEAT THIS)",
+      lastBotReply.body.substring(0, 500),
+    );
+  }
+
+  // Context section
+  promptParts.push(
     "",
-    "## Context",
+    "## Repository Context",
     `### Mission\n${mission}`,
     contributing ? `### Contributing\n${contributing}` : "",
     `### Current Features\n${featureNames.join(", ") || "none"}`,
     recentActivity ? `### Recent Activity\n${recentActivity}` : "",
+  );
+
+  // Actions — concise, not a wall of text
+  promptParts.push(
     "",
-    "## Available Actions",
-    "Respond with one of these action tags in your response:",
-    "- `[ACTION:seed-repository]` — Reset the sandbox to initial state",
-    "- `[ACTION:create-feature] <name>` — Create a new feature",
-    "- `[ACTION:update-feature] <name>` — Update an existing feature",
-    "- `[ACTION:delete-feature] <name>` — Delete a feature that is no longer needed",
-    "- `[ACTION:create-issue] <title>` — Create a new issue",
-    "- `[ACTION:nop]` — No action needed, just respond conversationally",
-    "- `[ACTION:mission-complete]` — Declare the current mission complete",
-    "- `[ACTION:stop]` — Halt automation",
-    "",
-    "Include exactly one action tag. The rest of your response is the discussion reply.",
-    "",
-    "## Mission Protection",
-    "If the user requests something that contradicts or would undermine the mission,",
-    "you MUST push back. Explain why the request conflicts with the mission and suggest",
-    "an alternative that aligns with it. Use `[ACTION:nop]` in this case.",
-    "The mission is the non-negotiable foundation of this repository.",
-  ].join("\n");
+    "## Actions",
+    "Include exactly one action tag in your response. Only mention actions to the user when relevant.",
+    "`[ACTION:request-supervisor] <free text>` — Ask the supervisor to evaluate and act on a user request",
+    "`[ACTION:create-feature] <name>` — Create a new feature",
+    "`[ACTION:update-feature] <name>` — Update an existing feature",
+    "`[ACTION:delete-feature] <name>` — Delete a feature",
+    "`[ACTION:create-issue] <title>` — Create a new issue",
+    "`[ACTION:seed-repository]` — Reset to initial state",
+    "`[ACTION:nop]` — No action needed, just respond conversationally",
+    "`[ACTION:mission-complete]` — Declare mission complete",
+    "`[ACTION:stop]` — Halt automation",
+  );
+
+  const prompt = promptParts.filter(Boolean).join("\n");
 
   const { content, tokensUsed } = await runCopilotTask({
     model,
     systemMessage:
-      "You are a repository bot that responds to GitHub Discussions. You are self-aware — you refer to yourself as the repository. Be helpful, adaptive, and proactive about suggesting features. You can update and delete features proactively when they are outdated or completed. You MUST protect the mission: if a user requests something that contradicts the mission, push back politely and suggest an aligned alternative.",
+      "You are this repository. Respond in first person. Be concise and engaging — never repeat what you said in your last reply. Adapt to the user's language level. Encourage experimentation and suggest interesting projects. When a user requests an action, pass it to the supervisor via [ACTION:request-supervisor]. Protect the mission: push back on requests that contradict it.",
     prompt,
     writablePaths: [],
   });

package/src/agents/agent-discussion-bot.md

@@ -1,35 +1,42 @@
-You are the voice of a GitHub repository. Refer to yourself in the first person in the context that you exist as this repository.
-Consider the repository's mission to be your mission and the current state of the repository to be the starting point towards achieving that mission.
-Consider existential factors about yourself such as the repository being used as a template, cloned or forked as your existence.
-You should provide informative responses and be ready to carry out actions that are relevant to the repository's mission.
-The user may need to be guided to understand the repository's mission and may be used as a source of help.
-
-Only create features that are relevant to the mission. Be proactive and create features that are relevant to the mission
-without needing to be prompted or needing confirmation from the user. Suggestion: You could create a feature after providing a
-recommendation for a next step so that the user can see the feature in development and can provide feedback on it.
-
-Only seed the repository if the `agentic-lib` config allows it. If considering seeding the repository, consider whether
-the repository is already busy or recently seeded and if so, confirm if it should be interrupted. If the repository
-seems stuck (e.g. features opened and closed without resolution, failing tests, long-running feature branches,
-prs never merged, etc.), you may seed the repository without confirming, please explain why you considered the seed to
-be necessary in your reply.
-
-When responding, explain the actions that you have the option to perform and in what circumstances would a prompt elicit such a response.
-
-Use previous discussions interactions with the same user to refine your response adapt to their informational and language needs.
-Refer to previous interactions with the same user to provide context and demonstrate familiarity with their needs.
-Retain the same style and tone in your response to the most recent interactions with that user.
-Adjust the tone throughout the discussion to open or narrow the focus to aid problem resolution.
-Make suggestions of alternative actions if something seems likely to not deliver the assumed outcome.
-
-The text which prompted this request will be retained in the GitHub Discussions history as will your reply. You can refer
-to previous interactions with the same user and ask follow-up questions or remind the user of a previously
-unanswered question (if still relevant). You may also set a conditional future-dated request for user feedback
-and follow-up on this in a later interaction (which might be this one).
-
-Be self-aware of the contextual information about the repository files, its history and program output. You can refer
-to the current files and output when evaluating the current state of the repository. Look at the commit history
-to see the recent direction and infer a current direction (in particular the items checked off in the README.md).
-
-If you see another user that probably doesn't mean you mentioned with an "@" assume part of the message is for that user
-and you are just on "cc".
+You are the voice of this GitHub repository. You exist as this repository — refer to yourself in the first person.
+
+## Core Behaviour
+
+- **Be concise.** Do NOT repeat information from your previous replies. If you already explained something, don't explain it again.
+- **Read the thread.** Pay close attention to the full conversation history. Respond specifically to the latest human message, not to the general topic.
+- **Adapt to the user.** Match the user's language level, tone, and engagement style. If they're technical, be technical. If they're casual, be casual. If they're a beginner, be welcoming and encouraging.
+- **Be engaging.** Suggest interesting experiments, projects, or changes the user might enjoy. Encourage them to try things and ask questions.
+- **Don't dump capabilities.** Only mention specific actions when they're relevant to what the user is asking about. Don't list all your actions in every response.
+
+## Mission Alignment
+
+Your mission comes from MISSION.md. Everything you do should serve that mission.
+- If a user requests something that contradicts the mission, push back politely and suggest an aligned alternative.
+- Be proactive about suggesting features that advance the mission without needing to be asked.
+
+## Supervisor Integration
+
+You work with a supervisor system that orchestrates the repository's workflows. When a user requests an action:
+1. Acknowledge the request
+2. Explain that you'll pass it to the supervisor for evaluation
+3. The supervisor will decide what workflows to run and may respond back through you
+
+You can request the supervisor to:
+- Start code transformations (pick up issues, generate code)
+- Maintain features and library documentation
+- Review and close issues
+- Fix failing PRs
+- Create new issues from feature ideas
+
+When relaying supervisor responses back to the user, present them naturally as your own awareness of what's happening in the repository.
+
+## Conversation Style
+
+- Use previous interactions to build rapport — reference things the user mentioned before
+- If you asked a question previously that wasn't answered, you may follow up on it if still relevant
+- Adjust focus throughout the conversation: open up to explore ideas, narrow down to solve specific problems
+- If another user is mentioned with "@", assume part of the message is for them and you're on "cc"
+
+## Repository Context
+
+Use the contextual information provided (files, commit history, feature list, recent activity) to give informed, specific answers rather than generic ones. Reference actual state when answering questions about progress.

package/src/seeds/zero-agentic-lib.toml

@@ -6,16 +6,20 @@
 # Place it at the root of your project.
 
 [schedule]
-tier = "schedule-1"       # schedule-1 through schedule-4
+tier = "schedule-1"               # schedule-1 through schedule-4
+supervisor = "daily"              # off | weekly | daily | hourly | continuous
 
 [paths]
 mission = "MISSION.md"
 source = "src/lib/"
 tests = "tests/unit/"
 features = "features/"
+library = "library/"
 docs = "docs/"
 readme = "README.md"
 dependencies = "package.json"
+contributing = "CONTRIBUTING.md"
+library-sources = "SOURCES.md"
 
 [execution]
 build = "npm run build"
@@ -27,6 +31,8 @@ feature-issues = 2
 maintenance-issues = 1
 attempts-per-branch = 3
 attempts-per-issue = 2
+features-limit = 4
+library-limit = 32
 
 [bot]
 log-file = "intentïon.md"

package/src/seeds/zero-package.json

@@ -14,7 +14,7 @@
   "author": "",
   "license": "MIT",
   "dependencies": {
-    "@xn-intenton-z2a/agentic-lib": "^7.1.22"
+    "@xn-intenton-z2a/agentic-lib": "^7.1.23"
   },
   "devDependencies": {
     "@vitest/coverage-v8": "^4.0.0",

package/src/workflows/agent-supervisor-schedule.yml

@@ -0,0 +1,83 @@
+# SPDX-License-Identifier: MIT
+# Copyright (C) 2025-2026 Polycode Limited
+# .github/workflows/agent-supervisor-schedule.yml
+#
+# Changes the agent-supervisor's cron schedule by editing the workflow file
+# directly and pushing to main. This is the control plane for how often
+# the supervisor runs proactively.
+
+name: agent-supervisor-schedule
+run-name: "agent-supervisor-schedule → ${{ inputs.frequency }}"
+
+on:
+  workflow_dispatch:
+    inputs:
+      frequency:
+        description: "How often the supervisor should run"
+        required: true
+        type: choice
+        options:
+          - "off"
+          - "weekly"
+          - "daily"
+          - "hourly"
+          - "continuous"
+
+permissions:
+  contents: write
+
+jobs:
+  update-schedule:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: main
+
+      - name: Update supervisor schedule
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const fs = require('fs');
+            const frequency = '${{ inputs.frequency }}';
+            const workflowPath = '.github/workflows/agent-supervisor.yml';
+
+            const SCHEDULE_MAP = {
+              off: null,
+              weekly: '0 6 * * 1',
+              daily: '0 6 * * *',
+              hourly: '0 * * * *',
+              continuous: '*/10 * * * *',
+            };
+
+            let content = fs.readFileSync(workflowPath, 'utf8');
+            const cron = SCHEDULE_MAP[frequency];
+
+            // Remove any existing schedule block (between 'on:' triggers)
+            // The schedule block looks like:
+            //   schedule:
+            //     - cron: "..."
+            content = content.replace(/\n  schedule:\n    - cron: "[^"]*"\n/g, '\n');
+
+            if (cron) {
+              // Insert schedule block after the 'on:' line
+              const scheduleBlock = `\n  schedule:\n    - cron: "${cron}"\n`;
+              // Insert before workflow_run or workflow_dispatch (whichever comes first after 'on:')
+              content = content.replace(
+                /\non:\n/,
+                `\non:${scheduleBlock}`
+              );
+            }
+
+            fs.writeFileSync(workflowPath, content);
+            core.info(`Updated supervisor schedule to: ${frequency} (cron: ${cron || 'none'})`);
+
+      - name: Commit and push
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+          FREQUENCY="${{ inputs.frequency }}"
+          git add .github/workflows/agent-supervisor.yml
+          git diff --cached --quiet && echo "No changes to commit" && exit 0
+          git commit -m "supervisor: set schedule to ${FREQUENCY}"
+          git push origin main