Backed by: state/lib/sweep.ts + state/lib/xano.ts

bug-triage

Reads sweep snapshot (filtering to items matching bug keywords), gh issue list --state=open across active repos, and Xano error-log rows from the last N days. Clusters by stack-trace fingerprint or keyword overlap.

Steps

1. Collect the three sources in parallel.
2. Normalize to {source, ref, text, ts, repo?}.
3. Cluster: exact-match on stack fingerprint first, then fuzzy on

keyword Jaccard ≥ 0.4.

1. Rank clusters by size × recency.
2. Emit state/log/bug-triage/<date>.md.

Eval

score("bug-triage", run_id, {
  score:
    shape_ok && clusters_are_unique ? 1.0 :
    shape_ok ? 0.5 :
    0.0,
  total_signals: total,
  cluster_count: clusters.length,
  unclustered: unclustered.length,
  primary_issue:
    !shape_ok ? "shape-failed" :
    unclustered.length > total * 0.5 ? "clustering-threshold-too-tight" :
    null,
});

clusters_are_unique: no two clusters share the same fingerprint. Shape gate prevents silent clustering failure.

Gotchas

• gh must be authenticated; if not, log the auth failure and continue

with the other two sources rather than hard-failing.

• Jaccard threshold 0.4 is a guess; tune once we have a week of data.

Rubric

criteria:
  - name: output_file_created
    kind: deterministic
    check: "File 'state/log/bug-triage/<date>.md' exists and is non-empty (file size > 100 bytes)."
  - name: clusters_nonzero
    kind: deterministic
    check: "Clusters array has length > 0 (at least one cluster identified; not empty array)."
  - name: cluster_uniqueness
    kind: deterministic
    check: "clusters_are_unique = true; no two clusters share the same stack fingerprint."
  - name: signal_count_threshold
    kind: deterministic
    check: "total_signals ≥ 1 (at least one signal collected from sweep, GitHub, or Xano)."
  - name: cluster_quality
    kind: judge
    check: "Clusters are semantically cohesive (signals within a cluster share root cause); unclustered < total * 0.5; data sources are properly integrated."

bug-triage - loader

Per-turn rules for the bug-triage skill. Full reference: state/skills/bug-triage/SKILL.md. Do not skip these.

Critical Rules

• NEVER hard-fail when gh is unauthenticated - log the auth failure and continue with the other two sources (sweep + Xano)
• ALWAYS cluster by exact stack-fingerprint FIRST, then fall back to fuzzy keyword Jaccard ≥ 0.4 - not the other way around
• ALWAYS rank clusters by size × recency, not size alone - old loud bugs shouldn't drown out fresh ones

Commands

| ui model | live composition via compose_inline, persisted as artifact lang_body, reopened with OpenArtifact | |invoke: collect sweep snapshot + gh issue list --state=open + Xano error-log, normalize, cluster, write state/log/bug-triage/<date>.md |verify: clusters_are_unique (no two clusters share the same fingerprint) AND shape gate |eval log: state/log/evals.ndjson (skill: "bug-triage")

Known Pitfalls

• Jaccard threshold 0.4 is a guess. Tune once a week of data exists. If unclustered.length > total * 0.5, primary_issue is clustering-threshold-too-tight.
• shape_ok is the floor - score 0.5 if shape passes but uniqueness fails; 0.0 if shape itself fails.

Self-Test

An agent reading this should correctly:

1. [ ] Continue triage when gh auth is missing (log + proceed)
2. [ ] Cluster by stack-fingerprint before keyword Jaccard
3. [ ] Flag unclustered > 50% as a tuning issue, not a failure

Found a gap? Edit this file. <!-- footer-injection-point -->