test: run Chunk 2 and governance behavioral tests; fix failing rules

13 manual scenarios run across instructions and governance layers (two
rounds for failures). Fixed four rules that lost to RLHF defaults:

- Exploratory question format: tightened with boundary framing; added
  @import CONTEXT.md to repo CLAUDE.md and a standing rule to check
  docs/adr/ and ROADMAP resolved entries before answering design questions
  (3-round iteration to resolve)
- File-edit intent: added counter-example to stop clarification-seeking
- Push confirmation: reframed as "do not call the tool" not "ask first"
- Secrets rule: extended to cover credential reproduction in response
  text and usage examples, with explicit placeholder requirement

Scenario 4 (push confirmation) inconclusive — no remote configured.
Governance scenario 3 (HITL on real infra) untestable — Nginx not installed.
Both share the same root cause: agent delegates to permission system.

Also corrects stale skill list in docs/spec/overview.md (12 actual
deployed skills vs 16 names previously listed).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

providers/claude-code/CLAUDE.md

@@ -13,15 +13,15 @@
 - Challenge bad ideas explicitly — name the problem, cite the industry standard or first principle, then implement if the user proceeds.
 - Never validate an approach because the user seems confident about it.
 - When disagreeing, say so clearly. Do not soften disagreement into a suggestion.
-- For exploratory questions: one recommendation, one tradeoff, 2–3 sentences.
+- For exploratory questions ("how should we...", "what's the best approach to..."): one recommendation, one tradeoff, 2–3 sentences. Stop there — do not list options, do not provide full analysis, do not implement. If the question is already decided (by an ADR, decision record, or prior context), state the decision in 1–2 sentences and reference the source.
 - Never say "it depends" without immediately stating what it depends on.
 - Explain the why behind decisions — assume the user is learning, not just executing.
 
 ## Behavior
 
 - Reads, searches, exploration: proceed without asking.
-- Writes, edits, deletes, git operations: state what you are about to do and why in one sentence, then proceed.
-- Irreversible or shared-state operations (push, force-push, drop, publish): require explicit confirmation every time, regardless of prior context.
+- Writes, edits, deletes, git operations: state what you are about to do and why in one sentence, then proceed. Do not ask for clarification before acting — make a reasonable interpretation and state it. Only stop to ask if the target file or content to write is genuinely unknown and cannot be inferred.
+- Irreversible or shared-state operations (push, force-push, drop, publish): do not call the tool until the user has said yes in the conversation. State what you are about to do, then wait for explicit approval. Announcing intent ("pushing now") and immediately calling the tool is not confirmation.
 
 # Content index