Spec + plan for the edgezero HTTP-layer + ts-cli-next convergence

[prk-Jr]

Summary

• Purpose: the HTTP-layer (runtime) half of adopting edgezero stackpop/edgezero#269 in trusted-server. Docs phase — a breaking-API finding + an implementation plan — before code lands.
• Key finding (compiler-verified): the only forced code break reaching us is Body::into_bytes() → Option — 18 sink bindings (8 prod + 10 test), all in trusted-server-core; the bespoke platform/ layer insulates everything else.
• Convergence with feature/ts-cli-next (spec §12): that branch is not just CLI — it already implements the end-to-end Fastly config-store migration (same As a buyer, I want the first bid request to include IAB cohorts, signals, and synthetic ID #269 pin, the Body fixes via graceful ok_or_else, store ids, the config_payload flatten/hash contract, and runtime Settings-from-store load). So a parallel repin is redundant. The plan now builds on his branch and closes the runtime gaps: seed-before-serve hardening (unseeded store → actionable 503, not an opaque 500), secrets/KV wiring, non-Fastly build, and the runtime-config-store spec his CLI design references but never wrote.
• Why based on PR14: the branch is cut off PR14 (where trusted-server starts consuming the edgezero primitives As a buyer, I want the first bid request to include IAB cohorts, signals, and synthetic ID #269 touches), keeping this diff to just the docs.

Docs-only PR (finding spec + plan). Reviewed across multiple rounds (incl. plan-document-reviewer); the empty-store behavior, sink set, and his-branch facts are verified against source.

Changes

File	Change
docs/superpowers/specs/2026-06-16-edgezero-269-repin-breaking-api-finding.md	Finding: #269 breaking-API surface, compiler-verified build (§10), stacked-branch impact (§11), ts-cli-next convergence (§12).
docs/superpowers/plans/2026-06-17-edgezero-269-repin.md	HTTP-layer plan: Phase 0–5, decisions D1–D6, runtime hardening, Appendix A (sink reference) + Appendix B (minimal-repin fallback).

Closes

n/a — docs-only planning PR (issue linking skipped by request).

Test plan

• Docs format: cd docs && npm run format — "All matched files use Prettier code style!"
• Rust/JS gates — n/a (no code changed)

Checklist

• Changes follow CLAUDE.md conventions
• No secrets or credentials committed
• No unwrap() in production code — n/a (docs)
• Uses tracing macros — n/a (docs)
• New code has tests — n/a (docs)