feat: update init-hooks.ts to write YAML config (GIT-91)

[TonyCasey]

Summary

• Create .git-mem/ directory if it doesn't exist
• Write config as YAML to .git-mem/.git-mem.yaml
• Update path references and console messages
• Remove entire .git-mem/ directory in remove mode
• Parse existing config as YAML when merging

Closes GIT-91

Test plan

• npm run pre-commit passes (type-check + lint)
• All 529 tests pass (438 unit + 91 integration)

🤖 Generated with Claude Code

Summary by CodeRabbit

• Refactor

  • Configuration storage moved to a YAML file inside the tool's config directory; install now ensures the config directory exists and safely merges existing settings into defaults. Removal cleans up the entire config directory and updates install/remove messaging to reference the new YAML path.

• Bug Fixes

  • Configuration loader returns defaults when the config is missing or unparseable, preventing errors.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

📝 Walkthrough

Walkthrough

Replaces per-repo hook config file .git-mem.json with a YAML file at .git-mem/.git-mem.yaml. Updates init/remove flows and loader docs to read/write YAML, ensure/remove the .git-mem/ directory, and deep-merge defaults with existing YAML config; adjusts messaging accordingly.

Changes

Cohort / File(s)	Summary
Hook Configuration Migration src/commands/init-hooks.ts	Switches hook config storage to YAML at .git-mem/.git-mem.yaml: adds YAML parse/stringify imports, uses getConfigDir/getConfigPath, ensures .git-mem/ directory creation, reads existing YAML, deep-merges defaults, writes YAML, and removes the directory on uninstall (rmSync). Updates log messages and next-step hints to the new path.
Loader docs update src/infrastructure/services/HookConfigLoader.ts	Updates header/docstring to state configs are read from .git-mem/.git-mem.yaml and that loader returns defaults when the file is missing or parsing fails; implementation unchanged.
Doc comment update src/domain/interfaces/IHookConfig.ts	Updates top-level documentation to reference .git-mem/.git-mem.yaml instead of .git-mem.json; no interface/type changes.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• test: integration tests for hook entry points (GIT-58) #27: Tests interact with init-hooks/config logic that previously read/wrote .git-mem.json; likely must be updated for YAML and new path.
• feat: unified git-mem init command (GIT-61) #28: Modifies src/commands/init-hooks.ts and helper utilities — likely overlaps with the init-hooks YAML migration and path changes.
• chore: add yaml dependency (GIT-88) #59: Introduces/updates the YAML dependency or related parsing utilities used by this migration.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating init-hooks.ts to use YAML configuration instead of JSON. It is specific, concise, and clearly communicates the primary objective of the changeset.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch git-91

---

No actionable comments were generated in the recent review. 🎉

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@src/commands/init-hooks.ts`:
- Around line 12-17: The file HookConfigLoader.ts contains stale doc comments
mentioning the old JSON filename; update those comment lines to reference the
current YAML filename and behavior—replace occurrences of ".git-mem.json" with
".git-mem.yaml" and adjust any mention of JSON parsing to indicate YAML parsing
(e.g., reference parseYaml or YAML migration). Ensure comments near the
HookConfigLoader class and its CONFIG_FILE constant (and any doc text around
methods that describe returning defaults on parse errors) reflect the YAML
migration and the non-throwing error handling semantics.
- Around line 273-283: parseYaml can return null, so coercion is needed before
passing parsed YAML into deepMergeGitMemConfig: update the existingGitMemConfig
assignment (the block that calls parseYaml and sets existingGitMemConfig) to
treat null or non-object results as an empty object (e.g., if parseYaml(...)
returns null or a non-plain-object, set existingGitMemConfig = {}); ensure this
change references the symbols parseYaml, existingGitMemConfig,
deepMergeGitMemConfig, buildGitMemConfig and writeFileSync in
src/commands/init-hooks.ts, and apply the identical guard in the analogous code
in src/commands/init.ts.