Summary

• Problem: repo-triage.yaml (Claude variant) is the only triage workflow; running it on every cadence burns Claude tokens and is blocked when the nested-Claude-Code session bug (2 issues: v0.3.5: CLI workflow run silently hangs — dotenv loads .env from CWD instead of ~/.archon/.env,, + rchon serve hardcodes skipPlatformAdapters:true — Telegram/Discord/Slack adapters are unreachable #1067) hits.
• Why it matters: Same precedent as maintainer-standup-minimax.yaml (feat(maintainer): Pi/Minimax variant of maintainer-standup + dual-format persist #1480) — a Pi/Minimax M2.7 port lets the daily/weekly maintenance run cheaply and avoids the nested-Claude class of failure.
• What changed: Adds .archon/workflows/maintainer/repo-triage-minimax.yaml. Identical DAG shape and state files as the Claude variant; all four LLM-orchestrated nodes rewritten to process issues/PRs inline (Pi has no Task tool / no inline sub-agents).
• What did not change (scope boundary): No engine changes. No code changes. The existing repo-triage.yaml is untouched. State files (.archon/state/triage-state.json, closed-dedup-state.json, closed-pr-dedup-state.json, pr-state.json, stale-nudge-state.json) are wire-compatible with the Claude variant — runs of either workflow can resume from the other's state.

UX Journey

Before

Maintainer                Archon CLI                 Claude Sonnet
──────────                ──────────                 ─────────────
runs repo-triage ───────▶ executes triage-issues ──▶ briefs issues (Task fan-out)
                          executes link-prs      ──▶ matches PRs (Task fan-out)
                          ...                                ...
sees digest ◀──────────── synthesises digest    ◀── (Sonnet, ~50–200k tokens)

After (additive — Claude path unchanged)

Maintainer                Archon CLI                  Pi / Minimax M2.7
──────────                ──────────                  ─────────────────
runs repo-triage-minimax  executes triage-issues ───▶ briefs issues *inline* (one prompt)
                          executes link-prs      ───▶ matches PRs *inline* (one prompt)
                          ...                                 ...
sees digest ◀──────────── synthesises digest     ◀─── (Minimax M2.7, no Task fan-out)

Architecture Diagram

Before

.archon/workflows/maintainer/
├── maintainer-review-pr.yaml
├── maintainer-standup.yaml          (Claude)
├── maintainer-standup-minimax.yaml  (Pi/Minimax)
└── repo-triage.yaml                 (Claude — sole triage workflow)

After

.archon/workflows/maintainer/
├── maintainer-review-pr.yaml
├── maintainer-standup.yaml
├── maintainer-standup-minimax.yaml
├── repo-triage.yaml                 (Claude — unchanged)
└── repo-triage-minimax.yaml         [+]  (Pi/Minimax — same DAG, Task-free prompts)

Connection inventory:

Label Snapshot

• Risk: risk: low
• Size: size: M
• Scope: workflows
• Module: workflows:maintainer

Change Metadata

• Change type: feature
• Primary scope: workflows

Linked Issue

• Closes #
• Related # 1480 (maintainer-standup-minimax precedent)
• Related # 1067 (nested-Claude-Code session hang — motivates the Pi variant)

Validation Evidence

bun run cli validate workflows repo-triage-minimax
# Validating workflows in /Users/rasmus/Projects/cole/Archon
#   repo-triage-minimax                      ok
# Results: 1 valid, 0 with errors

• Evidence provided (test/log/trace/screenshot): validator output above
• Skipped commands: bun run validate (full suite — no code changed; YAML-only PR)

Security Impact

• New permissions/capabilities? No
• New external network calls? No (same gh + Slack-webhook surface as Claude variant)
• Secrets/tokens handling changed? No
• File system access scope changed? No (writes only under .archon/state/ and $ARTIFACTS_DIR, identical to Claude variant)

Compatibility / Migration

• Backward compatible? Yes — additive; existing repo-triage.yaml untouched.
• Config/env changes? No — uses the same DRY_RUN, SKIP_*, and SLACK_WEBHOOK env vars as the Claude variant.
• Database migration needed? No
• Upgrade steps: none. To use, run bun run cli workflow run repo-triage-minimax.

Human Verification

• Verified scenarios:
  • bun run cli validate workflows repo-triage-minimax passes clean (no warnings).
  • Audited the diff against repo-triage.yaml: identical DAG (triage-issues → closed-dedup-check, triage-issues → link-prs, standalone closed-pr-dedup-check and stale-nudge, all → digest).
  • Confirmed every reference to inline agents: blocks, Task calls, and named sub-agents (brief-gen, closed-brief-gen, pr-brief-gen, pr-issue-matcher, triage-agent) has been removed or converted to a negative ("no Task fan-out") instruction.
  • State-file shapes are unchanged from the Claude variant — wire-compatible for resumption.
• Edge cases checked:
  • DRY_RUN=1 path still works (the [DRY] would ... instructions remain, just without the Task-prepend sub-bullet).
  • SKIP_* escape hatches preserved verbatim for staged rollouts.
  • LABEL pass intentionally skipped under Pi — guardrail rewritten to point at the Claude variant for label coverage.
• What was not verified:
  • End-to-end live run against GitHub. The workflow is read-mostly and gated by DRY_RUN; recommend a first run with DRY_RUN=1 before any live invocation. (The Claude variant's behavioural guarantees apply.)
  • Quality of Minimax M2.7's clustering / template-adherence judgements vs Claude Sonnet — empirical, evaluate after the first non-dry run.

Side Effects / Blast Radius

• Affected subsystems/workflows: only the maintainer triage flow when the maintainer explicitly invokes repo-triage-minimax. No effect on default workflows or any code path.
• Potential unintended effects:
  • If a prior run of repo-triage.yaml left briefs in triage-state.json, the Pi variant will re-shape them on its next BRIEF PASS (same JSON shape — no data loss; cached briefs are simply re-validated against new sha digests).
  • Per-issue inline iteration costs more output tokens than parallel Task fan-out; on repos with > ~200 open issues the single-prompt context could push limits.
• Guardrails/monitoring:
  • Validator passes locally and in CI.
  • First production run should be DRY_RUN=1; the workflow's own summary lists every would-be mutation.

Rollback Plan

• Fast rollback command: git revert <commit> or rm .archon/workflows/maintainer/repo-triage-minimax.yaml.
• Feature flags / config toggles: per-node skip env vars (SKIP_CLOSED_DEDUP, SKIP_CLOSED_PR_DEDUP, SKIP_PR_LINK, SKIP_STALE_NUDGE) work identically to the Claude variant.
• Observable failure symptoms: validator failure (caught at CLI / CI); workflow run errors surface in $ARTIFACTS_DIR/digest.md and the per-node summaries.

Risks and Mitigations

• Risk: Minimax M2.7 produces lower-quality clusters / weaker fully-addresses judgements than Sonnet, leading to noisy or wrong dedup comments.
  • Mitigation: workflow's own conservative bias remains intact ("default to related", "when in doubt, skip"); operator runs DRY_RUN first; the Claude variant remains the gold-standard fallback.
• Risk: Single-prompt inline iteration hits context limits on very large repos.
  • Mitigation: gh issue list --limit 200 cap is unchanged. If a run truncates, increase the cap or fall back to the Claude variant (which uses Task fan-out).
• Risk: Drift between the two variants over time (a fix lands in one but not the other).
  • Mitigation: keep the diff between the two YAMLs minimal — only model swap + sub-agent removal. Cross-link in commit messages when touching either.

Summary by CodeRabbit

• New Features
  • Automated issue duplicate detection with deduplication notifications
  • Smart pull request linking to related issues
  • Stale issue and PR reminder system
  • Automated repository activity digests