chore(deps): bump google-github-actions/auth from 2 to 3

.clusterfuzzlite/build.sh

@@ -0,0 +1,106 @@
+#!/bin/bash
+# .clusterfuzzlite/build.sh
+# ClusterFuzzLite build script — required by OSS-Fuzz and ClusterFuzzLite
+# to build Python fuzz targets with atheris.
+#
+# OpenSSF Scorecard: Fuzzing check — this file enables ClusterFuzzLite
+# to detect bugs via continuous coverage-guided fuzzing.
+
+set -eux
+
+pip install atheris
+
+# Build fuzz target for Modbus register parser
+cat > "${OUT}/fuzz_modbus_registers" << 'EOF'
+#!/usr/bin/env python3
+"""ClusterFuzzLite fuzz target: Modbus register parsing.
+
+This target tests that arbitrary byte inputs to the register parser:
+1. Never cause unhandled exceptions or crashes
+2. Always produce safe SOC/power values within IEC 62619 limits
+"""
+import sys
+import struct
+import atheris
+
+sys.path.insert(0, "/src")
+
+
+def parse_modbus_register_safe(data: bytes) -> dict:
+    """Simulate register parsing as done in simulator_driver.py."""
+    if len(data) < 4:
+        return {}
+    try:
+        raw_soc = struct.unpack(">H", data[:2])[0]
+        raw_power = struct.unpack(">h", data[2:4])[0]
+        soc_pct = raw_soc / 100.0
+        power_kw = raw_power / 10.0
+        assert 0.0 <= soc_pct <= 100.0, f"SOC out of range: {soc_pct}"
+        assert -10000.0 <= power_kw <= 10000.0, f"Power out of range: {power_kw}"
+        return {"soc": soc_pct, "power_kw": power_kw}
+    except struct.error:
+        return {}
+
+
+def parse_register_extended(data: bytes) -> None:
+    if len(data) < 8:
+        return
+    try:
+        temp_raw = struct.unpack(">H", data[4:6])[0]
+        volt_raw = struct.unpack(">H", data[6:8])[0]
+        temp_c = temp_raw / 10.0
+        volt_v = volt_raw / 10.0
+        assert temp_c < 200.0
+        assert volt_v < 2000.0
+    except struct.error:
+        pass
+
+
+@atheris.instrument_func
+def TestOneInput(data: bytes) -> None:
+    fdp = atheris.FuzzedDataProvider(data)
+    raw = fdp.ConsumeBytes(64)
+    parse_modbus_register_safe(raw)
+    parse_register_extended(raw)
+
+
+if __name__ == "__main__":
+    atheris.Setup(sys.argv, TestOneInput)
+    atheris.Fuzz()
+EOF
+
+chmod +x "${OUT}/fuzz_modbus_registers"
+
+# Build fuzz target for MQTT payload parser
+cat > "${OUT}/fuzz_mqtt_payload" << 'EOF'
+#!/usr/bin/env python3
+"""ClusterFuzzLite fuzz target: MQTT telemetry payload parsing."""
+import sys
+import json
+import atheris
+
+sys.path.insert(0, "/src")
+
+
+@atheris.instrument_func
+def TestOneInput(data: bytes) -> None:
+    fdp = atheris.FuzzedDataProvider(data)
+    raw_str = fdp.ConsumeUnicodeNoSurrogates(256)
+    try:
+        payload = json.loads(raw_str)
+        if isinstance(payload, dict):
+            _ = payload.get("soc", 0.0)
+            _ = payload.get("power_kw", 0.0)
+            _ = payload.get("site_id", "")
+    except (json.JSONDecodeError, ValueError, TypeError):
+        pass  # Graceful failure is expected
+
+
+if __name__ == "__main__":
+    atheris.Setup(sys.argv, TestOneInput)
+    atheris.Fuzz()
+EOF
+
+chmod +x "${OUT}/fuzz_mqtt_payload"
+
+echo "✅ ClusterFuzzLite build complete — 2 fuzz targets built."

.github/DISCUSSION_TEMPLATE/adopter_introduction.yml

@@ -0,0 +1,82 @@
+title: "Adopter Introduction"
+description: "Introduce your organization as a user or integrator of BESSAI Edge Gateway. Join the community of adopters!"
+labels: ["adopter", "community"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Welcome to the BESSAI community! 🎉
+        If your organization is using, deploying, or building on BESSAI Edge Gateway, we'd love to hear from you. Adopter introductions help us understand real-world use cases and prioritize the roadmap.
+
+        Your organization can also be listed in [`docs/adopters.md`](../docs/adopters.md) — just mention it below and open a PR!
+
+  - type: input
+    id: organization
+    attributes:
+      label: Organization name
+      placeholder: "e.g., Energía Renovable S.A."
+    validations:
+      required: true
+
+  - type: input
+    id: country
+    attributes:
+      label: Country / Region
+      placeholder: "e.g., Chile, Germany, Australia"
+    validations:
+      required: true
+
+  - type: dropdown
+    id: adopter_tier
+    attributes:
+      label: How are you using BESSAI?
+      options:
+        - "🔌 Integrator — deploying BESSAI in customer projects"
+        - "🏭 Operator — running BESSAI at our own sites"
+        - "🔬 Research — using BESSAI for academic or R&D purposes"
+        - "🤝 Contributor — contributing code, drivers, or documentation"
+        - "👀 Evaluating — assessing BESSAI for future use"
+    validations:
+      required: true
+
+  - type: dropdown
+    id: hardware
+    attributes:
+      label: Hardware you are connecting with
+      multiple: true
+      options:
+        - "Huawei SUN2000"
+        - "SMA Sunny Tripower"
+        - "Victron MultiPlus-II"
+        - "Fronius GEN24"
+        - "Other (describe below)"
+    validations:
+      required: false
+
+  - type: textarea
+    id: use_case
+    attributes:
+      label: Your use case
+      description: Brief description of your deployment or project. No confidential details needed.
+      placeholder: "We are using BESSAI to manage a 500 kWh LFP installation at a solar farm in the Atacama region, integrating with our existing SCADA system via MQTT..."
+
+  - type: textarea
+    id: feedback
+    attributes:
+      label: Feedback or feature requests
+      description: What would make BESSAI work better for your use case?
+
+  - type: checkboxes
+    id: listing
+    attributes:
+      label: Adopter listing
+      options:
+        - label: "I consent to my organization being listed in `docs/adopters.md` (you can open a PR or we can add it)"
+        - label: I would be interested in joining the Technical Steering Committee (TSC) as an external member
+
+  - type: input
+    id: contact
+    attributes:
+      label: Contact (optional)
+      description: GitHub handle, email, or LinkedIn — only share what you are comfortable making public
+      placeholder: "@github-handle or contact@example.com"

.github/DISCUSSION_TEMPLATE/bep_discussion.yml

@@ -0,0 +1,67 @@
+title: "BEP Pre-Discussion"
+description: "Start a discussion before writing a formal BEP. Early feedback helps determine if a BEP is the right vehicle and shapes the proposal."
+labels: ["bep", "discussion"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Before you open this discussion
+        A BEP (BESSAI Enhancement Proposal) is required only for changes that affect:
+        - BESSAI-SPEC-* specifications (driver interface, safety requirements, telemetry schema)
+        - GOVERNANCE.md or the BEP process itself
+        - Architectural changes that break compatibility for external adopters
+
+        **For bug fixes, new device drivers, or non-breaking features, open a PR directly.**
+
+  - type: input
+    id: title
+    attributes:
+      label: Proposal title
+      placeholder: "e.g., Add SoH% as a required tag in BESSAI-SPEC-001"
+    validations:
+      required: true
+
+  - type: dropdown
+    id: bep_type
+    attributes:
+      label: Expected BEP type
+      options:
+        - "Standards Track (changes to BESSAI-SPEC-*)"
+        - "Governance (changes to GOVERNANCE.md or BEP process)"
+        - "Informational (significant observation, no normative changes)"
+    validations:
+      required: true
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem statement
+      description: What problem are you trying to solve? Why does it need a formal specification change?
+      placeholder: "Currently, conforming drivers are not required to report State of Health. This means the SafetyGuard cannot account for degraded batteries..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposed_solution
+    attributes:
+      label: Proposed solution (sketch)
+      description: A rough outline of your proposed change. This will evolve into the BEP specification section.
+      placeholder: "Add SoH_% as a RECOMMENDED tag in BESSAI-SPEC-001 §5.3, with a MUST requirement for all drivers that support the tag to return a value in [0, 100]..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: What else did you consider? This helps the community understand your reasoning.
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Pre-discussion checklist
+      options:
+        - label: I have searched existing BEPs and GitHub Discussions for similar proposals
+          required: true
+        - label: I believe this change requires a formal BEP (not just a PR)
+          required: true

.github/FUNDING.yml

@@ -0,0 +1,16 @@
+# GitHub Sponsors & Funding
+# See: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository
+
+github: []
+open_collective: ""
+ko_fi: ""
+tidelift: ""
+community_bridge: ""
+liberapay: ""
+issuehunt: ""
+lfx_crowdfunding: ""
+otechie: ""
+polar: ""
+custom:
+  - "https://bess-solutions.cl/sponsor"
+  - "https://github.com/bess-solutions/open-bess-edge/discussions/1"

.github/ISSUE_TEMPLATE/hardware_support.yml

@@ -0,0 +1,80 @@
+name: 🔌 Hardware Support Request
+description: Request support for a new inverter, battery or hardware device
+title: "[Hardware]: Add support for "
+labels: ["hardware-support", "enhancement"]
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        BESSAI supports **Huawei SUN2000, SMA Sunny Tripower, Victron MultiPlus-II** and **Fronius GEN24**.
+        If you need support for a new device, fill out the information below and we will create a Modbus registry profile.
+
+        **Before submitting:** Check if the [registry/](../registry/) folder already has a profile for your device.
+
+  - type: input
+    id: manufacturer
+    attributes:
+      label: Manufacturer
+      placeholder: "e.g., Tesla, ABB, Sungrow, SolarEdge"
+    validations:
+      required: true
+
+  - type: input
+    id: model
+    attributes:
+      label: Model / Series
+      placeholder: "e.g., Powerwall 3, Fimer React 2, Sungrow SH10RS"
+    validations:
+      required: true
+
+  - type: dropdown
+    id: protocol
+    attributes:
+      label: Communication Protocol
+      options:
+        - Modbus TCP
+        - Modbus RTU
+        - SunSpec (Modbus)
+        - OPC UA
+        - REST API
+        - Other / Unknown
+    validations:
+      required: true
+
+  - type: input
+    id: datasheet
+    attributes:
+      label: Modbus Register Map / Datasheet URL
+      description: Link to official Modbus register map (PDF or URL)
+      placeholder: "https://..."
+
+  - type: textarea
+    id: registers
+    attributes:
+      label: Key Registers (if known)
+      description: |
+        List the critical Modbus registers you need (address, type, description).
+        If you don't know them, attach/link the register map above.
+      placeholder: |
+        Address 40001 — SOC (%) UINT16 scale 0.1
+        Address 40002 — Power (W) INT32 scale 1
+        ...
+
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Priority
+      description: How urgently do you need this?
+      options:
+        - "🔴 Critical — blocking production deployment"
+        - "🟡 Medium — needed in next 3 months"
+        - "🟢 Nice to have — no urgent deadline"
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: Any other relevant info (country, project size, willingness to test)