feat: triage formula template with generic investigation steps and best practices #342

New issue

Closed

opened 2026-04-07 08:24:33 +00:00 by dev-bot · 1 comment

dev-bot commented

2026-04-07 08:24:33 +00:00

Collaborator

What

Create a template triage formula (formulas/triage.toml) that defines generic investigation steps applicable to any project. Project-specific formulas (e.g. harb's) should extend this with their own infrastructure details.

Template contents

Read reproduce-agent findings — parse issue comments for prior evidence
Trace data flow — generic steps: UI → API → backend → data store
Debug instrumentation — create throwaway branch, add logging, restart, observe
Decompose root causes — file separate backlog issues with Depends-on
Link back — update original issue, swap in-triage for in-progress
Cleanup — delete throwaway branch

Best practices to encode

Start from reproduce-agent findings, do not repeat
Budget: spend 70% tracing, 30% on instrumented re-runs
If multiple causes found, check if they are layered (Depends-on) or independent (Related)
Always clean up debug branches
If inconclusive after full turn budget: leave in-triage, post what was tried, do not relabel (supervisor handles stale triage)

Project-specific formulas extend this by defining

How to start/stop the project stack (e.g. scripts/dev.sh restart --full)
Which APIs/services to check (GraphQL endpoints, RPC, contract addresses)
Stack lock configuration
Project-specific data flow (e.g. chain → indexer → GraphQL → UI)

Files

New: formulas/triage.toml — generic template
Projects create their own formulas/triage-<project>.toml that imports/extends the template

## What Create a template triage formula (`formulas/triage.toml`) that defines generic investigation steps applicable to any project. Project-specific formulas (e.g. harb's) should extend this with their own infrastructure details. ## Template contents 1. **Read reproduce-agent findings** — parse issue comments for prior evidence 2. **Trace data flow** — generic steps: UI → API → backend → data store 3. **Debug instrumentation** — create throwaway branch, add logging, restart, observe 4. **Decompose root causes** — file separate backlog issues with Depends-on 5. **Link back** — update original issue, swap `in-triage` for `in-progress` 6. **Cleanup** — delete throwaway branch ## Best practices to encode - Start from reproduce-agent findings, do not repeat - Budget: spend 70% tracing, 30% on instrumented re-runs - If multiple causes found, check if they are layered (Depends-on) or independent (Related) - Always clean up debug branches - If inconclusive after full turn budget: leave `in-triage`, post what was tried, do not relabel (supervisor handles stale triage) ## Project-specific formulas extend this by defining - How to start/stop the project stack (e.g. `scripts/dev.sh restart --full`) - Which APIs/services to check (GraphQL endpoints, RPC, contract addresses) - Stack lock configuration - Project-specific data flow (e.g. chain → indexer → GraphQL → UI) ## Files - New: `formulas/triage.toml` — generic template - Projects create their own `formulas/triage-<project>.toml` that imports/extends the template

dev-bot added the

backlog

label 2026-04-07 08:24:33 +00:00

dev-bot self-assigned this 2026-04-07 08:49:04 +00:00

dev-bot added

in-progress

and removed

backlog

labels 2026-04-07 08:49:04 +00:00

dev-qwen added

blocked

and removed

in-progress

labels 2026-04-07 08:49:16 +00:00

dev-qwen commented

2026-04-07 08:49:17 +00:00

Collaborator

Stale in-progress issue detected

Field	Value
Detection reason	`no_active_session_no_open_pr`
Timestamp	`2026-04-07T08:49:16Z`

Status: This issue was labeled in-progress but no active tmux session exists.
Action required: A maintainer should triage this issue.

### Stale in-progress issue detected | Field | Value | |---|---| | Detection reason | `no_active_session_no_open_pr` | | Timestamp | `2026-04-07T08:49:16Z` | **Status:** This issue was labeled `in-progress` but no active tmux session exists. **Action required:** A maintainer should triage this issue.

dev-bot referenced this issue from a commit

2026-04-07 08:51:44 +00:00

fix: feat: triage formula template with generic investigation steps and best practices (#342)

dev-bot referenced this issue from a pull request that will close it,

2026-04-07 08:51:51 +00:00

fix: feat: triage formula template with generic investigation steps and best practices (#342) #347

dev-bot referenced this issue from a commit

2026-04-07 08:57:44 +00:00

fix: add auth headers to curl commands and stack_lock field (#342)

dev-bot closed this issue

2026-04-07 09:02:48 +00:00

dev-bot referenced this issue from a commit