v0.2.1: docs: update README and TODO for git subtree workflow

Replace submodule instructions with git subtree approach:
- subtree add with --prefix=scripts
- named remote for convenience (git remote add repokit-common)
- pull/push commands for bidirectional sync
- note about existing scripts/ files needing temporary move

This reflects the proven setup tested with DazzleLink.

Author: djdarcy

README.md

@@ -1,20 +1,32 @@
 # git-repokit-common
 
-Shared scripts, hooks, and developer tools for DazzleTools projects. Consumed as a git submodule in `scripts/`.
+Shared scripts, hooks, and developer tools for DazzleTools projects. Consumed as a git subtree in `scripts/`.
 
 ## Quick Start
 
 Add to your project:
 
 ```bash
-git submodule add https://github.com/DazzleTools/git-repokit-common.git scripts/repokit-common
-bash scripts/repokit-common/install-hooks.sh
+# Add as a subtree at scripts/
+git subtree add --prefix=scripts https://github.com/DazzleTools/git-repokit-common.git main --squash
+
+# Add named remote for convenience
+git remote add repokit-common https://github.com/DazzleTools/git-repokit-common.git
+
+# Install git hooks
+bash scripts/install-hooks.sh
 ```
 
 Update to latest:
 
 ```bash
-cd scripts/repokit-common && git pull origin main
+git subtree pull --prefix=scripts repokit-common main --squash
+```
+
+Push local improvements back upstream:
+
+```bash
+git subtree push --prefix=scripts repokit-common main
 ```
 
 ## What's Included

TODO.md

@@ -1,8 +1,24 @@
 # Post-Setup TODO
 
-After adding `git-repokit-common` as a submodule or worktree, complete these steps:
+## Adding to Your Project (git subtree)
 
-## Required
+```bash
+# 1. Add repokit-common as a subtree in your scripts/ directory
+git subtree add --prefix=scripts https://github.com/DazzleTools/git-repokit-common.git main --squash
+
+# 2. Add a named remote so you don't type the URL each time
+git remote add repokit-common https://github.com/DazzleTools/git-repokit-common.git
+
+# 3. Future updates
+git subtree pull --prefix=scripts repokit-common main --squash
+
+# 4. Push local improvements back upstream
+git subtree push --prefix=scripts repokit-common main
+```
+
+Note: If you already have files in `scripts/`, move them out first, do the subtree add, then move them back. Git subtree requires an empty prefix directory on first add.
+
+## Required (after subtree add)
 
 - [ ] **Configure pyproject.toml**: Add `[tool.repokit-common]` section (hooks depend on this):
   ```toml
@@ -14,11 +30,11 @@ After adding `git-repokit-common` as a submodule or worktree, complete these ste
   private-patterns = ["private/", "local/", ".env"]
   ```
 - [ ] **Create `_version.py`**: Copy the version module template into your package directory and edit the initial version values
-- [ ] **Install hooks**: Run `bash scripts/repokit-common/install-hooks.sh`
+- [ ] **Install hooks**: Run `bash scripts/install-hooks.sh`
 
 ## Customize (as needed)
 
-- [ ] **VHS demo tapes** (`vhs/*.tape`): Replace `repokit-common` with your actual CLI command name
+- [ ] **VHS demo tapes** (`scripts/vhs/*.tape`): Replace placeholder CLI commands with your actual command name
 - [ ] **demo_render.py**: Rewrite with your project's output format (the existing content is a template/example)
 - [ ] **Pre-push hook**: Verify the auto-detected package directory is correct for your project
 
@@ -32,4 +48,5 @@ After adding `git-repokit-common` as a submodule or worktree, complete these ste
 
 - The hooks auto-detect your Python package directory (looks for `__init__.py` at the project root)
 - `sync-versions.py` reads config from `pyproject.toml [tool.repokit-common]` automatically
-- Update this submodule anytime: `cd scripts/repokit-common && git pull origin main`
+- `--prefix=scripts` must be used consistently for all subtree operations
+- Your project-specific scripts can coexist alongside repokit-common files in `scripts/`