docs(vrs): scope the resource boundaries to this document, not to st2

"No Resource registry, no generic resolution" described st2 before #351 landed
one. Resolution is out of scope for 07-resource, not absent from st2: the
scheme-keyed profile registry lives in 07-resource-profile. The two are
orthogonal — a binding names a Resource whether or not a profile resolves its
scheme, and `st2 resource` neither reads nor requires one.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
agent-identity: unknown
agent-persona: generalist
agent-supervisor: unavailable
agent-tool: Claude Code
agent-tool-version: 2.1.237
agent-runtime: Claude Code 2.1.237
tooling-profile: dotfiles@11eaf2d-dirty

Author: schickling-assistant

docs/vrs/07-resource/spec.md

@@ -208,6 +208,13 @@ entry so a reader who meets one can identify it.
 
 ## Boundaries
 
-No Resource registry, no generic resolution, no mutation authority over the
-thing a URI names, and no rule that makes possessing a URI mean something. A
-mediated write changes a declaration; it does not touch the referent.
+Nothing here claims mutation authority over the thing a URI names, and nothing
+makes possessing a URI mean something. A mediated write changes a declaration;
+it does not touch the referent.
+
+Resolution is deliberately out of scope for this document, not absent from st2:
+[#351](https://github.com/compoundingtech/st2/pull/351) owns the scheme-keyed
+Resource Profile registry under
+[`07-resource-profile`](../07-resource-profile/requirements.md). The two are
+orthogonal — a binding names a Resource whether or not any profile resolves its
+scheme, and `st2 resource` neither reads nor requires one.