@memnexus-ai/mx-agent-cli 0.1.165 → 0.1.167

package/dist/agent-config/settings.json

@@ -0,0 +1,196 @@
+{
+  "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1",
+  "hooks": {
+    "PreToolUse": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bash -c 'H=\"${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null)}/.claude/hooks/memory-checkpoint-reminder.sh\"; [ -f \"$H\" ] && exec bash \"$H\" || exit 0'"
+          }
+        ]
+      },
+      {
+        "matcher": "Bash",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bash -c 'H=\"${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null)}/.claude/hooks/worktree-guard.sh\"; [ -f \"$H\" ] && exec bash \"$H\" || exit 0'"
+          },
+          {
+            "type": "command",
+            "command": "bash -c 'H=\"${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null)}/.claude/hooks/mx-guard-hook.sh\"; [ -f \"$H\" ] && exec bash \"$H\" || exit 0'"
+          },
+          {
+            "type": "command",
+            "command": "bash -c 'H=\"${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null)}/.claude/hooks/ci-validate-hook.sh\"; [ -f \"$H\" ] && exec bash \"$H\" || exit 0'"
+          },
+          {
+            "type": "command",
+            "command": "bash -c 'H=\"${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null)}/.claude/hooks/workflow-dispatch-guard.sh\"; [ -f \"$H\" ] && exec bash \"$H\" || exit 0'"
+          },
+          {
+            "type": "command",
+            "command": "bash -c 'H=\"${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null)}/.claude/hooks/git-mutation-guard.sh\"; [ -f \"$H\" ] && exec bash \"$H\" || exit 0'"
+          },
+          {
+            "type": "command",
+            "command": "bash -c 'H=\"${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null)}/.claude/hooks/named-memory-write-guard.sh\"; [ -f \"$H\" ] && exec bash \"$H\" || exit 0'"
+          }
+        ]
+      }
+    ],
+    "PostToolUse": [
+      {
+        "matcher": "Bash",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bash -c 'H=\"${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null)}/.claude/hooks/deploy-verification-reminder.sh\"; [ -f \"$H\" ] && exec bash \"$H\" || exit 0'"
+          }
+        ]
+      }
+    ],
+    "PreCompact": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bash -c 'H=\"${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null)}/.claude/hooks/auto-checkpoint.sh\"; [ -f \"$H\" ] && exec bash \"$H\" || exit 0'"
+          },
+          {
+            "type": "command",
+            "command": "bash -c 'H=\"${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null)}/.claude/hooks/auto-capture-precompact.sh\"; [ -f \"$H\" ] && exec bash \"$H\" || exit 0'"
+          }
+        ]
+      }
+    ],
+    "SessionStart": [
+      {
+        "matcher": "compact",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bash -c 'H=\"${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null)}/.claude/hooks/reload-checkpoint.sh\"; [ -f \"$H\" ] && exec bash \"$H\" || exit 0'"
+          }
+        ]
+      },
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bash -c 'H=\"${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null)}/.claude/hooks/set-terminal-appearance.sh\"; [ -f \"$H\" ] && exec bash \"$H\" || exit 0'"
+          }
+        ]
+      }
+    ],
+    "Stop": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "mx-agent sync --api-url https://api.dev.memnexus.ai/internal/observability --quiet 2>/dev/null || true"
+          },
+          {
+            "type": "command",
+            "command": "bash -c 'H=\"${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null)}/.claude/hooks/auto-capture-session-end.sh\"; [ -f \"$H\" ] && exec bash \"$H\" || exit 0'"
+          },
+          {
+            "type": "command",
+            "command": "bash -c 'H=\"${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null)}/.claude/hooks/delegation-audit.sh\"; [ -f \"$H\" ] && exec bash \"$H\" || exit 0'"
+          },
+          {
+            "type": "command",
+            "command": "bash -c 'H=\"${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null)}/.claude/hooks/iteration-log-check.sh\"; [ -f \"$H\" ] && exec bash \"$H\" || exit 0'"
+          }
+        ]
+      }
+    ]
+  },
+  "permissions": {
+    "allow": [
+      "mcp__MX__search_memories",
+      "mcp__MX__create_memory",
+      "mcp__MX__retrieve_episodic_memory",
+      "mcp__MX__get_patterns",
+      "mcp__MX__detect_patterns",
+      "mcp__MX__get_topic_summary",
+      "mcp__MX__search_semantic_facts",
+      "mcp__MX__find_conversations_by_topic",
+      "mcp__MX__graphrag_query",
+      "mcp__MX__get_memory_usage",
+      "mcp__MX__list_conversations",
+      "Bash",
+      "Read",
+      "Edit",
+      "Write",
+      "Glob",
+      "Grep",
+      "WebFetch",
+      "WebSearch",
+      "Task",
+      "NotebookEdit"
+    ],
+    "deny": [
+      "Bash(rm -rf /*)",
+      "Bash(rm -rf /)",
+      "Bash(rm -rf ~)",
+      "Bash(rm -rf ~/*)",
+      "Bash(dd if=/dev/zero *)",
+      "Bash(mkfs *)",
+      "Bash(shred *)",
+      "Bash(git reset --hard HEAD~*)",
+      "Bash(git reset --hard HEAD^*)",
+      "Bash(git checkout -- *)",
+      "Bash(git restore --worktree*)",
+      "Bash(git clean -fd *)",
+      "Bash(git clean -fdx *)",
+      "Bash(kubectl delete namespace *)",
+      "Bash(kubectl delete node *)",
+      "Bash(helm uninstall *)",
+      "Bash(az group delete *)",
+      "Bash(az aks delete *)",
+      "Bash(az deployment group delete *)",
+      "Bash(git checkout main)",
+      "Bash(git checkout main *)",
+      "Bash(git checkout -)",
+      "Bash(git switch main)",
+      "Bash(git switch main *)",
+      "Bash(git checkout -b *)",
+      "Bash(git switch -c *)",
+      "Bash(git switch --create *)",
+      "Bash(git branch * *)",
+      "Bash(git merge *)",
+      "Bash(git push origin main)",
+      "Bash(git push origin main *)",
+      "Bash(git push -u origin main)",
+      "Bash(git push -u origin main *)",
+      "Bash(git push --force origin main)",
+      "Bash(git push --force origin main *)",
+      "Bash(git push -f origin main)",
+      "Bash(git push -f origin main *)"
+    ],
+    "ask": [
+      "Bash(sudo *)",
+      "Bash(chown *)",
+      "Bash(docker kill *)",
+      "Bash(docker rm *)",
+      "Bash(docker rmi *)",
+      "Bash(kubectl delete pod *)",
+      "Bash(kubectl delete deployment *)",
+      "Bash(kubectl delete service *)",
+      "Bash(kubectl drain *)",
+      "Bash(kubectl taint *)",
+      "Bash(helm upgrade *)",
+      "Bash(helm rollback *)",
+      "Bash(az aks upgrade *)",
+      "Bash(az aks scale *)",
+      "Bash(az deployment group create *)",
+      "Bash(az vm delete *)",
+      "Bash(az storage account delete *)"
+    ]
+  }
+}

package/dist/agent-config/shared/eval-tiered-rigor.md

@@ -0,0 +1,15 @@
+# Eval Tiered Rigor Policy (PO-adopted 2026-07-04)
+
+Reference for all teams requesting or consuming eval measurements. Gate intensity scales with **instrument novelty**, not run size.
+
+| Tier | When | Gates | Turnaround | Claims |
+|---|---|---|---|---|
+| A | New mechanism/instrument, or claim-grade result | Full: prereg + Bar Raiser + Red Team + mutation-tested Code Review + pre-launch Step-6 | Days | Claim-ledger grade |
+| B | Repeat run on a validated harness (model/corpus/config pin swap) | Preflight + runtime canaries + single-reviewer checklist + Step-6 | ~1 day | Claim-ledger grade with Tier-B tag |
+| C | Exploratory / diagnostic | Leader judgment + runtime canaries | Hours | NON-CLAIMABLE by construction |
+
+Non-negotiable at every tier: the runtime guards (preflight checks, delivery/injection canaries, completeness gates, hard flag/pin checks). They are minutes-cheap and exist because each one's absence once produced a wrong number.
+
+Precision/speed trades available on request: stratified sampling (~70 tasks, CI ~±7pp) for direction-finding; matched symmetric concurrency (unbiased for arm deltas). Full-corpus ±4pp runs on request for claim-grade needs.
+
+Asking teams: file requests via cross-team escalations with the question + tier you need; eval will quote turnaround per this table.

package/dist/agent-config/shared/team-operating-rules.md

@@ -0,0 +1,37 @@
+# Shared Team Operating Rules
+
+These rules apply to every mx-agent team. Role guides may add stricter requirements.
+
+## Worktree Discipline
+
+- Work only inside your assigned worktree unless the user explicitly asks otherwise.
+- Do not create a second implementation worktree from inside an already isolated worktree. Delegate work on the current branch and review the resulting diff there.
+- Do not cherry-pick sub-agent commits back from nested worktrees as a normal workflow.
+
+## Evidence and Review
+
+- Search existing memories, issues, docs, and code before starting non-trivial work.
+- Treat harnesses, migrations, retrieval logic, protocol code, and scoring code as high-risk even when the patch is small.
+- For high-risk code, use an independent Code Reviewer or tester before merging.
+- Do not self-certify important findings. A claim that affects product, benchmark, customer, or roadmap decisions needs independent reproduction or a clear caveat.
+
+## Delegation Gates
+
+- Team leads coordinate the work and activate the relevant specialists from the role guide.
+- Before closing an iteration, confirm implementation, review, testing, and memory/state updates were actually completed.
+- If a role guide defines gate artifacts, produce those artifacts before claiming the work is done.
+
+## Command and Hook Output
+
+- Interpret hook output carefully. A reminder printed by a hook is not a command failure unless the tool result or exit code indicates failure.
+- When a hook is noisy but non-blocking, continue with the task and note the interpretation in the iteration record if relevant.
+
+## Memory and State
+
+- Save memories for material decisions, failures, fixes, gotchas, and iteration closeouts.
+- Named state memories must use the project prefix required by `CLAUDE.local.md`.
+- When updating a conclusion, clearly state what superseded or invalidated the prior belief.
+
+## Stop Conditions
+
+Pause and ask for direction when authority is unclear, evidence contradicts a committed direction, deployment verification fails and cannot be resolved, or required independent review cannot be obtained for high-risk work.

package/dist/agent-config/skills/eval-claim-impact/SKILL.md

@@ -0,0 +1,20 @@
+# Eval Claim Impact
+
+Use this skill before stating or relying on a benchmark conclusion.
+
+## Procedure
+
+1. State the claim in one sentence.
+2. Link the exact runs, commits, config, data slice, and report that support it.
+3. Check whether any known harness issue, fixture gap, sampling flaw, or analysis bug could explain the result.
+4. Compare the claim against raw examples, not only aggregate metrics.
+5. Assign confidence: low, medium, high, or invalidated.
+6. If confidence is below high, state the next validation needed before the claim can guide product decisions.
+7. Save or update the claim ledger memory with the current status.
+
+## Required Output
+
+- Claim.
+- Evidence.
+- Counterevidence or known risks.
+- Confidence and next validation step.

package/dist/agent-config/skills/eval-harness-review/SKILL.md

@@ -0,0 +1,21 @@
+# Eval Harness Review
+
+Use this skill when reviewing or changing benchmark harnesses, scoring code, fixtures, sampling, persistence, or eval reports.
+
+## Procedure
+
+1. Identify the decision the eval is supposed to support.
+2. Read the harness entrypoint, scorer, fixture loader, persistence layer, and report generator.
+3. List P0 failure modes that would invalidate the result.
+4. Add or verify fixtures for each P0 path, including negative controls and boundary cases.
+5. Replay at least one known-good and one known-bad transcript through the scorer.
+6. Inspect raw run records and aggregate outputs for consistency.
+7. Ask an independent reviewer to check the diff and the interpretation.
+8. Record unresolved risk in the claim ledger before publishing results.
+
+## Required Output
+
+- Files reviewed.
+- Fixtures or replays run.
+- Bugs found or explicitly ruled out.
+- Remaining risks and confidence level.

package/dist/agent-config/skills/mx-checkpoint/SKILL.md

@@ -0,0 +1,111 @@
+---
+name: mx-checkpoint
+description: "Comprehensive checkpoint for major milestones or context switches. Interactively gathers project context, decisions, blockers, and next steps to create a thorough memory."
+disable-model-invocation: true
+version: "1.7.158"
+---
+
+# Checkpoint Memory
+
+You are helping create a comprehensive checkpoint memory for a project or major initiative. These serve as context hubs that make future recall much easier.
+
+## When to Use
+
+- Starting or pausing major work
+- Context switching between tasks
+- Completing a significant milestone
+- Creating a searchable project anchor
+
+## Information to Gather
+
+Ask the user for these (skip items that don't apply):
+
+1. **Project/Initiative Name** — What is this work called?
+2. **Planning Documents** — Where is the spec or design doc?
+3. **GitHub Issues/PRs** — What issues or PRs track this work?
+4. **Goal/Purpose** — What is the main objective?
+5. **Current Status** — Planning, in-progress, paused, completed?
+6. **Key Files/Directories** — Main files being created/modified?
+7. **Technologies/Tools** — What key technologies are involved?
+8. **Next Steps** — What should happen next?
+9. **Blockers/Dependencies** — Anything blocking progress?
+
+## Memory Content Template
+
+```
+[Project Name] — [Status]
+
+Planning doc: [path/to/doc.md]
+GitHub issue: #[number]
+Related PRs: #[numbers]
+
+Goal: [1-2 sentence objective]
+
+Current status: [What's done, what's pending, decisions made]
+
+Key files:
+- [path/to/file1.ts]
+- [path/to/file2.md]
+
+Technologies: [comma-separated list]
+
+Next steps: [What to do when resuming]
+
+Blockers: [If any]
+```
+
+## Topic Selection
+
+Choose 6-10 topics. Only add manual topics for:
+- **Status**: `completed`, `in-progress`, `blocked`, `paused`
+- **Component**: project-specific component names
+
+Other topics are auto-extracted from content.
+
+## Conversation Tracking
+
+1. Check if you already have a conversation ID from this session
+2. If yes → reuse it
+3. If no → use conversationId: "NEW"
+4. Capture the conv_xxx ID for follow-up memories
+
+## How to Save
+
+**Prefer MCP tools:**
+
+```
+create_memory({
+  content: "YOUR GENERATED CONTENT",
+  conversationId: "<ID or NEW>",
+  topics: ["component", "status"]
+})
+```
+
+**Fallback to CLI:**
+
+```bash
+mx memories create \
+  --conversation-id "<ID or NEW>" \
+  --content "YOUR GENERATED CONTENT" \
+  --topics "component,status"
+```
+
+## Context Switch Pattern
+
+If the user is pausing work, suggest a "breadcrumb" memory:
+
+```
+Pausing work on [project name] at [checkpoint].
+
+Status: [current state and what was just completed]
+Next: [specific next action when resuming]
+Context: [important context needed to resume]
+```
+
+## After Saving
+
+Report back:
+- Memory ID created
+- Brief confirmation
+- Conversation ID for follow-up
+- Suggest testing recall: `search_memories({ query: "[project name]" })`

package/dist/agent-config/skills/mx-fix-pr/SKILL.md

@@ -0,0 +1,90 @@
+---
+name: mx-fix-pr
+description: Diagnose and fix a PR that is not mergeable, has failing CI, or won't trigger checks. Use when a PR is stuck.
+---
+
+Use this workflow when a PR is stuck — not mergeable, CI failing, checks not triggering, or blocked.
+
+## Step 1: Check PR State
+
+```bash
+gh pr view <number> --json mergeable,mergeStateStatus,statusCheckRollup
+```
+
+Read the output carefully. The `mergeStateStatus` tells you the problem category.
+
+## Step 2: Diagnose and Fix
+
+Based on the PR state, follow the appropriate branch:
+
+### Not Mergeable / DIRTY
+
+The branch has diverged from main or has merge conflicts.
+
+- Delegate to Git Expert (`.claude/agents/git-expert.md`) to rebase the branch onto `origin/main` and force-push with lease.
+- Do NOT attempt git operations yourself.
+
+### CI Failing
+
+One or more status checks failed.
+
+```bash
+# Find the failing run
+gh pr checks <number>
+
+# Read the failure logs
+gh run view <run-id> --log-failed
+```
+
+- Read the failure output. Fix the code.
+- Delegate code fixes to Implementation Engineer if the fix is non-trivial.
+- Push a new commit with the fix.
+
+### CI Not Triggered / PENDING Forever
+
+Checks are not running or stuck in pending state.
+
+- The branch may need a force-push to re-trigger workflows. Delegate to Git Expert.
+- Check if the workflow file has `paths:` filters that exclude your changed files.
+- Check if the branch name matches the workflow's `branches:` trigger pattern.
+
+### BLOCKED
+
+Required status checks are missing entirely.
+
+- Verify the workflow file exists and is on the default branch.
+- Verify the branch name matches the workflow trigger pattern.
+- Check branch protection rules: `gh api repos/{owner}/{repo}/branches/main/protection`
+
+### Merge Conflicts Shown on GitHub
+
+GitHub shows conflict markers but the branch was clean locally.
+
+- Delegate to Git Expert to rebase on `origin/main` and resolve conflicts.
+- After rebase and force-push, GitHub will re-evaluate mergeability.
+
+## Step 3: Verify Fix
+
+After applying the fix:
+
+```bash
+# Check all status checks are green
+gh pr checks <number>
+
+# Confirm PR is mergeable
+gh pr view <number> --json mergeable
+```
+
+Both must pass. If not, return to Step 2.
+
+## Step 4: Handle Queued CI
+
+If CI is queued but not running:
+
+```bash
+gh run list --limit 5 --json status,name
+```
+
+If runners are busy, wait for the queue to clear. Do NOT stack additional pushes — each push resets the queue position.
+
+> Always delegate git operations to Git Expert. Only push code fixes yourself via the Implementation Engineer.

package/dist/agent-config/skills/mx-gap-assessment/SKILL.md

@@ -0,0 +1,90 @@
+---
+name: mx-gap-assessment
+description: Identify the next gap to pursue with mandatory prior art search and Red Team challenge. Use at Step 2/3 of the improvement loop.
+---
+
+Follow this workflow to identify, validate, and document the next gap. Every step is mandatory.
+
+## Step 1: Prior Art Search
+
+Delegate to Prior Art Researcher (`.claude/agents/prior-art-researcher.md`) to search for prior work in the problem area. The researcher should check:
+
+- Existing memories and patterns related to the gap area
+- Previous iterations that touched this area
+- Known issues and gotchas
+
+**Wait for the prior art report before proceeding.**
+
+> The Bar Raiser checks for prior art search evidence at every iteration close. A gap assessment without prior art search results is a blocking finding.
+
+## Step 2: Check GitHub Issues
+
+```bash
+gh issue list --state open --search "<team keywords>" --limit 20
+```
+
+Review open issues. P1/P2 issues override metric-driven gap selection — if a critical issue exists, it becomes the gap regardless of other signals.
+
+## Step 3: Identify the Highest-Impact Gap
+
+Review all available evidence:
+
+- Metrics and production data from your team's dashboard
+- Feedback from users or other teams
+- Prior art report from Step 1
+- Open GitHub issues from Step 2
+
+Select the single highest-impact gap using your team's prioritization framework. One gap per iteration — do not bundle multiple gaps.
+
+## Step 4: Write the Gap Assessment
+
+Document the gap with these sections:
+
+1. **Gap description** — what is broken, missing, or underperforming
+2. **Evidence** — specific metrics, production data, or user feedback that demonstrate the gap
+3. **Priority rationale** — why this gap over alternatives
+4. **Prior art results** — what the Prior Art Researcher found (prior attempts, related work, known constraints)
+5. **Proposed approach** — high-level plan to close the gap
+
+## Step 5: Red Team Challenge
+
+Delegate to Red Team (`.claude/agents/red-team.md`) to challenge the gap selection:
+
+- Is this really the highest-impact gap? What alternatives were considered?
+- Pre-mortem: assume this approach fails in 2 weeks — what went wrong?
+- Are there hidden dependencies or risks not addressed in the assessment?
+
+**Wait for the Red Team response.**
+
+## Step 6: Address the Challenge
+
+Review the Red Team's challenges. For each one:
+
+- **Accept and adjust** — modify the plan to address the concern
+- **Reject with rationale** — document why the challenge was considered but rejected
+
+Update the gap assessment with the Red Team findings and your responses.
+
+## Step 7: Store the Gap Assessment
+
+Save the gap assessment as a memory:
+
+```
+create_memory({
+  conversationId: "NEW",
+  content: "<full gap assessment with Red Team responses>",
+  topics: ["<component>", "in-progress"]
+})
+```
+
+Capture the new `conversationId` from the response — use it for all subsequent memories in this iteration.
+
+## Step 8: Create Tracking Issue
+
+Create a GitHub issue to track the iteration:
+
+```bash
+gh issue create --title "Iteration N: <gap title>" --body "<gap summary, acceptance criteria, approach>"
+```
+
+Record the issue number in your leader-state memory.

package/dist/agent-config/skills/mx-iteration-close/SKILL.md

@@ -0,0 +1,81 @@
+---
+name: mx-iteration-close
+description: Close out the current iteration with all required artifacts. Use at Step 7/8 after validation and measurement are complete.
+---
+
+Complete every step in order. An iteration is NOT complete until all 7 steps are done. Do not start the next iteration before finishing this checklist.
+
+## Step 1: Verify All PRs Merged and Deployed
+
+List PRs for this iteration. Every PR must be merged.
+
+```bash
+gh pr list --state open --search "<iteration keywords>"
+```
+
+If any PRs are open, merge them first. Do not proceed with open PRs.
+
+## Step 2: Verify Deployment
+
+For each merged PR, confirm the deploy pipeline succeeded:
+
+```bash
+# Get the merge commit SHA
+gh pr view <number> --json mergeCommit --jq '.mergeCommit.oid'
+
+# Check pipeline status
+gh run list --commit <sha> --json status,conclusion,name --jq '.[]'
+```
+
+- **Service changes:** Pipeline conclusion must be `success`.
+- **CLI changes:** `npm view <package> version` must show the new version.
+- **If pipeline is running:** Wait. Do not proceed.
+- **If pipeline failed:** Fix it. Do not proceed.
+
+## Step 3: Delegate to Status Reporter
+
+Delegate to Status Reporter (`.claude/agents/status-reporter.md`) to produce all iteration artifacts.
+Named-memory keys below are `<product-slug>-<team>-<type>`: `<product-slug>` is the `projectSlug` from
+`mx-agent.config.json` (**`memnexus` in this repository**) and `<team>` is your team slug — e.g.
+`<product-slug>-<team>-iteration-log` resolves to `memnexus-platform-iteration-log`.
+
+1. **Write the dev-log file** for this iteration
+2. **Update `<product-slug>-<team>-iteration-log`** — add a new row: iteration number, focus, human intervention (yes/no), measurable outcome (yes/no), status, PR numbers
+3. **Update `<product-slug>-<team>-leader-state`** — reflect iteration complete + next planned action
+4. **Update `<product-slug>-<team>-known-issues`** — mark resolved issues, add any new ones discovered
+5. **Create an iteration report memory** with full details
+
+Wait for the Status Reporter to complete before proceeding.
+
+## Step 4: Close Tracking Issue
+
+Close the GitHub issue that was tracking this iteration. Add a summary comment:
+
+```bash
+gh issue close <number> --comment "Iteration N complete. <brief summary>. PRs: #X, #Y."
+```
+
+## Step 5: Delegate to Dogfood Auditor
+
+Delegate to Dogfood Auditor (`.claude/agents/dogfood-auditor.md`) to run the self-audit checklist. Address any findings before declaring the iteration complete.
+
+## Step 6: Save Memory Checkpoint
+
+Save a checkpoint memory with the iteration summary:
+
+```
+create_memory({
+  conversationId: "<current_conv_id>",
+  content: "Iteration N complete. Focus: <what>. Outcome: <measurable result>. PRs: #X, #Y. Next: <next step>.",
+  topics: ["<component>", "completed"]
+})
+```
+
+## Step 7: Verify Dual-Logging
+
+Confirm both artifacts exist:
+
+1. **Dev-log file** — check the file exists in the repo at the expected path
+2. **MemNexus memory** — search for the iteration report memory
+
+If either is missing, create it now. Both are required for auditability.