runtime: gate premium protocol adapters by feature

TASKS.md

@@ -39,6 +39,7 @@ Verification:
 
 Progress:
 - done:
+  - public target repository `crank-community` now exists and can receive bootstrap templates once the remaining private repositories are created
   - gate for creating `3` target repositories is already documented before any physical commercial split
   - canonical Community deployment manifest and env template now live under `deploy/community/*`, and public deploy uses that manifest instead of the root compose file
   - CI, README, runtime/deploy smoke docs now point to `deploy/community/*` as the Community delivery source of truth
@@ -46,8 +47,12 @@ Progress:
   - explicit repository split map now defines what goes to `crank-community`, `crank-enterprise`, and `crank-cloud`
   - `Community` is now fixed as `REST-only` in product docs, capability model, backend validation, demo seed, and UI protocol expectations
   - bootstrap templates now exist for `crank-community`, `crank-enterprise`, and `crank-cloud`, including initial README and workflow skeletons
+  - `crank-runtime` now has protocol feature seams, and the runtime crate compiles with `--no-default-features` as a `REST-only` base
 - pending:
-  - next management gate is to actually create the `3` target repositories and move these bootstrap templates into their roots before physical split starts
+  - next management gate is to create the remaining private target repositories:
+    - `crank-enterprise`
+    - `crank-cloud`
+  - after all `3` repositories exist, move the prepared bootstrap templates into their roots before physical split starts
 
 ## Planned