The Calculinux bring-up, both console-font builds, the GPL-2.0 text that belongs beside the 6x8 one, and the xiao-radio firmware kit move under scripts/picocalc/; the SPI bridge is scripts/uconsole/meshterm-spi-bridge. The folder's own README is gone: its per-file index is now a section of docs/hardware.md, next to the table that says which manual is yours. Every path in the manuals, NOTICE, CLAUDE.md, the tests, the package docstrings and the scripts' own headers follows. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
37 lines
1.1 KiB
Plaintext
37 lines
1.1 KiB
Plaintext
# Python
|
|
__pycache__/
|
|
*.py[cod]
|
|
*.egg-info/
|
|
build/
|
|
dist/
|
|
|
|
# Ignore all dot-directories (.venv, .pytest_cache, .ruff_cache, .vscode, ...)
|
|
.*/
|
|
# ...except the project's tracked Claude config. Private working notes stay out:
|
|
# settings.local.json is per-machine, and plans/ + housekeeping.md are internal
|
|
# planning that names hardware and unshipped ideas.
|
|
!.claude/
|
|
.claude/settings.local.json
|
|
.claude/scheduled_tasks.lock
|
|
.claude/plans/
|
|
.claude/housekeeping.md
|
|
# ...and except the GitHub configuration, which only works where GitHub looks for
|
|
# it. The catch-all above hid it silently: a workflow that is never committed is
|
|
# indistinguishable from one that never runs.
|
|
!.github/
|
|
|
|
# Other virtual environments
|
|
venv/
|
|
|
|
# MeshTerm runtime data
|
|
*.db
|
|
output/
|
|
|
|
# Developer environment: the machine-specific half of the .claude/ skills (device
|
|
# addresses, logins, the local venv path). .dev.env.example is tracked and shows the shape.
|
|
.dev.env
|
|
|
|
# Built radio firmware (scripts/picocalc/xiao-radio/build-firmware.sh writes it here)
|
|
scripts/picocalc/xiao-radio/*.uf2
|
|
scripts/picocalc/xiao-radio/_meshcore-build/
|