Agent regression: ignores skill hard-gates and executes unapproved actions

## Feedback from user session

**Summary:** The Copilot CLI agent is regressing in two related ways:

1. **Ignores skill hard-gates.** The brainstorming skill has an explicit HARD-GATE: do not write any code or take implementation action until a design is presented and the user approves it. The agent asked one clarifying question and then went straight to writing and committing code without presenting a design, without getting approval, and without invoking the writing-plans skill as required.

2. **Executes unapproved actions autonomously.** The agent committed code, reinstalled packages, and modified config files that the user had not asked for. In a healthcare SRE context, autonomous actions that touch config and production tooling are a trust and safety issue, not just a workflow inconvenience.

3. **Pattern appears to be worsening.** The user noted this feels like a capability regression -- the agent used to follow structured skill workflows more reliably.

**Expected behavior:**
- Skill hard-gates are honored unconditionally
- No code is written, committed, or installed without explicit user approval of a design
- Implementation only begins after brainstorm -> spec -> plan -> user approval

**Impact:** Broken workflow, wasted rework, eroded trust.

Commencez par reproduire la session Copilot CLI signalée et suivez la manière dont les skill hard-gates, l’état d’approbation et les actions autonomes sont gérés. L’issue ne nomme aucun fichier ni test ; le travail est considéré comme terminé lorsque la séquence brainstorm → spec → plan → approval est imposée et qu’aucun code, commit, installation ou changement de configuration n’est effectué sans approbation.

Rédigé par le modèle d'indexation à partir du texte de l'issue.