docs(s-65): post-ship doc sweep for the S-64 watcher#100
Merged
Conversation
Five surfaces had stale or actively-misleading framing of the dotfiles maintenance workflow after S-64 shipped: - `docs/llm-dotfiles.md`: literal "No daemon, no watcher" line is now false. Replaced with a section explaining the watcher's complement to `/dotfiles-sync`. - `README.md`: pitch + cheat sheet + two-layer-model section now name the watcher. New cheat-sheet row points at `dotfiles watch install`. - `install.sh`: Next-steps block gets a step 5 "Optional: dotfiles watch install" in both gum-styled and plain-fallback branches. - `home/dot_claude/commands/dotfiles-sync.md`: Step 2 "Scan for drift" now opens with a paragraph setting the expectation that empty Drift sections are the steady state on watcher-equipped machines (not a signal something's broken). - `docs/decisions/006-auto-commit-workflow.md`: appended an "Exception" section explaining why the S-64 watcher deliberately breaks the commit-on-change default (no human authored the edit; review gate needs to live at `git diff`; public repo means daemon commits are higher-risk). New section 6 in `tests/dotfiles-watch.sh` (7 grep cases) locks the post-state in tests. Full suite is now 17/17 on Mac mini (up from 10/10). Two edits got clobbered mid-PR by stale Zed buffers re-saving (per the `zed-clobbers-claude-edits` pattern). Caught by section-6 grep tests failing on first run; re-applied with immediate post-edit `grep` verification before commit. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Five surfaces had stale or actively-misleading framing after S-64 shipped:
docs/llm-dotfiles.mdL276/dotfiles-syncREADME.mdpitch + cheat sheet + how-it-works/dotfiles-synconlyinstall.shNext stepshome/dot_claude/commands/dotfiles-sync.mdStep 2docs/decisions/006-auto-commit-workflow.mdgit diff-> public repo means daemon commits are higher-risk)Full design in
docs/specs/S-65-dotfiles-watcher-doc-sweep.md.Test plan
bash tests/dotfiles-watch.sh-- 17/17 pass (was 10/10; +7 new docs cross-reference cases in new "Section 6").home/dotfiles-watcher.md+home/.chezmoiignorework in the working tree (explicitgit addper-file).Notes
install.shandhome/dot_claude/commands/dotfiles-sync.mdwere silently clobbered by stale Zed buffers re-saving mid-PR. Caught by the section-6 grep tests failing on first run; re-applied with immediate post-editgrepverification before committing. Matches thezed-clobbers-claude-editsmemory pattern.🤖 Generated with Claude Code