docs: define community whitelist boundary

TASKS.md

@@ -39,7 +39,8 @@ Verification:
 
 Progress:
 - done:
-  - `crank-community` now contains the first imported public baseline from the current monorepo
+  - `crank-community` baseline-import was removed from history; the repository is back to bootstrap-only state until a clean whitelist-based import is ready
+  - the first baseline import was used only as a private split rehearsal and must not be treated as the final public source state
   - bootstrap templates have been pushed into:
     - `crank-community`
     - `crank-enterprise`
@@ -58,7 +59,10 @@ 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:
-  - trim `crank-community` from bootstrap baseline to the final public Community source of truth
+  - implement the whitelist from `docs/community-source-whitelist.md`
+  - make Community workspace compile and run without premium protocol crates
+  - make Community UI export stop depending on premium wizard and streaming surfaces
+  - only after that, perform a clean whitelist-based force-push into `crank-community`
   - continue physical split by isolating `enterprise/cloud` delta away from the extracted Community base
 
 ## Planned