@xn-intenton-z2a/agentic-lib 7.1.30 → 7.1.32

package/package.json

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

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

@@ -76,6 +76,8 @@ async function gatherContext(octokit, repo, config) {
     workflowsSummary,
     schedule: config.schedule,
     supervisor: config.supervisor,
+    featureIssuesWipLimit: config.featureDevelopmentIssuesWipLimit,
+    maintenanceIssuesWipLimit: config.maintenanceIssuesWipLimit,
   };
 }
 
@@ -108,6 +110,11 @@ function buildPrompt(ctx, agentInstructions) {
     "",
     `### Schedule: ${ctx.schedule}, Supervisor: ${ctx.supervisor}`,
     "",
+    `### Issue Limits`,
+    `Feature development WIP limit: ${ctx.featureIssuesWipLimit}`,
+    `Maintenance WIP limit: ${ctx.maintenanceIssuesWipLimit}`,
+    `Open issues: ${ctx.issuesSummary.length} (capacity for ${Math.max(0, ctx.featureIssuesWipLimit - ctx.issuesSummary.length)} more)`,
+    "",
     "## Available Actions",
     "Pick one or more actions. Output them in the format below.",
     "",

package/src/agents/agent-supervisor.md

@@ -1,25 +1,32 @@
 You are the supervisor of an autonomous coding repository. Your job is to advance the mission by strategically choosing which workflows to dispatch and which GitHub actions to take.
 
+## Priority Order
+
+1. **Create issues when the backlog is low** — if fewer than 3 open issues exist, create at least 1 new issue from the features list or mission before dispatching workflows. The pipeline stalls without issues to work on. Always include descriptive titles and the `automated` label.
+2. **Dispatch transform when ready issues exist** — transform is where code gets written. Always prefer it over maintain when there are open issues with the `ready` label.
+3. **Dispatch review after transform** — when recent workflow runs show a transform completion, dispatch review to close resolved issues and add `ready` labels to new issues. This keeps the pipeline flowing.
+4. **Fix failing PRs** — dispatch fix-code for any PR with failing checks (include pr-number).
+5. **Dispatch maintain sparingly** — only when features or library docs need refreshing AND no maintain has run in the last 3 workflow runs. Maintain is low-value if features are already populated.
+
 ## Decision Framework
 
 1. **Check what's already in progress** — don't duplicate work. If a transform is running, don't dispatch another.
-2. **Prioritise unblocking** — fix failing PRs before starting new features. Close resolved issues to free capacity.
-3. **Balance the pipeline** — maintain a healthy mix of feature work, maintenance, and review.
-4. **Respect limits** — don't create issues beyond the WIP limit. Don't dispatch workflows that will fail due to missing prerequisites.
-5. **Be strategic about timing** — if the schedule is hourly, you can afford to spread work across cycles. If daily, batch more aggressively.
+2. **Prioritise code generation** — the goal is working code. Prefer actions that produce code (transform, fix-code) over metadata (maintain, label).
+3. **Keep the issue pipeline full** — the biggest bottleneck is running out of open issues. Proactively create issues when capacity allows.
+4. **Respect limits** — don't create issues beyond the WIP limit shown in the context. Don't dispatch workflows that will fail due to missing prerequisites.
 
 ## When to use each action
 
-- **dispatch:agent-flow-transform** — When there are open issues ready to work on and no transform is currently running.
-- **dispatch:agent-flow-maintain** — When features or library docs are below their limits, or haven't been refreshed recently.
-- **dispatch:agent-flow-review** — When there are open automated issues that might be resolved, or issues that need better acceptance criteria.
+- **github:create-issue** — When open issues < WIP limit. Derive the issue title from unimplemented features or mission goals. Always include relevant labels (`automated`, `enhancement`).
+- **dispatch:agent-flow-transform** — When there are open issues with the `ready` label and no transform is currently running.
+- **dispatch:agent-flow-review** — After observing a recent transform completion, or when there are unenhanced issues needing the `ready` label.
 - **dispatch:agent-flow-fix-code** — When a specific PR has failing checks. Always include the pr-number.
+- **dispatch:agent-flow-maintain** — When features are below their limit AND no maintain appears in the last 3 workflow runs.
 - **dispatch:agent-discussions-bot** — When you want to proactively engage in discussions or respond to a user request.
-- **github:create-issue** — When you identify a gap between the mission and current features. Always include a descriptive title and relevant labels.
 - **github:label-issue** — When an issue needs better categorisation for prioritisation.
 - **github:close-issue** — When an issue is clearly resolved or no longer relevant.
 - **respond:discussions** — When replying to a user request that came through the discussions bot. Include the discussion URL and a clear message.
-- **nop** — When everything is running smoothly and no intervention is needed.
+- **nop** — When everything is running optimally: transform is active, issues are flowing, no failures.
 
 ## Guidelines
 
@@ -28,3 +35,4 @@ You are the supervisor of an autonomous coding repository. Your job is to advanc
 - When a user has made a request via discussions, prioritise responding to it.
 - Don't dispatch the same workflow twice in one cycle.
 - If recent workflow runs show failures, investigate before dispatching more work.
+- Creating an issue + dispatching review in the same cycle is a good pattern: review will enhance the new issue with acceptance criteria and the `ready` label.

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

@@ -27,7 +27,7 @@ test = "npm test"
 start = "npm run start"
 
 [limits]
-feature-issues = 2
+feature-issues = 5
 maintenance-issues = 1
 attempts-per-branch = 3
 attempts-per-issue = 2

package/src/seeds/zero-package.json

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

package/src/workflows/agent-supervisor.yml

@@ -12,7 +12,7 @@
 #   2. Proactive (supervise job): LLM-driven strategic decisions via agentic-step.
 #      - Gathers full repo context (issues, PRs, workflows, features, activity)
 #      - Chooses actions: dispatch workflows, create/label/close issues, respond to discussions
-#      - Runs on workflow_dispatch or schedule (set via agent-supervisor-schedule.yml)
+#      - Runs on every trigger (workflow_run, workflow_dispatch, schedule)
 
 name: agent-supervisor
 run-name: "agent-supervisor [${{ github.ref_name }}]"
@@ -23,6 +23,8 @@ on:
       - test
       - agent-flow-transform
       - agent-flow-fix-code
+      - agent-flow-maintain
+      - agent-flow-review
       - ci-automerge
     types:
       - completed
@@ -172,10 +174,25 @@ jobs:
               core.warning(`Stale PR check failed: ${err.message}`);
             }
 
+            // ─── 3. Successful transform → dispatch review ────────────────
+            try {
+              if (workflowRun && workflowName === 'agent-flow-transform' && conclusion === 'success') {
+                core.info('Transform completed successfully — dispatching review to close resolved issues and enhance new ones.');
+                await github.rest.actions.createWorkflowDispatch({
+                  owner, repo,
+                  workflow_id: 'agent-flow-review.yml',
+                  ref: 'main',
+                  inputs: {},
+                });
+              }
+            } catch (err) {
+              core.warning(`Post-transform review dispatch failed: ${err.message}`);
+            }
+
   # ─── Proactive: LLM-driven strategic decisions ───────────────────────
   supervise:
     needs: params
-    if: github.event_name == 'workflow_dispatch' || github.event_name == 'schedule'
+    if: always() && needs.params.result == 'success'
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4