bug: replicator init does not add .uf/replicator runtime files to .gitignore #85

Bug

replicator init creates the .uf/replicator/ directory and seeds cells.json, but does not add any .gitignore entries for runtime files produced by other commands.

Impact

When a user runs replicator serve, the log file .uf/replicator/replicator.log is created. Because no .gitignore entry exists, this file (and potentially database files) will be tracked by git in the user's project.

The replicator repo's own root .gitignore covers these patterns (lines 40-44), but those entries are not scaffolded into user projects by replicator init.

Steps to Reproduce

1. Run replicator init in a fresh git repo
2. Run replicator serve (creates .uf/replicator/replicator.log)
3. Run git status — the log file shows as untracked

Expected Behavior

replicator init should ensure the project's .gitignore includes entries for .uf/replicator/ runtime files:

.uf/replicator/*.log
.uf/replicator/*.db
.uf/replicator/*.db-shm
.uf/replicator/*.db-wal
.uf/replicator/*.lock

Actual Behavior

No .gitignore entries are written by replicator init. Runtime files get picked up by git.

Relevant Code

• cmd/replicator/init.go:41-58 — init implementation (no gitignore logic)
• cmd/replicator/serve.go:66 — log file creation
• Root .gitignore lines 40-44 — patterns that exist for the replicator repo itself but are not scaffolded