anhedral 0.1.10 → 0.4.0

package/CHANGELOG.md

@@ -0,0 +1,119 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and versions follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## Unreleased
+
+## 0.4.0 - 2026-07-22
+
+### Added
+
+- Add the `electron-updater` feature module, including packaged-app update checks, private R2 storage, a read-only bound Cloudflare Worker on a custom domain, ordered architecture-specific publishing commands, and a complete generated release runbook.
+- Make the `anhedral-init` coding-agent skill the recommended setup path, with project/domain intake, Computer Use and subagent orchestration, provider provisioning order, authentication and secret-generation stops, and verified Cloudflare/Vercel domain handoffs.
+- Add the canonical fixed-width master stack map to the published documentation and route the coding-agent skill through it for whole-platform planning and explanation.
+- Add a transactional project-upgrade path so compatible 0.3 projects can adopt 0.4 without regeneration.
+- Add a focused default development loop for the primary web and API surfaces, with `dev:all` available for intentionally launching every selected client.
+
+### Changed
+
+- Make generated onboarding follow the real environment, managed-Neon, verification, and framework source layout instead of promising an unconfigured one-command boot.
+- Treat developer extension points as user-owned source while retaining conflict protection for generated wiring and mergeable workspace configuration.
+- Publish the skill's provisioning references from their canonical `docs/references` location and validate every packed local documentation link.
+- Upgrade GitHub artifact transfer actions to their Node.js 24-native releases and keep manual npm publication routed through the trusted-publisher workflow identity.
+
+### Fixed
+
+- Canonicalize module ordering when an incremental feature contributes a previously absent dependency.
+- Attach release integrity metadata beside the npm tarball in GitHub Releases.
+
+## 0.3.0 - 2026-07-21
+
+### Added
+
+- Add a unified `anhedral ui add` workflow that routes DOM clients to shadcn/ui and Expo clients to React Native Reusables.
+- Add interactive starter-component selection after app surfaces and feature sets, with NativeWind or Uniwind selection for Expo.
+- Add React Native Reusables-ready Expo configuration, theme CSS, aliases, utilities, Metro integration, and portal hosting.
+- Add manifest schema v5 UI configuration and per-client component installation records.
+- Add staged provider execution, dry-run plans, duplicate-install detection, target validation, and provider routing tests.
+- Add `anhedral new <directory>` as the primary complete-stack creation flow while retaining `init` for an empty current directory.
+- Generate selection-aware `README.md`, `docs/DEVELOPMENT.md`, `docs/STACK.md`, and `SKILL.md` guidance that maps product tasks to ordinary framework source.
+- Publish the repository skill, manual scaffolding reference, conventions, and output-tree contract with the npm package.
+
+### Changed
+
+- Pin the component installer to shadcn 4.13.0 and run all provider mutations inside Anhedral transaction staging.
+- Preserve Anhedral's exact Expo SDK dependency while resolving React Native Reusables registry dependencies before the root workspace install.
+- Present Anhedral as a readable TypeScript stack generator with native Next.js, Expo, Fastify, Drizzle, Electron, and WXT conventions rather than a proprietary application runtime.
+- Use argument-vector process execution for workspace installation instead of invoking a command through a shell.
+- Remove the retired one-app compiler experiment from the production CLI and package surface.
+
+### Security
+
+- Reject symbolic-link scaffold roots before creating transaction metadata or modifying their targets.
+- Override vulnerable `shell-quote` and `sharp` dependency ranges in generated workspaces.
+
+## 0.2.1 - 2026-07-16
+
+### Added
+
+- Add integrity-checked bundled framework substrates, typed module contributions, deterministic root composers, and manifest schema v4 template provenance.
+- Add template tamper, symbolic-link, package-content, and contribution-composition regression tests.
+- Add exact-artifact portability checks at the minimum Node.js 20 and 22 releases and the pinned Node.js 24 release on macOS and Windows.
+- Add scheduled and release-gated Electron, WXT, and Expo native runtime acceptance lanes.
+- Add deterministic workflow, Renovate extraction, release declaration, registry recovery, and module-topology policy tests.
+
+### Security
+
+- Reject altered template catalogs, mismatched substrate digests, symbolic links, forbidden generated artifacts, and oversized template trees before transactional commit.
+- Scan all tracked text, built output, and final package tarballs for high-confidence secret formats before publication.
+- Clarify that public package availability grants no installation, execution, or generated-output rights without a separate written agreement.
+
+## 0.2.0 - 2026-07-15
+
+### Added
+
+- Add manifest schema v3 with deterministic module dependency resolution, file ownership, hashes, modes, and an explicit toolchain channel.
+- Add transactional `init` and `add` operations with locking, journaling, rollback, dry-run plans, and JSON output.
+- Add the `anhedral doctor` command.
+- Add deterministic output-tree contracts for representative scaffold combinations.
+
+### Changed
+
+- Generate only the dependencies, source files, environment keys, apps, and shared packages required by selected modules.
+- Align Vercel Services output with the current `services` schema and mount Fastify routes under the preserved `/api` path.
+- Refresh the verified Next.js, Expo, Clerk, Electron, WXT, Vite, and RevenueCat integration matrix.
+- Separate the side-effect-free package API from the executable CLI entry point.
+- Preserve user-owned documentation, workflows, package fields, and mergeable root configuration during incremental adds.
+- Build from a clean `dist/` directory before tests and packaging.
+- Publish one verified tarball and compare its integrity with npm before tagging.
+- Pin the release Node.js/npm packer so recovery rebuilds remain reproducible.
+- Install the exact release artifact and run its `.bin/anhedral` shim in package smoke tests.
+- Enforce an explicit npm package allowlist and artifact size policy.
+- Test the CLI on Node.js 20, 22, and 24 in CI.
+- Wire Clerk controls and token-aware API helpers into web and mobile templates, and make the desktop account action open Clerk sign-in or profile UI.
+- Bootstrap RevenueCat only for `native-subscriptions`, connect native purchases to the authenticated user, and expose a native paywall action.
+- Put pnpm overrides, build permissions, and peer policy in `pnpm-workspace.yaml`, with conflict-safe structural merges.
+- Keep public API GET requests simple by omitting unused platform and content-type headers.
+- Remove unused provider dependencies and environment placeholders from generated clients.
+- Wire Tailwind CSS v4 into generated web and desktop builds, including semantic shadcn color tokens.
+- Keep canonical module IDs and valid RFC 3986 URI schemes in generated project metadata and documentation.
+- Refresh generator-owned Node.js and pnpm policy during incremental adds when the recorded package manifest is unmodified.
+
+### Removed
+
+- Remove pre-schema-v3 manifest migration, generated-layout adoption, deprecated module aliases, and duplicate `stack.json` output. Projects must be generated with the current CLI and use canonical module IDs.
+
+### Security
+
+- Reject modified managed files and unowned path collisions before committing incremental changes.
+- Validate recovery journals, reject symlink traversal, and persist transaction intent before moving files.
+- Audit every locked CLI dependency through OSV after pnpm's retired audit endpoint became unavailable.
+- Make RevenueCat webhook processing fail closed and persist idempotency records when billing is selected.
+- Scope npm credentials to the single publish step in the protected release job.
+- Separate read-only release verification from npm publication and Git tag creation.
+- Pin GitHub Actions to verified upstream commit SHAs.
+- Default Fastify proxy trust to off, require an explicit bounded trusted-hop count, and minimize conditional Chrome permissions.
+- Reconcile exact package versions against detailed OSV advisory ranges when the batch index is over-broad.
+- Reject manifest-recorded directories and other non-regular paths during project health checks.

package/CONTRIBUTING.md

@@ -0,0 +1,73 @@
+# Contributing
+
+## Local setup
+
+Anhedral requires Node.js 20.19+ or 22.12+ and pnpm 10.34.5.
+
+```sh
+pnpm install --frozen-lockfile
+pnpm build
+pnpm lint
+pnpm check:security
+pnpm check:release-policy
+pnpm audit:osv
+pnpm test
+```
+
+## Before opening a pull request
+
+Run the checks relevant to the files you changed:
+
+```sh
+pnpm typecheck
+pnpm test
+pnpm test:pack
+pnpm test:packlist
+pnpm test:release-tooling
+```
+
+Changes to generated templates or dependency pins should also run:
+
+```sh
+pnpm test:deps
+pnpm test:e2e
+```
+
+The E2E test installs upstream packages in a disposable operating-system temp directory, so it requires network access and may take several minutes. It removes the workspace in a `finally` block; set `ANHEDRAL_E2E_KEEP=1` only when you intentionally need to inspect a failed or completed run.
+
+After an intentional scaffold-output change, regenerate and review the path/mode/SHA-256 contracts and generated tree documentation:
+
+```sh
+pnpm build
+node tests/update-output-tree-contracts.js
+```
+
+## Package changes
+
+- Keep the public package allowlist narrow.
+- Do not commit `dist/`, tarballs, `release-artifact/`, or temporary E2E/demo workspaces.
+- Add or update a regression test for CLI behavior and generated configuration changes.
+- Keep stable toolchain commands pinned; mutable upstream versions belong only in the `latest` lane.
+- Run the OSV audit against a newly installed representative generated lockfile when changing framework or runtime pins.
+
+## Ownership and required review
+
+Repository administrators must map the following roles to real maintainers in branch protection, the protected `npm` environment, private vulnerability reporting, and workflow-failure notifications:
+
+- **Generator owner:** core architecture, transactions, manifests, and generated-file ownership.
+- **Runtime owner:** application templates, provider integrations, and the stable dependency manifest.
+- **Release owner:** package metadata, CI workflows, registry publication, tags, and recovery.
+- **Security responder:** vulnerability intake, secret-exposure response, and supply-chain incidents.
+
+No `CODEOWNERS` file is committed until an actual GitHub user or team slug is selected. A placeholder would create false confidence without enforcing review. Require at least one appropriate owner review for generator/runtime changes and a release-owner review for `.github/workflows/`, `scripts/`, `package.json`, `renovate.json`, `SECURITY.md`, or `docs/RELEASING.md`.
+
+Scheduled Toolchain Drift failures and release-workflow failures must alert the release owner. Security-policy, secret-scan, or OSV failures must additionally alert the security responder. Configure those routes in repository notification settings and test them after changing ownership.
+
+## Releases
+
+Do not run `npm publish` from a development checkout. Version changes are reviewed before release, and CI publishes the verified tarball. See [docs/RELEASING.md](docs/RELEASING.md).
+
+This repository and package are licensed under the Apache License 2.0. Unless
+explicitly stated otherwise, contributions intentionally submitted for
+inclusion in Anhedral are provided under the same license, as described in
+Section 5 of [LICENSE](LICENSE).

package/LICENSE

@@ -1,22 +1,201 @@
-All Rights Reserved
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
 
-Copyright (c) 2026 Anhedral, Inc.
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
 
-   THE CONTENTS OF THIS PROJECT ARE PROPRIETARY AND CONFIDENTIAL.
-   UNAUTHORIZED COPYING, TRANSFERRING OR REPRODUCTION OF THE CONTENTS
-   OF THIS PROJECT, VIA ANY MEDIUM, IS STRICTLY PROHIBITED.
+   1. Definitions.
 
-   The receipt or possession of the source code and/or any parts thereof
-   does not convey or imply any right to use them for any purpose other
-   than the purpose for which they were provided to you.
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
 
-   The software is provided "AS IS", without warranty of any kind,
-   express or implied, including but not limited to the warranties of
-   merchantability, fitness for a particular purpose and noninfringement.
-   In no event shall the authors or copyright holders be liable for any
-   claim, damages or other liability, whether in an action of contract,
-   tort or otherwise, arising from, out of or in connection with the
-   software or the use or other dealings in the software.
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
 
-   The above copyright notice and this permission notice shall be
-   included in all copies or substantial portions of the software.
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Anhedral, Inc.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.