create-koppajs 1.2.1 → 1.2.3

package/template/CONTRIBUTING.md

@@ -1,92 +0,0 @@
-# Contributing
-
-## Setup
-
-Requirements:
-
-- Node.js 20.19+, 22.13+, or 24+
-- pnpm 10 or newer
-
-Node 23 is intentionally not part of the supported range because the current
-upstream frontend tooling excludes it.
-
-Install and run:
-
-```bash
-pnpm install
-pnpm dev
-```
-
-Install the Playwright browser once if you plan to run browser smoke tests locally:
-
-```bash
-pnpm exec playwright install chromium
-```
-
-Useful commands:
-
-```bash
-pnpm lint
-pnpm format:check
-pnpm typecheck
-pnpm test:run
-pnpm test:coverage
-pnpm test:e2e
-pnpm check
-pnpm validate
-pnpm release:check
-pnpm build
-pnpm serve
-```
-
-Commit messages use Conventional Commits.
-Examples:
-
-```text
-feat: add release baseline
-docs: update contributing guide
-fix: align bootstrap docs
-```
-
-## Workflow
-
-1. Read [DECISION_HIERARCHY.md](./DECISION_HIERARCHY.md), [ARCHITECTURE.md](./ARCHITECTURE.md), and any relevant spec or ADR before changing source files.
-2. For non-trivial work, update or create the relevant spec in [docs/specs](./docs/specs) first.
-3. If the change alters architecture, tooling, public tags, or repository workflow, add or update an ADR in [docs/adr](./docs/adr).
-4. Implement the smallest change that satisfies the spec.
-5. Run the applicable quality gates from [TESTING_STRATEGY.md](./TESTING_STRATEGY.md). Use `pnpm check` for the local baseline and `pnpm validate` before merge when the UI, bootstrap, or tooling changed.
-6. If the change touches versioning, changelog, or release automation, update `CHANGELOG.md`, `RELEASE.md`, and the affected workflow in the same change.
-7. Update architecture, development, testing, and README docs when the actual project state changes.
-
-## Releases
-
-- Release notes live in [`CHANGELOG.md`](./CHANGELOG.md).
-- The maintainer release procedure lives in [`RELEASE.md`](./RELEASE.md).
-- Releases are prepared on `develop`, moved through `release/*`, merged into `main`, and tagged as `vX.Y.Z`.
-- The release workflow creates GitHub Releases only. The repository starts
-  `private`, so no npm publish step is configured by default.
-- Run `pnpm release:check` before cutting a release tag.
-
-## Commit policy
-
-- Commit messages are validated by `.husky/commit-msg` using `commitlint`.
-- Use Conventional Commits such as `feat: ...`, `fix: ...`, `docs: ...`, `test: ...`, `ci: ...`, or `chore: ...`.
-- Keep the commit header at 72 characters or fewer.
-- Merge, revert, `fixup!`, and `squash!` commits may bypass validation when Git creates them automatically.
-
-## Pull request expectations
-
-- Keep the starter minimal unless expansion is explicitly approved.
-- Explain user-visible behavior changes and architecture-impacting decisions.
-- Do not silently swap dependency sources, add build tools, or introduce new subsystems.
-- Keep docs and code aligned in the same change.
-- Keep hooks fast; heavy validation belongs in `pnpm validate` and CI, not in `pre-commit`.
-
-## AI-assisted contributions
-
-AI contributors follow the same rules as humans:
-
-- read governing docs before editing,
-- prefer existing patterns,
-- do not invent architecture casually,
-- update the meta layer whenever structure or rules change.

package/template/DECISION_HIERARCHY.md

@@ -1,32 +0,0 @@
-# Decision Hierarchy
-
-When repository documents conflict, use this order of precedence.
-
-1. Approved specifications in [`docs/specs/`](./docs/specs)
-2. Architecture Decision Records in [`docs/adr/`](./docs/adr)
-3. [`AI_CONSTITUTION.md`](./AI_CONSTITUTION.md)
-4. [`ARCHITECTURE.md`](./ARCHITECTURE.md) and supporting architecture docs in [`docs/architecture/`](./docs/architecture)
-5. [`DEVELOPMENT_RULES.md`](./DEVELOPMENT_RULES.md) and [`TESTING_STRATEGY.md`](./TESTING_STRATEGY.md)
-6. Quality and maintenance guidance in [`docs/quality/`](./docs/quality) and [`docs/meta/`](./docs/meta)
-7. Contributor guidance and examples in [`CONTRIBUTING.md`](./CONTRIBUTING.md), [`README.md`](./README.md), and inline comments
-
-## Interpretation rules
-
-- The most specific document wins when two documents have the same rank.
-- A newer document does not override a higher-ranked document by default.
-- If a lower-ranked document is wrong, fix it instead of following it.
-- If no applicable spec exists for a non-trivial change, create or update one before implementation.
-- If a change would invalidate an ADR, create a superseding ADR instead of silently drifting away from it.
-
-## Required reading order for non-trivial changes
-
-1. This file
-2. [AI_CONSTITUTION.md](./AI_CONSTITUTION.md)
-3. [ARCHITECTURE.md](./ARCHITECTURE.md)
-4. Relevant spec in [docs/specs](./docs/specs)
-5. Relevant ADR in [docs/adr](./docs/adr)
-6. [DEVELOPMENT_RULES.md](./DEVELOPMENT_RULES.md) and [TESTING_STRATEGY.md](./TESTING_STRATEGY.md)
-
-## Escalation rule
-
-When a change creates a new lasting rule, boundary, or tradeoff, encode it as a spec or ADR rather than relying on chat history or commit messages.

package/template/DEVELOPMENT_RULES.md

@@ -1,57 +0,0 @@
-# Development Rules
-
-## Scope
-
-These rules describe how code and documentation are expected to evolve in this repository.
-
-## Source layout rules
-
-- Keep `index.html` as a static shell with asset references and the single root element.
-- Keep `src/main.ts` limited to bootstrap concerns: imports, `Core.take(...)` registrations, and the single public bootstrap call via `Core()`.
-- Use `.kpa` files for UI composition, local component state, and component-scoped CSS.
-- If logic becomes reusable, asynchronous, or branch-heavy, move it into `.ts` modules under `src/`.
-- Keep `public/` for static assets only.
-- Keep automated tests under `tests/`, split by `unit`, `integration`, and `e2e` only when each level is meaningfully used.
-
-## Naming conventions
-
-- Custom element names must be kebab-case.
-- Root-level application components should use `app-` prefixes when they represent app shells or app-wide structure.
-- Component filenames should match their primary exported or registered concept.
-- New files and folders should use descriptive names over abbreviations.
-
-## Dependency rules
-
-- Runtime dependencies must be justified by a concrete need in a spec or ADR.
-- Prefer browser APIs and KoppaJS primitives before adding helper libraries.
-- Keep this repository wired to published npm packages unless there is an explicit ADR stating otherwise.
-- Build tooling changes must update contributor docs and architecture docs in the same change.
-- Quality tooling must stay proportionate to the starter. Prefer one clear tool per job over overlapping stacks.
-
-## Coding patterns
-
-- Favor simple, local state over premature abstraction.
-- Keep methods short and named by behavior.
-- Avoid hidden side effects during import.
-- Keep CSS local to components unless the style truly applies application-wide.
-- Preserve strict TypeScript settings; do not weaken `tsconfig.json` to work around errors.
-- Give interactive controls stable accessible names when feasible so smoke tests can target public semantics instead of brittle selectors.
-- Keep Playwright assertions user-facing. Implementation-detail checks belong in Vitest, not in browser tests.
-
-## Forbidden without a spec and ADR
-
-- Introducing routing
-- Adding global state containers
-- Adding network or persistence layers
-- Introducing SSR, multi-page bootstraps, or multiple root entries
-- Switching dependency sourcing from npm packages to local monorepo links
-- Expanding the starter into a multi-feature demo application
-- Adding heavyweight hooks that run the entire suite on every commit
-
-## Documentation obligations
-
-- Update [ARCHITECTURE.md](./ARCHITECTURE.md) when source layout or runtime flow changes.
-- Update [TESTING_STRATEGY.md](./TESTING_STRATEGY.md) when quality gates or tooling change.
-- Update or create a spec in [docs/specs](./docs/specs) for user-visible changes.
-- Add an ADR in [docs/adr](./docs/adr) for durable technical decisions.
-- Update [docs/quality/quality-gates.md](./docs/quality/quality-gates.md) when scripts, hooks, CI checks, or browser-smoke expectations change.

package/template/LICENSE

@@ -1,201 +0,0 @@
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "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 Bastian Bensch
-
-   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.

package/template/RELEASE.md

@@ -1,230 +0,0 @@
-# Release Process for `__PROJECT_NAME__`
-
-This document describes the repository-specific release workflow for
-`__PROJECT_NAME__`.
-
-The project uses a manual, tag-driven release process.
-Only tagged versions are official releases.
-
-The effective flow is:
-
-1. Finalize the release content on `develop`
-2. Update `package.json` and `CHANGELOG.md`
-3. Validate the release candidate locally
-4. Create a `release/*` branch from that state
-5. Merge the release branch into `main`
-6. Tag the release commit on `main` as `vX.Y.Z`
-7. Push the tag
-8. Let GitHub Actions validate and create the GitHub Release
-9. Merge the updated `main` back into `develop`
-
----
-
-## Release Model
-
-This repository does not use automated versioning tools such as Changesets or
-semantic-release.
-
-The release is controlled by:
-
-- the version in `package.json`
-- the release entry in `CHANGELOG.md`
-- the merge of the release-ready state into `main`
-- the Git tag in the form `vX.Y.Z`
-- the GitHub Actions workflow in `.github/workflows/release.yml`
-
-Important consequences:
-
-- A merge to `main` alone does not create a release
-- A tag triggers the release workflow
-- The tag version must exactly match `package.json`
-- The tag must point to the release commit on `main`
-- After a successful release, `main` should be merged back into `develop`
-
-The included release workflow creates GitHub Releases only and does not publish
-to npm by default.
-
-If this project later needs npm publishing or another release target, update
-this file, `package.json`, and `.github/workflows/release.yml` in the same
-change.
-
-Do not tag `develop`.
-Do not tag the `release/*` branch.
-Tag only the release commit that is already on `main`.
-
----
-
-## Preconditions
-
-Before cutting a release, ensure all of the following are true:
-
-- The intended release scope is already complete on `develop`
-- `package.json` contains the target version
-- `CHANGELOG.md` contains the corresponding release notes
-- The lockfile is up to date
-- The release content has been reviewed
-
-Tooling expectations for local verification:
-
-- Node.js 20.19+, 22.13+, or 24+
-- pnpm 10 or newer
-
-Node 23 is intentionally not treated as supported here because the current
-upstream frontend toolchain excludes it.
-
-This repository also enforces `engine-strict=true` in `.npmrc`, so incompatible
-Node.js or pnpm versions should be treated as a release blocker.
-
----
-
-## Local Validation Before Branching
-
-Before creating the release branch, validate the exact release candidate
-locally.
-
-Recommended commands:
-
-```bash
-pnpm install
-pnpm release:check
-```
-
-`pnpm release:check` runs the same full validation path used by the release
-workflow, including Playwright.
-
-If Chromium is not installed locally yet, install it once:
-
-```bash
-pnpm exec playwright install chromium
-```
-
----
-
-## Step-by-Step Release Workflow
-
-### 1. Finalize the release on `develop`
-
-Ensure `develop` already contains the exact release content.
-
-Typical release preparation includes:
-
-- updating `package.json` from the previous version to the next release version
-- moving the relevant notes into the final section in `CHANGELOG.md`
-- committing any last release fixes
-
-Make sure the release-ready state is committed before creating `release/*`.
-
-### 2. Create the `release/*` branch
-
-Create a release branch from the validated `develop` state.
-
-Example:
-
-```bash
-git checkout develop
-git pull
-git checkout -b release/X.Y.Z
-```
-
-### 3. Merge the release branch into `main`
-
-Merge `release/*` into `main` using the repository's normal process.
-
-The critical requirement is:
-
-- `main` must contain the final release commit before tagging
-
-Conceptually:
-
-```bash
-git checkout main
-git pull
-git merge --no-ff release/X.Y.Z
-```
-
-### 4. Tag the release commit on `main`
-
-After the release branch has been merged, create the Git tag on the release
-commit that is now on `main`.
-
-Example:
-
-```bash
-git checkout main
-git pull
-git tag vX.Y.Z
-```
-
-The tag format is mandatory:
-
-- `vX.Y.Z` is valid
-- `X.Y.Z` is not valid for this workflow
-
-### 5. Push `main` and the tag
-
-Push the merged `main` branch and then the tag.
-
-Example:
-
-```bash
-git push origin main
-git push origin vX.Y.Z
-```
-
-### 6. Wait for the release workflow to finish
-
-Verify that:
-
-- the GitHub Actions release workflow passed
-- the GitHub Release was created
-- the version-check step confirmed tag and `package.json` alignment
-
-### 7. Merge `main` back into `develop`
-
-After the release has completed successfully, merge the updated `main` back
-into `develop`.
-
-Conceptually:
-
-```bash
-git checkout develop
-git pull
-git merge --no-ff main
-```
-
----
-
-## GitHub Workflow Behavior
-
-The workflow `.github/workflows/release.yml` runs on pushed tags matching
-`vX.Y.Z`.
-
-For each matching tag it will:
-
-1. install dependencies
-2. install the Playwright Chromium browser
-3. run `pnpm validate`
-4. verify that the tag version matches `package.json`
-5. create a GitHub Release with generated release notes
-
-If any step fails, the release job stops immediately.
-
----
-
-## Maintainer Checklist
-
-Use this as the maintainer checklist for every release:
-
-1. Verify the release scope on `develop`
-2. Update `package.json`
-3. Update `CHANGELOG.md`
-4. Run `pnpm release:check`
-5. Create `release/*` from `develop`
-6. Merge `release/*` into `main`
-7. Confirm the merged commit on `main` has the correct version and changelog
-8. Create the `vX.Y.Z` tag on `main`
-9. Push `main`
-10. Push the tag
-11. Watch the GitHub Actions release workflow
-12. Verify the GitHub Release exists
-13. Merge `main` back into `develop`

package/template/ROADMAP.md

@@ -1,34 +0,0 @@
-# Roadmap
-
-This roadmap describes intended directions, not guaranteed delivery dates.
-
-## Current priorities
-
-- Keep the starter minimal and production-like.
-- Preserve a clear bootstrap path for new KoppaJS users.
-- Keep the meta layer synchronized with the actual repository.
-
-## Near-term opportunities
-
-- Add a lightweight automated test runner when the repository gains logic that warrants it.
-- Replace or harden any documentation that still assumes old monorepo-linked dependencies.
-- Add more feature specs only when new starter capabilities are intentionally introduced.
-
-## Longer-term expansion triggers
-
-These should happen only with a spec and ADR:
-
-- routing
-- async data fetching
-- persistence
-- richer component examples
-- CI automation
-
-## Meta-layer maintenance
-
-Every release or architecture-changing change should answer:
-
-- Does the architecture document still match the code?
-- Did any new decision deserve an ADR?
-- Did testing expectations change?
-- Did contributor instructions stay accurate?