steersync 0.2.0__py3-none-any.whl

steersync-0.2.0.dist-info/METADATA

@@ -0,0 +1,342 @@
+Metadata-Version: 2.5
+Name: steersync
+Version: 0.2.0
+Summary: Sync Kiro steering documents between developer machines and a central git repository.
+Project-URL: Homepage, https://github.com/SCGIS-Wales/steersync
+Project-URL: Repository, https://github.com/SCGIS-Wales/steersync
+Project-URL: Issues, https://github.com/SCGIS-Wales/steersync/issues
+Project-URL: Changelog, https://github.com/SCGIS-Wales/steersync/blob/main/CHANGELOG.md
+Author-email: Dejan Gregor <dejan.gregor@gmail.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: developer-experience,git,kiro,mcp,pre-push,steering
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Version Control :: Git
+Classifier: Typing :: Typed
+Requires-Python: >=3.14
+Requires-Dist: click<9,>=8.5
+Requires-Dist: pydantic<3,>=2.14
+Requires-Dist: pymarkdownlnt<1,>=0.9.40
+Requires-Dist: python-frontmatter<2,>=1.3
+Requires-Dist: pyyaml<7,>=6.0.3
+Provides-Extra: mcp
+Requires-Dist: mcp<3,>=2.3; extra == 'mcp'
+Description-Content-Type: text/markdown
+
+# steersync
+
+Sync the whole [Kiro](https://kiro.dev) `.kiro/` configuration, steering, specs, skills,
+agents, hooks and settings, between developer machines and a central git repository. A plain
+Python CLI runs from a git pre-push hook and shells out to the `git` binary, so your existing
+SSH agent or credential helper does the authentication. An MCP server and Kiro session hooks
+are optional layers on top of the same core.
+
+Kiro CLI has no built in command to import or sync its configuration from a remote
+repository; its guidance is to copy files from a central repository into `~/.kiro/` and
+`.kiro/`. steersync automates that in both directions for every *collection* it is
+configured with:
+
+| Direction | Command | What happens |
+|---|---|---|
+| Central to local | `steersync pull` | Shallow clones or refreshes the central repository, writes `global/<collection>/` to `~/.kiro/<dir>/` and `projects/<slug>/<collection>/` to `<repo>/.kiro/<dir>/`, prunes files removed centrally, keeps files you edited locally. |
+| Local to central | `steersync push` | Lints every collection with its own profile, pushes them together to one branch named after the project, user and content hash, and sends GitLab push options so a merge request is opened for review. |
+
+## Collections
+
+A collection is one kind of Kiro content. The packaged defaults cover the full `.kiro/`
+layout; each one is configurable and new ones are added with a single YAML block.
+
+| Collection | Workspace | Global (`~/.kiro`) | Central directory | Files | Lint profile |
+|---|---|---|---|---|---|
+| `steering` | `.kiro/steering` | `steering` | `steering/` | `**/*.md` | `steering`: Kiro front matter, references, secrets, markdown |
+| `specs` | `.kiro/specs` | none | `specs/` | `**/*.md` | `markdown`: secrets and markdown style |
+| `skills` | `.kiro/skills` | `skills` | `skills/` | everything (`SKILL.md`, `scripts/`, `references/`, `assets/`) | `skill`: `SKILL.md` needs `name` and `description`, secrets in scripts |
+| `agents` | `.kiro/agents` | `agents` | `agents/` | `**/*.json`, `**/*.md` | `agent`: valid JSON with a `name`, flags deprecated `toolsSettings` |
+| `hooks` | `.kiro/hooks` | `hooks` | `hooks/` | `**/*.json` | `hooks`: `version`, `hooks[]` with `name`, `trigger`, `action` |
+| `settings` | `.kiro/settings` | none | `settings/` | `lsp.json`, `mcp.json` | `json`: valid JSON and secrets |
+
+Execute bits on skill scripts survive the round trip, hidden files are never synced, and
+files a collection's patterns do not select are never touched on either side. Limit any
+command to some collections with `--collection NAME` (repeatable), list them with
+`steersync config collections`, and see [docs/central-layout.md](docs/central-layout.md) for
+a worked example of a full `.kiro/` tree in the central repository.
+
+## Install
+
+Requires Python 3.14 or newer and git 2.18 or newer. Every
+[GitHub release](https://github.com/SCGIS-Wales/steersync/releases) carries the wheel, the
+sdist and a `SHA256SUMS` file, with signed build provenance.
+
+```bash
+VERSION=0.2.0
+uv tool install "https://github.com/SCGIS-Wales/steersync/releases/download/v${VERSION}/steersync-${VERSION}-py3-none-any.whl"
+# with the MCP server
+uv tool install "steersync[mcp] @ https://github.com/SCGIS-Wales/steersync/releases/download/v${VERSION}/steersync-${VERSION}-py3-none-any.whl"
+# verify where the wheel came from
+gh attestation verify "steersync-${VERSION}-py3-none-any.whl" --repo SCGIS-Wales/steersync
+```
+
+Every release is also published to [PyPI](https://pypi.org/project/steersync/) through
+trusted publishing, so `uv tool install steersync` (or `steersync[mcp]`) installs the same
+files that the GitHub release carries.
+
+## Quick start
+
+1. Point steersync at the central repository, once per machine:
+
+   ```bash
+   mkdir -p ~/.config/steersync
+   cat > ~/.config/steersync/config.yaml <<'YAML'
+   remote:
+     url: git@gitlab.example.com:platform/kiro-steering.git
+     allowed_hosts: [gitlab.example.com]
+   YAML
+   steersync config validate
+   ```
+
+2. Prepare a project. This adds every synced directory (`.kiro/steering/`, `.kiro/specs/`,
+   `.kiro/skills/`, ...) and the lock file to `.git/info/exclude` (so centrally managed
+   content is never committed to the project by accident; set `git_exclude: false` on a
+   collection to keep committing it) and installs a chaining pre-push hook:
+
+   ```bash
+   cd ~/code/my-service
+   steersync init --hook
+   steersync pull
+   ```
+
+3. Edit anything under `.kiro/`. On your next `git push`, or on demand with
+   `steersync push`, every collection is proposed to the central repository as one merge
+   request.
+
+Run `steersync doctor` at any time to see what steersync has resolved.
+
+## Central repository layout
+
+```text
+kiro-config/
+├── global/                        # applied to every machine (~/.kiro)
+│   ├── steering/engineering-rules.md
+│   ├── skills/release-checklist/SKILL.md
+│   └── hooks/steersync.json
+└── projects/
+    └── acme/platform/api/         # derived from the project's origin URL
+        ├── steering/product.md
+        ├── specs/tls-cert-staged-rotation/tasks.md
+        ├── skills/venafi-tpp-websdk/SKILL.md
+        ├── agents/entra-app-registration.json
+        ├── hooks/tests-on-stop.json
+        └── settings/lsp.json
+```
+
+The project slug is the remote path with the host and `.git` removed and unsafe characters
+replaced, so `ssh://git@gitlab.example.com/acme/platform/api.git` becomes
+`acme/platform/api`. The `global` and `projects` directory names and every collection
+directory are configurable. Repositories created with steersync 0.1, which kept steering
+directly under `global/` and `projects/<slug>/`, need their files moved into a `steering/`
+subdirectory; `pull` and `status` print a warning pointing at them until that is done.
+
+## Commands
+
+| Command | Purpose |
+|---|---|
+| `steersync pull [--force] [--dry-run] [--no-global] [--no-workspace] [--strict] [--best-effort] [-c NAME] [--json]` | Apply central collections locally. `--best-effort` warns and exits 0 on failure. |
+| `steersync push [--dry-run] [--scope global] [--no-lint] [-m MSG] [-c NAME] [--json]` | Propose local collections centrally in one branch. `--from-hook` is used by git hooks and never blocks the push unless strict. |
+| `steersync status [-c NAME] [--json]` | Show adds, updates, deletes and local edits per collection in both directions. |
+| `steersync lint [PATHS] [-c NAME] [--profile P] [--json]` | Validate every collection with its profile, or explicit paths. Exit code 4 on errors. |
+| `steersync init [--write-config] [--hook] [--no-exclude]` | Prepare a repository. |
+| `steersync install-hook [--force]` | Install or update the chaining pre-push hook. |
+| `steersync kiro-hook [--engine v2\|v3] [--write]` | Render a Kiro hook that runs `steersync pull --quiet` at session start. |
+| `steersync mcp-config [--remote URL]` | Render an `mcp.json` fragment. |
+| `steersync mcp` | Run the MCP stdio server. |
+| `steersync config show\|validate\|default\|collections` | Inspect configuration and the resolved collection directories. |
+| `steersync doctor` | Report git version, resolved paths, remote and project slug. |
+
+Global options: `--config PATH`, `--log-level`, `--log-format text|json`, `--quiet`.
+
+## Configuration
+
+Configuration is layered: packaged defaults, then one YAML file, then environment variables.
+The file is found in this order: `--config`, `$STEERSYNC_CONFIG`, `<repo>/.kiro/steersync.yaml`,
+`$XDG_CONFIG_HOME/steersync/config.yaml` (default `~/.config/steersync/config.yaml`). See
+[`steersync.example.yaml`](steersync.example.yaml) for every key and `steersync config default`
+for the packaged defaults.
+
+| Variable | Overrides |
+|---|---|
+| `STEERSYNC_REMOTE` | `remote.url` |
+| `STEERSYNC_DEFAULT_BRANCH` | `remote.default_branch` |
+| `STEERSYNC_CACHE_DIR` | `paths.cache_dir` |
+| `STEERSYNC_GIT_BINARY` | `git.binary` |
+| `STEERSYNC_LOG_LEVEL`, `STEERSYNC_LOG_FORMAT` | `logging.*` |
+| `STEERSYNC_STRICT` | `hook.strict` |
+| `KIRO_HOME` | Location of `~/.kiro`, as honoured by kiro-cli |
+
+Unknown keys, invalid patterns, unsafe paths and malformed push options are rejected at load
+time with a precise message. The pre 0.2 keys `paths.workspace_steering` and
+`paths.global_steering` still load, with a deprecation warning, as the steering collection's
+`workspace_path` and `global_path`.
+
+### Adding or changing a collection
+
+Collections are merged over the packaged defaults, so a project only lists what differs:
+
+```yaml
+collections:
+  specs:
+    enabled: false                # do not sync plans for this project
+  settings:
+    include: [lsp.json]           # keep mcp.json local
+  runbooks:                       # a new collection, central directory runbooks/
+    description: Operational runbooks
+    workspace_path: docs/runbooks
+    include: ["**/*.md"]
+    lint: markdown
+    git_exclude: false            # the project keeps committing these too
+  agents-md:                      # a single file at the repository root
+    workspace_path: .
+    include: [AGENTS.md]
+    max_depth: 1
+    lint: markdown
+    git_exclude: false
+```
+
+Every key is documented in `steersync config default`. A collection needs a `workspace_path`
+or a `global_path`; `central_dir` defaults to the collection name; enabled collections may not
+share a directory on either side.
+
+## Reliability
+
+| Mechanism | Configuration |
+|---|---|
+| Clone, fetch, ls-remote and push retry transient network and server errors with exponential backoff and jitter. Authentication and not found errors fail at once. | `git.retries`, `git.retry_backoff_seconds`, `git.retry_max_backoff_seconds` |
+| An exclusive lock serialises processes sharing a cache clone, such as a Kiro session hook and a git hook. The operating system releases it if a process dies. | `sync.lock_timeout_seconds` |
+| A corrupt or half written cache clone, or a stale `index.lock`, is deleted and cloned again. The cache is never deleted for network errors. | automatic |
+| A failed push always resets the cache clone to a clean default branch. | automatic |
+| From a pre-push hook each git call is capped and retried at most once, and no failure, including an unexpected bug, blocks the push unless strict mode is on. | `hook.timeout_seconds`, `hook.strict` |
+| Central and local content larger than the limits is refused. | `sync.max_files`, `sync.max_total_bytes` |
+
+## How pull decides what to write
+
+steersync records the hash of every file it wrote, per collection, in a lock file
+(`.kiro/steersync.lock.json` in the workspace, `~/.kiro/steersync.lock.json` globally).
+Version 1 lock files written by steersync 0.1 are read as the steering collection. On the
+next pull:
+
+| Local file | Compared with | Result |
+|---|---|---|
+| Missing | | Added |
+| Equals central | | Unchanged |
+| Equals lock, differs from central | | Updated |
+| Differs from lock and central | | Kept and reported as a conflict (`--force` overwrites) |
+| In lock, removed centrally, unmodified | | Deleted (`sync.prune: false` keeps it) |
+| Never synced | | Left alone and reported as local only |
+
+Kiro metadata is never written into steering front matter; all tool state lives in the lock
+file, so documents stay exactly as authored. Pulling a subset of collections leaves the lock
+entries of the others untouched.
+
+## Git hook
+
+`steersync install-hook` writes `.git/hooks/pre-push`. An existing hook is preserved as
+`pre-push.local` and run first with the same arguments and stdin. `core.hooksPath` is never
+changed. The hook calls `steersync push --from-hook --remote-url "$2"`, exits 0 on any sync
+failure unless `hook.strict` or `STEERSYNC_STRICT=1` is set, and skips pushes that only delete
+branches.
+
+Teams that already use [pre-commit](https://pre-commit.com) can use the published hook instead:
+
+```yaml
+# .pre-commit-config.yaml in the project
+default_install_hook_types: [pre-commit, pre-push]
+repos:
+  - repo: https://github.com/SCGIS-Wales/steersync
+    rev: v0.2.0
+    hooks:
+      - id: steersync-push
+      - id: steersync-lint
+```
+
+The lint hook receives the changed files under `.kiro/` and lints each with the profile of
+the collection it belongs to.
+
+## GitLab merge requests
+
+The default push options create a merge request against the default branch, remove the source
+branch on merge and set a title. Branch names follow `steering/{project}/{user}-{hash}`, where
+the hash covers every file, so two people proposing identical content share one branch and a
+second identical push is reported as `already-proposed`. Servers that do not advertise push
+options (GitHub, plain bare repositories) make git fail, so steersync retries once without them
+and says so. Push options may use `{default_branch}`, `{project}`, `{user}` and `{hash}`.
+
+## Lint rules
+
+Each collection runs one lint profile. The `steering` profile applies every rule below.
+`markdown` (specs, prompts, references) applies the encoding, size, secret and markdown rules
+without Kiro front matter checks. `skill` adds `skill-front-matter-required`,
+`skill-requires-metadata` and `skill-name-mismatch` for `SKILL.md`. `json` adds `json-syntax`,
+`hooks` adds `hook-schema`, `hook-trigger` and `hook-action`, `agent` adds `agent-schema`,
+`agent-name` and `agent-deprecated-key`, and `generic` only enforces the size limit and secret
+scanning, allowing binary assets. New profiles are one function in `steersync.lint.PROFILES`.
+
+| Rule | Severity | Check |
+|---|---|---|
+| `front-matter-position` | error | Front matter must start on line 1; Kiro ignores it after a blank line. |
+| `front-matter-yaml` | error | Front matter must be valid YAML. |
+| `inclusion-value` | error | `inclusion` is `always`, `fileMatch`, `manual` or `auto`. |
+| `filematch-pattern-required`, `filematch-pattern-type` | error | `fileMatch` needs a string or list of strings. |
+| `auto-requires-metadata` | error | `auto` needs `name` and `description`. |
+| `unknown-key` | warning | Keys Kiro does not know are ignored; `x-steersync` is allowed. |
+| `encoding-utf8`, `max-size` | error | UTF-8 only; default limit 64 KiB because always included bytes cost context. |
+| `require-h1` | warning | A level one heading is expected. |
+| `file-reference-missing`, `file-reference-escape` | warning, error | `#[[file:path]]`, `#[[file:path:line]]`, `#[[file:path:start-end]]` and `#[[folder:path]]` targets must exist inside the workspace. |
+| `forbidden-*` | error | AWS keys, private keys, GitHub, GitLab and Slack tokens, generic credentials. Patterns are configurable. |
+| `markdown-MD*` | configurable | pymarkdown rules with the front matter extension enabled. |
+
+## Kiro integration
+
+**Session hook (V3).** `steersync kiro-hook --write` creates `.kiro/hooks/steersync.json` with a
+`SessionStart` trigger that runs `steersync pull --quiet --best-effort`. For CLI 2.x agents paste the output of
+`steersync kiro-hook --engine v2` into the agent's `hooks` block. Field reports say Kiro hooks fire
+only in headless runs or with a custom agent active, so treat them as a convenience and keep the
+git hook as the dependable trigger.
+
+**MCP server.** Add the fragment from `steersync mcp-config` to `.kiro/settings/mcp.json`. The
+server exposes `pull_steering`, `push_steering`, `diff_steering` and `lint_steering`. Kiro does
+not pass the shell's `PATH`, `SSH_AUTH_SOCK` or proxy variables to MCP servers, so the rendered
+fragment forwards them explicitly through `env`; use an absolute `--command` if `uvx` is not on
+Kiro's path.
+
+**Custom agents.** On Kiro CLI V3 custom agents inherit steering, skills and `AGENTS.md` by
+default, so list only the always on steering files in `resources` and reference skills with
+`skill://.kiro/skills/*/SKILL.md`. A `file://.kiro/steering/**/*.md` glob loads every document
+at startup and defeats the `fileMatch`, `manual` and `auto` inclusion modes. On CLI 2.x list
+the documents you need explicitly.
+
+## Security
+
+See [SECURITY.md](SECURITY.md). In short: no credentials of its own, no shell, validated remote
+URLs with an optional host allow list, path containment for every write, central symlinks never
+followed, git hooks disabled in the cache, secret scanning before a push, recursion guards in
+hooks, redacted logs, SHA pinned actions, locked and audited dependencies, signed provenance on
+releases.
+
+## Development
+
+```bash
+uv sync --all-extras --group dev
+uv run pytest --cov
+uv run ruff check . && uv run ruff format --check . && uv run mypy
+```
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) and [docs/architecture.md](docs/architecture.md).
+
+## Licence
+
+Apache 2.0. Kiro is a trademark of Amazon Web Services; this project is not affiliated with AWS.

steersync-0.2.0.dist-info/RECORD

@@ -0,0 +1,20 @@
+steersync/__init__.py,sha256=Np72Y8tdiKOvVGI2yuOAv6hVrRBGRakLbWAwDJZrkeY,127
+steersync/__main__.py,sha256=ZJGm_TexJkz3KC_DFTZOqn7ejFjs9jBQ3doJhFlwIhE,106
+steersync/cli.py,sha256=ttsD6rxK8_e8SDLfJ458jZxP1DhWzZrTIJwexUZhh8w,27947
+steersync/config.py,sha256=ScqU0CLbpDIiKfGupyfWNEEH4M3UFkTkBsIFDVddMV0,20383
+steersync/errors.py,sha256=retrgxKxRt50B8WOIMYG8n0M9shwuKSinO_Y3dRdVOM,1103
+steersync/gitops.py,sha256=2lBWO6Tb6GmKruqKucEHdpCYeXxTP-2eX87r-Zz0RPc,19382
+steersync/hooks.py,sha256=vzvKKfwOoL-NNxPec_dVOy3j_Pw_o1G_jQHXGFWuRkk,4887
+steersync/lint.py,sha256=-S4495knumLWGuAGfC1Ujx_2nbnXvcYYfTFzdOcaj_w,21229
+steersync/locking.py,sha256=elEJKrOxdhfFrfgv3gUj6tNXdjZGJcF-biJ13sY4Bn0,2232
+steersync/logging_utils.py,sha256=zSfPglRDThVvEL35KcczdGFv853a7zAOi3n2PQY4W3E,2006
+steersync/mcp_server.py,sha256=g_af353Z0Ib8Fke7uTNvfR0PbheRag0LCOfq5q6DvRg,6291
+steersync/paths.py,sha256=SxfzWIfgPmu3fjr1dLy1GN8LLAYEwFbXlFdeAcYLmWs,3622
+steersync/steering.py,sha256=tLG8KibKacfkwd94gQx9V5ONjC_7rxpuWm0kdYddWt8,16174
+steersync/sync.py,sha256=zAk1Oo02yvSvt0-rHvHBMvnDcLmuDqXR_9V8QBNwuI0,25422
+steersync/resources/default_config.yaml,sha256=n8fDW64n9z2aAqBTVeFH4mt7qrzwzjoeaJgCxWoHTEs,5507
+steersync-0.2.0.dist-info/METADATA,sha256=XcMFypgxwbjHoXqM6vFVeUqZ_6zPkXypZXeFDOqZu5E,18038
+steersync-0.2.0.dist-info/WHEEL,sha256=W3fkpkm7-wf9vBI5Z-7s0eWkeM-spu78I8Neb98DeEg,87
+steersync-0.2.0.dist-info/entry_points.txt,sha256=ibMQBakb7MufxLcc0b-qNTFPiZq3naJ73DY8ScQanmU,48
+steersync-0.2.0.dist-info/licenses/LICENSE,sha256=4Hl9Bp9jHMcRxleKG0sPRzT0jGQ0YYhsu82ILO_JDqM,10787
+steersync-0.2.0.dist-info/RECORD,,

steersync-0.2.0.dist-info/WHEEL

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

steersync-0.2.0.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+steersync = steersync.cli:run

steersync-0.2.0.dist-info/licenses/LICENSE

@@ -0,0 +1,190 @@
+                                 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
+
+   Copyright 2026 SCGIS Wales and the steersync contributors
+
+   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.