Forbid local artifact generation as MCP fallback

Observed behavior: when the MCP returns Auth required, Codex fell
through to "let me generate the .pptx/.xlsx myself" — probing for
python-pptx/openpyxl/xlsxwriter and then PowerPoint/Excel COM
automation. Any artifact produced that way has fabricated SKUs,
prices, and templates — worse than no artifact.

Previous guardrails forbade reconstructing the KB locally and
inventing SKUs, but did not explicitly forbid local artifact
generation. Add that rule: if the MCP is unreachable, no artifacts
are produced, full stop.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

skills/oci-deal-accelerator/SKILL.md

@@ -52,7 +52,8 @@ Do **NOT**:
 - attempt to reconstruct `kb://*` resources by searching the local workspace — the knowledge base lives **server-side only** and is never present in any cloned repo, plugin cache, or skill directory;
 - invent SKUs, pricing, service names, or quantities to fill the gap;
 - generate partial artifacts (deck, BOM, diagram) using inferred data;
-- retry the same tool call more than once before surfacing the fix to the user.
+- retry the same tool call more than once before surfacing the fix to the user;
+- **generate artifacts locally as a fallback**. Do not spawn `python-pptx`, `openpyxl`, `xlsxwriter`, PowerPoint/Excel COM automation, LaTeX, pandoc, or any other local tooling to produce `.pptx`, `.xlsx`, `.pdf`, `.docx`, `.png`, or `.svg` files. All artifact generation flows through MCP tools (`generate_deck`, `generate_bom`, `generate_diagram`, etc.). If the MCP is unreachable, **no artifacts** — only surface the fix command to the user.
 
 Exploration of the local filesystem on auth failure wastes context and produces wrong answers. Fail fast, surface the command, wait for the user.