create-koppajs 1.2.2 → 1.2.3

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,227 +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 22 or newer
-- pnpm 10 or newer
-
-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?

package/template/TESTING_STRATEGY.md

@@ -1,96 +0,0 @@
-# Testing Strategy
-
-## Current state
-
-This repository now has a small automated testing stack aligned with the actual starter risk profile:
-
-- `pnpm test:run` for unit and integration tests in Vitest
-- `pnpm test:coverage` for local coverage reporting
-- `pnpm test:e2e` for a Playwright smoke test against `vite preview`
-- `pnpm check` for the fast repository baseline
-- `pnpm validate` for the full local and CI validation path
-- `pnpm release:check` for tagged release candidates
-- `commitlint` through `.husky/commit-msg` for commit message validation
-- `pnpm typecheck`
-- `pnpm build`
-
-## Philosophy
-
-- Test the smallest meaningful unit that gives confidence.
-- Prefer extracting logic into `.ts` modules when it becomes complex enough to warrant focused unit tests.
-- Add test infrastructure only when the repository's behavior justifies it; do not add tools for ceremony alone.
-- Avoid brittle tests that mirror implementation details instead of observable behavior.
-- Reuse the real Vite loading path in automated tests whenever `.kpa` handling is part of the risk surface.
-
-## Test pyramid for this repository
-
-### Unit tests
-
-Use unit tests for isolated logic that can fail independently of the browser runtime.
-
-Today the starter does not ship dedicated extracted helper modules, so unit-only
-coverage is optional until new isolated logic actually exists.
-
-Typical triggers:
-
-- value transformations
-- branching business rules
-- reusable helpers
-- local tooling helpers
-
-### Integration or component tests
-
-Use integration tests when multiple local boundaries must be verified together but a full browser run would be disproportionate.
-
-Typical triggers:
-
-- bootstrap registration in `src/main.ts`
-- build-time behavior that depends on the Vite plugin
-- shared state or lifecycle interactions that are not yet broad enough for end-to-end coverage
-
-### End-to-end tests
-
-This repository has a real interactive UI, so it carries one Playwright smoke test already. Keep that layer intentionally small and user-facing.
-
-Typical triggers:
-
-- root UI rendering
-- critical starter interactions such as the counter behavior
-- preview/build regressions that would not be caught by Vitest alone
-
-Escalate E2E coverage beyond smoke scope only when the starter gains broader workflows such as routing, async data flows, persistence, or deployment-sensitive behavior.
-
-## Mocking policy
-
-- Prefer testing pure extracted logic without mocks.
-- Mock only at external boundaries such as HTTP, storage, or browser APIs that are expensive or nondeterministic.
-- Use selective mocks in integration tests only to observe bootstrap boundaries that would otherwise be opaque.
-
-## Coverage expectations
-
-- There is no blanket repository percentage target right now.
-- New non-trivial logic should come with focused tests.
-- When a subsystem introduces branching logic, asynchronous behavior, or state shared across components, test automation stops being optional.
-- Coverage reports are a decision aid, not a target game. Raise thresholds only when the code surface justifies them.
-
-## Quality gates by change size
-
-- Documentation-only change: verify links and document consistency.
-- Small style or copy change: run `pnpm check`.
-- Source or config change: run `pnpm check`.
-- UI, bootstrap, or browser-sensitive change: run `pnpm validate`.
-- Version, changelog, or release workflow change: run `pnpm release:check`.
-- Commit convention change: validate `commitlint.config.mjs` and `.husky/commit-msg` together.
-- New subsystem or new state model: add tests appropriate to the risk level and update this strategy.
-
-## Style linting position
-
-Stylelint is intentionally not part of the current baseline.
-
-- The meaningful styling surface lives inside `.kpa` files.
-- Adding Stylelint only for `src/style.css` would mostly lint the global reset and miss the component-local styles that matter.
-- Revisit this decision only when KoppaJS gains a low-friction way to lint embedded `.kpa` CSS blocks or when the repository starts moving substantial styles into standalone CSS files.
-
-## Maintenance rule
-
-Whenever test tooling, quality gates, or expected confidence levels change, update this file and [docs/quality/quality-gates.md](./docs/quality/quality-gates.md) in the same change.

package/template/_editorconfig

@@ -1,12 +0,0 @@
-root = true
-
-[*]
-charset = utf-8
-end_of_line = lf
-indent_size = 2
-indent_style = space
-insert_final_newline = true
-trim_trailing_whitespace = true
-
-[*.md]
-trim_trailing_whitespace = false

package/template/_github/instructions/ai-workflow.md

@@ -1,33 +0,0 @@
-# AI Workflow Instructions
-
-## Read before editing
-
-For any non-trivial change, read these documents in order:
-
-1. `DECISION_HIERARCHY.md`
-2. `AI_CONSTITUTION.md`
-3. `ARCHITECTURE.md`
-4. the relevant spec in `docs/specs/`
-5. the relevant ADR in `docs/adr/`
-6. `DEVELOPMENT_RULES.md`
-7. `TESTING_STRATEGY.md`
-
-For release-related work also read `CHANGELOG.md` and `RELEASE.md`.
-
-## Required behavior
-
-- Prefer existing repository patterns over new abstractions.
-- Do not silently change public component tags, startup flow, or dependency sourcing.
-- Use `spec -> quality plan -> implementation -> documentation`.
-- Update the meta layer in the same change when architecture, rules, or workflows change.
-- Record durable technical decisions in ADRs.
-- Keep hooks fast and put heavier validation into `pnpm validate` and CI.
-- If versioning, changelog, or release automation changes, update `CHANGELOG.md`, `RELEASE.md`, and the affected workflow in the same change.
-- If you create commits, use Conventional Commits that satisfy `commitlint`.
-
-## Required validation
-
-- Run `pnpm check` for source, config, test, or tooling changes.
-- Run `pnpm validate` when UI behavior, bootstrap wiring, browser-facing assets, or quality tooling changes.
-- Run `pnpm release:check` when versioning, changelog, or release workflow behavior changes.
-- If a local browser check cannot be run, say so explicitly instead of implying it passed.

package/template/_github/workflows/ci.yml

@@ -1,41 +0,0 @@
-name: CI
-
-on:
-  pull_request:
-    branches:
-      - develop
-      - main
-  push:
-    branches:
-      - main
-
-jobs:
-  validate:
-    runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        node: [22, 24]
-
-    steps:
-      - name: Check out repository
-        uses: actions/checkout@v4
-
-      - name: Set up pnpm
-        uses: pnpm/action-setup@v4
-        with:
-          version: 10.12.1
-
-      - name: Set up Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: ${{ matrix.node }}
-          cache: pnpm
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      - name: Install Playwright browser
-        run: pnpm exec playwright install --with-deps chromium
-
-      - name: Run repository validation
-        run: pnpm validate