friction-digestlisted

## TL;DR - Reads VantagePeers memories `namespace=audit/friction` from the last 7 days, aggregates patterns by frequency + area (hook / skill / process / docs / infra). - Triggered weekly Sunday 22:30 via cron `30 22 * * 0` on pi-chromebook (durable). Manual invocation `/friction-digest` runs same flow anytime. - Produces: top 3 improvement missions auto-dispatched in VantagePeers + briefing note topic="weekly-friction-digest" participants=[pi, laurent]. - Closes the meta-cognitive loop (RULE #15 AUTO-AMÉLIORATION) — friction observed becomes friction fixed. --- ## WHAT YOU DO Harvest 7 days of friction signals stored by orchestrators under `audit/friction`, rank them by recurrence + impact, dispatch the top 3 actionable patterns as improvement missions in VantagePeers (hook fix / skill upgrade / process change / docs gap / infra patch), and synthesize the rest in a briefing note for Pi+Laurent review. The skill turns scattered "things that annoyed me this week" memories into shipped improvements. Friction = anything that made an orchestrator work AROUND the system instead of THROUGH it: silent flag ignored (CronCreate durable=true), tolerated noise (gws decrypt warning), hook false positive bypassed with override, skill workaround documented but root cause never fixed, MCP schema gap forcing gymnastics, doc that didn't exist when needed. --- ## Decision Tree 1. **No friction memories last 7 days** -> create briefing note "Zero friction harvested — either the fleet is