docs(spec): defer per-profile access control to app-access-control

- v1: any queue:submit user may use any profile; listing reuses cluster:view
- app:use / app:view design kept in the brief and moved to the new backlog
  item app-access-control (depends on rbac-persistence for API grants)

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

.kiro/specs/xcecli-presets/brief.md

@@ -21,7 +21,7 @@ configuration level.
   only the expanded values.
 - **Handled fully on the client.** Presets never reach the controller, WAL
   or scheduler, own no attribute, are not a configuration level and carry
-  no privilege: `app:use`, `queue:submit`, the profile's essentials, queue
+  no privilege: `queue:submit` (later `app:use`), the profile's essentials, queue
   ceilings and project quotas still apply at submit.
 - **One file per preset** (user, 2026-10-12), the same layout on client
   and server:
@@ -113,7 +113,7 @@ configuration level.
     in the job record; an explicit `set:` overrides.
   - A captured name the job's profile defines is dropped by the client with
     a note; an explicit `set:` that conflicts is still rejected by the
-    server (additive rule). The client reads the profile (`app:view`).
+    server (additive rule). The client reads the profile (`cluster:view` in v1).
   - `pass: all` is opt-in; no capture is the default (today's behaviour).
     CLI only: portal and REST have no shell env and use `set:` only.
   - Today's `xcecli jobs submit --env` (whole `os.Environ()`,