buenosairesam 74f03566f1 Ignore client rigs at the repo root, before rig's tree lands
A rig is a copy of rig/ renamed after the environment it models, so its k8s
files spell out a real architecture — the one thing that must not be committed
here. rig/.gitignore already refuses them, but only within rig/: a copy is a
SIBLING of rig/, where that file has no reach. spr had no rule at all, so the
first `git add -A` after the fold would have committed one.

Anchored at the root, and the negation names the full path because `*-rig/` is
unanchored and would otherwise match rig/sample-rig too.

Verified both ways: a file under client-rig/ is ignored, one under
rig/sample-rig/ is not.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-19 02:54:45 -03:00
2026-08-11 07:30:27 -03:00
2026-08-11 07:30:27 -03:00
2026-08-11 07:30:27 -03:00
2026-04-12 12:34:25 -03:00
2026-08-11 07:30:27 -03:00
2026-08-11 07:30:27 -03:00
2026-08-10 09:19:19 -03:00
2026-08-11 07:30:27 -03:00
2026-05-06 12:04:19 -03:00
2026-08-10 09:19:19 -03:00

soleprint

Development workflow platform. Wraps existing applications with tools, testing, and documentation — without touching source code.

Cada paso deja huella.


Docs

cd docs && python -m http.server 8080

Visit http://localhost:8080. Start with Concepts for the mental model, then Quickstart to run your first room.

Description
No description provided
Readme 13 MiB
Languages
Python 54%
HTML 21.7%
Shell 17.1%
CSS 2%
Vue 1.5%
Other 3.6%