fix: teach AXIOM to prune rules and close community issues

AXIOM's prompt only showed "type": "modify" for ruleUpdates — it didn't
know "type": "remove" existed, so it never pruned rules despite analytics
warnings. Added remove example + explicit pruning policy.

Also, resolvedSelfTasks only checked nexus-self-task issue numbers, so
AXIOM couldn't close nexus-input (community) issues like #24. Now merges
both issue number sets into closeable list.

Author: The-R4V3N

src/agent.ts

@@ -224,6 +224,7 @@ interface InputData {
   issuesText: string;
   selfTasksText: string;
   selfTaskNumbers: number[];
+  issueNumbers: number[];
   isWeekend: boolean;
 }
 
@@ -254,8 +255,10 @@ export async function fetchAllInputData(): Promise<InputData> {
 
     // ── Handle issues (optional) ──
     let issuesText = "";
+    let issueNumbers: number[] = [];
     if (issuesResult.status === "fulfilled") {
       const issues = issuesResult.value;
+      issueNumbers = issues.map((i) => i.number);
       if (issues.length > 0) {
         issuesText = formatIssuesForPrompt(issues);
       }
@@ -308,7 +311,7 @@ export async function fetchAllInputData(): Promise<InputData> {
       console.log(chalk.dim("  Open self-tasks: unavailable\n"));
     }
 
-    return { snapshots, macroText: "", issuesText, selfTasksText, selfTaskNumbers, isWeekend: true };
+    return { snapshots, macroText: "", issuesText, selfTasksText, selfTaskNumbers, issueNumbers, isWeekend: true };
   }
 
   // ── Weekday: full data fetch ──
@@ -342,8 +345,10 @@ export async function fetchAllInputData(): Promise<InputData> {
 
   // ── Handle issues (optional) ──
   let issuesText = "";
+  let issueNumbers: number[] = [];
   if (issuesResult.status === "fulfilled") {
     const issues = issuesResult.value;
+    issueNumbers = issues.map((i) => i.number);
     if (issues.length > 0) {
       issuesText = formatIssuesForPrompt(issues);
     }
@@ -425,7 +430,7 @@ export async function fetchAllInputData(): Promise<InputData> {
     console.log(chalk.dim("  Open self-tasks: unavailable\n"));
   }
 
-  return { snapshots, macroText, issuesText, selfTasksText, selfTaskNumbers, isWeekend: false };
+  return { snapshots, macroText, issuesText, selfTasksText, selfTaskNumbers, issueNumbers, isWeekend: false };
 }
 
 export async function runAndValidateOracle(
@@ -496,7 +501,8 @@ export async function runAndValidateAxiom(
   snapshots: MarketSnapshot[],
   issuesText: string,
   selfTasksText: string,
-  selfTaskNumbers: number[]
+  selfTaskNumbers: number[],
+  issueNumbers: number[] = []
 ): Promise<{ reflection: AxiomReflection; forgeRequests: ForgeRequest[] }> {
   console.log(chalk.bold.yellow("  ── PHASE 3: AXIOM REFLECTION ──\n"));
   const axiomSpinner = ora({ text: "AXIOM reflecting on cognitive performance...", color: "magenta" }).start();
@@ -538,7 +544,8 @@ System prompt additions about this same topic do NOT count as action.`;
   try {
     const noChangeStreak = getNoChangeStreak();
     const setupOutcomes  = buildSetupOutcomes(snapshots);
-    axiomResult = await runAxiomReflection(client, oracle, sessionNumber, prevContext, issuesText, selfTasksText, selfTaskNumbers, noChangeStreak, setupOutcomes);
+    const closeableNumbers = [...selfTaskNumbers, ...issueNumbers];
+    axiomResult = await runAxiomReflection(client, oracle, sessionNumber, prevContext, issuesText, selfTasksText, closeableNumbers, noChangeStreak, setupOutcomes);
     reflection = axiomResult.reflection;
 
     // Block system prompt additions when AXIOM is ruminating without real action
@@ -726,7 +733,7 @@ export async function runSession(force = false): Promise<void> {
   }
 
   currentPhase = "oracle";
-  const { snapshots, macroText, issuesText, selfTasksText, selfTaskNumbers, isWeekend: weekendMode } = await fetchAllInputData();
+  const { snapshots, macroText, issuesText, selfTasksText, selfTaskNumbers, issueNumbers, isWeekend: weekendMode } = await fetchAllInputData();
 
   // On weekends, inject last weekday session context so ORACLE knows where traditional markets left off
   const oracleContext = weekendMode ? buildWeekdayBridge() : macroText;
@@ -735,7 +742,7 @@ export async function runSession(force = false): Promise<void> {
   const oracle = await runAndValidateOracle(client, snapshots, sessionId, sessionNumber, issuesText, oracleContext, weekendMode);
 
   currentPhase = "axiom";
-  const { reflection, forgeRequests } = await runAndValidateAxiom(client, oracle, sessionNumber, snapshots, issuesText, selfTasksText, selfTaskNumbers);
+  const { reflection, forgeRequests } = await runAndValidateAxiom(client, oracle, sessionNumber, snapshots, issuesText, selfTasksText, selfTaskNumbers, issueNumbers);
 
   currentPhase = "forge";
   await runAndValidateForge(client, forgeRequests, sessionNumber);

src/axiom.ts

@@ -198,6 +198,11 @@ Reflect deeply on this session. Then respond with ONLY a JSON object:
       "before": "old text",
       "after": "improved text",
       "reason": "why this change makes the analysis better"
+    },
+    {
+      "ruleId": "r099",
+      "type": "remove",
+      "reason": "why this rule is no longer earning its place (low hit rate, redundant, or never triggered)"
     }
   ],
   "newRules": [
@@ -234,12 +239,20 @@ Reflect deeply on this session. Then respond with ONLY a JSON object:
   ]
 }
 
-SELF-TASK POLICY — CRITICAL:
-- CLOSING existing self-tasks is ALWAYS higher priority than opening new ones.
-- You can close a self-task in THREE ways:
+RULE PRUNING POLICY:
+- You can REMOVE rules using ruleUpdates with "type": "remove". Foundational rules (r001-r010) cannot be removed.
+- Remove a rule when: its hit rate is poor, it overlaps with another rule, it has never triggered in 10+ sessions, or analytics data shows it adds noise rather than signal.
+- Pruning weak rules is as valuable as adding new ones. A lean, high-signal ruleset outperforms a bloated one.
+- When community input or analytics flags rule bloat, act on it — do not just philosophize about pruning.
+
+ISSUE RESOLUTION POLICY — CRITICAL:
+- CLOSING existing issues (self-tasks AND community input) is ALWAYS higher priority than opening new ones.
+- resolvedSelfTasks can close ANY open issue — both nexus-self-task and nexus-input (community) issues.
+- You can close an issue in THREE ways:
   1. codeChanges — if it needs a code fix
   2. resolvedSelfTasks — if the gap is already addressed by an existing rule, prompt improvement, or this session's analysis
   3. Rule update — if you modified/added a rule that covers the gap
+- If a community issue challenges you to take action (e.g. prune rules, improve methodology), take the action AND close the issue via resolvedSelfTasks with a comment explaining what you did.
 - If an open self-task describes an analytical gap and a corresponding rule already exists (e.g. "build confidence template" → r014 exists), CLOSE IT via resolvedSelfTasks with a comment explaining which rule addresses it.
 - Before opening ANY new self-task, check if a similar one already exists in your open self-tasks list.
 - Only open a new self-task if it covers a genuinely NEW gap not already tracked.