fix: address PR #30 review comments

CLAUDE.md:
- Fix "seems" → "seem" (subject-verb agreement) + add missing period
- Add missing period on line 86
- Fix "Fetch the git origin" → "Fetch from origin"
- Fix "errors was" → "errors were" + "ooriginating" → "originating"

.claude/settings.json:
- Add comprehensive force push deny patterns (+branch, mid-command --force/-f)
- Simplify Edit/Write allow rules (deny rules take precedence for sensitive paths)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: mikkeldamsgaard

.claude/settings.json

@@ -13,7 +13,10 @@
       "Bash(git push * master)",
       "Bash(git push * master *)",
       "Bash(git push --force *)",
+      "Bash(git push * --force *)",
       "Bash(git push -f *)",
+      "Bash(git push * -f *)",
+      "Bash(git push * +*)",
       "Bash(git reset --hard*)",
       "Bash(git clean -f*)",
       "Bash(git branch -D *)",
@@ -46,8 +49,8 @@
       "WebSearch",
       "Task",
 
-      "Edit(/**)",
-      "Write(/**)",
+      "Edit",
+      "Write",
 
       "Bash(git status*)",
       "Bash(git log*)",

CLAUDE.md

@@ -81,19 +81,19 @@ Agent execution constraints (for local runners / GH actions)
 - Avoid making assumptions without asking for confirmation.
 
 19) When running locally, prefer the mcp edit tool to direct file edits.
-- If issues arise where files seems unedited, alert the user before continuing
+- If issues arise where files seem unedited, alert the user before continuing.
 
-20) Prefer bash commands/scripts to python3 when investigating
+20) Prefer bash commands/scripts to python3 when investigating.
 
 Definition of implement issue
 - Find the issue in github issues.
 - If not found, inform the user.
 - If found:
-    - Fetch the git origin
+    - Fetch from origin
     - Create a branch with the issue number in the name from origin/main.
     - Implement the issue.
     - Run all e2e tests.
-    - If during implementation, obvious errors was found in the ooriginating issue, also add a comment to the issue about the fix.
+    - If during implementation, obvious errors were found in the originating issue, also add a comment to the issue about the fix.
     - If running from Claude Code or Claude Desktop:
       - Do NOT create a PR automatically.
       - Instead, present a summary of changes and let the user decide when to create the PR.