DD-181 Wave 2 followups: contract renames, pack rewrite, catalog fixes

[piersdd]

Migrated from the vault DEVFU register by the DD-422 sweep (frozen-index entry [055], DD-181 Wave 2 followups).

Context (register entry, verbatim)

DD-181 Wave 2 followups — (a) vultr-blade-mcp dns-v1 → dns-authoritative-v1 rename in stallari-plugin.yaml; (b) cloudflare-edge-platform.yaml multi-service pack rewrite; (c) controld conformance retest under protective-dns-v1; (d) onedrive not_supported catalog surfacing (needs FlexibleContract in build-catalog.js); (e) catalog count discrepancy (73 built vs 69 deployed — investigate dedup logic).

Acceptance criteria

Five heterogeneous items — triage recommendation (2026-07-16): dispatch (a) and (d) as agent work; (b) needs pack design, (c) needs a live controld run, (e) is an investigation spike. Split out sub-issues if any single item stalls the rest.

• (a) vultr-blade-mcp stallari-plugin.yaml: dns-v1 → dns-authoritative-v1 rename; catalog entry follows; validate green.
• (b) cloudflare-edge-platform.yaml rewritten as a multi-service pack; schema-validates; served catalog reflects it.
• (c) controld conformance retested under protective-dns-v1; result recorded in the catalog entry (conformance counts updated).
• (d) onedrive not_supported surfaced in the catalog — requires FlexibleContract handling in scripts/build-catalog.js.
• (e) 73-built-vs-69-deployed count discrepancy explained; dedup logic fixed or the intended dedup documented.

Issue closes when all five land (or are spun into their own tracked issues).

Blocked by

None - can start immediately

---

Acceptance criteria shaped by AI triage, 2026-07-16.

[piersdd]

Decision brief (AI triage, 2026-07-16) — routing call for the 5-item bundle.

Recommended routing:

• (a) vultr dns-v1 rename + (d) onedrive FlexibleContract surfacing → dispatch now as agent work (both bounded, single-repo-ish, testable).
• (b) cloudflare-edge-platform.yaml multi-service rewrite → needs pack design; keep ready-for-human until you sketch the target service set.
• (c) controld conformance retest under protective-dns-v1 → live vendor run; schedule alongside the next /harden-blade-style session.
• (e) 73-vs-69 catalog count discrepancy → investigation spike; cheap agent read-only dispatch any time.

Your move: approve the split and I'll cut (a)+(d) (and optionally (e)) into sub-issues labelled ready-for-agent, leaving this umbrella tracking (b)+(c).