Habit memory API

Habit memory routes let a signed-in user control how Chiro handles repeated procedural patterns for that person.

The current implementation path uses automation-rules. The documentation calls this product surface Habits because the behavior is procedural memory: repeated patterns, utility, suppression, and approval.

Routes

Method	Path	Purpose
POST	/api/user/memory/automation-rules/:templateId/unsuppress	Clear the caller's personal suppression cooldown for one habit.
POST	/api/user/memory/automation-rules/:templateId/require-approval	Require or remove personal approval for one habit.

These routes change the caller's personal habit controls. They do not expose organization-wide habit state.