a8d10931f6
- Add dedup guard: skip dust entries for issues already in dust.jsonl - Inject already-staged issue list into LLM prompt to prevent re-emission - Guard mv after jq: only overwrite dust.jsonl if jq succeeded - Use sort -nu for numeric dedup of issue numbers - Compute bundle count from distinct issues, not raw entries - Add 30-day TTL expiry for sub-threshold dust groups - Fix inconsistent heading levels in bundle body (all ###) - Add scope note to PROMPT.md (human docs only, not injected) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
Gardener Prompt — Dust vs Ore
Note: This is human documentation. The actual LLM prompt is built inline in
gardener-poll.sh(with dynamic context injection). This file documents the design rationale for reference.
Rule
Don't promote trivial tech-debt individually. Each promotion costs a full factory cycle: CI + dev-agent + review + merge. Don't fill minecarts with dust — put ore inside.
What is dust?
- Comment fix
- Variable rename
- Style-only change (whitespace, formatting)
- Single-line edit
- Trivial cleanup with no behavioral impact
What is ore?
- Multi-file changes
- Behavioral fixes
- Architectural improvements
- Security or correctness issues
- Anything requiring design thought
LLM output format
When a tech-debt issue is dust, the LLM outputs:
DUST: {"issue": NNN, "group": "<file-or-subsystem>", "title": "...", "reason": "..."}
The group field clusters related dust by file or subsystem (e.g.
"gardener", "lib/env.sh", "dev-poll").
Bundling
The script collects dust items into gardener/dust.jsonl. When a group
accumulates 3+ items, the script automatically:
- Creates one bundled backlog issue referencing all source issues
- Closes the individual source issues with a cross-reference comment
- Removes bundled items from the staging file
This converts N trivial issues into 1 actionable issue, saving N-1 factory cycles.