Revert "chore(agents): reconcile scaffolded output + Windows git exec bit"

This reverts commit 4c00709. Both rules were too project-specific for
global memory: the packwiz url add nuance only applies to the modpacks
repo s pack scaffolding, and the Windows exec-bit / pre-commit hook
interaction only matters in repos that wire that hook. Moving the
narrower versions to marcusk-studio/modpacks AGENTS.md instead.

Author: ChipWolf

home/dot_agents/AGENTS.md

@@ -12,7 +12,6 @@ These constraints are unconditional. Apply them without being asked.
 
 - **No em dashes.** Use commas, colons, or restructure the sentence. Never generate inline `—` or `—` as punctuation. (Markdown horizontal rules: `---` alone on a line is fine.)
 - **Never guess schemas or APIs.** Read the authoritative source first: Go structs, official docs, or the project's own examples. Blog posts and AI-generated examples are not acceptable.
-- **Reconcile scaffolded output with repo conventions before committing.** When a CLI generates files (`packwiz url add`, `cargo init`, framework generators, etc.), diff its output against an existing peer in the repo before staging. Tools use their own defaults for fields like `side`, `hash`/`hash-format`, field order, license header, line endings, exec bit; those defaults rarely match a specific repo's convention. Hand-edit the deviations, wrap the tool, or rerun with the right flags. Do not stage raw scaffolded output just because the tool reported success.
 - **Verify a dependency supports the target platform before designing around it.** Before locking in a spec that depends on a third-party tool on a specific OS, confirm artifacts and source actually support that OS: run `gh release view --json assets` to see what's published, check the upstream CI matrix for the OSes it builds, and grep the source for OS-specific imports or build tags. Project names and descriptions don't imply cross-platform binaries; many "general" tools are Linux-only at the artifact level even when the README sounds portable.
 - **Diagnose from logs, not theory.** When investigating a failure (CI, runtime, hang, regression), the last lines of output before the failure are ground truth, not a guess based on which script's name matches your current hypothesis or which prior bug looked similar. If the visible log doesn't pin the cause, add a diagnostic and re-run rather than speculate further. When reporting findings, mark claims as observed ("log line N says X") versus suspected ("I think Y because…") and never let suspicion harden into assertion without evidence.
 - **Clone, don't curl.** When reading another repository's source, `git clone` first and read locally. Never `curl` GitHub API endpoints or `curl` raw file URLs to read source, even when docs don't render. (Using `WebFetch` for public documentation pages is fine.)
@@ -67,7 +66,6 @@ Always edit the source, not the deployed file. When updating any memory file: re
 - On Windows, when admin rights are required, launch elevated commands with `Start-Process -Verb RunAs` instead of failing back to manual instructions.
 - On Windows, use the Bash tool (not PowerShell) for POSIX-style commands like `grep`, `find`, `head`, `tail`, and path operations that use forward slashes. Use PowerShell only when you need Windows-native cmdlets, `$env:` variables, or paths with backslashes that POSIX tools cannot handle.
 - On Windows, POSIX-style paths like `/tmp/...` resolve only inside the Bash tool. Native filesystem tools (read/edit/write/grep/glob in any agent harness) use Windows file APIs and need Windows-style paths (`C:\...` or `C:/...`). When a Bash command reports a canonical path (e.g. `Cloning into 'C:/Users/.../Temp/repo'`), use that path for subsequent tool calls; do not reuse the `/tmp/` shortcut.
-- On Windows, the filesystem exec bit does not round-trip to git's index when scripts are created via the Write tool or `chmod +x` against a fresh worktree. After creating any executable script (shell, Python, etc.), run `git update-index --chmod=+x <path>` so the bit travels with the commit. Otherwise pre-commit's `check-shebang-scripts-are-executable` hook (or the Linux runner that invokes the script) will fail in CI.
 
 ---