Add synchronous ADK tools

Proto comments become the model-facing tool description and JSON Schema. Handlers run in-process via ADK functiontool; the same service methods can later back gRPC if you register them.

Before creating any new package, search the build module for existing tools wiring using discovery signals (MyTools, NewTool, ToolsService). Extend existing packages rather than creating parallel ones. Do not refactor the user's layout to match templates. Templates provide greenfield defaults for new projects only.

Runtime Context

This skill may be loaded with an <alis-runtime-context> block injected at the top of these instructions by the Alis Build MCP LoadSkill handler. The handler reads alis.context.requires below and uses it as the read_mask on GetContext — the block carries only those fields.

Resolution order — when discovering workspace values before edits:

1. Resolve script — bash scripts/resolve-alis-workspace.sh --json (pass --cwd when the working directory differs from the target neuron). Prefer script output when a field is present.
2. <alis-runtime-context> — for any read-mask field still missing after the script, use the block verbatim. Do not re-derive or ask the user to confirm values already provided.
3. MCP — ListLandingZones -> GetLandingZone -> ViewProduct(lz, product) for neuron lists, versions, and environments. Use CloneProduct / PullDefine for canonical clone paths. Never invent environment IDs.
4. Neuron anchors — nearest go.mod under workstations.build_repos; tools.proto under workstations.define_repos.
5. Ask user — Smallest missing piece only.