groom

name	groom
description	Groom Gradient ideas and debt into public-safe, lifecycle-aware work. Trigger: /groom, /backlog, /rethink.
argument-hint	[--emphasis explore|rethink|moonshot|scaffold] [context]

/groom

Grooming here is product-contract triage. There is no backlog.d/ yet, so work items live in user requests, docs, and explicit debt notes until a tracker is added.

This repo now has backlog.d as the Work adapter v0, but no closure detector beyond the tracer-bullet fixture. Until a detector exists, preserve work references manually and mark closure mechanics unverified.

Always Tidy

1. Check for shipped-but-active work contradictions if a tracker exists.
2. Today, record the absence of a tracker as lifecycle debt when it matters.
3. Keep active work public-safe and module-scoped.

Triage Questions

• Which lifecycle stage does this strengthen?
• Is this core semantics, profile config, or adapter behavior?
• Does it belong in this public repo or a private deployment profile?
• What evidence would prove it worked?
• Does it reduce overfit to Spellbook, Orbital, or Olympus?

Gate

The load-bearing ship gate is ./scripts/validate.sh, plus reviewer judgment for lifecycle semantics in docs/architecture.md and docs/module-contracts.md when docs change.

Output

Produce a concise candidate item with goal, lifecycle stage, files likely touched, acceptance criteria, evidence, and public-safe risk.