split: bootstrap community repository

TASKS.md

@@ -39,6 +39,15 @@ Verification:
 
 Progress:
 - done:
+  - `crank-community` now contains the first imported public baseline from the current monorepo
+  - bootstrap templates have been pushed into:
+    - `crank-community`
+    - `crank-enterprise`
+    - `crank-cloud`
+  - all `3` target repositories now exist:
+    - `crank-community`
+    - `crank-enterprise`
+    - `crank-cloud`
   - 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
@@ -49,10 +58,8 @@ Progress:
   - 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 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
+  - trim `crank-community` from bootstrap baseline to the final public Community source of truth
+  - continue physical split by isolating `enterprise/cloud` delta away from the extracted Community base
 
 ## Planned