create-koppajs 1.2.2 → 1.2.3

package/template/prettier.config.mjs

@@ -1,6 +0,0 @@
-export default {
-  semi: true,
-  singleQuote: false,
-  tabWidth: 2,
-  trailingComma: "all",
-};

package/template/public/favicon.svg

@@ -1,15 +0,0 @@
-<svg width="410" height="404" viewBox="0 0 410 404" fill="none" xmlns="http://www.w3.org/2000/svg">
-<path d="M399.641 59.5246L215.643 388.545C211.844 395.338 202.084 395.378 198.228 388.618L10.5817 59.5563C6.38087 52.1896 12.6802 43.2665 21.0281 44.7586L205.223 77.6824C206.398 77.8924 207.601 77.8904 208.776 77.6763L389.119 44.8058C397.439 43.2894 403.768 52.1434 399.641 59.5246Z" fill="url(#paint0_linear)"/>
-<path d="M292.965 1.5744L156.801 28.2552C154.563 28.6937 152.906 30.5903 152.771 32.8664L144.395 174.33C144.198 177.662 147.258 180.248 150.51 179.498L188.42 170.749C191.967 169.931 195.172 173.055 194.443 176.622L183.18 231.775C182.422 235.487 185.907 238.661 189.532 237.56L212.947 230.446C216.577 229.344 220.065 232.527 219.297 236.242L201.398 322.875C200.278 328.294 207.486 331.249 210.492 326.603L212.5 323.5L323.454 102.072C325.312 98.3645 322.108 94.137 318.036 94.9228L279.014 102.454C275.347 103.161 272.227 99.746 273.262 96.1583L298.731 7.86689C299.767 4.27314 296.636 0.855181 292.965 1.5744Z" fill="url(#paint1_linear)"/>
-<defs>
-<linearGradient id="paint0_linear" x1="6.00017" y1="32.9999" x2="235" y2="344" gradientUnits="userSpaceOnUse">
-<stop stop-color="#41D1FF"/>
-<stop offset="1" stop-color="#BD34FE"/>
-</linearGradient>
-<linearGradient id="paint1_linear" x1="194.651" y1="8.81818" x2="236.076" y2="292.989" gradientUnits="userSpaceOnUse">
-<stop stop-color="#FFEA83"/>
-<stop offset="0.0833333" stop-color="#FFDD35"/>
-<stop offset="1" stop-color="#FFA800"/>
-</linearGradient>
-</defs>
-</svg>

package/template/tests/e2e/app.spec.ts

@@ -1,18 +0,0 @@
-import { expect, test } from "@playwright/test";
-
-test("renders the starter and updates the counter", async ({ page }) => {
-  await page.goto("/");
-
-  await expect(page.getByText("Minimal Starter")).toBeVisible();
-
-  const counterValue = page.getByRole("status");
-
-  await expect(counterValue).toHaveText("0");
-
-  await page.getByRole("button", { name: "Increment counter" }).click();
-  await expect(counterValue).toHaveText("1");
-
-  await page.getByRole("button", { name: "Decrement counter" }).click();
-  await page.getByRole("button", { name: "Decrement counter" }).click();
-  await expect(counterValue).toHaveText("-1");
-});

package/template/tests/integration/main-bootstrap.test.ts

@@ -1,33 +0,0 @@
-import { afterEach, describe, expect, it, vi } from "vitest";
-
-const { core, take } = vi.hoisted(() => {
-  const take = vi.fn();
-  const core = Object.assign(vi.fn(), { take });
-
-  return { core, take };
-});
-
-vi.mock("@koppajs/koppajs-core", () => ({
-  Core: core,
-}));
-
-describe("main bootstrap", () => {
-  afterEach(() => {
-    core.mockClear();
-    take.mockClear();
-    vi.resetModules();
-  });
-
-  it("registers the root components and boots the app once", async () => {
-    await import("../../src/main");
-
-    expect(take).toHaveBeenCalledTimes(2);
-    expect(take).toHaveBeenNthCalledWith(1, expect.anything(), "app-view");
-    expect(take).toHaveBeenNthCalledWith(
-      2,
-      expect.anything(),
-      "counter-component",
-    );
-    expect(core).toHaveBeenCalledTimes(1);
-  });
-});

package/template/vite.config.d.mts

@@ -1,5 +0,0 @@
-import type { UserConfig } from "vite";
-
-declare const config: UserConfig;
-
-export default config;

package/template/vitest.config.mjs

@@ -1,19 +0,0 @@
-import { defineConfig, mergeConfig } from "vitest/config";
-
-import viteConfig from "./vite.config.mjs";
-
-export default mergeConfig(
-  viteConfig,
-  defineConfig({
-    test: {
-      include: ["tests/**/*.test.ts"],
-      coverage: {
-        provider: "v8",
-        reporter: ["text", "html"],
-        reportsDirectory: "./coverage",
-        include: ["src/**/*.ts"],
-        exclude: ["playwright.config.ts", "tests/**/*.ts", "vitest.config.mjs"],
-      },
-    },
-  }),
-);

package/template-overlays/router/ARCHITECTURE.md

@@ -1,86 +0,0 @@
-# Architecture
-
-This repository is a small KoppaJS router starter. It demonstrates a clear
-bootstrap path: HTML shell, TypeScript entrypoint, one root app shell
-component, one router instance, two primary routes, and one explicit not-found
-route. The repository also carries the same quality and release automation
-baseline as the minimal starter so the example remains production-like.
-
-## System overview
-
-- `index.html` provides the document shell, loads global CSS, declares the
-  `<app-view>` root element, and imports the TypeScript entrypoint.
-- `src/main.ts` registers local components with `Core.take(...)`, calls
-  `Core()` once, waits for the route outlet to exist, and initializes one
-  `KoppajsRouter` instance.
-- `src/app-view.kpa` is the root shell. It renders the hero area, the primary
-  navigation, and the `#app-outlet` container that receives route content.
-- `src/home-page.kpa` is the default route and composes `counter-component`.
-- `src/router-page.kpa` is the second route and explains the router wiring.
-- `src/not-found-page.kpa` is the explicit catch-all route.
-- `src/counter-component.kpa` remains the example local-state component.
-- `src/style.css` defines global tokens, base layout, and the background.
-- `tests/integration/` verifies bootstrap wiring and router startup.
-- `tests/e2e/` verifies the user-visible route flow and counter behavior.
-
-More detailed boundaries live in [docs/architecture/module-boundaries.md](./docs/architecture/module-boundaries.md).
-
-## Runtime flow
-
-1. The browser loads [`index.html`](./index.html).
-2. The document loads [`src/style.css`](./src/style.css) and [`src/main.ts`](./src/main.ts).
-3. [`src/main.ts`](./src/main.ts) registers `app-view`, `home-page`,
-   `router-page`, `not-found-page`, and `counter-component`, then calls
-   `Core()`.
-4. KoppaJS instantiates `<app-view>`.
-5. [`src/app-view.kpa`](./src/app-view.kpa) renders the app shell, navigation,
-   and `#app-outlet`.
-6. `src/main.ts` initializes `KoppajsRouter` with the route table and outlet.
-7. The router renders the matching route component into `#app-outlet`,
-   synchronizes active links, and updates the current browser URL.
-
-## Quality automation layer
-
-- `eslint.config.mjs` lint-checks TypeScript source plus tooling files.
-- `prettier.config.mjs` and `.editorconfig` keep supported text files consistent.
-- `.npmrc` enforces the declared engine floor during installs.
-- `.husky/pre-commit` runs `lint-staged`.
-- `.husky/commit-msg` validates commit headers with `commitlint`.
-- `.github/workflows/ci.yml` runs the full repository validation flow on GitHub.
-- `.github/workflows/release.yml` runs tagged release validation and creates GitHub Releases.
-
-## Module responsibilities
-
-| Module                      | Responsibility                                                   | Must not do                                            |
-| --------------------------- | ---------------------------------------------------------------- | ------------------------------------------------------ |
-| `index.html`                | Declare the root tag and static assets                           | Hold feature logic or router setup                     |
-| `src/main.ts`               | Bootstrap the app, register components, and start one router     | Accumulate page copy or unrelated UI state             |
-| `src/app-view.kpa`          | Render the shared shell, nav, and router outlet                  | Own route resolution or register components            |
-| `src/home-page.kpa`         | Render the landing route and compose the counter example         | Reach into router internals or mutate global DOM state |
-| `src/router-page.kpa`       | Render the second route and explain the router baseline          | Own bootstrap logic or global navigation state         |
-| `src/not-found-page.kpa`    | Render the explicit fallback route                               | Replace route matching or bootstrap responsibilities   |
-| `src/counter-component.kpa` | Demonstrate local interactive state                              | Reach into route orchestration or app-shell concerns   |
-| `src/style.css`             | Hold global tokens and truly global base styles                  | Duplicate component-local visuals                      |
-| `tests/integration/`        | Verify bootstrap and router-start boundaries                     | Duplicate full browser smoke expectations              |
-| `tests/e2e/`                | Verify visible navigation and counter behavior in a real browser | Assert brittle implementation details                  |
-
-## Invariants
-
-- There is exactly one bootstrap entrypoint.
-- The root tag in `index.html` must match a component registered in `src/main.ts`.
-- `Core()` is called once from `src/main.ts`.
-- The starter owns exactly one router instance.
-- The route table contains an explicit `*` fallback route.
-- Route rendering happens through `#app-outlet`.
-- Official releases require matching versions across `package.json`,
-  `CHANGELOG.md`, and `vX.Y.Z` tags.
-
-## Extension guidance
-
-- Add new route components under `src/` and register them from `src/main.ts`.
-- Keep route definitions in one obvious place.
-- Extract reusable route helpers into `.ts` modules only when logic becomes
-  shared or branch-heavy.
-- Add a spec before changing visible navigation behavior.
-- Add an ADR before changing the routing model, adding data fetching,
-  persistence, or another major subsystem.

package/template-overlays/router/CHANGELOG.md

@@ -1,50 +0,0 @@
-# Change Log
-
-All notable changes to **__PROJECT_NAME__** are documented in this file.
-
-This project uses a **manual, tag-driven release process**.
-Only tagged versions represent official releases.
-
-This changelog documents **intentional milestones and guarantees**,
-not every internal refactor.
-
----
-
-## [Unreleased]
-
-### Changed
-
-- raised the minimum Node.js version to `>=22` and expanded CI coverage to
-  Node 24
-- refreshed the router starter dependency baseline to the current
-  `@koppajs/koppajs-core`, `@koppajs/koppajs-vite-plugin`, and
-  `@koppajs/koppajs-router` releases
-
----
-
-## [1.0.0] — Initial Starter Baseline
-
-**2026-03-17**
-
-### Added
-
-- a small KoppaJS router app shell with `app-view`, `home-page`,
-  `router-page`, `not-found-page`, and `counter-component`
-- route-based rendering through `@koppajs/koppajs-router`
-- ESLint, Prettier, Vitest, Playwright, Husky, lint-staged, and commitlint
-- starter governance docs, ADRs, specs, and release workflow files
-
----
-
-## Versioning Policy
-
-- Semantic Versioning (SemVer) is followed pragmatically
-- **Breaking changes** include:
-  - public runtime behavior changes
-  - route structure changes
-  - release workflow changes
-
----
-
-_This changelog documents intent.
-If something is not written here, it is not guaranteed._

package/template-overlays/router/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, route definitions, and initialization of the single router instance.
-- Use `.kpa` files for UI composition, local component state, and component-scoped CSS.
-- Keep the route outlet inside `app-view.kpa` and keep route rendering consumer-owned.
-- If logic becomes reusable, asynchronous, or branch-heavy, move it into `.ts` modules under `src/`.
-- Keep `public/` for static assets only.
-
-## 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.
-- Route component filenames should match their registered component tags or route purpose.
-- 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.
-
-## Coding patterns
-
-- Favor simple, local state over premature abstraction.
-- Keep route definitions obvious and close to router initialization.
-- 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 so smoke tests can target public semantics instead of brittle selectors.
-
-## Forbidden without a spec and ADR
-
-- Replacing the starter's single-router model with a second navigation system
-- 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 feature-rich 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-overlays/router/ROADMAP.md

@@ -1,34 +0,0 @@
-# Roadmap
-
-This roadmap describes intended directions, not guaranteed delivery dates.
-
-## Current priorities
-
-- Keep the router starter focused 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 route-level examples only when they demonstrate a real starter need.
-- Strengthen route-related tests if the starter gains redirects, params, or nested routes.
-- Keep documentation aligned with the actual router wiring.
-
-## Longer-term expansion triggers
-
-These should happen only with a spec and ADR:
-
-- async data fetching
-- persistence
-- richer route hierarchies
-- shared state beyond local component state
-- CI automation changes
-
-## 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-overlays/router/TESTING_STRATEGY.md

@@ -1,67 +0,0 @@
-# Testing Strategy
-
-## Current state
-
-This repository carries a small automated testing stack aligned with the router starter's actual 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
-
-## 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.
-- 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.
-
-### Integration or component tests
-
-Use integration tests when bootstrap, component registration, and router startup
-must be verified together but a full browser run would be disproportionate.
-
-Typical triggers:
-
-- bootstrap registration in `src/main.ts`
-- router startup wiring and route table shape
-- build-time behavior that depends on the Vite plugin
-
-### End-to-end tests
-
-Keep Playwright intentionally user-facing and smoke-level.
-
-Typical triggers:
-
-- root UI rendering
-- route navigation between starter pages
-- critical starter interactions such as the counter behavior
-- preview/build regressions that would not be caught by Vitest alone
-
-## Coverage expectations
-
-- There is no blanket repository percentage target right now.
-- New non-trivial logic should come with focused tests.
-- When a subsystem introduces more branching logic, async behavior, or shared state, test automation stops being optional.
-
-## 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`.
-
-## 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-overlays/router/docs/adr/0001-keep-the-starter-minimal.md

@@ -1,32 +0,0 @@
-# ADR 0001: Keep the router starter focused
-
-## Context
-
-This repository starts from the maintained KoppaJS router starter baseline.
-Its audience needs a runnable reference that demonstrates routing without
-turning into a broad showcase application.
-
-## Decision
-
-The router starter remains intentionally small:
-
-- one HTML shell,
-- one TypeScript bootstrap file,
-- one root KoppaJS view,
-- one router instance,
-- two primary routes plus one explicit fallback route,
-- one stateful child component,
-- published npm packages instead of local monorepo `file:` dependencies.
-
-Any expansion beyond that baseline requires a spec and ADR.
-
-## Consequences
-
-- New users get a fast example of routing without a lot of incidental complexity.
-- The repository stays easy to audit and maintain.
-- More advanced route features must be introduced deliberately rather than accumulating ad hoc.
-
-## Alternatives considered
-
-- A feature-rich demo app that showcases many KoppaJS patterns at once
-- A monorepo-linked starter that depends on local sibling packages

package/template-overlays/router/docs/architecture/module-boundaries.md

@@ -1,39 +0,0 @@
-# Module Boundaries
-
-## Repository boundary model
-
-This repository is intentionally shallow. Its boundaries keep the starter easy to inspect.
-
-| Path                        | Responsibility                                                    | Allowed dependencies                                                     | Must not depend on                                  |
-| --------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------ | --------------------------------------------------- |
-| `index.html`                | Document shell, root element, asset references                    | Static assets, `src/main.ts`, `src/style.css`                            | Feature logic, router setup, extra scripts          |
-| `src/main.ts`               | Application bootstrap, component registration, and router startup | `@koppajs/koppajs-core`, `@koppajs/koppajs-router`, local `.kpa` modules | Page copy, route component visuals, unrelated state |
-| `src/app-view.kpa`          | Shared shell, primary navigation, and route outlet                | Local markup, local CSS                                                  | Route matching, component registration              |
-| `src/home-page.kpa`         | Landing-route content and counter composition                     | Local markup, local CSS, `counter-component`                             | Router setup or global shell orchestration          |
-| `src/router-page.kpa`       | Second-route content                                              | Local markup and local CSS                                               | Bootstrap or route resolution concerns              |
-| `src/not-found-page.kpa`    | Explicit fallback-route content                                   | Local markup and local CSS                                               | Route matching rules or global state                |
-| `src/counter-component.kpa` | Example local state and interaction                               | Local markup, local methods, local CSS                                   | Route orchestration or app-shell concerns           |
-| `src/style.css`             | Global tokens and truly global base rules                         | Standard CSS                                                             | Route-specific or component-specific visual rules   |
-| `tests/integration/`        | Bootstrap and router boundary verification                        | Vitest, local modules, selective mocks                                   | Browser-only smoke assertions                       |
-| `tests/e2e/`                | Real-browser smoke coverage                                       | Playwright, preview server                                               | Implementation-detail assertions                    |
-| `vite.config.mjs`           | Build and dev server integration                                  | Vite and the KoppaJS Vite plugin                                         | Application runtime logic                           |
-
-## Boundary rules
-
-- Registration and route configuration happen in `src/main.ts`.
-- `app-view.kpa` may compose navigation and the outlet but must not become a second router.
-- Route components own their own copy and layout.
-- Shared logic belongs in dedicated `.ts` modules once reuse or complexity justifies it.
-- Vitest owns helper-level and bootstrap-level confidence; Playwright owns browser smoke confidence.
-
-## Escalation rules
-
-Before crossing existing boundaries, add a spec and ADR if the change introduces:
-
-- nested or parameterized routing beyond the current baseline,
-- shared state,
-- async workflows,
-- persistence,
-- more than one root entrypoint,
-- npm publishing or deployment automation,
-- new top-level source folders.

package/template-overlays/router/docs/meta/maintenance.md

@@ -1,38 +0,0 @@
-# Meta-Layer Maintenance
-
-The meta layer is a living system. Any change that alters the real system must update the corresponding governance document in the same change.
-
-## Update matrix
-
-| Change                                     | Required updates                                                                               |
-| ------------------------------------------ | ---------------------------------------------------------------------------------------------- |
-| New feature or behavior                    | Add or update a spec in `docs/specs/`; update `README.md` if setup or visible behavior changes |
-| New enduring technical decision            | Add or update an ADR in `docs/adr/`                                                            |
-| New module, folder, or data flow           | Update `ARCHITECTURE.md` and `docs/architecture/module-boundaries.md`                          |
-| New coding pattern or dependency rule      | Update `DEVELOPMENT_RULES.md`                                                                  |
-| New test tooling or quality gate           | Update `TESTING_STRATEGY.md` and `docs/quality/quality-gates.md`                               |
-| New hook, CI step, or contributor workflow | Update `CONTRIBUTING.md` and `.github/instructions/ai-workflow.md`                             |
-| Version, changelog, or release workflow    | Update `CHANGELOG.md`, `RELEASE.md`, `package.json`, and affected GitHub workflow files        |
-
-## Review triggers
-
-Perform a meta-layer review when:
-
-- a pull request changes the repo structure,
-- a new dependency is added,
-- a public component tag changes,
-- a build or test command changes,
-- a hook or CI workflow changes,
-- the routing model or route surface changes,
-- a README section no longer matches the actual code.
-
-## Periodic review checklist
-
-- Does [ARCHITECTURE.md](../../ARCHITECTURE.md) still match the runtime flow?
-- Do current specs cover the user-visible behaviors in the repo?
-- Do ADRs still represent active decisions?
-- Do contributor instructions still match the actual toolchain?
-- Did a recent change deserve a new quality gate?
-- Do `CHANGELOG.md`, `RELEASE.md`, and the release workflow still match actual branch and tag practice?
-
-If any answer is "no", update the meta layer before considering the repository aligned.

package/template-overlays/router/docs/specs/README.md

@@ -1,19 +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.
-
-## Current specs
-
-- [`app-bootstrap.md`](./app-bootstrap.md)
-- [`counter-component.md`](./counter-component.md)
-- [`router-navigation.md`](./router-navigation.md)
-- [`quality-workflow.md`](./quality-workflow.md)

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

@@ -1,42 +0,0 @@
-# Spec: App bootstrap
-
-## Status
-
-Approved
-
-## Purpose
-
-Provide a predictable startup path for a KoppaJS application that includes the official router runtime.
-
-## 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`, `home-page`, `router-page`, `not-found-page`, and `counter-component` with KoppaJS Core.
-- `src/main.ts` invokes `Core()` once and starts one `KoppajsRouter` instance.
-
-## Inputs
-
-- Browser loading `index.html`
-- Static asset and source file paths resolved by Vite
-
-## Outputs
-
-- A rendered `<app-view>` application shell
-- A rendered route component inside `#app-outlet`
-- A registered `<counter-component>` available to the home route
-
-## 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`.
-- `Core()` must remain the only KoppaJS bootstrap call.
-- Router initialization must happen after the route outlet exists.
-- No extra runtime dependencies are required beyond the declared npm packages.
-
-## 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 route outlet is initialized by the router and can render the home route immediately after bootstrap.

package/template-overlays/router/docs/specs/router-navigation.md

@@ -1,41 +0,0 @@
-# Spec: Router navigation
-
-## Status
-
-Approved
-
-## Purpose
-
-Define the starter's router baseline so the generated project demonstrates a small but real navigation flow.
-
-## Behavior
-
-- The starter initializes one `KoppajsRouter` instance from `src/main.ts`.
-- The router renders matched route components into `#app-outlet`.
-- Primary navigation links use `data-route` and participate in active-link state updates.
-- The starter includes a home route, a second content route, and an explicit `*` fallback route.
-
-## Inputs
-
-- Route definitions declared in `src/main.ts`
-- Browser URL and History API state
-- User clicks on matching `data-route` links
-
-## Outputs
-
-- URL changes that stay aligned with the rendered route component
-- Active navigation state on the current route link
-- A predictable not-found page for unmatched paths
-
-## Constraints
-
-- The route table must stay small and inspectable.
-- The fallback route must be explicit rather than implicit.
-- Route content stays in consumer-owned `.kpa` files, not inside the router package.
-
-## Acceptance criteria
-
-- Visiting `/` renders the home route.
-- Visiting `/router` renders the second route.
-- Visiting an unmatched path renders the fallback route.
-- The active navigation link exposes `aria-current="page"` for the current route.