vwf-stack-adapter plugins

Cloudflare stack plugin for vwf — **scope is deliberately parked**. It currently covers **Zero Trust Access** only: putting a project that must not be publicly reachable behind an identity-aware proxy on its own hostname, independent of which cloud actually hosts it. Workers, Pages, R2, D1, KV, Durable Objects, Queues, Images and Stream are **not** offered yet and arrive under their own dedicated plan — so the menu says what it does not cover rather than coming back quietly short. Implements the vwf stack-adapter contract.

Google Cloud stack plugin for vwf — the judgment layer an SDK reference cannot give you: which service to pick and when it stops being the answer, how each one bills and the traps that multiply it, which services have local emulators (and where they lie), and least-privilege IAM shapes. Covers the full Firebase suite plus Cloud SQL, AlloyDB, Memorystore, Bigtable, BigQuery, Pub/Sub, Cloud Tasks, Scheduler, Eventarc, Workflows, Cloud Storage, Cloud Run, GKE, Artifact Registry, Cloud Deploy, Cloud Armor, VPC, DNS, Load Balancing, CDN, KMS, Backup & DR, reCAPTCHA Enterprise and Vertex AI. Observability is OpenTelemetry only — GCP services appear as OTLP sinks, never as vendor SDKs. Implements the vwf stack-adapter contract.

The principles-driven stack materializer — implements the vwf stack-adapter contract with a dispatch rule: a technology a shipped pack covers is copied from the pack; anything uncovered is generated (Context7 research → vwf's principles catalog → the stackgen-skill-reviewer gate). Both paths land directly in the repo's committed .claude/ tree — skills, agents, hooks and rules only, structured per a closed kind vocabulary, recorded in a lockfile — editable and plugin-independent for collaborators. Re-sync is explicit and diffed, never silent. Waves A–C landed 21 packs and 19 bundles across seven kinds; Wave D adds the eighth kind, deploy-target, whose container-image pack is the curated answer the container-generic bundle used to generate, assets/artifact-doctrine.md — the host rules deciding whether a generated skill, agent or hook is valid at all — and the ninth kind, design-tool, whose three packs land vwf's design adapters at fixed names in the repo's own .claude/. Two tool axes (design, cicd) let a pack be reached by the config token that selects it, which is what rescued a CI pack no menu could offer.