Vigilante issue implementation on bazel

Vigilante Bazel Issue Implementation

Focus

• Read the prompt for the detected stack, workspace hints, and shared local-service contract before changing code.
• Limit edits and validation to the affected Bazel targets unless broader changes are required.
• If local services are required, call vigilante-local-service-dependencies first and then use the shared docker-compose-launch contract instead of writing ad hoc Compose logic.

Workflow

• Follow the base vigilante-issue-implementation-on-monorepo workflow for issue comments, validation, push, and PR creation, including stacked base-branch detection (Base branch: directive in the issue body).
• Use vigilante commit for all commit-producing operations. Do not use git commit or GitHub CLI commit flows directly.
• Any commit or amend must preserve the user's existing git author, committer, and signing configuration. Commit on behalf of the user and do not overwrite git config with a coding-agent identity.
• Do not add Co-authored by: trailers or any other agent attribution for Codex, Claude, Gemini, or similar coding-agent identities.
• Use Bazel-native target commands when they exist and match the touched code.
• Keep service startup scoped to the assigned worktree and only for implementation or test dependencies.