opencode-skills-collection 4.0.71 → 4.0.72

package/bundled-skills/.antigravity-install-manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "updatedAt": "2026-09-23T02:09:47.535Z",
+  "updatedAt": "2026-09-24T01:56:44.424Z",
   "entries": [
     "00-andruia-consultant",
     "007",
@@ -475,6 +475,7 @@
     "changelog-automation",
     "changelog-updates",
     "chat-widget",
+    "chatexport-need-miner",
     "check-identity-pack",
     "chrome-extension-developer",
     "churn-prevention",
@@ -656,6 +657,7 @@
     "daily",
     "daily-gift",
     "daily-news-report",
+    "dali-short-address-commissioner",
     "dast-scanning",
     "data-engineer",
     "data-engineering-data-driven-feature",
@@ -869,6 +871,7 @@
     "enterprise-vpn-attack",
     "entropy-box",
     "environment-setup-guide",
+    "eol-resistor-calculator",
     "error-debugging-error-analysis",
     "error-debugging-error-trace",
     "error-debugging-multi-agent-review",
@@ -877,6 +880,7 @@
     "error-diagnostics-error-trace",
     "error-diagnostics-smart-debug",
     "error-handling-patterns",
+    "esl-price-sync",
     "ethical-hacking-methodology",
     "evaluation",
     "event-sourcing-architect",
@@ -1477,6 +1481,7 @@
     "markstream-vue2",
     "markstream-vue2-cli",
     "markstream-vue2-vite",
+    "marlin-bed-leveling",
     "matematico-tao",
     "mathguard",
     "matplotlib",
@@ -1655,6 +1660,7 @@
     "onboarding-cro",
     "onboarding-psychologist",
     "one-drive-automation",
+    "oneroster-csv-validator",
     "ontoly-software-graph",
     "open-dynamic-workflows",
     "open-source-marketing",

package/bundled-skills/chatexport-need-miner/SKILL.md

@@ -0,0 +1,196 @@
+---
+name: chatexport-need-miner
+description: "Mines offline Telegram Desktop chat exports (result.json) for unmet market needs and product opportunities using chunked streaming and verbatim quote grounding. Trigger phrases: mine chat export, telegram result.json, find unmet needs, analyze telegram chat."
+category: development
+risk: safe
+source: community
+source_repo: wwewtech/chatexport-need-miner
+source_type: community
+date_added: "2026-09-22"
+author: wwewtech
+tags: [telegram, market-research, text-mining, offline-analytics, developer-tools]
+tools: [claude, cursor, gemini, windsurf]
+license: "MIT"
+---
+
+# ChatExport Need Miner: Offline Market Signal & Pain-Point Extractor
+
+Transform offline Telegram Desktop chat exports (`result.json`) into quantified, quote-grounded rankings of unmet market needs with zero memory crashes and absolute source fidelity.
+
+## When to Use This Skill
+
+Activate this skill when:
+- The user provides an offline Telegram Desktop chat export (`result.json` or multi-file directory) and requests market research, customer problem analysis, or tool opportunity discovery.
+- The user asks: "What are people in this chat struggling with?", "Find product ideas from this export", "What tools do users wish existed?", or "Mine complaints from this group".
+- Analyzing multi-megabyte or gigabyte JSON dumps where standard in-memory deserialization (`json.load()`) risks out-of-memory (OOM) fatal crashes.
+- Cross-referencing user complaints across multiple independent communities to eliminate echo-chamber noise.
+
+Do NOT use this skill when:
+- The user wants live channel scraping, continuous bot monitoring, or MTProto API automation (use dedicated online fetchers).
+- Analyzing personal 1-on-1 romantic or private relationships.
+- Processing generic SaaS helpdesk feeds (Zendesk, Intercom, Gong) with structured ticket schemas.
+
+## Core Mental Models & Non-Negotiable Rules
+
+1. **The 4MB Stream & Overlap Invariant (Memory Ceiling <= 8MB)**:
+   - Telegram Desktop `result.json` files routinely exceed 500MB to 5GB.
+   - NEVER load an entire export into memory with `json.load()` or `fs.readFileSync()`.
+   - Read the file in fixed 4MB chunks with a 4KB overlap tail.
+   - **Boundary Counting Law**: A substring hit is recorded if and only if its terminus falls past the overlap boundary. This guarantees zero missed boundary-spanning phrases and strictly zero duplicate counts.
+
+2. **Cross-Chat Multiplicity Law ($U \ge 3$ Priority)**:
+   - One user posting 50 complaints in a single chat is an anecdote; 5 distinct users posting the same complaint across 3 independent chats is a market signal.
+   - Cluster rank score is calculated as:
+     $$\text{Score} = U \times \sqrt{H}$$
+     where $U$ is the number of distinct chat exports containing the signal, and $H$ is the total verified keyword hits.
+   - A pattern appearing in $U \ge 3$ chats always outranks a pattern confined to $U = 1$, regardless of raw hit volume.
+
+3. **Verbatim Quote Anchor & Anti-Hallucination Law**:
+   - Every identified need theme MUST be backed by 2 to 5 verbatim quotes with exact ISO timestamp (`date`) and chat identifier.
+   - NEVER paraphrase a quote inside quotation marks. NEVER synthesize synthetic user statements.
+   - If a hypothesized theme lacks verbatim quote support, it MUST be marked `[UNCONFIRMED / NO VERBATIM EVIDENCE]`.
+
+4. **Bi-Lingual Case-Insensitive Seed Lexicons**:
+   - Russian Lexicon: `не хватает`, `вот бы`, `бесит`, `надоело`, `задолбал`, `ищу инструмент`, `ищу бот`, `есть ли бот`, `есть ли сервис`, `посоветуйте тул`, `не работает`, `вручную`, `рутина`, `приходится руками`.
+   - English Lexicon: `i wish`, `missing`, `annoying`, `frustrating`, `looking for a tool`, `is there an app`, `is there a bot`, `any alternative to`, `doesn't work`, `manually`, `repetitive`, `waste of time`.
+   - Custom terms may be added only when explicitly approved or provided by the user.
+
+5. **Strict Air-Gap & Zero Exfiltration**:
+   - The entire analysis executes locally and offline. No network requests, no external telemetry, no remote LLM proxying of raw message contents.
+
+## Named Sins & Anti-Patterns (Что категорически ЗАПРЕЩЕНО)
+
+| Anti-Pattern | Manifestation in Code/Workflow | Mandatory Production Counter-Rule |
+| :--- | :--- | :--- |
+| **The OOM Slurp** | `data = json.load(open('result.json'))` on 800MB file. | Use incremental regex streaming or chunked buffered file reading with `<= 8MB` RAM footprint. |
+| **Chunk Boundary Blindness** | Chunking without overlap, truncating `"looking for a tool"` across 4096-byte splits. | Maintain a 4KB sliding overlap tail across chunk transitions. |
+| **Double-Count Overlap Trap** | Counting hits found in both chunk $N$ and the overlap window of chunk $N+1$. | Only increment match counter if `match.end() > overlap_size`. |
+| **The Echo-Chamber Distortion** | Elevating a bug mentioned 80 times by 1 single user in 1 chat to the #1 product opportunity. | Apply Cross-Chat Multiplicity Law ($U \times \sqrt{H}$) and count unique authors when available. |
+| **Hallucinated Quotations** | "User expressed desire for better sync" written in quotes as `"I really need better sync"`. | Exact substring slice from source buffer; if unquoted, label as synthetic analysis. |
+| **Service Message Pollution** | Mining system notifications (`"pinned a message"`, `"joined group"`, bot spam) as human needs. | Filter out messages where `type == "service"` or text begins with known bot commands (`/start`). |
+| **Premature Uniqueness Claim** | Stating "No tool currently exists for this problem" without validation. | Run explicit coverage audit; if unverified, output strictly: `I cannot confirm this`. |
+| **Lossy Encoding Crash** | Crashing on multi-byte emoji surrogate pairs or non-UTF-8 characters in chat history. | Decode with `errors='replace'` or raw byte-level UTF-8 traversal. |
+| **Monolithic Theme Lumping** | Grouping all complaints under `"Users want better UI"` or `"Performance issues"`. | Disaggregate into specific actionable workflows (e.g. `"No zero-downtime database migration path"`). |
+| **API Creep** | Prompting the user for Telegram Bot tokens or phone numbers for MTProto login. | Reject live requests; reiterate that input contract requires offline `result.json` exports only. |
+
+## Concrete Archetypes / Presets
+
+### Archetype 1: Streaming Regex Need Scanner (Python 3.10+)
+```python
+import re
+import os
+from typing import Generator, Dict, List, Tuple
+
+CHUNK_SIZE = 4 * 1024 * 1024  # 4 MB
+OVERLAP = 4096                 # 4 KB
+
+RU_LEXICON = re.compile(
+    r"(?i)\b(не\s+хватает|вот\s+бы|бесит|надоело|задолбал|ищу\s+(?:инструмент|бот|софт)|"
+    r"есть\s+ли\s+(?:бот|сервис|тул)|посоветуйте|вручную|рутина|приходится\s+руками)\b"
+)
+EN_LEXICON = re.compile(
+    r"(?i)\b(i\s+wish|missing|annoying|frustrating|looking\s+for\s+a\s+(?:tool|bot|app)|"
+    r"is\s+there\s+(?:an?\s+app|a\s+bot|a\s+tool)|any\s+alternative\s+to|manually|waste\s+of\s+time)\b"
+)
+
+def stream_chat_chunks(filepath: str) -> Generator[Tuple[str, int], None, None]:
+    overlap_tail = ""
+    with open(filepath, "r", encoding="utf-8", errors="replace") as f:
+        while True:
+            chunk = f.read(CHUNK_SIZE)
+            if not chunk:
+                break
+            combined = overlap_tail + chunk
+            yield combined, len(overlap_tail)
+            overlap_tail = combined[-OVERLAP:] if len(combined) >= OVERLAP else combined
+
+def mine_need_signals(filepath: str, regex: re.Pattern, max_samples: int = 5) -> Dict:
+    hits = 0
+    samples: List[str] = []
+    for text_block, overlap_len in stream_chat_chunks(filepath):
+        for m in regex.finditer(text_block):
+            if m.end() > overlap_len:
+                hits += 1
+                if len(samples) < max_samples:
+                    start = max(0, m.start() - 60)
+                    end = min(len(text_block), m.end() + 140)
+                    snippet = " ".join(text_block[start:end].split())
+                    samples.append(snippet)
+    return {"total_hits": hits, "samples": samples}
+```
+
+### Archetype 2: Need Cluster & Prioritization Schema
+```json
+{
+  "theme_id": "NEED-001",
+  "theme_name": "Zero-Downtime SQLite Replication for Edge Daemons",
+  "aggregate_score": 14.14,
+  "distinct_chats": 4,
+  "total_hits": 50,
+  "chats_observed": ["devops_talk_ru", "sqlite_users", "homelab_ops", "backend_craft"],
+  "evidence": [
+    {
+      "date": "2026-08-14T11:22:04",
+      "chat": "devops_talk_ru",
+      "verbatim_quote": "бесит что нет нормальной репликации для sqlite на edge серверах без поднятия тяжелого postgres"
+    },
+    {
+      "date": "2026-09-02T19:40:12",
+      "chat": "sqlite_users",
+      "verbatim_quote": "is there a tool that actually handles multi-master sqlite sync without crashing on high concurrency?"
+    }
+  ],
+  "existing_coverage": [
+    {"tool": "LiteFS", "gap": "Requires Consul / Fly.io infrastructure; complex on bare-metal edge."},
+    {"tool": "rqlite", "gap": "Raft layer alters SQLite interface semantics."}
+  ],
+  "verdict": "Real commercial gap for turnkey lightweight edge replication."
+}
+```
+
+### Archetype 3: Multi-File Directory Batch Orchestrator
+```python
+def process_export_directory(dir_path: str, pattern: re.Pattern) -> List[Dict]:
+    results = []
+    for root, _, files in os.walk(dir_path):
+        for file in files:
+            if file == "result.json" or file.endswith(".json"):
+                full_path = os.path.join(root, file)
+                chat_name = os.path.basename(root) if file == "result.json" else file
+                data = mine_need_signals(full_path, pattern)
+                if data["total_hits"] > 0:
+                    results.append({"chat": chat_name, **data})
+    return results
+```
+
+## The Pre-Emit Quality Gate Checklist
+
+Before emitting any market research summary or opportunity report, verify:
+- [ ] **Memory Protection**: Confirmed that raw JSON was parsed via chunked stream or filtered iterator, never loaded as a monolithic object.
+- [ ] **Boundary Integrity**: Overlap boundary logic was applied so split phrases across chunk cuts were not lost or double-counted.
+- [ ] **Verbatim Quote Integrity**: Every listed quote exists word-for-word in the input file with exact date and source. Zero paraphrasing.
+- [ ] **Cross-Chat Breadth**: Verified how many independent chat files the signal appeared in ($U \ge 3$ emphasized).
+- [ ] **Service Message Stripping**: Confirmed system and bot notifications were not tabulated as customer pain points.
+- [ ] **Honesty and Verification Clause**: If a gap or existing competitor cannot be verified, explicitly output: `"I cannot confirm this"`.
+- [ ] **Actionable Granularity**: Themes are tied to specific engineering or operational workflows, not generic platitudes.
+
+## Self-Correction & Verification Loop
+
+### Bad (Vibe-Coded AI Slop Output):
+> "I reviewed the chats and users are looking for better dev tools. Many people complain about speed and say they wish things worked better. There is a huge opportunity to build an AI bot for developers."
+*Problems: Zero verbatim quotes, zero date citations, zero chat distribution count, ungrounded speculation, generic meaningless advice.*
+
+### Good (Production ChatExport Need Miner Output):
+> ### 1. Schema Migration Rollbacks for Flyway in CI/CD — 38 hits across 4 chats ($U=4, H=38, \text{Score}=24.66$)
+> - **Chat Distribution**: `k8s_ru` (14 hits), `devops_community` (12 hits), `backend_pro` (8 hits), `java_chat` (4 hits).
+> - **Evidence 1**: *"бесит когда flyway падает на миграции в CI и приходится вручную чистить schema_version таблицу на стейдже"* (2026-07-19T09:12:44, `devops_community`).
+> - **Evidence 2**: *"is there a tool to safely dry-run flyway down migrations before merging to master?"* (2026-08-04T16:21:09, `k8s_ru`).
+> - **Coverage Check**: Flyway Pro provides undo migrations; however, community tier users lack automated sandbox validation without custom Docker scripts.
+> - **Verdict**: Confirmed gap for a lightweight CLI pre-flight validator for open-source Flyway migrations.
+
+## Limitations
+
+- Use only exports you are authorized to analyze. Chat exports can contain personal or sensitive information; minimize copied excerpts, redact identifiers in reports, and follow applicable retention and privacy requirements.
+- Keep raw exports local and offline as described above. Do not upload messages, quotes, or identifiers to external services or include them in public reports without explicit authorization.
+- Keyword counts and clustered themes are exploratory signals, not representative market research. Validate conclusions with independent evidence and do not infer intent from isolated messages.
+- Chunked text scanning is not a complete Telegram JSON parser; malformed exports, escaped content, nested schemas, or encoding issues can affect counts. Verify any quoted excerpt against the original export.

package/bundled-skills/dali-short-address-commissioner/SKILL.md

@@ -0,0 +1,185 @@
+---
+name: dali-short-address-commissioner
+description: "Commissions DALI and DALI-2 (IEC 62386) lighting buses: short-address assignment (0-63), 24-bit binary search collision resolution, groups, and DT8 color control. Trigger phrases: commission dali, dali short address, dali collision resolution, dali bus addressing, dali-2 setup."
+category: architecture
+risk: safe
+source: community
+source_repo: wwewtech/dali-short-address-commissioner
+source_type: community
+date_added: "2026-09-22"
+author: wwewtech
+tags: [dali, dali-2, lighting-control, iec-62386, building-automation, iot]
+tools: [claude, cursor, gemini, windsurf]
+license: "MIT"
+---
+
+# DALI Short-Address Commissioner: Deterministic IEC 62386 Bus Provisioning
+
+Systematically discover, resolve address collisions, assign short addresses (0–63), program groups and scenes, configure DT8 color gear, and schedule emergency battery duration tests on DALI and DALI-2 networks per IEC 62386.
+
+## When to Use This Skill
+
+Activate this skill when:
+- Bringing up, commissioning, or expanding DALI or DALI-2 lighting installations (KNX/DALI gateways, Tridonic, Philips Dynalite, Helvar, Osram, Lunatone).
+- The user asks: "How do I commission this DALI bus?", "Fix duplicate DALI short addresses", "Assign DALI addresses without erasing existing fixtures", or "Program DALI groups and DT8 tunable white".
+- Resolving address clash loops where multiple ballasts respond simultaneously to broadcast queries.
+- Designing or scheduling DALI-2 Part 202 emergency lighting duration and function tests across staggered floor circuits.
+
+Do NOT use this skill when:
+- Commissioning DMX512/RDM stage lighting, 0–10V analog dimming, or proprietary wireless RF networks (Zigbee, Bluetooth Mesh, Casambi).
+- Diagnosing dead ballasts or physical wiring faults before basic DALI bus voltage (12V–20.5V DC) and current limits (<= 250mA) are confirmed.
+- Programming building-wide KNX logic (this skill covers the DALI protocol domain strictly).
+
+## Core Mental Models & Non-Negotiable Rules
+
+1. **The 64-Address Bus Capacity Law**:
+   - A single DALI subnet supports strictly **0 to 63 short addresses** (64 control gear units maximum).
+   - Groups are strictly bounded to **0 to 15** (16 groups).
+   - Scenes are strictly bounded to **0 to 15** (16 scenes).
+   - If an installation has 65+ ballasts, the physical bus MUST be segmented into multiple DALI subnets with separate line masters or gateways.
+
+2. **The Double-Command 100ms Transmission Invariant**:
+   - Configuration and addressing commands (INITIALISE [cmd 258], RANDOMISE [259], SET SHORT ADDRESS [267], ENABLE WRITE [cmd 32], etc.) MUST be transmitted **twice within 100ms** to be executed by control gear.
+   - Sending an addressing command only once will result in silent ignored execution by all IEC 62386 compliant gear.
+
+3. **The 15-Minute Hardware Commissioning Timer**:
+   - Transmitting `INITIALISE` (cmd 258) starts a mandatory 15-minute countdown timer inside every ballast's micro-controller.
+   - All discovery, random address binary searching, and short address assignment MUST complete within 15 minutes, or the bus must receive a periodic keep-alive `INITIALISE` refresh.
+   - Upon completion, the master MUST transmit `TERMINATE` (cmd 257) to lock operational memory and exit programming state.
+
+4. **24-Bit Random Address Binary Search ($2^{24} = 16,777,216$ Space)**:
+   - When gear enters randomizing state (`RANDOMISE`), each unit generates a pseudo-random 24-bit integer (`0x000000` to `0xFFFFFF`).
+   - The master searches the 24-bit space using `SEARCHADDRH`, `SEARCHADDRM`, `SEARCHADDRL` and `COMPARE` (cmd 265).
+   - If multiple ballasts match, the master performs binary search down to a single device.
+   - Once isolated, assign short address via `PROGRAM SHORT ADDRESS` (cmd 267) and immediately transmit `WITHDRAW` (cmd 266) so the addressed fixture drops out of remaining search iterations.
+
+5. **Physical Identify & Non-Destructive Extension Invariant**:
+   - Every assigned short address MUST be verified visually using `IDENTIFY` or toggling `RECALL MAX LEVEL` / `OFF` before committing to lighting schedules.
+   - When adding fixtures to an existing operational line, NEVER broadcast a global `INITIALISE (all)`; use `INITIALISE (without short address)` so already-commissioned ballasts (0–63) preserve their programming.
+
+## Named Sins & Anti-Patterns (Что категорически ЗАПРЕЩЕНО)
+
+| Anti-Pattern | Manifestation in Code/Workflow | Mandatory Production Counter-Rule |
+| :--- | :--- | :--- |
+| **Single-Shot Addressing Commands** | Sending cmd 258 or cmd 267 once without repetition. | Always repeat configuration commands within a strict 100ms window. |
+| **Exceeding 64 Short Addresses** | Attempting to assign address 64 or 65 on one loop. | Partition into Subnet A and Subnet B; enforce 0–63 maximum. |
+| **Timer Starvation** | Letting the 15-minute `INITIALISE` window expire mid-search. | Issue keep-alive refresh or optimize binary search loop to < 3 minutes. |
+| **Ghost Address Overwrite** | Assigning address 0 without scanning if address 0 is in use. | Run non-destructive `QUERY STATUS` (cmd 144) across 0–63 before reassigning. |
+| **Bus Overcurrent Overload** | Connecting 64 ballasts (2mA each) + sensors to a 100mA PSU. | Verify total quiescent load $\le$ PSU rating (250mA max per IEC 62386). |
+| **DT8 / DT6 Type Mismatch** | Controlling tunable white gear with single-channel DT6 arc power. | Issue `SELECT DIMMING CURVE / COLOUR` (Part 209) and send DT8 color coordinates. |
+| **Simultaneous Emergency Discharge** | Triggering 3-hour duration tests on all emergency lights at once. | Stagger tests across alternating weeks/groups to ensure safety illumination. |
+| **Missing WITHDRAW Command** | Forgetting cmd 266 after addressing a found ballast. | Send `WITHDRAW` immediately after `PROGRAM SHORT ADDRESS` to exclude from search. |
+| **DALI Polarity Panic** | Halting installation claiming standard DALI requires polarity. | Note DALI uses an integrated bridge rectifier; polarity is non-critical (though consistent coloring is advised). |
+| **Energizing Unverified Mains** | Commissioning ballasts while 230V live mains work is ongoing. | Enforce physical lockout/tagout (LOTO) prior to terminal connection. |
+
+## Concrete Archetypes / Presets
+
+### Archetype 1: Greenfield DALI Discovery & Binary Search (Python/C Pseudo-code)
+```python
+import time
+
+def send_dali_double_cmd(cmd_byte1: int, cmd_byte2: int):
+    transmit_dali_frame(cmd_byte1, cmd_byte2)
+    time.sleep(0.015)  # 15ms spacing
+    transmit_dali_frame(cmd_byte1, cmd_byte2)
+
+def commission_greenfield_bus() -> dict:
+    assigned = {}
+    # 1. Start 15-min commissioning session
+    send_dali_double_cmd(0xA5, 0x00)  # INITIALISE (all gear)
+    send_dali_double_cmd(0xA7, 0x00)  # RANDOMISE
+    time.sleep(0.100)                  # Wait 100ms for random address generation
+
+    next_short_addr = 0
+    while next_short_addr < 64:
+        low, high = 0x000000, 0xFFFFFF
+        found_random_addr = None
+
+        # Binary search 24-bit space
+        while low <= high:
+            mid = (low + high) // 2
+            set_search_address(mid)
+            if query_compare():  # cmd 265: does any gear have random_addr <= mid?
+                found_random_addr = mid
+                high = mid - 1
+            else:
+                low = mid + 1
+
+        if found_random_addr is None:
+            break  # No more unaddressed fixtures on the bus
+
+        # Isolate and assign
+        set_search_address(found_random_addr)
+        short_addr_payload = (next_short_addr << 1) | 0x01
+        send_dali_double_cmd(0xB7, short_addr_payload)  # PROGRAM SHORT ADDRESS
+        send_dali_cmd(0xAB, 0x00)                       # WITHDRAW (cmd 266)
+
+        # Physical verify
+        flash_fixture(next_short_addr)
+        assigned[next_short_addr] = hex(found_random_addr)
+        next_short_addr += 1
+
+    send_dali_cmd(0xA1, 0x00)  # TERMINATE (cmd 257)
+    return assigned
+```
+
+### Archetype 2: Surgical Replacement of a Failed Ballast
+```python
+def replace_single_failed_ballast(expected_short_addr: int):
+    # Do NOT wipe existing 63 ballasts:
+    send_dali_double_cmd(0xA5, 0xFF)  # INITIALISE (ONLY gear without short address)
+    send_dali_double_cmd(0xA7, 0x00)  # RANDOMISE
+    time.sleep(0.100)
+
+    # Perform binary search for the single new replacement unit
+    random_addr = search_single_unit()
+    set_search_address(random_addr)
+
+    # Program directly into the missing slot
+    payload = (expected_short_addr << 1) | 0x01
+    send_dali_double_cmd(0xB7, payload)
+    send_dali_cmd(0xAB, 0x00)  # WITHDRAW
+    send_dali_cmd(0xA1, 0x00)  # TERMINATE
+```
+
+### Archetype 3: Group & DT8 Tunable White Configuration
+```python
+def configure_dt8_tunable_white(short_addr: int, mirek: int, group_id: int):
+    # Mirek = 1,000,000 / Kelvin (e.g. 2700K = 370 mirek, 6500K = 153 mirek)
+    send_dali_cmd(0x01, 0x00)  # DTR0: low byte of mirek
+    send_dali_cmd(0x03, 0x00)  # DTR1: high byte of mirek
+    send_dali_double_cmd(0xE7, 0x20)  # SET TEMP COLOUR (DT8 Part 209)
+    # Add to group (0-15)
+    group_payload = 0x60 | (group_id & 0x0F)
+    send_dali_double_cmd(0x01 | (short_addr << 1), group_payload)
+```
+
+## The Pre-Emit Quality Gate Checklist
+
+Before finalizing any DALI commissioning plan or script, check:
+- [ ] **Address Ceiling**: Total short addresses $\le 64$ (addresses 0–63).
+- [ ] **Double Transmission Timing**: Configuration commands repeat twice within 100ms.
+- [ ] **Commissioning Window**: 15-minute timer monitored with `TERMINATE` sent at conclusion.
+- [ ] **Withdrawal Discipline**: `WITHDRAW` (cmd 266) sent immediately after each address assignment.
+- [ ] **Bus Current Check**: Total quiescent load calculated ($\le 250\text{mA}$ power supply capacity).
+- [ ] **Emergency Test Staggering**: Emergency battery duration tests scheduled in alternating groups.
+- [ ] **Physical Verification**: `IDENTIFY` / `WINK` toggle step included for human visual signoff.
+
+## Self-Correction & Verification Loop
+
+### Bad (Vibe-Coded AI Slop Output):
+> "To assign addresses on DALI, loop from 1 to 100 and send cmd 267 to each light. If lights don't respond, change the positive and negative wires because DALI needs polarity."
+*Problems: Exceeds 64 addresses, addresses start at 1 instead of 0, misses double-command transmission, forgets random search, wrongly asserts DALI polarity dependence.*
+
+### Good (Production DALI Commissioner Output):
+> 1. Verify bus PSU delivers 16V DC with total load under 250mA (e.g., 42 ballasts $\times$ 2mA = 84mA).
+> 2. Send `INITIALISE (all)` [cmd 258] twice within 100ms, starting the 15-minute commissioning watchdog.
+> 3. Transmit `RANDOMISE` [cmd 259] twice within 100ms.
+> 4. Execute 24-bit binary search across `SEARCHADDR` space. For each isolated unit, transmit `PROGRAM SHORT ADDRESS` (slot 0–41) twice within 100ms, immediately followed by `WITHDRAW` [cmd 266].
+> 5. Issue `TERMINATE` [cmd 257] to exit programming mode and physically pulse each luminaire to verify mapping.
+
+## Limitations
+
+- DALI command support, timing, gear limits, and DT8 behavior vary by control gear, device type, and IEC 62386 edition. Confirm commands against the exact gear and gateway manuals before transmission.
+- Commissioning can disrupt occupied lighting and emergency systems. Coordinate an approved outage and have a qualified lighting professional verify any live bus operation; never treat these examples as a substitute for site procedures.
+- Pseudo-code is illustrative and is not a tested gateway driver. Verify address mapping and every fixture physically before saving configuration.

package/bundled-skills/eol-resistor-calculator/SKILL.md

@@ -0,0 +1,211 @@
+---
+name: eol-resistor-calculator
+description: "Calculates and validates end-of-line (EOL, SEOL, DEOL, TEOL) resistor loops for intrusion alarm panels (Honeywell, DSC, Paradox, Bosch) with wire gauge drop and state tables. Trigger phrases: eol resistor, deol wiring, alarm zone resistor, calculate end of line, double eol tamper."
+category: architecture
+risk: safe
+source: community
+source_repo: wwewtech/eol-resistor-calculator
+source_type: community
+date_added: "2026-09-22"
+author: wwewtech
+tags: [security-systems, hardware, electronics, alarm-panel, circuit-design, electrical-engineering]
+tools: [claude, cursor, gemini, windsurf]
+license: "MIT"
+---
+
+# EOL Resistor Calculator: Precision Intrusion Loop Supervision & State Solver
+
+Accurately size, configure, and troubleshoot Single (SEOL), Double (DEOL), and Triple (TEOL) end-of-line resistor loops across major security panel architectures with copper wire drop compensation and tamper state discrimination.
+
+## When to Use This Skill
+
+Activate this skill when:
+- Sizing, retrofitting, or diagnosing hardwired security loops on alarm panels (DSC PowerSeries/Neo, Honeywell Ademco Vista, Paradox EVO/Spectra, Bosch B/G Series, Texecom Premier Elite).
+- The user asks: "How do I wire double EOL on a DSC panel?", "Calculate zone loop resistance for a 200m cable run", "Troubleshoot a constant zone tamper fault", or "What resistor values does Honeywell Vista use?".
+- Differentiating between Normal, Alarm, Tamper (Short), and Cut (Open) circuit states across varying panel threshold windows.
+- Sizing copper loop resistance drops on long perimeter runs (e.g. 22 AWG over 150+ meters) to prevent phantom false alarms.
+
+Do NOT use this skill when:
+- Designing wireless sensors or addressable polling loop multiplexers (polling loops use digital transponders, not passive EOL resistors).
+- Bypassing safety or life-safety supervision circuits (never advise strapping out resistors or bypassing line supervision).
+- Working on 2-wire smoke detector loops without consulting panel-specific smoke circuit polarity and current-limiting specs.
+
+## Core Mental Models & Non-Negotiable Rules
+
+1. **The Far-End Placement Axiom (Strict Anti-Panel Stacking)**:
+   - Resistors MUST be installed **inside the sensor housing at the farthest physical end of the cable run**.
+   - Placing resistors across screw terminals inside the alarm panel enclosure protects only the metal cabinet itself; the entire 50-meter cable run to the sensor is left vulnerable to undetected wire cuts or staple shorts.
+   - Any wiring diagram showing EOL resistors at the panel board for field sensors is flagged as a Grade 2/Grade 3 compliance violation.
+
+2. **The 4-State Double-EOL (DEOL) Truth Table**:
+   - Double EOL uses two resistors: an End-of-Line resistor ($R_{EOL}$) and an Alarm contact resistor ($R_{ALARM}$).
+   - Standard series-parallel configuration (e.g., DSC standard 5.6k / 5.6k):
+     $$\text{Loop State} = \begin{cases} 
+     0\ \Omega\ (\text{Short Circuit}) & \implies \mathbf{Tamper\ (Short)} \\
+     R_{EOL}\ (5.6\text{k}\ \Omega) & \implies \mathbf{Normal\ (Secure)} \\
+     R_{EOL} + R_{ALARM}\ (11.2\text{k}\ \Omega) & \implies \mathbf{Alarm\ (Tripped)} \\
+     \infty\ \Omega\ (\text{Open Circuit}) & \implies \mathbf{Tamper\ (Cut\ Wire)}
+     \end{cases}$$
+   - This provides complete supervised discrimination between intruder activation and physical sabotage.
+
+3. **Copper Wire Resistance Compensation Formula**:
+   - Long field cable runs add series loop resistance across both conductors:
+     $$R_{loop} = 2 \times D \times \rho_{gauge}$$
+     where $D$ is one-way distance in meters, and $\rho_{gauge}$ is resistance per meter:
+     - **22 AWG (0.326 mm²)**: $0.053\ \Omega/\text{meter}$ ($16.14\ \Omega/1000\text{ft}$)
+     - **20 AWG (0.518 mm²)**: $0.033\ \Omega/\text{meter}$ ($10.15\ \Omega/1000\text{ft}$)
+     - **18 AWG (0.823 mm²)**: $0.021\ \Omega/\text{meter}$ ($6.38\ \Omega/1000\text{ft}$)
+   - A 150m run of 22 AWG adds $2 \times 150 \times 0.053 \approx 15.9\ \Omega$. Ensure total loop resistance does not push readings beyond the panel's $\pm 15\%$ ADC tolerance window.
+
+4. **Panel Reference Resistor Standards Matrix**:
+   - **DSC PowerSeries / Neo**: $5.6\text{k}\ \Omega$ SEOL / $5.6\text{k} + 5.6\text{k}$ DEOL.
+   - **Honeywell Ademco Vista**: $2.0\text{k}\ \Omega$ SEOL (Standard zones), $1.0\text{k}$ (Zone 1 on some models).
+   - **Paradox EVO / Spectra**: $1.0\text{k}\ \Omega$ SEOL / $1.0\text{k} + 1.0\text{k}$ DEOL (or ATZ mode with $1.0\text{k} / 2.2\text{k}$).
+   - **Bosch B / G Series**: Dual supervision with $1.0\text{k} / 2.0\text{k}$ or panel-selectable windows.
+   - **Texecom Premier Elite**: $2.2\text{k} / 4.7\text{k}$ or selectable Grade 3 Triple-EOL ($4.7\text{k} / 4.7\text{k} / 2.2\text{k}$ anti-mask).
+
+5. **ADC Voltage Divider Acceptance Windows**:
+   - Security panels measure zone voltage through an internal pull-up resistor ($R_{pullup}$, typically $1\text{k}$ to $3.3\text{k}\ \Omega$) connected to a reference voltage ($V_{ref}$, typically $5.0\text{V}$ or $13.8\text{V}$).
+   - Terminal voltage is given by:
+     $$V_{zone} = V_{ref} \times \frac{R_{loop\_total}}{R_{pullup} + R_{loop\_total}}$$
+   - Always confirm whether a measured terminal voltage falls inside the manufacturer's specified ADC threshold window before replacing field hardware.
+
+## Named Sins & Anti-Patterns (Что категорически ЗАПРЕЩЕНО)
+
+| Anti-Pattern | Manifestation in Code/Workflow | Mandatory Production Counter-Rule |
+| :--- | :--- | :--- |
+| **Panel-Terminal Resistor Stacking** | Crimping EOL resistors into the screw terminals on the panel PCB. | Install resistors exclusively inside the remote sensor housing. |
+| **Vendor Value Cross-Contamination** | Putting 2.0k Honeywell resistors onto a DSC panel requiring 5.6k. | Verify panel model and enforce manufacturer-specific resistance ratings. |
+| **DEOL Series/Parallel Inversion** | Swapping series and parallel resistors on an alarm PIR contact. | Wire $R_{ALARM}$ in parallel with NC alarm switch; wire $R_{EOL}$ in series with loop. |
+| **Neglecting Wire Drop on Long Runs** | Ignoring 40+ $\Omega$ wire resistance on a 300-meter warehouse fence zone. | Calculate loop resistance $2 \times D \times \rho$ and verify against panel budget. |
+| **Twist-and-Tape Resistor Splices** | Twisting resistor leads by hand and wrapping with electrical tape. | Use soldered heat-shrink sleeves or grease-filled B-connectors/crimps. |
+| **Fire/Burg Supervised Mix-up** | Applying burglar DEOL tamper logic to 2-wire latching fire zones. | Fire loops strictly require Normally Open (NO) contacts with SEOL supervision. |
+| **Unshielded AC Parallel Run** | Running 22/4 unshielded alarm cable in parallel with 230V mains. | Maintain 300mm physical separation or use twisted shielded pair (STP). |
+| **Strapping Out Trouble Zones** | Advising a user to twist zone wires together to clear a trouble condition. | Diagnose root cause (open wire, bad contact, corroded resistor) methodically. |
+| **Confusing NO and NC Contacts** | Treating a magnetic reed switch (NC) like an exit request button (NO). | Verify sensor contact behavior in quiescent, non-alarm states. |
+| **Unrecorded Commissioning Values** | Leaving an install without recording measured DC resistance values. | Deliver an audit log of measured loop ohms across Normal, Alarm, and Tamper. |
+
+## Concrete Archetypes / Presets
+
+### Archetype 1: Double-EOL (DEOL) Sensor Wiring Schematic (DSC 5.6k)
+```
+       (+) ZONE TERMINAL (Panel)
+               │
+               ▼  [Core 1: Field Wire]
+       ┌───────┴────────────────────────┐
+       │ SENSOR HOUSING (Far End)       │
+       │                                │
+       │    TAMPER SWITCH (NC)          │
+       │     ┌────[ / ]────┐            │
+       │     │             │            │
+       │     ▼             ▼            │
+       │    ( )           ( )           │
+       │     │             │            │
+       │     │        ALARM RELAY (NC)  │
+       │     │     ┌────[ / ]────┐      │
+       │     │     │             │      │
+       │     │     │   R_ALARM   │      │
+       │     │     └───[5.6k]────┘      │
+       │     │             │            │
+       │     ▼             ▼            │
+       │   R_EOL [5.6k]    │            │
+       │     │             │            │
+       └─────┼─────────────┼────────────┘
+             │             │
+             └─────────────┘
+               ▲
+               │  [Core 2: Field Wire]
+       (─) COMMON TERMINAL (Panel)
+
+State Resistance:
+• Secure:  5.6k Ω
+• Alarm:  11.2k Ω (Alarm contact opens, forcing current through R_ALARM)
+• Tamper: 0 Ω (Short circuit) or ∞ Ω (Cut wire or Tamper contact opens)
+```
+
+### Archetype 2: Loop Resistance & Tolerance Calculator (Python 3.10+)
+```python
+def calculate_loop_parameters(
+    panel_eol_nominal: float,
+    panel_tolerance_pct: float,
+    one_way_distance_m: float,
+    wire_gauge_awg: int = 22,
+    deol_mode: bool = True
+) -> dict:
+    # Ohms per meter for solid annealed copper conductors
+    RESISTANCE_PER_M = {18: 0.0209, 20: 0.0333, 22: 0.0530, 24: 0.0842}
+    rho = RESISTANCE_PER_M.get(wire_gauge_awg, 0.0530)
+    
+    wire_loop_ohms = 2.0 * one_way_distance_m * rho
+    normal_resistance = panel_eol_nominal + wire_loop_ohms
+    alarm_resistance = (panel_eol_nominal * 2.0 if deol_mode else float('inf')) + wire_loop_ohms
+    
+    tol_window = panel_eol_nominal * (panel_tolerance_pct / 100.0)
+    normal_min = panel_eol_nominal - tol_window
+    normal_max = panel_eol_nominal + tol_window
+    
+    is_normal_acceptable = (normal_min <= normal_resistance <= normal_max)
+    
+    return {
+        "wire_loop_resistance_ohms": round(wire_loop_ohms, 2),
+        "measured_normal_expected": round(normal_resistance, 2),
+        "measured_alarm_expected": round(alarm_resistance, 2),
+        "panel_acceptance_window": (round(normal_min, 2), round(normal_max, 2)),
+        "is_acceptable": is_normal_acceptable,
+        "recommendation": "OK" if is_normal_acceptable else "Wire resistance exceeds panel tolerance! Upsize to 20 AWG or 18 AWG."
+    }
+```
+
+### Archetype 3: Multimeter Field Diagnostic Workflow
+```markdown
+1. Disconnect zone loop wires from panel terminal Z1 and COM.
+2. Set digital multimeter to 20k Ω DC resistance range.
+3. Clip probes to black and red loop wires.
+4. Read resistance:
+   - Reading = 0 Ω: Direct short on cable or tamper circuit pinched.
+   - Reading = ~5.6k Ω: Loop is secure and healthy.
+   - Reading = ~11.2k Ω: Sensor is currently tripped (door open, motion active).
+   - Reading = O.L (∞ Ω): Broken conductor, disconnected terminal, or open tamper switch.
+5. Reconnect to panel and verify terminal voltage across Z1 and COM:
+   - Normal secure: 2.2V - 2.8V DC (on 5V pullup).
+   - Alarm: 3.5V - 4.1V DC.
+   - Tamper/Short: 0.0V DC.
+   - Cut/Open: 5.0V DC.
+```
+
+## The Pre-Emit Quality Gate Checklist
+
+Before emitting any alarm wiring advice, schematic, or resistor calculation:
+- [ ] **Placement Verification**: Explicitly mandate resistor placement at the remote detector, strictly barring panel-terminal stacking.
+- [ ] **Manufacturer Compliance**: Verified nominal EOL values match the specific panel model (Honeywell 2.0k, DSC 5.6k, Paradox 1.0k, etc.).
+- [ ] **Wire Gauge Compensation**: Calculated two-conductor wire loop resistance for distances $> 50$ meters.
+- [ ] **DEOL State Coverage**: Documented all 4 states (Normal, Alarm, Tamper Short, Tamper Open).
+- [ ] **Fire Circuit Distinction**: Confirmed burglary DEOL logic is never recommended for latching fire loops.
+- [ ] **Physical Connection Standards**: Specified soldered heat-shrink or B-connector crimps over raw tape twists.
+- [ ] **Zero Supervision Bypass**: Zero instructions provided to defeat or bypass loop supervision resistors.
+
+## Self-Correction & Verification Loop
+
+### Bad (Vibe-Coded AI Slop Output):
+> "To wire an alarm sensor, just twist the resistor onto the zone screw terminals on the panel board. A 1k resistor usually works for all panels. If you get a zone fault, just bypass the zone or short the wires together."
+*Problems: Fatal panel-terminal stacking, generic wrong resistor value, advises bypassing safety supervision, ignores tamper discrimination.*
+
+### Good (Production EOL Resistor Calculator Output):
+> For a **DSC PowerSeries Neo** panel using a **Double-EOL (DEOL)** PIR detector over an **80m run of 22 AWG** cable:
+> 1. **Resistor Placement**: Install two 5.6k $\Omega$ resistors (5% tolerance, 0.25W) strictly inside the PIR housing at the far end of the run.
+> 2. **Wiring Topology**:
+>    - Connect Tamper switch in series with the loop.
+>    - Connect first 5.6k $\Omega$ resistor ($R_{EOL}$) in series with the loop.
+>    - Connect second 5.6k $\Omega$ resistor ($R_{ALARM}$) in parallel across the NC Alarm relay contacts.
+> 3. **Wire Resistance Drop**: 80m of 22 AWG adds $2 \times 80 \times 0.053 = 8.48\ \Omega$. Total secure loop resistance will be $5,608.5\ \Omega$, well within DSC's $\pm 10\%$ acceptance window ($5,040\ \Omega$ to $6,160\ \Omega$).
+> 4. **Multimeter Diagnostic Verification**:
+>    - Secure: $5.61\text{k}\ \Omega$.
+>    - Walk-test (Alarm): $11.21\text{k}\ \Omega$.
+>    - Sensor cover removed (Tamper): $\infty\ \Omega$ (Open).
+>    - Crushed wire (Short): $8.5\ \Omega$ (Panel registers Tamper Short).
+
+## Limitations
+
+- EOL values, wiring topologies, and zone states are panel- and detector-specific. Use the installation manual and approved wiring diagram for the exact model; the examples are not universal specifications.
+- Work on alarm systems only with owner authorization and qualified personnel. Do not bypass supervision, disable an active alarm, or leave a protected site without a verified restored state.
+- Cable resistance and resistor tolerances are estimates. Measure the installed loop and confirm the panel's published acceptance ranges before changing configuration.