coily lockdown writes .claude/settings.json without trailing newline, fighting end-of-file-fixer #135

New issue

Closed

opened 2026-05-28 07:01:15 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-05-28 07:01:15 +00:00

Owner

Problem coily lockdown writes .claude/settings.json without a trailing newline, fighting end-of-file-fixer.

After coily lockdown --apply --replace (or coily setup's recursive re-baseline), .claude/settings.json shows a \ No newline at end of file diff in any repo whose committed copy ends in a trailing newline:

-}
+}
\ No newline at end of file

In repos where the end-of-file-fixer pre-commit hook runs, the committed copy gets a trailing newline, but coily regenerates without one. Every coily upgrade / re-baseline re-dirties .claude/settings.json; the next commit re-adds the newline; the two tools fight forever.

Observed on coily v2.43.0 (Linuxbrew, kai-server). Repos showing only the newline diff after re-baseline: agentic-os-kai, cli-guard, coily, repo-recall.

Fix Have the lockdown renderer emit a trailing newline on settings.json (and check lockdown-deny.sh). Standard for generated files; removes the perpetual churn against end-of-file-fixer.

Surfaced while upgrading local coily 2.29.1 -> 2.43.0 and re-baselining lockdown across the coilysiren/* tree.

**Problem** coily lockdown writes `.claude/settings.json` without a trailing newline, fighting `end-of-file-fixer`. After `coily lockdown --apply --replace` (or `coily setup`'s recursive re-baseline), `.claude/settings.json` shows a `\ No newline at end of file` diff in any repo whose committed copy ends in a trailing newline: ``` -} +} \ No newline at end of file ``` In repos where the `end-of-file-fixer` pre-commit hook runs, the committed copy gets a trailing newline, but coily regenerates without one. Every coily upgrade / re-baseline re-dirties `.claude/settings.json`; the next commit re-adds the newline; the two tools fight forever. **Observed on** coily v2.43.0 (Linuxbrew, kai-server). Repos showing only the newline diff after re-baseline: agentic-os-kai, cli-guard, coily, repo-recall. **Fix** Have the lockdown renderer emit a trailing newline on `settings.json` (and check `lockdown-deny.sh`). Standard for generated files; removes the perpetual churn against `end-of-file-fixer`. Surfaced while upgrading local coily 2.29.1 -> 2.43.0 and re-baselining lockdown across the coilysiren/* tree.

coilysiren referenced this issue from coilyco-flight-deck/cli-guard

2026-05-28 07:06:04 +00:00

lockdown renders .claude/settings.json without trailing newline #32

coilysiren commented

2026-05-28 07:14:10 +00:00

Author

Owner

Root cause and fix are in cli-guard (the lockdown renderer): coilysiren/cli-guard#32, fixed in cli-guard@02aeb5b. The renderer now appends a trailing newline to .claude/settings.json, matching user_hook.go, with regression test TestBuildPlan_AfterEndsWithNewline.

This won't reach coily lockdown output until cli-guard is tagged and coily bumps its cli-guard dependency, rebuilds, and ships a new release. Leaving this open until a coily release carries the fix; closing cli-guard#32 as the code-level fix.

Root cause and fix are in cli-guard (the lockdown renderer): coilysiren/cli-guard#32, fixed in cli-guard@02aeb5b. The renderer now appends a trailing newline to `.claude/settings.json`, matching `user_hook.go`, with regression test `TestBuildPlan_AfterEndsWithNewline`. This won't reach `coily lockdown` output until cli-guard is tagged and coily bumps its cli-guard dependency, rebuilds, and ships a new release. Leaving this open until a coily release carries the fix; closing cli-guard#32 as the code-level fix.

coilysiren referenced this issue

2026-05-28 07:28:28 +00:00

eco/factorio --help tests fail on main with exit status 1 from go run subprocess #136

coilysiren referenced this issue from a commit

2026-05-28 07:29:16 +00:00

chore(deps): bump cli-guard to v0.1.0 for lockdown newline fix

coilysiren closed this issue

2026-05-28 07:29:16 +00:00

coilysiren referenced this issue

2026-05-28 07:32:46 +00:00

release automation: bump-formula fails every run and push did not trigger a new run #137

coilysiren referenced this issue from a commit