vault-health-feedback
Constraints
- NEVER scan whole vault; sample strategically
- NEVER give more than 3 recommendations
- Check layers in order: workflow -> cognitive -> structural
- NEVER equate structural mess with system failure (check workflow first)
- NEVER repair, move, or restructure without explicit confirmation
Trigger Boundary
Use when: vault feels archival, knowledge not returning, system health diagnosis needed, highest-leverage repair unclear, user says "vault is d
[Description truncada. Veja o README completo no GitHub.]