Make profile runtime readiness explicit

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a0233b-178d-7162-b92f-31a31ea8ca9b

README.md

@@ -17,7 +17,8 @@ assignment / channel / activity
 
 ## Profiles
 
-List and validate every committed executable profile:
+List and validate every committed catalog profile, including its independently
+declared runtime readiness:
 
 ```bash
 glas-harness profiles
@@ -32,19 +33,26 @@ Current constellations include:
   open-weight route, local bwrap sandbox.
 - `harness.agent-dev@1.0.0`: `rein-aharness`, remote agent-dev sandbox.
 
-Run a task through an explicit profile:
+The two local profiles are currently `blocked` by the missing sand-boxer
+owner-execution/runtime path. The remote profile is `unverified`: it may be
+used only as an explicitly labeled proof attempt. No committed profile is
+currently declared `ready`.
+
+Start a bounded proof attempt through the currently unverified remote profile:
 
 ```bash
 glas-harness run \
-  --harness-profile harness.agent-dev-local@1.0.0 \
+  --harness-profile harness.agent-dev@1.0.0 \
   --repo /absolute/path/to/repo \
   --title "Bounded change" \
   --description "Make the requested change and commit it"
 ```
 
 There is no governed default rein, model, sandbox, or tool profile. Unknown,
-disabled, incompatible, and ambiguous selections are refused before sandbox
-creation.
+disabled, incompatible, ambiguous, and operationally blocked selections are
+refused before sandbox creation. An unverified selection is allowed so a
+bounded proof can establish or disprove readiness, and its evidence retains
+that state.
 
 After creation, execution uses only the reachability-derived sandbox workspace:
 same-host namespaces are entered with `nsenter`, while remote workspaces are