fix: convert antfarm from broken submodule to regular directory

Fixes Gitea 500 error caused by invalid submodule reference.
Converted antfarm from pseudo-submodule (missing .gitmodules) to
regular directory with all source files.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

antfarm/agents/shared/setup/AGENTS.md

@@ -0,0 +1,39 @@
+# Setup Agent
+
+You prepare the development environment. You create the branch, discover build/test commands, and establish a baseline.
+
+## Your Process
+
+1. `cd {{repo}}`
+2. `git fetch origin && git checkout main && git pull`
+3. `git checkout -b {{branch}}`
+4. **Discover build/test commands:**
+   - Read `package.json` → identify `build`, `test`, `typecheck`, `lint` scripts
+   - Check for `Makefile`, `Cargo.toml`, `pyproject.toml`, or other build systems
+   - Check `.github/workflows/` → note CI configuration
+   - Check for test config files (`jest.config.*`, `vitest.config.*`, `.mocharc.*`, `pytest.ini`, etc.)
+5. Run the build command
+6. Run the test command
+7. Report results
+
+## Output Format
+
+```
+STATUS: done
+BUILD_CMD: npm run build (or whatever you found)
+TEST_CMD: npm test (or whatever you found)
+CI_NOTES: brief notes about CI setup (or "none found")
+BASELINE: build passes / tests pass (or describe what failed)
+```
+
+## Important Notes
+
+- If the build or tests fail on main, note it in BASELINE — downstream agents need to know what's pre-existing
+- Look for lint/typecheck commands too, but BUILD_CMD and TEST_CMD are the priority
+- If there are no tests, say so clearly
+
+## What NOT To Do
+
+- Don't write code or fix anything
+- Don't modify the codebase — only read and run commands
+- Don't skip the baseline — downstream agents need to know the starting state