chore(functions-compiler): publish the package publicly

[yurynix]

Note

Description

Flips @base44/functions-compiler from restricted to public npm publish access so apper's bundler service can install it directly from the registry. Publishing publicly does not make it a supported public API — the CLI still bundles it at build time, so end users never install it, and the package carries no compatibility promise outside this repo. The README's "Status and scope" section is reworded to say exactly that, so the change in visibility is not mistaken for a stability guarantee.

Related Issue

None

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Other (please describe): packaging/release configuration change (publishConfig.access)

Changes Made

• packages/functions-compiler/package.json: publishConfig.access changed from "restricted" to "public"
• packages/functions-compiler/README.md: rewrote the "Status and scope" paragraph — documents that the package is published public for apper's bundler service, while stating it is not a supported public API, that the CLI bundles it at build time so end users never install it, and that it carries no compatibility promise outside this repo

Testing

• I have tested these changes locally
• I have added/updated tests as needed
• All tests pass (npm test)

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (if applicable)
• My changes generate no new warnings
• I have updated docs/ (AGENTS.md) if I made architectural changes

Additional Notes

No source, build, or runtime behavior changes — publishConfig.access only affects registry visibility at publish time, and the CLI's bundling of the compiler is unaffected. Nothing else in the repo referenced the previous restricted setting. The Testing boxes are left unchecked because this diff touches only packaging metadata and prose: there is nothing executable to exercise, and no test run was performed as part of it.

---

_{🤖 Generated by Claude | 2026-09-16 16:04 UTC | 092ff93}

[github-actions]

🚀 Package Preview Available!

---

Install this PR's preview build with npm:

npm i @base44-preview/cli@0.1.15-pr.627.092ff93

Prefer not to change any import paths? Install using npm alias so your code still imports base44:

npm i "base44@npm:@base44-preview/cli@0.1.15-pr.627.092ff93"

Or add it to your package.json dependencies:

{
  "dependencies": {
    "base44": "npm:@base44-preview/cli@0.1.15-pr.627.092ff93"
  }
}

• 📦 Preview Package: @base44-preview/cli@0.1.15-pr.627.092ff93
• 🔗 View this commit on GitHub

---

_{Preview published to npm registry — try new features instantly!}