docs: add post-merge hooks and document git hooks in CLAUDE.md/AGENTS.md

Add post-merge hook to auto-sync submodule and run bun install after
pulls. Document all git hooks (pre-commit, pre-push, post-merge) in
CLAUDE.md and AGENTS.md. Simplify the post-pull instructions now that
the hook handles submodule sync and dependency install automatically.

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

Author: pRizz

.githooks/post-merge

@@ -0,0 +1,10 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+REPO_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
+
+echo "post-merge: syncing submodule..."
+git -C "$REPO_ROOT" submodule update --init --recursive
+
+echo "post-merge: installing dependencies..."
+bun install --cwd "$REPO_ROOT"

AGENTS.md

@@ -37,6 +37,14 @@ just run <args>  # Run CLI with arguments (e.g., just run status)
 just dev         # Start local runtime (local submodule + cached sandbox rebuild)
 ```
 
+## Git Hooks
+
+This repo uses git hooks (wired via `git config core.hooksPath .githooks`, set up by `just setup`):
+
+- **pre-commit** — Syncs README to npm packages, guards against unpublished submodule pins, runs cfn-lint on CloudFormation changes.
+- **pre-push** — Validates the opencode submodule commit is published.
+- **post-merge** — After every `git pull`, automatically syncs the submodule and runs `bun install`. No manual action needed.
+
 ## README Badge Sync
 
 `README.md` (superproject) and `packages/opencode/README.md` (submodule) use distinct generated badge blocks for different audiences.
@@ -83,7 +91,7 @@ The `scripts/set-all-versions.sh` script handles version updates automatically.
   - Rebase pull from `main` first (for example: `git pull --rebase origin main`).
   - Then push to `main`.
 - After committing and pushing changes in the `packages/opencode/` submodule, run `just update-opencode-commit` in the superproject to update the Dockerfile's `OPENCODE_COMMIT` pin. Commit and push the resulting Dockerfile change to `main`.
-- After pulling the superproject, run `git submodule update --init --recursive` to sync the submodule working tree, then run `just update-opencode-commit`. If the Dockerfile changed, commit and push the update to keep the submodule pointer and Dockerfile `OPENCODE_COMMIT` pin in sync.
+- After pulling the superproject, the `post-merge` hook automatically syncs the submodule and runs `bun install`. Then run `just update-opencode-commit` — if the Dockerfile changed, commit and push the update.
 - **Resolving `OPENCODE_COMMIT` merge conflicts:** If a rebase or merge produces a conflict in the Dockerfile's `OPENCODE_COMMIT` line, do not manually pick a SHA. Instead, accept either side to clear the conflict markers, then run `just update-opencode-commit` to set the correct value from the current submodule state.
 
 ## Working with Git Worktrees and Submodules

CLAUDE.md

@@ -37,6 +37,14 @@ just run <args>  # Run CLI with arguments (e.g., just run status)
 just dev         # Start local runtime (local submodule + cached sandbox rebuild)
 ```
 
+## Git Hooks
+
+This repo uses git hooks (wired via `git config core.hooksPath .githooks`, set up by `just setup`):
+
+- **pre-commit** — Syncs README to npm packages, guards against unpublished submodule pins, runs cfn-lint on CloudFormation changes.
+- **pre-push** — Validates the opencode submodule commit is published.
+- **post-merge** — After every `git pull`, automatically syncs the submodule and runs `bun install`. No manual action needed.
+
 ## README Badge Sync
 
 `README.md` (superproject) and `packages/opencode/README.md` (submodule) use distinct generated badge blocks for different audiences.
@@ -83,7 +91,7 @@ The `scripts/set-all-versions.sh` script handles version updates automatically.
   - Rebase pull from `main` first (for example: `git pull --rebase origin main`).
   - Then push to `main`.
 - After committing and pushing changes in the `packages/opencode/` submodule, run `just update-opencode-commit` in the superproject to update the Dockerfile's `OPENCODE_COMMIT` pin. Commit and push the resulting Dockerfile change to `main`.
-- After pulling the superproject, run `git submodule update --init --recursive` to sync the submodule working tree, then run `just update-opencode-commit`. If the Dockerfile changed, commit and push the update to keep the submodule pointer and Dockerfile `OPENCODE_COMMIT` pin in sync.
+- After pulling the superproject, the `post-merge` hook automatically syncs the submodule and runs `bun install`. Then run `just update-opencode-commit` — if the Dockerfile changed, commit and push the update.
 - **Resolving `OPENCODE_COMMIT` merge conflicts:** If a rebase or merge produces a conflict in the Dockerfile's `OPENCODE_COMMIT` line, do not manually pick a SHA. Instead, accept either side to clear the conflict markers, then run `just update-opencode-commit` to set the correct value from the current submodule state.
 
 ## Working with Git Worktrees and Submodules

packages/core/src/docker/Dockerfile

@@ -553,7 +553,7 @@ COPY --chown=opencoder:opencoder packages/opencode /tmp/opencode-local
 # Update it by running: ./scripts/update-opencode-commit.sh
 RUN set -eux; \
     OPENCODE_COMMIT_OVERRIDE="${OPENCODE_COMMIT:-}"; \
-    OPENCODE_COMMIT="c07c9b9e9579651831eb8295db5227b8fcef1071"; \
+    OPENCODE_COMMIT="9fd774b0238b11b2d2eb646b2d0122da8689d274"; \
     if [ -n "${OPENCODE_COMMIT_OVERRIDE}" ]; then OPENCODE_COMMIT="${OPENCODE_COMMIT_OVERRIDE}"; fi; \
     rm -rf /tmp/opencode-repo; \
     if [ "${OPENCODE_SOURCE}" = "local" ]; then \