Decide between a resolved java.net.URL and a deconstructed request URL model

[OmarAlJarrah]

Problem (decision/spike)

Request stores a single resolved java.net.URL (Request.kt:139). Structured URL manipulation (query params, path templating) has nowhere to live, forcing string surgery elsewhere. Worth resolving pre-1.0.

Proposed change

Prototype a deconstructed URL model (scheme/host/port/path-segments/query) while preserving the current DNS-free equality (url.toExternalForm(), Request.kt:52-71 — keep this; java.net.URL.equals does blocking DNS). Record the decision in docs/architecture.md.

Acceptance

• Decision recorded with rationale
• DNS-free equality preserved by whichever model wins

Blocks the QueryParams work.

Dependencies

• Blocks Build a first-class QueryParams multimap and remove the QueryParam stub #28 — QueryParams multimap (and transitively Define a minimal OperationParams SPI feeding the context chain #57 → Generate two-tier raw/cooked service methods #55 / Typed page classes that rebuild typed params, not URL strings #56)

---

Priority: high · Effort: large