chore(gastown): promote gastown-staging to main

[jrf0110]

Summary

Single-commit batch from `gastown-staging` carrying a local-dev binding fix that was missed from the previous promotion:

• fix(gastown): point dev `GIT_TOKEN_SERVICE` binding at `git-token-service-dev` — `services/git-token-service/wrangler.jsonc` overrides its worker name to `git-token-service-dev` in `env.dev`, but gastown's `env.dev.services` binding still referenced the base `git-token-service` name. Wrangler's local dev registry does exact-name matching, so the binding showed `[not connected]` whenever both workers ran side by side. Every other consumer in the repo (`cloud-agent-next`, `security-sync`, `security-auto-analysis`) already uses `git-token-service-dev` in their `env.dev` block — gastown was the outlier.

Production binding (top-level `services`) is untouched; only the `env.dev` block was changed.

Verification

• Manually restarted `wrangler dev --env dev` for both `services/git-token-service` and `services/gastown` locally and confirmed the gastown binding now shows as connected instead of `[not connected]`.

Visual Changes

N/A (wrangler config only).

Reviewer Notes

• One-line change in `services/gastown/wrangler.jsonc` `env.dev.services[0].service`. No runtime code touched, no impact on the deployed production worker.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (3 files)

• services/gastown/container/src/process-manager.ts
• services/gastown/container/src/process-manager.test.ts
• services/gastown/container/vitest.config.ts

---

_{Reviewed by gpt-5.5-20260423 · 783,937 tokens}