add guardrails to specific apis/types to ensure paths are right type

now that the specific apis are available- we should add guardrails and type safety to ensure that folks have passed the path type they tell us they passed. the agnostic api is stringly typed to give input flexibility, but the specific APIs should use Path and URL

Start by locating the specific APIs and their Path and URL types in the repository, then compare them with the agnostic API's stringly-typed path handling. Add checks so each specific API enforces the path type it documents, and verify that incorrect path types are rejected while valid Path and URL inputs continue to work.

Written by the indexing model from the issue text.