nomograph-kit 0.14.1

Verified tool registry manager -- manages developer toolchains from git-based registries
/target
/.cargo
/.rustup
*.bundle
checksums-*.txt
checksums.txt
*.sbom.cdx.json

# Fixtures seeded by jig agent-shape runs. Regenerated deterministically
# by scripts/agent-shape-fixture.sh; the output has no value tracked.
fixtures/

# Runtime jig stdout — verbose per-trial console log. Reports + checkpoints
# (.json / .md / .checkpoint.jsonl) are tracked; the runlog is not.
agent-shape-reports/*.runlog

# .agent/skills compat symlink: regenerated by `make agent-skills-symlink`.
# Intentionally untracked so external tools that rewrite symlinks (e.g.
# certain rune sync versions) cannot commit an absolute target. The
# symlink is the relative form `.agent/skills -> ../.claude/skills`.
.agent/skills

# `.claude/skills/` is materialized by `rune sync` from the source-of-
# truth registry (nomograph/runes). Tracking the synced copy creates a
# drift class where every rune update produces a "sync" commit on this
# repo, and the committed copy can fall behind the registry between
# syncs. Following the same pattern rune itself uses: gitignore the
# whole directory; `.claude/rune.lock` (which is tracked) pins which
# registry version each skill came from.
.claude/skills/

# `.claude/` is local-only: rune subscriptions, lockfile, and synced skill
# content are all per-developer state. Run `rune setup` then `rune sync` on
# a fresh clone to materialize.
.claude/
AGENTS.md