unitysvc-data 0.1.0__tar.gz

unitysvc_data-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 UnitySVC
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

unitysvc_data-0.1.0/PKG-INFO

@@ -0,0 +1,189 @@
+Metadata-Version: 2.4
+Name: unitysvc-data
+Version: 0.1.0
+Summary: Standard examples and presets for UnitySVC data packages
+Author-email: Bo Peng <bo.peng@unitysvc.com>
+Maintainer-email: Bo Peng <bo.peng@unitysvc.com>
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/unitysvc/unitysvc-data
+Project-URL: Issues, https://github.com/unitysvc/unitysvc-sellers/issues
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Operating System :: OS Independent
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: test
+Requires-Dist: pytest>=7; extra == "test"
+Requires-Dist: ruff; extra == "test"
+Dynamic: license-file
+
+# unitysvc-data
+
+Standard examples and presets for UnitySVC — primary consumer is
+[unitysvc-sellers](https://github.com/unitysvc/unitysvc-sellers), but the
+same preset / manifest machinery is intended to serve other parts of the
+platform too.
+
+A data-first Python package that ships:
+
+- Example files (connectivity tests, usage snippets, descriptions)
+  organised under `src/unitysvc_data/examples/<gateway>/<family>/`.
+- A generated manifest (`_manifest.json`) mapping every preset name to
+  its metadata and bundled file.
+- Two primitives for consumers:
+  - `doc_preset(source, **overrides)` — returns a full document
+    record (category, description, mime_type, file_path, ...) ready
+    to drop into `listing.json`. This is the expansion the SDK
+    applies to `$preset` JSON sentinels at upload time.
+  - `file_preset(source)` — returns the raw UTF-8 content of the
+    preset's bundled file. Useful when the example isn't a listing
+    document (embed as snippet, feed to a test harness, etc.).
+
+Both accept either a bare name (`"s3_connectivity"`,
+`"s3_connectivity_v1"`) or a `{"$preset": "...", "$with": {...}}`
+sentinel, so the same function works from JSON walkers and from
+programmatic Python code.
+
+Sellers reference a preset from their `listing.json` like this:
+
+```json
+{
+  "documents": {
+    "Connectivity test": { "$preset": "s3_connectivity" },
+    "Usage (Python)":    { "$preset": "s3_code_example_v1",
+                           "$with": { "description": "Lists objects in our bucket" } }
+  }
+}
+```
+
+The SDK walks the parsed listing and calls `doc_preset(...)` on each
+sentinel, substituting the bundled file's absolute path into
+`file_path`, then feeds the result into the existing upload pipeline.
+No custom URL scheme, no extra render pass.
+
+## CLI
+
+Installing the package provides a `usvc_data` command for shell-level
+access to the same data:
+
+```bash
+usvc_data list                                       # every preset + aliases
+usvc_data list --json                                # machine-readable form
+
+usvc_data info s3_connectivity                       # README prose for a preset
+
+usvc_data doc-preset s3_connectivity                 # expanded JSON record
+usvc_data doc-preset s3_connectivity --with '{"description":"ours"}'
+usvc_data doc-preset s3_connectivity --compact       # single-line JSON
+
+usvc_data file-preset s3_connectivity                # raw file content to stdout
+usvc_data file-preset s3_connectivity > /tmp/s3.py   # pipe to file (raw template)
+```
+
+Note that `file-preset` returns the raw file content — `.j2` templates
+come through with Jinja2 markers intact. The sellers SDK renders them
+with per-listing context at upload time; if you pipe a `.j2` preset
+directly to an executable file you'll get a template, not a runnable
+script.
+
+`--with` accepts a JSON object whose keys are the overridable fields
+(`description`, `is_active`, `is_public`, `meta`). Forbidden keys and
+unknown preset names exit with status 1 and a message on stderr.
+
+## Layout
+
+```
+src/unitysvc_data/
+├── __init__.py              # example_path / read_example / list_examples
+├── presets.py               # doc_preset / file_preset / PRESETS / ALIASES
+├── cli.py                   # usvc_data entry point
+├── _manifest.json           # generated — committed — source of truth at runtime
+└── examples/
+    ├── api/                 # generic HTTP services
+    │   └── connectivity/
+    │       ├── README.md                 # front-matter + prose
+    │       └── connectivity-v1.sh.j2
+    ├── llm/                 # LLM gateway
+    │   └── request-template/
+    │       ├── README.md
+    │       └── request-template-v1.json
+    ├── s3/                  # S3-compatible storage gateway
+    │   ├── code-example/ ...
+    │   ├── connectivity/ ...
+    │   └── description/ ...
+    └── smtp/                # SMTP relay
+        └── connectivity/ ...
+
+tools/
+└── build.py                 # regenerate _manifest.json + MANIFEST.md
+```
+
+Each gateway holds one or more **preset families** (e.g. `s3/connectivity/`).
+A family directory contains:
+
+- `README.md` with TOML front-matter delimited by `+++` lines. The
+  front-matter has every piece of metadata for the family
+  (`preset_name`, `category`, `mime_type`, `file`, `description`,
+  `is_active`, `is_public`, `meta`). Prose under the front-matter
+  documents the example and any per-version differences.
+- One file per version, named `<stem>-v<N>.<suffix>` where stem and
+  suffix come from the `file` field — so `file = "connectivity.sh.j2"`
+  matches `connectivity-v1.sh.j2`, `connectivity-v2.sh.j2`, ....
+
+Versions are **discovered automatically** by scanning the family
+directory; authors never list them explicitly. Adding a new version
+is purely "drop a new `-v<N>.<ext>` file and rebuild."
+
+[`MANIFEST.md`](MANIFEST.md) at the repo root is the human-readable
+roster of every preset, also generated by `tools/build.py`.
+
+## Preset naming
+
+| Form                              | Resolves to                                | Use when             |
+|-----------------------------------|--------------------------------------------|----------------------|
+| `s3_connectivity_v1`              | version 1 of the `s3/connectivity` family  | pinning to an exact version |
+| `s3_connectivity` (alias)         | latest version of that family              | tracking the latest  |
+
+Seller data that pins to a versioned name stays byte-identical across
+`pip upgrade`s. Data that uses the alias tracks the newest version
+automatically.
+
+## Versioning discipline
+
+- Example files are **append-only**. `connectivity-v1.py.j2` is
+  frozen forever; fixes ship as `connectivity-v2.py.j2` dropped into
+  the same directory.
+- The version-less alias always points at the highest-`v` file in the
+  family. Landing a new version shifts the alias automatically the
+  next time `python tools/build.py` runs.
+- `preset_name` is globally unique across the whole tree — declaring
+  the same `preset_name` in two READMEs is a build error.
+- Package version bumps are additive (new version or new family →
+  minor bump; never mutate existing `_vN` → no breaking release).
+  Bump major only to remove a `_vN` (should be vanishingly rare).
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for the full walkthrough: how
+to add a new family, how to publish a new version, front-matter
+reference, filename conventions, and the pre-submission checklist.
+
+In one line: drop your file at
+`src/unitysvc_data/examples/<gateway>/<family>/<stem>-v<N>.<ext>[.j2]`,
+write the family's `README.md`, run `python tools/build.py`, open the PR.
+
+## Development
+
+```bash
+uv pip install -e '.[test]'
+pytest -q                      # runs tests + manifest-freshness check
+python tools/build.py          # regenerate manifest + roster
+python tools/build.py --check  # CI mode: non-zero exit if stale
+```
+
+CI ([`.github/workflows/ci.yml`](.github/workflows/ci.yml)) runs
+`tools/build.py --check`, `ruff`, `pytest` on Python 3.11 and 3.12,
+then builds a wheel and verifies it includes every example file and
+the manifest.

unitysvc_data-0.1.0/README.md

@@ -0,0 +1,168 @@
+# unitysvc-data
+
+Standard examples and presets for UnitySVC — primary consumer is
+[unitysvc-sellers](https://github.com/unitysvc/unitysvc-sellers), but the
+same preset / manifest machinery is intended to serve other parts of the
+platform too.
+
+A data-first Python package that ships:
+
+- Example files (connectivity tests, usage snippets, descriptions)
+  organised under `src/unitysvc_data/examples/<gateway>/<family>/`.
+- A generated manifest (`_manifest.json`) mapping every preset name to
+  its metadata and bundled file.
+- Two primitives for consumers:
+  - `doc_preset(source, **overrides)` — returns a full document
+    record (category, description, mime_type, file_path, ...) ready
+    to drop into `listing.json`. This is the expansion the SDK
+    applies to `$preset` JSON sentinels at upload time.
+  - `file_preset(source)` — returns the raw UTF-8 content of the
+    preset's bundled file. Useful when the example isn't a listing
+    document (embed as snippet, feed to a test harness, etc.).
+
+Both accept either a bare name (`"s3_connectivity"`,
+`"s3_connectivity_v1"`) or a `{"$preset": "...", "$with": {...}}`
+sentinel, so the same function works from JSON walkers and from
+programmatic Python code.
+
+Sellers reference a preset from their `listing.json` like this:
+
+```json
+{
+  "documents": {
+    "Connectivity test": { "$preset": "s3_connectivity" },
+    "Usage (Python)":    { "$preset": "s3_code_example_v1",
+                           "$with": { "description": "Lists objects in our bucket" } }
+  }
+}
+```
+
+The SDK walks the parsed listing and calls `doc_preset(...)` on each
+sentinel, substituting the bundled file's absolute path into
+`file_path`, then feeds the result into the existing upload pipeline.
+No custom URL scheme, no extra render pass.
+
+## CLI
+
+Installing the package provides a `usvc_data` command for shell-level
+access to the same data:
+
+```bash
+usvc_data list                                       # every preset + aliases
+usvc_data list --json                                # machine-readable form
+
+usvc_data info s3_connectivity                       # README prose for a preset
+
+usvc_data doc-preset s3_connectivity                 # expanded JSON record
+usvc_data doc-preset s3_connectivity --with '{"description":"ours"}'
+usvc_data doc-preset s3_connectivity --compact       # single-line JSON
+
+usvc_data file-preset s3_connectivity                # raw file content to stdout
+usvc_data file-preset s3_connectivity > /tmp/s3.py   # pipe to file (raw template)
+```
+
+Note that `file-preset` returns the raw file content — `.j2` templates
+come through with Jinja2 markers intact. The sellers SDK renders them
+with per-listing context at upload time; if you pipe a `.j2` preset
+directly to an executable file you'll get a template, not a runnable
+script.
+
+`--with` accepts a JSON object whose keys are the overridable fields
+(`description`, `is_active`, `is_public`, `meta`). Forbidden keys and
+unknown preset names exit with status 1 and a message on stderr.
+
+## Layout
+
+```
+src/unitysvc_data/
+├── __init__.py              # example_path / read_example / list_examples
+├── presets.py               # doc_preset / file_preset / PRESETS / ALIASES
+├── cli.py                   # usvc_data entry point
+├── _manifest.json           # generated — committed — source of truth at runtime
+└── examples/
+    ├── api/                 # generic HTTP services
+    │   └── connectivity/
+    │       ├── README.md                 # front-matter + prose
+    │       └── connectivity-v1.sh.j2
+    ├── llm/                 # LLM gateway
+    │   └── request-template/
+    │       ├── README.md
+    │       └── request-template-v1.json
+    ├── s3/                  # S3-compatible storage gateway
+    │   ├── code-example/ ...
+    │   ├── connectivity/ ...
+    │   └── description/ ...
+    └── smtp/                # SMTP relay
+        └── connectivity/ ...
+
+tools/
+└── build.py                 # regenerate _manifest.json + MANIFEST.md
+```
+
+Each gateway holds one or more **preset families** (e.g. `s3/connectivity/`).
+A family directory contains:
+
+- `README.md` with TOML front-matter delimited by `+++` lines. The
+  front-matter has every piece of metadata for the family
+  (`preset_name`, `category`, `mime_type`, `file`, `description`,
+  `is_active`, `is_public`, `meta`). Prose under the front-matter
+  documents the example and any per-version differences.
+- One file per version, named `<stem>-v<N>.<suffix>` where stem and
+  suffix come from the `file` field — so `file = "connectivity.sh.j2"`
+  matches `connectivity-v1.sh.j2`, `connectivity-v2.sh.j2`, ....
+
+Versions are **discovered automatically** by scanning the family
+directory; authors never list them explicitly. Adding a new version
+is purely "drop a new `-v<N>.<ext>` file and rebuild."
+
+[`MANIFEST.md`](MANIFEST.md) at the repo root is the human-readable
+roster of every preset, also generated by `tools/build.py`.
+
+## Preset naming
+
+| Form                              | Resolves to                                | Use when             |
+|-----------------------------------|--------------------------------------------|----------------------|
+| `s3_connectivity_v1`              | version 1 of the `s3/connectivity` family  | pinning to an exact version |
+| `s3_connectivity` (alias)         | latest version of that family              | tracking the latest  |
+
+Seller data that pins to a versioned name stays byte-identical across
+`pip upgrade`s. Data that uses the alias tracks the newest version
+automatically.
+
+## Versioning discipline
+
+- Example files are **append-only**. `connectivity-v1.py.j2` is
+  frozen forever; fixes ship as `connectivity-v2.py.j2` dropped into
+  the same directory.
+- The version-less alias always points at the highest-`v` file in the
+  family. Landing a new version shifts the alias automatically the
+  next time `python tools/build.py` runs.
+- `preset_name` is globally unique across the whole tree — declaring
+  the same `preset_name` in two READMEs is a build error.
+- Package version bumps are additive (new version or new family →
+  minor bump; never mutate existing `_vN` → no breaking release).
+  Bump major only to remove a `_vN` (should be vanishingly rare).
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for the full walkthrough: how
+to add a new family, how to publish a new version, front-matter
+reference, filename conventions, and the pre-submission checklist.
+
+In one line: drop your file at
+`src/unitysvc_data/examples/<gateway>/<family>/<stem>-v<N>.<ext>[.j2]`,
+write the family's `README.md`, run `python tools/build.py`, open the PR.
+
+## Development
+
+```bash
+uv pip install -e '.[test]'
+pytest -q                      # runs tests + manifest-freshness check
+python tools/build.py          # regenerate manifest + roster
+python tools/build.py --check  # CI mode: non-zero exit if stale
+```
+
+CI ([`.github/workflows/ci.yml`](.github/workflows/ci.yml)) runs
+`tools/build.py --check`, `ruff`, `pytest` on Python 3.11 and 3.12,
+then builds a wheel and verifies it includes every example file and
+the manifest.

unitysvc_data-0.1.0/pyproject.toml

@@ -0,0 +1,40 @@
+[build-system]
+requires = ["setuptools>=61.0", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "unitysvc-data"
+version = "0.1.0"
+description = "Standard examples and presets for UnitySVC data packages"
+readme = "README.md"
+authors = [{ name = "Bo Peng", email = "bo.peng@unitysvc.com" }]
+maintainers = [{ name = "Bo Peng", email = "bo.peng@unitysvc.com" }]
+license = "MIT"
+requires-python = ">=3.11"
+classifiers = [
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3 :: Only",
+  "Operating System :: OS Independent",
+  "Typing :: Typed",
+]
+dependencies = []
+
+[project.optional-dependencies]
+test = ["pytest>=7", "ruff"]
+
+[project.scripts]
+usvc_data = "unitysvc_data.cli:main"
+
+[project.urls]
+Homepage = "https://github.com/unitysvc/unitysvc-data"
+Issues  = "https://github.com/unitysvc/unitysvc-sellers/issues"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+unitysvc_data = ["examples/**/*", "_manifest.json", "py.typed"]
+
+[tool.ruff]
+line-length = 120
+target-version = "py311"

unitysvc_data-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

unitysvc_data-0.1.0/src/unitysvc_data/__init__.py

@@ -0,0 +1,119 @@
+"""Standard examples and presets for UnitySVC data packages.
+
+Pure-data package: ships example files under ``examples/`` organised by
+gateway and preset family, preset factories that return populated
+document records, and a JSON sentinel walker the sellers SDK calls at
+upload time. The same machinery is intended to serve other parts of the
+platform that need versioned, named references to bundled content.
+
+Preferred (preset-name) API:
+
+- :func:`doc_preset` — return a full document record for a preset,
+  from a bare name or a ``{"$preset": ..., "$with": {...}}`` sentinel.
+- :func:`file_preset` — return the raw UTF-8 content of a preset's
+  bundled example file.
+- :func:`list_presets` — enumerate every registered preset name
+  (versioned + aliases).
+- :data:`PRESETS` — mapping of preset name → factory function.
+- :data:`ALIASES` — mapping of version-less family name → latest
+  versioned preset name.
+- :data:`MANIFEST` — parsed ``_manifest.json`` content.
+- :data:`OVERRIDABLE` — fields that may be overridden in ``$with``.
+- :func:`register_jinja_globals` — expose every preset factory as a
+  Jinja2 global (for generated repos that render ``listing.json.j2``).
+
+Low-level (path-based) API — prefer the preset API above unless you
+specifically need to address files by their on-disk layout:
+
+- :func:`example_path`, :func:`read_example`, :func:`list_examples` —
+  resolve and read bundled example files by their path under
+  ``examples/``. These break if we ever reorganise the tree; preset
+  names don't.
+"""
+
+from __future__ import annotations
+
+from importlib.resources import files as _files
+from pathlib import Path
+
+from ._version import __version__
+
+_ROOT = _files(__name__).joinpath("examples")
+
+
+def example_path(name: str) -> Path:
+    """Return an absolute filesystem path for the bundled example *name*.
+
+    **Low-level.** Prefer :func:`file_preset` and :func:`doc_preset`
+    for anything that can key off a preset name — those are stable
+    across any future reorganisation of ``examples/``.
+
+    *name* is a path relative to ``examples/`` (e.g.
+    ``"s3/connectivity/connectivity-v1.py.j2"``). Raises
+    :class:`FileNotFoundError` if the file is not part of the
+    installed package.
+    """
+    target = _ROOT.joinpath(name)
+    if not target.is_file():
+        raise FileNotFoundError(f"Unknown example: {name!r}")
+    return Path(str(target))
+
+
+def read_example(name: str) -> str:
+    """Read the raw UTF-8 content of a bundled example by path.
+
+    **Low-level.** See :func:`example_path` for the name contract and
+    why :func:`file_preset` is usually the right choice.
+    """
+    return example_path(name).read_text(encoding="utf-8")
+
+
+def list_examples() -> list[str]:
+    """Return every bundled example filename, relative to ``examples/``.
+
+    **Low-level.** For enumerating presets by name, use
+    :func:`list_presets`. This function exposes on-disk paths
+    (including the gateway/family structure), which is rarely what a
+    consumer wants.
+
+    README files and hidden files are excluded.
+    """
+    root = Path(str(_ROOT))
+    return sorted(
+        path.relative_to(root).as_posix()
+        for path in root.rglob("*")
+        if path.is_file()
+        and path.name != "README.md"
+        and not path.name.startswith(".")
+    )
+
+
+# Imported last so presets.py can compute its own _EXAMPLES_ROOT without
+# reaching back into this module while __init__ is still loading.
+from .presets import (  # noqa: E402  (placement is deliberate)
+    ALIASES,
+    MANIFEST,
+    OVERRIDABLE,
+    PRESETS,
+    doc_preset,
+    file_preset,
+    list_presets,
+    register_jinja_globals,
+)
+
+__all__ = [
+    "__version__",
+    # Preferred preset API.
+    "doc_preset",
+    "file_preset",
+    "list_presets",
+    "PRESETS",
+    "ALIASES",
+    "MANIFEST",
+    "OVERRIDABLE",
+    "register_jinja_globals",
+    # Low-level path-based API.
+    "example_path",
+    "read_example",
+    "list_examples",
+]

unitysvc_data-0.1.0/src/unitysvc_data/_manifest.json

@@ -0,0 +1,91 @@
+{
+  "aliases": {
+    "api_connectivity": "api_connectivity_v1",
+    "llm_request_template": "llm_request_template_v1",
+    "s3_code_example": "s3_code_example_v1",
+    "s3_connectivity": "s3_connectivity_v1",
+    "s3_description": "s3_description_v1",
+    "smtp_connectivity": "smtp_connectivity_v1"
+  },
+  "presets": {
+    "api_connectivity_v1": {
+      "category": "connectivity_test",
+      "description": "Verify HTTP endpoint is reachable and returns a healthy status",
+      "example_file": "api/connectivity/connectivity-v1.sh.j2",
+      "is_active": true,
+      "is_public": false,
+      "meta": {
+        "output_contains": "connectivity ok"
+      },
+      "mime_type": "bash",
+      "preset_name": "api_connectivity",
+      "source_readme": "api/connectivity/README.md",
+      "version": 1
+    },
+    "llm_request_template_v1": {
+      "category": "request_template",
+      "description": "Minimal OpenAI-compatible chat completion request body",
+      "example_file": "llm/request-template/request-template-v1.json",
+      "is_active": true,
+      "is_public": false,
+      "meta": {},
+      "mime_type": "json",
+      "preset_name": "llm_request_template",
+      "source_readme": "llm/request-template/README.md",
+      "version": 1
+    },
+    "s3_code_example_v1": {
+      "category": "usage_example",
+      "description": "Python example: list objects in an S3 bucket via boto3",
+      "example_file": "s3/code-example/code-example-v1.py.j2",
+      "is_active": true,
+      "is_public": true,
+      "meta": {},
+      "mime_type": "python",
+      "preset_name": "s3_code_example",
+      "source_readme": "s3/code-example/README.md",
+      "version": 1
+    },
+    "s3_connectivity_v1": {
+      "category": "connectivity_test",
+      "description": "Verify S3 endpoint accepts the configured credentials",
+      "example_file": "s3/connectivity/connectivity-v1.py.j2",
+      "is_active": true,
+      "is_public": false,
+      "meta": {
+        "output_contains": "connectivity ok"
+      },
+      "mime_type": "python",
+      "preset_name": "s3_connectivity",
+      "source_readme": "s3/connectivity/README.md",
+      "version": 1
+    },
+    "s3_description_v1": {
+      "category": "description",
+      "description": "Customer-facing overview of the S3 gateway service",
+      "example_file": "s3/description/description-v1.md",
+      "is_active": true,
+      "is_public": true,
+      "meta": {},
+      "mime_type": "markdown",
+      "preset_name": "s3_description",
+      "source_readme": "s3/description/README.md",
+      "version": 1
+    },
+    "smtp_connectivity_v1": {
+      "category": "connectivity_test",
+      "description": "Verify SMTP server returns a 220 greeting on connect",
+      "example_file": "smtp/connectivity/connectivity-v1.sh.j2",
+      "is_active": true,
+      "is_public": false,
+      "meta": {
+        "output_contains": "connectivity ok"
+      },
+      "mime_type": "bash",
+      "preset_name": "smtp_connectivity",
+      "source_readme": "smtp/connectivity/README.md",
+      "version": 1
+    }
+  },
+  "version": "1"
+}

unitysvc_data-0.1.0/src/unitysvc_data/_version.py

@@ -0,0 +1 @@
+__version__ = "0.1.0"