docs(skills): ban python wrappers and mid-run skill edits in audit contract

[alexskatell]

Why

Latest test trace of the SQL-first audit contract blew the 4-call ceiling because:

1. The agent wrapped topline --agent query sql calls in python3 / execute_code subprocess loops to "verify" and "reshape" the output. Same anti-pattern as REST fan-out, different surface.
2. The agent invoked skill_manage during the audit to patch the topline-os-cli / topline-os-crm-audits skills — meaning the contract being tested wasn't the documented contract.

The two were the new dominant failure modes after this week's earlier PRs (#4, #5, #6) successfully killed REST-first fallback and adopted query doctor as step 1. Tightening the contract closes both loopholes.

What

skills/hermes/SKILL.md (1.3.0 -> 1.4.0)

• Readiness probe now documents the query doctor / query help fallback for stale binaries (real failure mode hit when feat(query): query doctor readiness probe + Hermes-aware install script (Phase 1) #5 merged but the local binary wasn't rebuilt). Recommends scripts/install-local.sh as the fix.
• Hard ceiling section explicitly bans three classes in the default flow:
  1. REST fan-out (pipeline audit, opportunities search, conversations search, message loops).
  2. python3 / execute_code / subprocess.run wrappers around topline. CLI returns JSON; parse it directly. Reshape in SQL with a final SELECT.
  3. skill_manage edits to either bundled skill during execution. Contract is read-only during a run; propose edits in a separate turn.
• Two new pitfalls (docs(skills): ban post-hoc math on query audit JSON #10 python wrappers, docs(skills): backport Flex lineage + manual-outreach pitfalls (v1.6.1) #11 mid-run skill edits).

skills/claude-code/SKILL.md

Mirrors the same contract in the shorter Claude Code-targeted form.

What this is not

• No CLI code changes. Pure skills/docs.
• Does not remove the underlying query commands, pipeline audit, or any tool. They remain available for the drilldown / diagnostic exceptions that already require the user to explicitly ask.

Follow-ups (separate PRs)

• Phase 2 in docs/plans/2026-05-13-sql-first-retrieval-improvements.md (query template registry).
• Phase 3 sales-native composite reports.
• os-mcp view rollforward (contact_timeline UNION appointments/call_events, pipeline_activity_window, pipeline_snapshot, pipeline_movement_window, warehouse_freshness) — different repo.