cv-renderer 0.1.0__tar.gz

cv_renderer-0.1.0/.env.example

@@ -0,0 +1,10 @@
+# Path to your CV data directory.
+# Default: user-data/ inside the repo (created by `uv run python render.py init`)
+# Override if your data lives outside the repo:
+# CV_DATA_DIR=/absolute/path/to/your/cv-data
+CV_DATA_DIR=
+
+# Path to write rendered HTML/PDF output.
+# Default: out/ inside the repo
+# CV_OUT_DIR=/absolute/path/to/your/output
+CV_OUT_DIR=

cv_renderer-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,39 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  quality:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+
+      - name: Install dependencies
+        run: uv sync --locked --dev
+
+      - name: Install Playwright Chromium
+        run: uv run playwright install --with-deps chromium
+
+      - name: Lint (ruff check)
+        run: uv run ruff check .
+
+      - name: Format check (ruff format)
+        run: uv run ruff format --check .
+
+      - name: Type check (mypy)
+        run: uv run mypy src/cv_renderer/
+
+      - name: Tests (pytest)
+        run: uv run pytest

cv_renderer-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,43 @@
+# Publish to PyPI on every GitHub Release (tag like v0.1.0).
+#
+# Uses PyPI Trusted Publishing (OIDC) — no API token stored in GitHub.
+# One-time setup on pypi.org: Account → Publishing → add a "pending publisher"
+# for project `cv-renderer`, repo `melisklc0/cv-renderer`, workflow `publish.yml`,
+# environment `pypi`.
+name: Publish
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+
+      - name: Build sdist + wheel
+        run: uv build
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write  # trusted publishing
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

cv_renderer-0.1.0/.gitignore

@@ -0,0 +1,226 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+
+# Rendered CV files
+out/
+
+# Personal CV data — tracked in a separate local git repo (user-data/.git)
+user-data/
+
+templates/images/*.png

cv_renderer-0.1.0/.python-version

@@ -0,0 +1 @@
+3.13

cv_renderer-0.1.0/AGENTS.md

@@ -0,0 +1,56 @@
+# AGENTS.md
+
+You are working on cv-renderer: a profile-driven CV renderer that produces tailored HTML and PDF exports from a single YAML data source.
+
+## How to Work
+
+- Read `user-data/data/base_en.yaml` before touching any CV content or generating profiles — the live data is the source of truth for tags, bullets, and skill categories.
+- Before writing or editing bullets, read `AGENTS.md` and the files under `docs/references/`.
+- Keep changes scoped. A profile change should not touch the template; a bullet edit should not touch filter logic.
+
+## Before Changing Common Areas
+
+- **Data files** (`base_en.yaml`, `base_tr.yaml`): structural keys and tags are always English, even in `base_tr.yaml`. Never add a tag that doesn't belong to the vocabulary without checking with the user first.
+- **Filter logic** (`src/cv_renderer/filter.py`): changes here affect every profile. Inspect existing behavior before modifying.
+- **Template** (`templates/main.html.j2`): visual-only changes. No content or data logic belongs here.
+- **Profile schema** (`src/cv_renderer/models.py`): adding a field requires updating examples and docs.
+
+## Critical Rules for CV Content
+
+- Every bullet must follow the XYZ formula. Read `docs/references/xyz-format-in-resumes.md`.
+- Every bullet must follow Harvard OCS language rules. Read `docs/references/harvard-resume-writing-guide.md`.
+- Every `about`/`about_override` summary follows the title → skills & accomplishments → career goals structure in `docs/references/about-me-section.md` — including the closing goals sentence, which the bullet-writing guides above don't cover.
+- No personal pronouns, no passive voice, no vague quantifiers in any bullet.
+- Tags are the only interface between data and profiles. A bullet gets all tags that truthfully apply — multiple tags on one bullet is correct. Do not invent tags outside the current vocabulary unless the user asks.
+- Skill items support the same tagging as bullets (`items: [{text, tags}, ...]`), not just the category-level `tags`. Leave an item untagged when it's generic (always shown); tag it when it should only surface for profiles focused on that tag.
+- Never name the target company anywhere in rendered CV content (`about_override`, bullets, etc.), even in a company-specific profile. A resume is a document that outlives one application and can get reused or shared — "Spotify" in the about section is a cover-letter move, not a CV move. Keep company-specific *content* generic; only the profile filename/metadata should name the company.
+- `user-data/` contains personal data. Never commit it to a public repo.
+
+## Profile Generation
+
+- Produce valid YAML matching the `Profile` schema in `src/cv_renderer/models.py`.
+- Save company-specific profiles to `user-data/profiles/companies/<company>.yaml`.
+- Do not add fields outside the schema.
+- Company-specific wording (a summary pitch tailored to one job posting) belongs in that profile's `title_override` / `about_override` fields, never patched into `base_en.yaml`/`base_tr.yaml`. The base files stay the single, company-agnostic source of truth; only tag-based selection and per-application overrides live in profiles.
+- Overrides are still real CV content: same XYZ/Harvard rules, no invented facts, and written natively in the profile's `lang` — never a literal translation from the other language file.
+- Tag filtering only selects among existing bullets and includes/excludes whole entries — it cannot reframe an accomplishment. When a job or project is genuinely relevant to the target posting but its base bullets are framed the wrong way (e.g. an AI-tagged project whose data-access-security work matters to a data-engineering posting), rewrite those bullets in `experience_overrides` / `project_overrides` (keyed by `company` / project `name`) rather than editing the base data or forcing tags that don't truthfully apply. An override also forces the entry to appear even if its tags would otherwise exclude it — use this only when something in it is honestly relevant; if nothing is, leave it out and let tag filtering drop it.
+- If a per-application skill grouping (e.g. splitting one base category into two) would only make sense for this one profile, use `skill_overrides`, not a `base_en.yaml`/`base_tr.yaml` category split — the base files are shared by every profile, including `general`, so a split there leaks into CVs that never asked for it.
+
+## Checks
+
+```bash
+uv run ruff check .
+uv run ruff format .
+```
+
+## References
+
+Read when relevant:
+
+```
+AGENTS.md
+docs/references/xyz-format-in-resumes.md
+docs/references/harvard-resume-writing-guide.md
+docs/references/about-me-section.md
+docs/roadmap.md
+```

cv_renderer-0.1.0/CLAUDE.md

@@ -0,0 +1,56 @@
+# CLAUDE.md
+
+You are working on cv-renderer: a profile-driven CV renderer that produces tailored HTML and PDF exports from a single YAML data source.
+
+## How to Work
+
+- Read `user-data/data/base_en.yaml` before touching any CV content or generating profiles — the live data is the source of truth for tags, bullets, and skill categories.
+- Before writing or editing bullets, read `AGENTS.md` and the files under `docs/references/`.
+- Keep changes scoped. A profile change should not touch the template; a bullet edit should not touch filter logic.
+
+## Before Changing Common Areas
+
+- **Data files** (`base_en.yaml`, `base_tr.yaml`): structural keys and tags are always English, even in `base_tr.yaml`. Never add a tag that doesn't belong to the vocabulary without checking with the user first.
+- **Filter logic** (`src/cv_renderer/filter.py`): changes here affect every profile. Inspect existing behavior before modifying.
+- **Template** (`templates/main.html.j2`): visual-only changes. No content or data logic belongs here.
+- **Profile schema** (`src/cv_renderer/models.py`): adding a field requires updating examples and docs.
+
+## Critical Rules for CV Content
+
+- Every bullet must follow the XYZ formula. Read `docs/references/xyz-format-in-resumes.md`.
+- Every bullet must follow Harvard OCS language rules. Read `docs/references/harvard-resume-writing-guide.md`.
+- Every `about`/`about_override` summary follows the title → skills & accomplishments → career goals structure in `docs/references/about-me-section.md` — including the closing goals sentence, which the bullet-writing guides above don't cover.
+- No personal pronouns, no passive voice, no vague quantifiers in any bullet.
+- Tags are the only interface between data and profiles. A bullet gets all tags that truthfully apply — multiple tags on one bullet is correct. Do not invent tags outside the current vocabulary unless the user asks.
+- Skill items support the same tagging as bullets (`items: [{text, tags}, ...]`), not just the category-level `tags`. Leave an item untagged when it's generic (always shown); tag it when it should only surface for profiles focused on that tag.
+- Never name the target company anywhere in rendered CV content (`about_override`, bullets, etc.), even in a company-specific profile. A resume is a document that outlives one application and can get reused or shared — "Spotify" in the about section is a cover-letter move, not a CV move. Keep company-specific *content* generic; only the profile filename/metadata should name the company.
+- `user-data/` contains personal data. Never commit it to a public repo.
+
+## Profile Generation
+
+- Produce valid YAML matching the `Profile` schema in `src/cv_renderer/models.py`.
+- Save company-specific profiles to `user-data/profiles/companies/<company>.yaml`.
+- Do not add fields outside the schema.
+- Company-specific wording (a summary pitch tailored to one job posting) belongs in that profile's `title_override` / `about_override` fields, never patched into `base_en.yaml`/`base_tr.yaml`. The base files stay the single, company-agnostic source of truth; only tag-based selection and per-application overrides live in profiles.
+- Overrides are still real CV content: same XYZ/Harvard rules, no invented facts, and written natively in the profile's `lang` — never a literal translation from the other language file.
+- Tag filtering only selects among existing bullets and includes/excludes whole entries — it cannot reframe an accomplishment. When a job or project is genuinely relevant to the target posting but its base bullets are framed the wrong way (e.g. an AI-tagged project whose data-access-security work matters to a data-engineering posting), rewrite those bullets in `experience_overrides` / `project_overrides` (keyed by `company` / project `name`) rather than editing the base data or forcing tags that don't truthfully apply. An override also forces the entry to appear even if its tags would otherwise exclude it — use this only when something in it is honestly relevant; if nothing is, leave it out and let tag filtering drop it.
+- If a per-application skill grouping (e.g. splitting one base category into two) would only make sense for this one profile, use `skill_overrides`, not a `base_en.yaml`/`base_tr.yaml` category split — the base files are shared by every profile, including `general`, so a split there leaks into CVs that never asked for it.
+
+## Checks
+
+```bash
+uv run ruff check .
+uv run ruff format .
+```
+
+## References
+
+Read when relevant:
+
+```
+AGENTS.md
+docs/references/xyz-format-in-resumes.md
+docs/references/harvard-resume-writing-guide.md
+docs/references/about-me-section.md
+docs/roadmap.md
+```

cv_renderer-0.1.0/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 Melis Kılıç
+
+   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.