feat: establish standalone Device Core repository

docs/REPOSITORY_BOUNDARY.md

@@ -0,0 +1,45 @@
+# Device Core repository boundary
+
+## Device Core owns
+
+- Device Manager UI and BFF;
+- Device Control Core, gateways and edge runtimes;
+- provider/model adapters and protocol contracts;
+- Device Plane and Device Edge VPS Compose/configuration sources;
+- Device Core deployment descriptor templates;
+- deterministic builders and tests for Device Core artifacts.
+
+## NODEDC Platform owns
+
+- the root-owned `nodedc-deploy` executable and component registry;
+- Hub and Authentik identities, grants and signed runtime claims;
+- Launcher integration and service catalogue entry;
+- the `device.nodedc.ru` reverse-proxy route;
+- shared platform secrets handed to Device Core at runtime;
+- platform deployment builders and acceptance checks for those integration
+  seams.
+
+## NODEDC Design Guideline owns
+
+- `@nodedc/tokens`, `@nodedc/ui-core` and `@nodedc/ui-react`;
+- canonical controls, icons, tokens and interaction patterns;
+- design-system validation and catalogue documentation.
+
+Device Core consumes these packages from the sibling canonical repository. It
+must not fork or hard-code their source.
+
+## Migration invariants
+
+Repository extraction is a source-ownership change only. It must not change:
+
+- deployed component names;
+- live filesystem roots;
+- Compose project or service names;
+- persistent volume names;
+- runtime secret paths;
+- mTLS keys/certificates or edge registrations;
+- public ingress policy;
+- release predecessor hashes already recorded by the deploy ledger.
+
+No runtime state, media upload, credential, private key, device password or
+real restricted identifier belongs in this repository.