Remove banned V (vlang); rewire repo-batcher to Zig

[hyperpolymath]

Summary

V (vlang) is now a banned language. Its functionality in repo-batcher
was already superseded by the Zig FFI layer (scaffoldia/repo-batcher/ffi/zig/),
so the V sources were orphaned.

• Deleted all 21 .v files — api/v/reposystem.v and the entire
  scaffoldia/repo-batcher/src/v/** CLI layer + V tests (~7,700 lines).
• Rewired repo-batcher/Justfile — build/build-dev/test/fmt
  now drive the existing ffi/zig project (zig build / zig build test
  / zig fmt); dropped v / v vet / v fmt invocations.
• CI: stripped *.v from dogfood-gate.yml in both copies
  (.github/ and rpa-elysium/.github/).
• Policy: added V (vlang) → Zig/Rust to the BANNED table in both
  .claude/CLAUDE.md and scaffoldia/.claude/CLAUDE.md.
• Docs: refreshed build-facing references in GETTING-STARTED.adoc
  and docs/ARCHITECTURE.adoc (toolchain install, structure tree, layer
  description) from V → Zig.

Out of scope / follow-ups

• Historical changelog records (IMPLEMENTATION-STATUS.md,
  OPERATIONS-EXPANSION-*.md) still mention V as point-in-time history;
  left as-is rather than rewriting dated logs.
• repo-batcher's CLI entrypoint was the V layer; the Zig layer is an
  FFI/execution library. A Zig (or Rust) CLI front-end is a separate
  reimplementation task, not done here.
• ReScript→AffineScript migration (and removal of vendored .ast
  BuckleScript artifacts) is a much larger, separate effort — explicitly
  NOT included here.
• Optional: add a .v blocker to the anti-pattern CI to enforce the new
  ban (policy updated; active enforcement not yet wired).

Test plan

• cd scaffoldia/repo-batcher && just build (ATS2 core + zig build)
• just test runs the Zig test steps
• dogfood-gate workflow parses (no *.v tokens)
• grep -rl '\.v$' returns nothing

https://claude.ai/code/session_01LKw5BvbbxFUWi9YMogGJTL

---

Generated by Claude Code