create-koppajs 1.2.1 → 1.2.3

package/template/docs/specs/README.md

@@ -1,36 +0,0 @@
-# Specifications
-
-Specs define expected behavior before or alongside implementation. They are the highest-precedence project documents.
-
-## When a spec is required
-
-Create or update a spec when a change:
-
-- introduces or changes user-visible behavior,
-- adds a subsystem,
-- changes public setup or bootstrap behavior,
-- changes a feature in a way that needs explicit acceptance criteria.
-
-## Required structure
-
-Use [`TEMPLATE.md`](./TEMPLATE.md). Each spec should define:
-
-- purpose
-- behavior
-- inputs
-- outputs
-- constraints
-- edge cases
-- acceptance criteria
-
-## Lifecycle
-
-- Draft or update the relevant spec before implementing a non-trivial change.
-- Keep the spec narrow and testable.
-- If implementation diverges from the spec, reconcile them immediately.
-
-## Current specs
-
-- [`app-bootstrap.md`](./app-bootstrap.md)
-- [`counter-component.md`](./counter-component.md)
-- [`quality-workflow.md`](./quality-workflow.md)

package/template/docs/specs/TEMPLATE.md

@@ -1,34 +0,0 @@
-# Spec: Title
-
-## Status
-
-Draft | Approved | Superseded
-
-## Purpose
-
-Describe why this behavior exists.
-
-## Behavior
-
-Describe the observable behavior.
-
-## Inputs
-
-Describe user, system, or configuration inputs.
-
-## Outputs
-
-Describe rendered output, state changes, or side effects.
-
-## Constraints
-
-List constraints that implementation must respect.
-
-## Edge cases
-
-List the important boundary conditions.
-
-## Acceptance criteria
-
-- Criterion 1
-- Criterion 2

package/template/docs/specs/app-bootstrap.md

@@ -1,46 +0,0 @@
-# Spec: App bootstrap
-
-## Status
-
-Approved
-
-## Purpose
-
-Provide a predictable, minimal startup path for a standalone KoppaJS application.
-
-## Behavior
-
-- The application starts from `index.html`.
-- The HTML shell loads one global stylesheet and one module entrypoint.
-- The document declares exactly one root custom element: `<app-view>`.
-- `src/main.ts` registers `app-view` and `counter-component` with KoppaJS Core.
-- `src/main.ts` invokes `Core()` once to bootstrap the application.
-
-## Inputs
-
-- Browser loading `index.html`
-- Static asset and source file paths resolved by Vite
-
-## Outputs
-
-- A rendered `<app-view>` application shell
-- A registered `<counter-component>` available to the root view
-
-## Constraints
-
-- There must be a single bootstrap entrypoint.
-- The root tag in `index.html` must stay aligned with the component registered in `src/main.ts`.
-- No hidden self-registration inside component modules.
-- Bootstrap must rely on the public KoppaJS root API via `Core()` rather than non-public setup helpers.
-- No extra runtime dependencies are required beyond the declared npm packages.
-
-## Edge cases
-
-- If a component tag changes, both `index.html` and `src/main.ts` must be updated together.
-- If more bootstrap behavior is added, it must not introduce a second source of truth for initialization.
-
-## Acceptance criteria
-
-- Opening the app through Vite renders the root view without manual DOM scripting.
-- `src/main.ts` remains the only location that calls `Core()`.
-- The root view can render the counter component immediately after bootstrap.

package/template/docs/specs/counter-component.md

@@ -1,48 +0,0 @@
-# Spec: Counter component
-
-## Status
-
-Approved
-
-## Purpose
-
-Demonstrate local interactive state in a minimal KoppaJS component.
-
-## Behavior
-
-- The component renders a "Counter" label, a numeric count, and increment/decrement buttons.
-- The initial count is `0`.
-- Clicking the increment button increases the count by `1`.
-- Clicking the decrement button decreases the count by `1`.
-- The displayed count updates immediately after each click.
-- The increment and decrement buttons expose stable accessible names.
-- The rendered count is announced politely to assistive technology when it changes.
-
-## Inputs
-
-- User clicks on the increment button
-- User clicks on the decrement button
-
-## Outputs
-
-- Updated numeric text rendered in the component
-- No external side effects
-
-## Constraints
-
-- State is local to the component.
-- The component performs no persistence, networking, or cross-component coordination.
-- The component remains embeddable inside the root app shell.
-
-## Edge cases
-
-- Negative values are allowed.
-- Repeated clicks continue to update the count linearly within normal JavaScript number behavior.
-
-## Acceptance criteria
-
-- The counter is visible inside the app shell when the starter loads.
-- The first rendered value is `0`.
-- A single click on `+` changes the value from `0` to `1`.
-- A single click on `-` changes the value from `0` to `-1`.
-- Assistive technology can distinguish the increment and decrement actions without relying on symbol glyphs alone.

package/template/docs/specs/quality-workflow.md

@@ -1,62 +0,0 @@
-# Spec: Quality workflow
-
-## Status
-
-Approved
-
-## Purpose
-
-Keep the starter's tooling, tests, and contributor workflow consistent enough that regressions are caught early without turning a minimal example into a heavyweight platform.
-
-## Behavior
-
-- The repository exposes a fast local validation path through `pnpm check`.
-- The repository exposes a fuller validation path through `pnpm validate`, which adds a real-browser smoke test.
-- Staged files run through a fast `lint-staged` pre-commit hook.
-- Commit messages are validated by `commitlint` in a `commit-msg` hook.
-- Source, config, and test changes are checked by ESLint, Prettier, TypeScript, and Vitest.
-- The real UI smoke path is checked by Playwright against `vite preview`.
-- CI runs the same full validation flow as local contributors.
-- Tagged releases rerun the full validation flow and verify tag/version alignment before a GitHub Release is created.
-- Stylelint is intentionally absent until the repository has a credible way to lint embedded `.kpa` CSS without covering only the least relevant styling surface.
-
-## Inputs
-
-- Source, config, test, and documentation changes
-- Staged files at commit time
-- Commit messages at commit time
-- Pull requests and pushes that trigger CI
-- Version, changelog, and tag pushes that trigger the release workflow
-
-## Outputs
-
-- Consistent formatting on supported file types
-- Conventional commit history for maintainable review and release preparation
-- Type-safe source and TypeScript tooling files
-- Automated confidence for the `.kpa` export workaround, bootstrap wiring, and the starter UI smoke path
-- A guarded GitHub release path that fails when the pushed tag does not match `package.json`
-- Fast feedback before commit and in CI
-
-## Constraints
-
-- Hooks must stay fast enough for normal local use.
-- Playwright coverage must remain focused on smoke-level user journeys until the UI surface grows.
-- Tooling should stay aligned with the starter's actual risk profile rather than generic best-practice checklists.
-- Release automation must stay consistent with the repository remaining `private`; it may create GitHub Releases but must not imply npm publishing.
-- Commit rules should stay simple enough that contributors can apply them without release tooling knowledge.
-
-## Edge cases
-
-- If browser binaries are not installed locally, contributors must install Chromium before running `pnpm test:e2e` or `pnpm validate`.
-- If Stylelint is introduced later, it must cover the meaningful styling surface rather than only `src/style.css`.
-- If the UI grows beyond a simple smoke surface, expand Playwright coverage deliberately and update this spec.
-- If a pushed tag does not match `package.json`, the release workflow must fail before creating a release artifact.
-- Auto-generated merge, revert, `fixup!`, and `squash!` commits may be exempted by the hook logic.
-
-## Acceptance criteria
-
-- `pnpm check` runs lint, format verification, type checking, Vitest, and build successfully on a clean checkout.
-- `pnpm validate` reuses the built output to run the Playwright smoke test successfully.
-- A commit with a staged lint or formatting error is blocked by the pre-commit hook.
-- A non-conventional commit message is blocked by the `commit-msg` hook.
-- A pushed `vX.Y.Z` tag is rejected by release automation when `package.json` contains a different version.

package/template/eslint.config.mjs

@@ -1,54 +0,0 @@
-import js from "@eslint/js";
-import globals from "globals";
-import { fileURLToPath } from "node:url";
-import tseslint from "typescript-eslint";
-
-const tsconfigRootDir = fileURLToPath(new URL(".", import.meta.url));
-
-export default tseslint.config(
-  {
-    ignores: [
-      ".ai/**",
-      "coverage/**",
-      "dist/**",
-      "node_modules/**",
-      "playwright-report/**",
-      "test-results/**",
-    ],
-  },
-  {
-    files: ["**/*.{js,mjs,cjs}"],
-    extends: [js.configs.recommended],
-    languageOptions: {
-      globals: {
-        ...globals.node,
-      },
-    },
-  },
-  {
-    files: ["**/*.{ts,mts,cts}"],
-    extends: [...tseslint.configs.recommendedTypeChecked],
-    languageOptions: {
-      parserOptions: {
-        projectService: true,
-        tsconfigRootDir,
-      },
-    },
-  },
-  {
-    files: ["src/**/*.ts"],
-    languageOptions: {
-      globals: {
-        ...globals.browser,
-      },
-    },
-  },
-  {
-    files: ["tests/**/*.ts", "*.config.ts"],
-    languageOptions: {
-      globals: {
-        ...globals.node,
-      },
-    },
-  },
-);

package/template/playwright.config.ts

@@ -1,31 +0,0 @@
-import { defineConfig, devices } from "@playwright/test";
-
-const port = 4173;
-
-export default defineConfig({
-  testDir: "./tests/e2e",
-  fullyParallel: true,
-  forbidOnly: Boolean(process.env.CI),
-  retries: process.env.CI ? 2 : 0,
-  reporter: process.env.CI ? "github" : "list",
-  use: {
-    baseURL: `http://127.0.0.1:${port}`,
-    screenshot: "only-on-failure",
-    trace: "on-first-retry",
-    video: "retain-on-failure",
-  },
-  webServer: {
-    command: "pnpm serve:e2e",
-    url: `http://127.0.0.1:${port}`,
-    reuseExistingServer: !process.env.CI,
-    timeout: 120_000,
-  },
-  projects: [
-    {
-      name: "chromium",
-      use: {
-        ...devices["Desktop Chrome"],
-      },
-    },
-  ],
-});