The developer environment hides where dotfiles hide

dev.env and dev.env.example become .dev.env and .dev.env.example, and the five
skills that name them follow. The .gitignore rule takes the dot too; it matches
the exact name, so the example stays tracked while the real one stays out.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

.dev.env.example

@@ -0,0 +1,28 @@
+# MeshTerm developer environment — the machine-specific half of the .claude/ skills.
+#
+# Copy to `.dev.env` (gitignored) and fill in your own values. Nothing in here is read by
+# the app: `meshterm` is configured by `config.toml` and its own `MESHTERM_*` variables.
+# These are only for driving *your* hardware from a dev session, so every name is
+# `DEV_`-prefixed and cannot collide with the app's.
+#
+#   set -a; . ./.dev.env; set +a      # sh/bash
+#   Get-Content .dev.env | ...        # or just read the values; nothing sources it for you
+
+# --- this workstation ---------------------------------------------------------------
+# Full path to the venv interpreter, so a skill can run the app without an install step.
+DEV_VENV_PYTHON=/path/to/MeshTerm/.venv/bin/python
+
+# --- the PicoCalc / Luckfox Lyra profiling device -----------------------------------
+# Reachable over the LAN; see the `profile-picocalc` skill for what is done with it.
+DEV_PICOCALC_HOST=192.0.2.10
+DEV_PICOCALC_USER=youruser
+DEV_PICOCALC_SSH_KEY=~/.ssh/your_key_ed25519
+# Fallback only — key auth is installed. Rotate this if it ever reaches a shared machine.
+DEV_PICOCALC_PASSWORD=changeme
+# Where the repo is checked out on the device (a `pip install -e .` tree).
+DEV_PICOCALC_REPO=/home/youruser/MeshTerm
+
+# --- BLE test companions ------------------------------------------------------------
+# Two MeshCore companions to verify against: one paired/PIN-protected, one open.
+DEV_BLE_COMPANION_PAIRED=MeshCore-Example
+DEV_BLE_COMPANION_OPEN=Example-Open