tinysocs-build-and-env

Rebuild TinySocs components from a clean checkout across C#, Python, and Inno Setup toolchains.

Updated Oct 12, 2025
One-click install
npx skills add https://github.com/lukefitzg/tinysocs --skill tinysocs-build-and-env-lukefitzg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tinysocs-build-and-env
Source: https://github.com/lukefitzg/tinysocs/tree/main/.claude/skills/tinysocs-build-and-env
Command: npx skills add https://github.com/lukefitzg/tinysocs --skill tinysocs-build-and-env-lukefitzg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building TinySocs from scratch involves a C# agent, multiple Python FastAPI services, ed25519 pack signing, and a Windows-only Inno Setup installer, each with non-obvious traps like silent compile-item exclusion and a YamlDotNet versus canonical-JSON split. This Skill documents verified build commands and known failure modes so you avoid rediscovering them. ## Core Features & Use Cases - C# Agent Build and Test: Run dotnet build, test, and win-x64 self-contained publish, including the explicit Compile Include allowlist trap that silently excludes new .cs files. - Python Services Setup: Create a venv, install with pip install -e ".[dev]", and run console scripts like tinysocs-feed, tinysocs-node, and the bot dashboard in demo mode. - Pack Signing and Migration: Generate ed25519 keys, sign rule packs with pack_sign.py, mint licence keys, and migrate v1 rules.yml to v2 packs. - CI Ground Truth: Reproduce ci.yml locally and understand known bugs like the build-installer.yml OpenSearch 2.18.0 versus 3.3.2 version mismatch and the missing xUnit step. - Use Case: You added a new Detection subdirectory to the agent and the build succeeds but your class is missing at runtime; this Skill tells you to add a Compile Include entry to the csproj. ## Quick Start Ask the assistant to walk you through building the TinySocs C# agent and running its xUnit tests on macOS from a clean checkout.

Frequently Asked Questions about tinysocs-build-and-env

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build and test the TinySocs C# agent?

Run dotnet build tinysocs.sln for a framework-dependent Debug build and dotnet test on the TinySocs.Agent.Tests project for the 70 xUnit tests. For release, use dotnet publish with -c Release -r win-x64 --self-contained, which cross-compiles on macOS but only runs on Windows.

Why is my new C# file not compiling in the agent project?

The csproj disables implicit globbing with Compile Remove for all .cs files and re-adds only named paths. A new top-level file or subdirectory is silently excluded until you add a matching Compile Include entry for it.

Can I build the TinySocs installer on macOS?

No, the Inno Setup compile step via ISCC.exe is Windows-only, and ISCC cannot compile from UNC paths. Everything else, including the win-x64 agent publish and Python services, builds on macOS.

Why is my edited pack.yml field not showing up at runtime?

The agent loads pack.yml.canonical, a sorted-key JSON sidecar, not the hand-edited YAML. Re-run pack_sign.py sign to regenerate the .canonical and .sig files after any edit.

Does TinySocs CI run the xUnit detection tests?

No, ci.yml runs ruff, mypy, and pytest, and the windows-test job only publishes the agent without executing dotnet test. The 70 xUnit tests only run when invoked locally.

How do I run the TinySocs dashboard locally without OpenSearch?

Run python -m tinysocs.api.bot --demo, which serves the dashboard at localhost:8090 with synthetic data. Demo mode sets TINYSOCS_DEMO_MODE=1 and requires no secrets or TLS certificates.