Finalize 2.0 release readiness

.github/workflows/release.yml

@@ -66,8 +66,13 @@ jobs:
         run: bun run build:figma
 
       - name: Build WordPress plugin
+        env:
+          APP_ENV: production
         run: bun run build:wp
 
+      - name: Verify WordPress production manifest
+        run: test -s packages/wp/dist/.vite/manifest.json
+
       - name: Verify open-source boundaries
         run: bun run check:open-source
 

README.md

@@ -314,7 +314,7 @@ The [Core Framework Marketplace](https://coreframework.com/marketplace) offers o
 
 Core Framework is built by a team focused on giving designers and developers powerful visual tools without taking away ownership of their work. We also build:
 
-- **[Motion.page](https://motion.page)** — a visual animation builder for WordPress with its own animation engine and SDK. It brings professional timelines, interactions, scroll effects, and responsive animation controls into a visual workflow, while providing an independent alternative to GSAP.
+- **[Motion.page](https://motion.page)** — a complete visual animation stack for the web, combining a desktop app, an SDK, and a WordPress plugin. Build professional timelines, interactions, scroll effects, and responsive animations visually, then use them on any website—not only WordPress—through Motion.page's independent animation engine and tooling.
 - **[Instatic](https://instatic.com)** — a free, full-featured, open-source alternative to Framer, Webflow, and WordPress. It is a self-hosted visual CMS for building and managing fast, content-driven websites. Explore the project at [instatic.com](https://instatic.com) or view the source on [GitHub](https://github.com/corebunch/instatic).
 
 ## Contributing

RELEASING.md

@@ -9,7 +9,7 @@ Core Framework uses a tag-driven release process. A push to `main` never publish
 3. Commit the release changes to `main`.
 4. Create and push a semantic version tag such as `v2.0.0`.
 5. GitHub Actions verifies the repository and builds versioned WordPress and Figma release bundles.
-6. The protected `wordpress-org` environment deploys the WordPress bundle to WordPress.org.
+6. The `wordpress-org` environment deploys the WordPress bundle to WordPress.org.
 7. GitHub Actions creates the GitHub Release and uploads both ZIPs.
 
 The workflow never deletes or rewrites an existing WordPress.org tag.
@@ -62,4 +62,4 @@ Create a protected environment named `wordpress-org` and add:
 - `SVN_USERNAME`
 - `SVN_PASSWORD`
 
-Require maintainer approval for that environment. The workflow uses the repository `GITHUB_TOKEN` to create the GitHub Release; no separate GitHub token is needed.
+For a multi-maintainer repository, consider requiring approval for this environment before deployment. In the current single-maintainer setup, possession of repository tag-push access is the release gate. The workflow uses the repository `GITHUB_TOKEN` to create the GitHub Release; no separate GitHub token is needed.

packages/wp/readme.txt

@@ -74,4 +74,14 @@ No. The font browser uses Google's public, keyless font endpoints.
 
 == Changelog ==
 
-The project changelog is available in the [source repository](https://github.com/corebunch/core-framework/blob/main/CHANGELOG.md) and the [documentation](https://docs.coreframework.com/changelog/changelog).
+= 2.0.0 =
+
+* Released Core Framework as free and open-source software under the MIT License.
+* Included the Gutenberg, Bricks, Oxygen, and Figma integrations without license checks or paid feature gates.
+* Updated the Oxygen 6 integration for Oxygen 6.1 and newer. Sites using Oxygen 6.0 should update Oxygen before installing Core Framework 2.0.
+* Replaced the Google Fonts API-key integration with a bundled catalog and keyless public endpoints.
+* Replaced the shared Figma cloud credential with direct, site-scoped connection keys.
+* Moved generated CSS to WordPress uploads storage and preserved it when upgrading from Core Framework 1.10.4.
+* Removed retired EDD licensing options while preserving site projects, integration preferences, fonts, and Figma connections.
+
+The complete changelog is available in the [source repository](https://github.com/corebunch/core-framework/blob/main/CHANGELOG.md) and the [documentation](https://docs.coreframework.com/changelog/changelog).

packages/wp/vite.config.js

@@ -12,12 +12,10 @@ const rootpath = "./src";
 // TODO: Check for 'development' APP_ENV variable
 if (!process.env.APP_ENV) {
 	process.stdout.write(`  ${red("Missing: APP_ENV")}\n`);
-	fs.writeFile(".env", "APP_ENV='development'", { flag: "a" }, (err) => {
-		if (err) process.exit();
-	});
+	fs.writeFileSync(".env", "APP_ENV='development'\n", { flag: "a" });
 	process.stdout.write(`  ${green("Created: APP_ENV='development'")}\n`);
 	process.stdout.write(`  ${yellow("Please, start project again.")}\n`);
-	process.exit();
+	process.exit(1);
 }
 
 const { CERT_PATH, HOME: HOME_DIR, DEV_URL: HOST, DEV_PROTOCOL: PROTOCOL } = process.env;