loopy-loop 0.2.0__py3-none-any.whl

loopy_loop-0.2.0.dist-info/METADATA

@@ -0,0 +1,408 @@
+Metadata-Version: 2.4
+Name: loopy-loop
+Version: 0.2.0
+Summary: A repo-local automation loop for AI agents built on team-harness.
+Project-URL: Homepage, https://github.com/writeitai/loopy-loop
+Project-URL: Repository, https://github.com/writeitai/loopy-loop
+Project-URL: Issues, https://github.com/writeitai/loopy-loop/issues
+Project-URL: Changelog, https://github.com/writeitai/loopy-loop/releases
+Author-email: "WriteIt.ai s.r.o." <info@writeit.ai>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agents,ai,automation,fastapi,loop,team-harness,workflow
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Software Development
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: >=3.12
+Requires-Dist: click>=8.1
+Requires-Dist: fastapi>=0.115.0
+Requires-Dist: filelock>=3.16
+Requires-Dist: httpx>=0.28
+Requires-Dist: pydantic>=2.11
+Requires-Dist: pyyaml>=6.0.2
+Requires-Dist: rich>=14.0
+Requires-Dist: team-harness>=0.2.10
+Requires-Dist: uvicorn[standard]>=0.32.0
+Provides-Extra: dev
+Requires-Dist: pyright>=1.1; extra == 'dev'
+Requires-Dist: pytest-asyncio>=0.25; extra == 'dev'
+Requires-Dist: pytest>=8.3; extra == 'dev'
+Requires-Dist: ruff>=0.4; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# loopy-loop
+
+`loopy-loop` is a repo-local automation loop for AI agents.
+
+- A FastAPI coordinator owns session-local loop state in
+  `.loopy_loop/sessions/<session_id>/state.json`.
+- One or more blocking workers poll the coordinator over HTTP.
+- Each assignment loads workflow files from the active workflow set, runs
+  `team_harness.TeamHarness`, writes iteration artifacts under
+  `.loopy_loop/sessions/<session_id>/iterations/`, and reports completion back
+  to the coordinator.
+
+## Install
+
+```bash
+uv sync --extra dev
+```
+
+Or:
+
+```bash
+uv pip install .
+```
+
+## Skills
+
+This repo ships an [Agent Skill](https://support.claude.com/en/articles/12512176-what-are-skills)
+that teaches Claude Code, Codex, and other compatible agents how to set up and
+run loopy-loop in a target repo. Install it with:
+
+```bash
+npx skills add https://github.com/writeitai/loopy-loop --skill loopy-loop
+```
+
+The skill source lives under [`skills/loopy-loop/`](./skills/loopy-loop/SKILL.md).
+
+## Repo Layout
+
+```text
+target repo/
+├── loopy_loop_config.yaml
+└── .loopy_loop/
+    ├── workflow_sets/<workflow_set>/workflows/<workflow_id>/{prompt.txt,config.yaml}
+    └── sessions/<session_id>/
+        ├── goal.md
+        ├── state.json
+        ├── child_requests/
+        ├── children/
+        └── iterations/
+```
+
+## Quick Start
+
+```bash
+loopy init
+loopy init --template inner_outer_eval
+loopy init --template pm_planner_dispatcher
+loopy coordinator --host 127.0.0.1 --port 8080
+loopy worker --coordinator http://127.0.0.1:8080
+loopy status
+loopy stop
+```
+
+`loopy init` is idempotent. It creates:
+
+- `loopy_loop_config.yaml`
+- `.loopy_loop/workflow_sets/main/workflows/goal_check/prompt.txt`
+- `.loopy_loop/workflow_sets/main/workflows/goal_check/config.yaml`
+- `.gitignore` entry for `.loopy_loop/sessions/`
+
+Use `loopy init --template inner_outer_eval` to scaffold the packaged workflow
+set for outer planning, inner implementation, eval review, and eval running.
+Use `loopy init --template pm_planner_dispatcher` to scaffold the packaged PM
+workflow set for planner/dispatcher orchestration that starts child sessions.
+
+## CLI Reference
+
+`loopy init [--template default|inner_outer_eval|pm_planner_dispatcher]`
+
+- Scaffolds the root config and reserved `goal_check` workflow.
+- `--template inner_outer_eval` scaffolds the packaged inner/outer/eval workflow
+  set instead: `outer`, `inner`, `eval_reviewer`, and `eval_runner`.
+- `--template pm_planner_dispatcher` scaffolds the packaged PM orchestration
+  workflow set: `planner` and `dispatcher`.
+- Does not overwrite existing workflow files.
+
+`loopy coordinator --host 0.0.0.0 --port 8080 [--resume] [--workflow-set NAME] [--goal-file PATH]`
+
+- Runs the FastAPI coordinator with exactly two endpoints: `/register` and `/finished`.
+- On a fresh start, creates a new session directory with `goal.md` and
+  session-local `state.json`.
+- If the latest session `state.json` is terminal, archives it next to that
+  session state file and starts fresh.
+- If the latest session `state.json` is already `running`, startup fails unless
+  `--resume` is passed.
+- `--workflow-set` overrides `workflow_set` for the new session.
+- `--goal-file` overrides the configured goal file for the new session.
+
+`loopy worker --coordinator http://127.0.0.1:8080`
+
+- Calls `/register` once to receive the first task.
+- Loops calling `/finished` after each completed task until it receives a `stop` response.
+- Loads `loopy_loop_config.yaml`,
+  `.loopy_loop/workflow_sets/<workflow_set>/workflows/<workflow_id>/config.yaml`,
+  and the matching `prompt.txt` from disk on each task.
+- Uses the coordinator `config_snapshot` as the execution snapshot for the session.
+
+`loopy status`
+
+- Prints current session id, iteration count, current task, and stop reason.
+
+`loopy stop`
+
+- Sets `stop_requested=true` in the latest session-local `state.json`.
+
+## Config Reference
+
+Root config (`loopy_loop_config.yaml` at the repo root):
+
+```yaml
+goal_file: "loopy_loop_goal.txt"
+workflow_set: "main"
+max_turns: 20
+goal_check_consecutive_failures_cap: 3
+team_harness_provider: "codex"
+team_harness_model: "gpt-5.5"
+team_harness_agents:
+  - "codex"
+  - "claude"
+  - "gemini"
+team_harness_agent_models:
+  codex: "gpt-5.5"
+  claude: "claude-opus-4-8"
+  gemini: "gemini-3.5-flash"
+team_harness_agent_reasoning_efforts: {}
+# Optional coordinator retry controls. Omit to use team-harness defaults.
+# team_harness_max_retries: 8
+# team_harness_retry_base_delay_s: 2.0
+# team_harness_retry_max_delay_s: 60.0
+team_harness_api_base: "https://openrouter.ai/api/v1"
+team_harness_api_key_env: "OPENROUTER_API_KEY"
+```
+
+Rules:
+
+- Session ids start with a UTC timestamp for filesystem sorting and include a
+  deterministic `goal_hash` derived from the text loaded from `goal_file`
+- `workflow_set` names the workflow set used when `loopy coordinator`
+  is started without `--workflow-set`
+- `goal_file` is resolved relative to `loopy_loop_config.yaml`; inline `goal`
+  values in YAML are rejected
+- `completion_criteria`, `stop_criteria`, and
+  `team_harness_system_prompt_extension` are optional; omitted criteria default
+  to empty lists and the prompt extension defaults to an empty string
+- `team_harness_model` controls the team-harness coordinator model; worker
+  subprocess defaults are controlled by `team_harness_agent_models`
+- `team_harness_api_base` is normalized by loopy-loop: trailing slash stripped, `/v1` appended when missing
+- `team_harness_api_key_env` must be set during coordinator preflight and again in the worker before `TeamHarness(...)`
+- `team_harness_agent_reasoning_efforts` is optional and only affects workers
+  whose team-harness template supports a reasoning-effort flag
+- `team_harness_max_retries`, `team_harness_retry_base_delay_s`, and
+  `team_harness_retry_max_delay_s` are optional coordinator retry controls for
+  transient team-harness API/network errors
+
+Workflow config:
+
+```yaml
+enabled: true
+priority: 0
+run_every: 1
+must_follow: null
+not_before_iteration: 0
+run_on_start: false
+run_after_successes: null
+emits_goal_check: false
+description: ""
+```
+
+Rules:
+
+- Workflow id is the folder name under
+  `.loopy_loop/workflow_sets/<workflow_set>/workflows/`
+- `must_follow` must resolve during coordinator preflight
+- `run_every` is based on completed iteration count, not wall clock
+- `priority` breaks ties among eligible workflows; higher values run first
+- `run_on_start=true` makes a workflow eligible before any successful workflow has run
+- `run_after_successes` can run a workflow after every N successful runs of another workflow:
+
+```yaml
+run_after_successes:
+  workflow_id: inner
+  every: 10
+```
+
+- `emits_goal_check=true` lets a non-`goal_check` workflow write `goal_check.json`
+  as a required eval artifact. To stop the loop, the workflow must update the
+  session-scoped `control.json`.
+- `goal_check` is reserved and scaffolded with `not_before_iteration: 1`
+
+## Workflow Sets and Child Sessions
+
+Workflow sets are mandatory. Even a single-loop repo uses
+`.loopy_loop/workflow_sets/main/workflows/...`; the old
+`.loopy_loop/workflows/...` layout is not loaded.
+
+A workflow can request one sequential child session by writing a JSON file under
+the active session's `child_requests/` directory:
+
+```json
+{
+  "workflow_set": "pm_planner_dispatcher",
+  "goal": "Implement the selected planner item.",
+  "schema_version": 1
+}
+```
+
+The coordinator creates the child session under the parent session's
+`children/` directory, copies the request goal into the child `goal.md`, runs
+the requested workflow set, and resumes the parent session after the child
+reaches a terminal state. v1 is depth-first and single-child-at-a-time.
+
+The packaged `pm_planner_dispatcher` workflow set uses this contract as a
+generic parent loop:
+
+- `planner` maintains PM state, selects one work item, and reviews terminal
+  child-session evidence.
+- `dispatcher` writes one child request for the selected work item or imports
+  terminal child evidence back into PM state.
+
+Cadence example:
+
+```yaml
+# Run eval_reviewer at the beginning and then after every 10 successful inner runs.
+enabled: true
+priority: 100
+run_on_start: true
+run_after_successes:
+  workflow_id: inner
+  every: 10
+```
+
+## HTTP Contract Summary
+
+Endpoints:
+
+- `POST /register`
+- `POST /finished`
+
+Both endpoints return a `TaskResponse` with `action` of either `"run"` or `"stop"`.
+
+A `run` response carries `workflow_id`, `session_id`, `iteration`, and `config_snapshot`.
+A `stop` response carries `stop_reason`.
+
+Stale `/finished` calls (mismatched `session_id`, `workflow_id`, or
+`iteration`) do not mutate state and return the current running task's response.
+If there is no active task, `/finished` acts like `/register` and dispatches the
+next available task. If a worker exits after writing `result.json` but before
+`/finished` is acknowledged, the next `/register` recovers the completed result
+from the iteration directory instead of marking it `abandoned`.
+
+See [docs/http-contract.md](docs/http-contract.md) for the exact JSON payloads.
+
+## Session Continuity
+
+Every `TeamHarness.run()` call is fresh. Continuity comes from:
+
+- git state in the target repo
+- `.loopy_loop/sessions/<session_id>/...` artifacts
+- the coordinator state in `.loopy_loop/sessions/<session_id>/state.json`
+
+`team-harness` outputs are routed into the active loopy-loop session under
+`.loopy_loop/sessions/<session_id>/harness_outputs/<NNNN>_<workflow_id>/<team_harness_run_id>/`.
+
+Workflow prompts receive session-scoped paths for reusable project state and
+eval definitions:
+
+- `.loopy_loop/sessions/<session_id>/project_state/`
+- `.loopy_loop/sessions/<session_id>/eval_checks/`
+- `.loopy_loop/sessions/<session_id>/goal.md`
+- `.loopy_loop/sessions/<session_id>/updates_from_user.md`
+- `.loopy_loop/sessions/<session_id>/child_requests/`
+- `.loopy_loop/sessions/<session_id>/control.json`
+- `.loopy_loop/sessions/<session_id>/project_state/finished.md`
+- `.loopy_loop/sessions/<session_id>/harness_outputs/`
+
+These directories are workflow-owned. The coordinator only owns
+`.loopy_loop/sessions/<session_id>/state.json` and iteration dispatch state.
+
+Each session's `goal.md` is the source of truth for the target, constraints,
+and completion intent. For top-level sessions it is copied from `goal_file` or
+the `--goal-file` CLI override. Workflow state should not copy or restate that
+goal.
+`project_state/README.md` should explain state ownership: `memory.md` is
+essential durable facts only, `finished.md` is outer-owned accepted completions
+only, `eval_results.md` owns eval detail, and `current_state.md` carries live
+status, the latest eval headline, and the next action.
+
+Write runtime requests for the outer loop into `updates_from_user.md`. The outer
+workflow should treat non-empty content as highest-priority planning input,
+reflect it into `project_state/`, and then clear the file. Verified completed
+work belongs in `project_state/finished.md`; `what_we_have.md` should remain the
+concise current capability summary.
+
+Eval workflows should run session checks with `--output-dir` pointing at
+`.loopy_loop/sessions/<session_id>/eval_results/`. Raw eval-banana reports stay
+there; `project_state/eval_results.md` should summarize and link the latest
+reports instead of copying them. `project_state/current_state.md` should only
+carry the latest eval headline and the next action.
+
+For implementation work that changes repo files, the default delivery path is a
+branch, PR, passing checks, and merge. Multi-repo work should create and merge
+one PR per changed repo when possible. Tasks should opt out only when they are
+session-state-only, eval-only, research-only, planning-only, or the repo has no
+usable remote or auth. `project_state/finished.md` should record delivery
+evidence for each changed repo: repo, branch, PR URL, merge status, merge
+commit, and checks/CI status. If PR creation or merge is blocked, record the
+exact blocker and remaining action in `project_state/current_state.md`.
+
+## Control Files
+
+`control.json` is the session-scoped workflow stop switch:
+
+```json
+{
+  "state": "running",
+  "reason": "session active",
+  "stop_reason": null,
+  "schema_version": 1
+}
+```
+
+Workflows leave it alone while the loop should continue. To stop successfully:
+
+```json
+{
+  "state": "stopped",
+  "reason": "evals passed",
+  "stop_reason": "goal_met",
+  "schema_version": 1
+}
+```
+
+To stop because the loop cannot continue:
+
+```json
+{
+  "state": "stopped",
+  "reason": "specific terminal blocker",
+  "stop_reason": "unresolvable_error",
+  "schema_version": 1
+}
+```
+
+`goal_check.json` is a per-iteration eval artifact for the reserved
+`goal_check` workflow or any workflow with `emits_goal_check=true`:
+
+```text
+.loopy_loop/sessions/<session_id>/iterations/<NNNN>_<workflow_id>/goal_check.json
+```
+
+```json
+{"goal_met": false, "reason": "docs still missing", "schema_version": 1}
+```
+
+If `goal_check.json` is missing or invalid repeatedly, the coordinator stops
+with `stop_reason="goal_check_broken"` after the configured failure cap. A
+valid `goal_check.json` does not stop the loop by itself; stopping is controlled
+by session `control.json`.

loopy_loop-0.2.0.dist-info/RECORD

@@ -0,0 +1,33 @@
+loopy_loop/__init__.py,sha256=Zn1KFblwuFHiDRdRAiRnDBRkbPttWh44jKa5zG2ov0E,22
+loopy_loop/cli.py,sha256=Q1wlAe_S-UFHgBC7wW0RmZP9FDlrIk6zd1MpdESNc08,9720
+loopy_loop/config.py,sha256=zd06Kqs5EAmKHgs-uWmyWOCNuFejtui8jAuG3vKyUqo,17496
+loopy_loop/coordinator_app.py,sha256=ishuUcx-WmdqK7UqDOBR_SUxLZQFml-gYwqkSKgiT20,27929
+loopy_loop/harness_runner.py,sha256=BT7CU4BwaZhKjd592HscHXboC2TEnm3VoTO3Ptnt3Jk,7260
+loopy_loop/models.py,sha256=9Vbd1UMXif1iB9BlOAlocLy_PRhy2EWS6cflRyw_cuU,5564
+loopy_loop/scheduler.py,sha256=UMdQF_hbO6x4FCEUs5GzVC_T7cdw2l7lXY6pVsCqDrY,7387
+loopy_loop/sessions.py,sha256=7jN4by8m_2oou-xcR9uI-r-WWrijb8wUDVx_t8sXkCc,10050
+loopy_loop/state_store.py,sha256=Pd_OyoEfthFP6bgkNOMG3yi2Aob4NKBF1ivSeKuWFZA,4058
+loopy_loop/worker.py,sha256=bYsuMvRris3AJQ-opLYAIsVnJh2WEEE9Y1Qeh8bGsgs,9839
+loopy_loop/templates/inner_outer_eval/.gitignore,sha256=t7txa4UH9t-UQWEhxdTG8u0_utM8Ejl_sUzQOe1H3KI,111
+loopy_loop/templates/inner_outer_eval/loopy_loop_config.yaml,sha256=0NxhxJ8yfcroFmjQklBnem2qO3tcyXX2TwM8N5yDvAQ,2037
+loopy_loop/templates/inner_outer_eval/loopy_loop_goal.txt,sha256=3B5rmIku6BQUQp5algquK4t0fu3j4mru7BOkusezikU,375
+loopy_loop/templates/inner_outer_eval/.loopy_loop/workflow_sets/inner_outer_eval/workflows/eval_reviewer/config.yaml,sha256=w71e4Mzh_ztOXMm-wsRODWZQj9A4zwXafkucRRJZ1R0,245
+loopy_loop/templates/inner_outer_eval/.loopy_loop/workflow_sets/inner_outer_eval/workflows/eval_reviewer/prompt.txt,sha256=QtO0lPQZPlO01UlWbO2QzyHG08RZphKgEl0ZsAuKTj4,4501
+loopy_loop/templates/inner_outer_eval/.loopy_loop/workflow_sets/inner_outer_eval/workflows/eval_runner/config.yaml,sha256=y0rIDYvEnoIy0Gl3Bfv7NXNWGyXDheXAiQNExSkh9sQ,292
+loopy_loop/templates/inner_outer_eval/.loopy_loop/workflow_sets/inner_outer_eval/workflows/eval_runner/prompt.txt,sha256=xNnSh8oaa8K5yq3pchoWE6e17cjp3wDVdCNhi7oKEIw,3457
+loopy_loop/templates/inner_outer_eval/.loopy_loop/workflow_sets/inner_outer_eval/workflows/inner/config.yaml,sha256=wU9y9V-quH3_pkDCpbq5C-pHFGpYtjaGyUk3cUG7MN8,243
+loopy_loop/templates/inner_outer_eval/.loopy_loop/workflow_sets/inner_outer_eval/workflows/inner/prompt.txt,sha256=kvYDIbAz832rRq5kZlsIJTbzaoh-CZQ0dnk6LvRLi1E,13023
+loopy_loop/templates/inner_outer_eval/.loopy_loop/workflow_sets/inner_outer_eval/workflows/outer/config.yaml,sha256=WG1prReflVi6Q3if-szoKJRfsiMkpVyjx-QC812i7UM,212
+loopy_loop/templates/inner_outer_eval/.loopy_loop/workflow_sets/inner_outer_eval/workflows/outer/prompt.txt,sha256=0tSiL__2KUzdbgV2eKLqH4pPgUKK1mJ59m1JPp8BkJU,18110
+loopy_loop/templates/pm_planner_dispatcher/.gitignore,sha256=ftBmOCBk1olSB3eLdL5TZJdLDoc7Umey6SHydU9k1Ko,22
+loopy_loop/templates/pm_planner_dispatcher/loopy_loop_config.yaml,sha256=hKCsAwYavAapY6-0ab2bd3NMg2cVgO7-Tfx_gkBS_TY,844
+loopy_loop/templates/pm_planner_dispatcher/loopy_loop_goal.txt,sha256=HnhC9uYFXmUCES7aqBkXXBceZL9p0YRJlQPzshq6t-E,186
+loopy_loop/templates/pm_planner_dispatcher/.loopy_loop/workflow_sets/pm_planner_dispatcher/workflows/dispatcher/config.yaml,sha256=vt5hO0gfoBgrI08BQgcUM4hQtx2ThOfL4vzsQ2VSTaQ,224
+loopy_loop/templates/pm_planner_dispatcher/.loopy_loop/workflow_sets/pm_planner_dispatcher/workflows/dispatcher/prompt.txt,sha256=b8CVY-apjxv5NyGOXE0Ag8jvc00OTiODlYzlZ7fNYTw,3135
+loopy_loop/templates/pm_planner_dispatcher/.loopy_loop/workflow_sets/pm_planner_dispatcher/workflows/planner/config.yaml,sha256=SvxJuDf9H-PCAfQMnqlXpd7FBvtjtJmVMM3uXUJe2zA,219
+loopy_loop/templates/pm_planner_dispatcher/.loopy_loop/workflow_sets/pm_planner_dispatcher/workflows/planner/prompt.txt,sha256=jK5hH8ghmQTx7tJn-I8qmQD4cqETlww48iJrSQBd1Bs,4359
+loopy_loop-0.2.0.dist-info/METADATA,sha256=wCCyx4uPnOKnlFzdp7uE1ie0petcRfmgQ24WGLfbvLk,14823
+loopy_loop-0.2.0.dist-info/WHEEL,sha256=QccIxa26bgl1E6uMy58deGWi-0aeIkkangHcxk2kWfw,87
+loopy_loop-0.2.0.dist-info/entry_points.txt,sha256=o4ZHqoeNaTFJKxQIFdLgFKK4Dc1yBorRmRWye2YpHas,79
+loopy_loop-0.2.0.dist-info/licenses/LICENSE,sha256=747cK9sKUpjOrQ4jGWMQQk94iO8W4AporrWzC-Fctng,11289
+loopy_loop-0.2.0.dist-info/RECORD,,

loopy_loop-0.2.0.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.29.0
+Root-Is-Purelib: true
+Tag: py3-none-any

loopy_loop-0.2.0.dist-info/entry_points.txt

@@ -0,0 +1,3 @@
+[console_scripts]
+loopy = loopy_loop.cli:main
+loopy-loop = loopy_loop.cli:main

loopy_loop-0.2.0.dist-info/licenses/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 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 Support. 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 support.
+
+   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 WriteIt.ai s.r.o.
+
+   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.