storymapper 0.1.0

package/ARCHITECTURE.md

@@ -0,0 +1,334 @@
+# Storymapper — Architecture
+
+This document is the map for anyone reading or contributing to the code. It
+covers the shape of the system, the deliberate design decisions, the data model,
+and the few non-obvious mechanisms that make the whole thing work. For install
+and usage, see [README.md](README.md).
+
+---
+
+## 1. The three surfaces
+
+One package exposes the same data three ways:
+
+```
+                         ┌───────────────────────────┐
+   Browser  ── HTTP ───▶ │                           │
+     UI     ◀─ WebSocket │       HTTP + WS server    │──▶ SQLite
+                         │        (server/*.js)       │    (revisions,
+   Claude  ── stdio ───▶ │       MCP server          │     snapshots,
+   (agent)   MCP         │        (server/mcp.js)     │     attachments)
+                         └───────────────────────────┘
+                                     │
+                              shared/core.js
+                        (pure domain logic, one copy)
+```
+
+- **HTTP + WebSocket server** (`server/server.js`) — serves the frontend, exposes
+  a REST surface, and pushes live changes to subscribed browsers.
+- **MCP server** (`server/mcp.js`) — ~70 stdio tools wrapping the same operations,
+  so an AI agent edits the same projects.
+- **SQLite storage** (`server/storage.js`) — the single persistence layer both
+  servers write through.
+
+A **process bus** (`server/bus.js`, a plain `EventEmitter`) decouples writes from
+push: storage emits `change`, the WebSocket layer relays it.
+
+## 2. Principles & deliberate non-goals
+
+These are load-bearing constraints, not preferences. Please honour them in PRs.
+
+- **No build step.** No bundler, transpiler or TypeScript. If you find yourself
+  wanting one, stop.
+- **No frontend framework, no ES modules in the browser.** Classical
+  `<script src>` tags loading UMD modules that attach to a `window.STORYMAP`
+  namespace. This keeps the page trivially serveable and debuggable.
+- **No HTTP framework.** Raw `http.createServer` with manual routing. It stays
+  small and dependency-light on purpose (Express, Fastify, etc. are out).
+- **Pure logic lives in exactly one file.** See §4.
+- **Single-user, local-first.** No auth layer yet; the seam exists (§13) but RBAC
+  is a later stage. The server is meant for loopback only.
+- **Constants, not magic numbers.** Layout sizes, limits, timeouts and debounce
+  windows live in a named constants block at the top of each module (e.g.
+  `STORY_MAP_LAYOUT`, `KANBAN_LAYOUT`, `LIMITS`, `RETENTION`). Tests reference the
+  constant, never the literal.
+
+## 3. Directory layout
+
+```
+shared/                 Single source of truth for pure logic.
+  core.js               normalize*, ops, resolveDefinitions, workflow +
+                        governance engines, diff, view-helpers. No I/O, no DOM.
+  core/graph.js         Pure graph algorithms (critical path, impact set, …).
+  ticket-import.js      CSV / JSON import parsing + value mapping.
+  project-io.js         Export / import of a whole project.
+  query*.js             The ticket query language + autocomplete.
+
+server/
+  core.js               Thin re-export of shared/core.js (legacy require path).
+  core/graph.js         Thin re-export of shared/core/graph.js.
+  storage.js            better-sqlite3 wrapper: per-project mutex, atomic
+                        transactional writes, monotonic revision IDs,
+                        count-based retention, attachments on disk.
+  validation.js         Per-op validators; delegates status-transition + limit
+                        rules to shared/core (no duplicated rules).
+  bus.js                Process-wide EventEmitter ('change', 'switch_request', …).
+  identity.js           Actor resolution + the pluggable authorize() choke-point.
+  server.js             HTTP routing + WebSocket layer. Exports startServer().
+  mcp.js                MCP tool definitions (~70) wrapping ops + storage.
+  mcp-native/           Dependency-free MCP layer (replaces the MCP SDK):
+    registry.js         Transport-agnostic tool registry: register/listTools/dispatch.
+    stdio.js            JSON-RPC 2.0 stdio frontend over the registry.
+  index.js              CLI entry: `storymapper server|mcp`. Shutdown handling.
+  ingest.js             PDF/DOCX slice-candidate extraction (import pipeline).
+
+frontend/
+  storymap.html         The shell: structure + CSS link + script tags + bootstrap.
+  css/storymap.css      Paperlike theme.
+  js/
+    core.js             Symlink → ../../shared/core.js (the single source).
+    core/graph.js       Symlink → ../../../shared/core/graph.js.
+    store.js            ProjectStore: local ops, undo/redo, applyRemote, hydrate.
+    adapters.js         Http / LocalStorage / Memory adapters + WS subscribe.
+    renderer-card.js    Shared ticket-card component (used by every view).
+    renderer-storymap.js  SVG/DOM Story Map (process steps × releases × epics).
+    renderer-kanban.js    Kanban board (status/board-column lanes).
+    renderer-ticket-modal.js / ticket-form.js   Ticket editor (modal + full page).
+    renderer-dependencies.js   Typed-link dependency graph view.
+    view-table.js / view-requirements.js / view-process-steps.js / view-settings.js
+    dnd.js              Pointer-event drag-and-drop engine.
+    card-animate.js     FLIP + pulse animations for external (live-sync) commits.
+    main.js             Bootstrap: pick adapter → store → views → menus.
+
+skill/SKILL.md          The agent-facing skill: how Claude should use the board.
+tests/                  Plain-Node test scripts + run.js loader (see §14).
+fixtures/               Seed snapshots for demos/smoke.
+```
+
+## 4. Single source for pure logic (the symlink pattern)
+
+Domain logic must run in three contexts — the browser, the HTTP server and the
+MCP server — without a build step and without hand-mirroring.
+
+- `shared/core.js` is the **only** copy. It is **UMD-wrapped**: `require()`d in
+  Node, and `<script src>`'d in the browser where it attaches to
+  `window.STORYMAP.core`.
+- `frontend/js/core.js` is a **symlink** to `shared/core.js`. The browser loads
+  the real file through it.
+- `server/core.js` is a **3-line re-export shim** (`module.exports =
+  require("../shared/core.js")`), so historical `require("./core.js")` paths keep
+  working.
+
+The same applies to `core/graph.js`, `ticket-import.js`, `project-io.js` and the
+query modules.
+
+> **Edit only `shared/…`.** Never edit `server/core.js` (a shim) or
+> `frontend/js/core.js` (a symlink). There is no mirror step and no parity test —
+> because there is only one file.
+
+## 5. Data model
+
+Everything is stored as **one JSON snapshot per project** (the canonical form),
+plus append-only revision rows and on-disk attachments.
+
+| Table | Purpose |
+| --- | --- |
+| `projects` | `id`, the full `snapshot` JSON, `saved_at`, current `revision`, soft-delete flags. |
+| `revisions` | `(project_id, revision)` PK, the full snapshot at that point, `op`, `actor`. Append-only, count-retained. |
+| `attachments` | Metadata + on-disk relative path (files live next to the DB, never as blobs). |
+
+Inside a snapshot, the domain entities are:
+
+- **Project** — name, ticket prefix + counter, `definitions` (DoR/DoD),
+  `workflow` (statuses/transitions), `boards.kanban.columns`, `ticketTypes`,
+  `entityTypeConfig`, labels.
+- **Ticket** — type (`epic` / `user-story` / `bug` / `task` / …), key, title,
+  description, status, `position` (`{epicId, processStepId, releaseId,
+  sortOrder}`), **frozen** `definitionOfReady` / `definitionOfDone`,
+  `acceptanceCriteria`, comments, labels, typed `links`.
+- **Release** — a shippable product version that bundles many features.
+- **ProcessStep** — a phase of the user journey; the columns of the story map.
+
+Every entity carries **audit** columns: `createdAt/By`, `updatedAt/By` (actor is
+`{type, id, name, sessionId?}`), and a monotonic `version` for optimistic locking.
+
+## 6. Definition of Ready / Definition of Done (first-class)
+
+Each project owns a `definitions` object with a `ready` and a `done` block. Each
+block has `global` items plus per-ticket-type `appended` or `overridden` items.
+The pure function `resolveDefinitions(definitions, ticketType)` produces the
+effective list for a type.
+
+- **Freeze on create.** When a ticket is created, the resolved checklist is
+  copied onto the ticket. Later project-level changes do **not** retroactively
+  alter open tickets.
+- **Gated transitions.** The workflow marks which transitions require a gate.
+  Moving into a `requireGate: "DoR"` status while a required DoR item is unchecked
+  throws `{ statusCode: 422, missing: [...] }`; likewise DoD on the way to `done`.
+- The MCP layer translates that 422 into a structured tool error, so the agent
+  gets a machine-readable list of what's still missing. **A conforming agent
+  never forces `done` — it checks the items off first.**
+
+## 7. The workflow engine
+
+`project.workflow` is fully configurable (Jira-style):
+
+- **Statuses** are objects `{id, name, category}` with `category ∈
+  todo | doing | blocked | done`.
+- **Transitions** are a named list: `{id, name, fromStatuses[], toStatus,
+  requireGate, allowFromAny}`. A transition matches when `toStatus` fits and
+  either `allowFromAny` is set or `fromStatuses` includes the current status.
+  Specific transitions win over generic ones.
+- `validateStatusTransition` (pure, in `shared/core.js`) is the single gate
+  checkpoint; the REST route, the store, and every MCP status tool go through it.
+  No matching transition → `422 { kind: "TRANSITION" }`.
+- Per-type overrides merge over the base workflow via `getWorkflowForType`.
+
+Legacy string-array workflows migrate automatically on load.
+
+## 8. Derived epic status (roll-up)
+
+An **epic has no manual status**. `deriveEpicStatus(snapshot, epicId)` rolls it up
+from its contained stories (resolved via `contains` links) over the status
+categories: no children → first `todo`; all children `done` → first `done`; any
+child in progress → first `doing`; else `todo`. `recomputeEpicStatuses` runs at
+the end of every mutating op that can change a child's status or containment, and
+as the last pass of `normalizeSnapshot` (which doubles as the migration for
+legacy data). It sets only `ticket.status` — never bumps `version` (it is a
+derivation, not an actor action). Every manual status path rejects epics with
+`{ statusCode: 422, kind: "EPIC_STATUS_DERIVED" }`.
+
+## 9. Kanban board mapping
+
+`project.boards.kanban.columns` is a list of `{id, name, statusIds[]}`. The board
+maps **N statuses → 1 column** (like Jira). The default is 1:1 with the workflow.
+`computeKanbanLayout` builds lanes from the columns; a status that maps to no
+column surfaces in a synthetic trailing lane so tickets are never invisible.
+Dropping a card into a column that already contains its status is a pure reorder;
+otherwise the card's status changes to the column's first status.
+
+## 10. Live sync
+
+The path from a write to a browser repaint:
+
+1. A write lands in `storage._writeLocked`, which — after the transaction commits
+   — calls `bus.emit("change", { projectId, revision, savedAt, op, actor,
+   originId })`.
+2. The WebSocket layer subscribes to `change` and **broadcasts** to every client
+   subscribed to that `projectId`.
+3. An **origin-id echo filter** suppresses the echo back to the client that
+   caused the change (each mutating client registers an `originId`; the browser
+   already applied its own change optimistically via the store).
+4. The browser's `ProjectStore.applyRemote(snapshot)` commits the incoming state
+   as a regular undo entry (a no-op if structurally identical), and the renderer
+   plays a **FLIP + pulse** animation (`card-animate.js`) so external changes are
+   visually obvious.
+
+**Cross-process** live sync (the MCP server writing while the HTTP server serves
+the browser): the two processes share the SQLite file but have separate buses.
+The MCP process forwards its `change` events to the HTTP server via
+`POST /api/internal/notify-change`, which re-emits them on the HTTP server's bus —
+from there the normal broadcast + echo-filter path runs unchanged. A browser sees
+an MCP write within ~50 ms, exactly as if another browser had made it.
+
+The same bridge also powers `request_switch_project`: an agent can ask the human's
+browser to switch to a project it just created, resolved through a WebSocket
+prompt and a long-poll.
+
+## 11. Storage internals
+
+- **Atomic writes.** Each save is one `better-sqlite3` transaction: upsert the
+  project row + insert the revision row + (periodically) prune. A mid-write throw
+  rolls the whole thing back; `bus.emit` fires only after commit.
+- **Per-project mutex.** An in-memory keyed promise chain serialises writes to a
+  project within the process, closing the lost-update window of a separate
+  load→save pair (`storage.mutate` does load-modify-write under one acquisition).
+- **Monotonic revision IDs.** `YYYYMMDD-HHmmss-mmm[-NNNN]` (UTC), minted by a
+  high-water-mark counter so IDs are strictly increasing and string-sortable.
+  Across two processes sharing a data dir, a same-millisecond collision on the
+  revisions PK is caught and the id re-minted (bounded retry); `busy_timeout`
+  makes the second writer wait rather than fail.
+- **Bounded retention.** Retention is purely count-based (newest N per project,
+  default 150), pruned inside the write transaction every Nth save. (An unbounded
+  history once grew a DB to ~1.8 GB — hence a hard cap, not an age window.)
+- **Attachments** live on disk next to the DB with size caps and path-containment
+  checks; the DB stores only metadata + a relative path.
+
+## 12. HTTP + WebSocket layer
+
+- Raw routing in `server/server.js#buildRouter`; handlers delegate to
+  `core.ops` + `validation` + `storage` and never contain domain logic.
+- A central JSON body reader enforces size caps, rejects invalid JSON, and strips
+  `__proto__` / `constructor` / `prototype` (prototype-pollution guard).
+- Static file serving resolves within `FRONTEND_DIR`, rejects `..`, and
+  re-checks `realpath` against the root (symlink-escape guard).
+- The WebSocket layer runs a **ping/pong heartbeat** that terminates
+  unresponsive clients so dead subscriptions don't leak.
+- Everything is loopback-gated (see the security model in the README).
+
+## 13. MCP layer
+
+- **Dependency-free.** The MCP server is served over stdio by
+  `server/mcp-native/` — a transport-agnostic tool registry (`registry.js`:
+  register / listTools / dispatch) plus a JSON-RPC 2.0 stdio frontend
+  (`stdio.js`) — with **no external dependency**. It replaced
+  `@modelcontextprotocol/sdk`, which pulled an entire Express 5 + Hono transport
+  tree that was never executed (MCP is stdio-only; the HTTP layer is raw `http`).
+  Zod v4 emits the `tools/list` JSON Schemas natively (`z.toJSONSchema`), so no
+  schema-converter dependency is needed. `tools/call` failures (unknown tool,
+  invalid args, a throwing handler) come back as `isError` tool results, not
+  JSON-RPC errors — matching prior behaviour.
+- ~70 tools, each defined with a Zod input schema and delegating to the shared
+  ops. Responses are **compact by default** (the changed entity + `revision` +
+  `savedAt`, not the whole snapshot).
+- A shared `persist()` helper wraps load-mutate-write and translates thrown
+  `{statusCode, kind, missing}` into a uniform structured tool error, so agents
+  get machine-readable failures (e.g. a DoD gate).
+- `tolerateJsonString` preprocesses nested arguments (position, patch, workflow,
+  board columns) that some MCP bridges serialise as JSON strings, so object and
+  string inputs both validate.
+- `server/identity.js` is the authorization seam: `resolveActor` /
+  `resolveAiActor` never mint an "unknown" actor on a write path, and a single
+  `authorize(actor, op, entity)` choke-point (no-op allow-all today) is where RBAC
+  will plug in.
+
+## 14. Frontend architecture
+
+- **Store-centric.** `ProjectStore` (`store.js`) is the source of truth in the
+  browser. All mutations run locally through `core.ops` and commit via
+  `_commit(next, reason)`; a debounced subscriber persists the whole snapshot via
+  `PUT /api/projects/:id`. This gives real **undo/redo** (Cmd-Z / Cmd-Shift-Z)
+  even over HTTP. `applyRemote` folds WebSocket pushes in as ordinary undo
+  entries. The accepted trade-off is last-write-wins at the browser level.
+- **Adapters** (`adapters.js`) abstract the backend: `HttpAdapter` (REST + WS
+  subscribe), `LocalStorageAdapter`, `MemoryAdapter`, chosen by `pickAdapter`.
+- **Shared card component** (`renderer-card.js`) renders the identical ticket card
+  in every view (DRY).
+- **Views** each mount/unmount against the store and re-render on commit: Story
+  Map, Kanban, Table, Dependencies, Requirements, Settings.
+- **Drag and drop** is a custom pointer-event engine (`dnd.js`) — HTML5 DnD was
+  unreliable across browsers — with live insertion-index previews.
+
+## 15. Testing
+
+- **Plain Node scripts.** `tests/test-*.js` with a tiny `test(name, fn)` helper;
+  `tests/run.js` loads them sequentially. No mocha/jest/vitest. `jsdom` in tests
+  only. Run with `npm test` (≈1800 assertions); CI runs it on Node 20 and 22.
+- **Layered coverage:** pure ops + normalize + workflow/governance;
+  storage atomicity/mutex/revisions; validation gates; REST + WebSocket
+  live-sync; MCP tools both in-process (`reg.handler`) **and** via a stdio
+  JSON-RPC subprocess; JSDOM renderer tests; and a **real-server end-to-end test**
+  (`tests/test-e2e.js`) that drives bootstrap → click → server round-trip → DOM
+  state, because only the composed test proves the pieces fit.
+- **Data safety:** tests only ever use `os.tmpdir()` — the suite never touches a
+  user data directory. This is a hard rule for any new test or script.
+
+New behaviour is written test-first; a bug gets a regression test before the fix;
+pure-logic changes go in `shared/core.js` and are covered there.
+
+## 16. Security model
+
+Summarised in the README. In short: loopback-only, CORS/CSP/WS-origin locked to
+local origins, prototype-pollution and path-traversal guards, body-size caps, and
+an authorization seam ready for a future auth stage. Do not expose the server
+beyond `127.0.0.1` without adding your own authentication in front.

package/LICENSE

@@ -0,0 +1,201 @@
+                                 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 Thomas Schwenger
+
+   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/NOTICE

@@ -0,0 +1,6 @@
+Storymapper
+Copyright 2026 Thomas Schwenger
+
+This product includes software developed by Thomas Schwenger.
+
+Licensed under the Apache License, Version 2.0. See the LICENSE file.