Add workspace-boundary guardrail to SKILL.md stub

Even when MCP auth is healthy, Codex wastes tool calls reading the
local workspace (README.md, plugin.json, Get-ChildItem -Recurse)
because the canonical methodology includes pre-flight checks that
read files like `kb/CHANGELOG.md` — those exist in the skill repo
but not in the plugin repo or the plugin install directory.

New section explicitly tells the agent: all methodology and KB
content lives in MCP resources; never read local files to satisfy
methodology steps. The working directory is only relevant when the
user explicitly asks about it.

Complements the Auth-required fallback by addressing the
healthy-MCP-but-still-exploring case.

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

skills/oci-deal-accelerator/SKILL.md

@@ -25,6 +25,14 @@ Additional knowledge-base resources exposed by the same MCP server:
 - `kb://competitive/index` — competitor comparisons
 - `kb://field-knowledge/pricing` — pricing model, BYOL rules, free tiers
 
+## Workspace boundary
+
+All methodology guidance and knowledge-base content lives in MCP resources served by the remote server (`skill://*`, `kb://*`). **This plugin ships no local KB files.**
+
+Do NOT read from the working directory to satisfy methodology steps — pre-flight checks, changelog banners, KB lookups, YAML catalogs, pricing files, and similar do not exist locally. Whatever directory Codex was invoked in, it is not the skill repo. Any `read_file`, `ls`, or grep targeting `kb/`, `docs/`, `templates/`, `prompts/`, or similar paths to support the methodology wastes context and returns nothing useful.
+
+The working directory matters only when the user explicitly asks about files in it (e.g. "resumí este README"). Everything else flows through MCP resources and tools.
+
 ## Tool surface (14)
 
 | Category | Tools |