Release v0.3.0-beta.1

Author: Maksym Shtembuliak

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -28,7 +28,7 @@ body:
     id: integration_version
     attributes:
       label: EyeBond Local version
-      placeholder: 0.1.43
+      placeholder: 0.2.0
     validations:
       required: true
   - type: input
@@ -83,3 +83,20 @@ body:
       label: Logs, screenshots, or additional context
       description: Paste relevant logs or screenshots. Redact secrets if needed.
       render: shell
+  - type: dropdown
+    id: discovery_source
+    attributes:
+      label: Where did you hear about EyeBond Local?
+      description: Optional. Helps understand where the project is found.
+      options:
+        - Prefer not to say
+        - Search engine (Google, etc.)
+        - Home Assistant Community
+        - Reddit
+        - Telegram
+        - YouTube
+        - GitHub
+        - Friend / installer
+        - Other
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/device_contribution.yml

@@ -0,0 +1,57 @@
+name: Device Contribution
+description: Share a learned device so it can be added to the built-in catalog.
+title: "device: "
+labels:
+  - device-contribution
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for helping support more inverters! This is for devices that the
+        integration identified as **partial** or **did not recognize**, where you
+        ran **learning** to discover the sensors and controls.
+
+        Before submitting:
+
+        1. In the integration options, run **Add controls (device learning)** to discover
+           the device's sensors and controls.
+        2. Create a **Support Archive**: *Configure → Diagnostics and service tools →
+           Create support archive*.
+        3. Attach the downloaded Support Archive (a `.zip`) to this issue.
+
+        The archive carries the device fingerprint, register map, and label correlations,
+        with **no** part number, serial number, IP, or account — those are stripped on your
+        device before the file is written. A maintainer turns the archive into a catalog
+        contribution.
+  - type: checkboxes
+    id: preflight
+    attributes:
+      label: Preflight
+      options:
+        - label: I ran device learning on this device.
+          required: true
+        - label: I will attach the Support Archive (.zip) to this issue.
+          required: true
+        - label: I searched existing issues first.
+          required: true
+  - type: input
+    id: model
+    attributes:
+      label: Inverter model (as printed on the unit)
+      placeholder: e.g. SMG II 4200 / Anenji ANJ-11KW-48V
+    validations:
+      required: true
+  - type: input
+    id: integration_version
+    attributes:
+      label: Integration version
+      placeholder: 0.2.0
+    validations:
+      required: true
+  - type: textarea
+    id: notes
+    attributes:
+      label: Notes
+      description: Anything unusual about the device, or sensors/controls you expected but did not get.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/support_archive.yml

@@ -86,3 +86,20 @@ body:
       label: Extra context
       description: Include anything the archive does not capture well, such as screenshots, a known-good vendor app behavior, or a short reproduction note.
       placeholder: The vendor app shows values correctly; Home Assistant only gets collector metadata.
+  - type: dropdown
+    id: discovery_source
+    attributes:
+      label: Where did you hear about EyeBond Local?
+      description: Optional. Helps understand where the project is found.
+      options:
+        - Prefer not to say
+        - Search engine (Google, etc.)
+        - Home Assistant Community
+        - Reddit
+        - Telegram
+        - YouTube
+        - GitHub
+        - Friend / installer
+        - Other
+    validations:
+      required: false

CHANGELOG.md

@@ -26,8 +26,8 @@ Anything that can live in JSON (capabilities, conditions, presets, register layo
 
 When deciding where new logic belongs, use this order:
 
-1. **`profiles/`** (JSON) — capability groups, writable metadata, conditions, presets, support annotations.
-2. **`register_schemas/`** (JSON) — read-side layouts, fields, enums, bit labels, model overlays.
+1. **`protocol_catalogs/profiles/`** (JSON) — capability groups, writable metadata, conditions, presets, support annotations.
+2. **`protocol_catalogs/register_schemas/`** (JSON) — read-side layouts, fields, enums, bit labels, model overlays.
 3. **`payload/`** (Python) — family-level framing and parse helpers.
 4. **`drivers/`** (Python) — probe, read, write, and procedural derived logic only.
 5. **HA entities** — purely presentational. No protocol or register knowledge.
@@ -59,16 +59,18 @@ custom_components/eybond_local/
 ├── runtime/                # coordinator, hub, transport orchestration
 ├── payload/                # protocol framing and parsing
 ├── drivers/                # probe + read + write orchestration
-├── profiles/               # capability metadata (JSON)
-├── register_schemas/       # register layouts (JSON)
-├── fixtures/               # offline replay helpers
+├── protocol_catalogs/
+│   ├── profiles/           # capability metadata (JSON)
+│   └── register_schemas/   # register layouts (JSON)
+├── fixtures/               # runtime fixture/replay helper package
 ├── support/                # support exports and evidence indexes
 ├── metadata/               # profile/schema loaders and local drafts
 └── *.py                    # entity platforms, config flow, services
 
 docs/                       # public docs and generated reports
+catalog/inverter_models/    # commercial model and sanitized source records
 tools/                      # CLI utilities, validation scripts, and release helpers
-.local/                     # maintainer-only local notes, fixtures, generated reports, and release scratch files (gitignored)
+.local/                     # maintainer-only notes, fixtures, design history, generated reports, and release scratch files (gitignored)
 tests/                      # unit and regression tests
 ```
 
@@ -90,11 +92,18 @@ To refresh generated documentation reports before running the quality gate:
 python3 tools/quality_gate.py --refresh-generated
 ```
 
+`pytest tests/` works too (`pytest.ini` disables the auto-plugins that
+conflict with the suite), and with `pytest-xdist` installed
+(`pip install pytest-xdist`) `pytest tests/ -n auto` runs it in parallel —
+that plugin is optional and not part of the base environment.
+
 The quality gate checks profile validity, unit tests, and public generated-doc freshness. PRs should leave it green.
 
 Fixture replay and fixture-derived reports are local-only workflows. Keep those artifacts under `.local/` and run them manually when you need debugging evidence.
 
-A complete reference of CLI tools (probing, local fixtures, validation, doc generation) is in [tools/README.md](tools/README.md).
+A short reference for supported validation, catalog, release, and contribution
+tools is in [tools/README.md](tools/README.md). Low-level hardware probes and
+local fixture workflows are maintainer-only notes under `.local/`.
 
 ---
 
@@ -107,7 +116,7 @@ These are the hard rules — don't cross them without discussion:
 - **Fixture-first over live debugging** when feasible — but keep those fixtures local unless you intentionally sanitize them for sharing.
 - **JSON-first over Python** for new family additions.
 - **Local fixtures and maintainer-only notes belong under `.local/`** and are not part of the public repository.
-- **`tools/` is public project tooling** used by CI, release validation, and generated-doc checks.
+- **`tools/` is supported project tooling** for CI, release validation, catalog validation, generated-doc checks, and sanitized contribution workflows.
 - **`.local/generated/`, `.local/release-notes/`, and raw research dumps** remain local-only artifacts and should stay out of git.
 
 ---