feat(standards): add Drone CI standard (PyPI package + Docker deployment)

Document the two `.drone.yml` shapes used across the org, derived from the
repos:

- Type A `python-lib.yaml`: build-and-publish-pypi + backfill-pypi-from-tags
- Type B `service-docker.yaml`: build-and-deploy-service + build-and-deploy-site

- add reference page `10_drone_pipelines`
- vendor `src/templates/drone/` into the MCP bundle (`drone.json`)
- expose `registry://drone` + `list_drone_templates` / `get_drone_template`
- wire `build.py` to vendor drone templates; rebuild nav/index (14 modules)

standards/src/lib/index.md

@@ -14,6 +14,7 @@ patterns, and the internal library catalog that agents consult while coding.
 - **Worker & Progress** — queued work, progress reporting, and visibility.
 - **Human-in-the-Loop** — guardrails and approvals inside automations.
 - **Infra Adapters** — how infrastructure connects without leaking into domain.
+- **Drone Pipelines** — the two CI shapes: a PyPI package or a Docker deployment.
 - **Genericity Matrix** — what is library-backed, template-provided, or authored.
 - **Auth Integration** — consuming the shared auth-server service (spec-driven,
   no auth code).