Add Xquik REST example and encode path params

[kriptoburak]

Summary

• add a REST header-auth example that points API Agent at Xquik's public OpenAPI specification
• cover an OpenAPI 3.1 Xquik search endpoint, optional parameter filtering, and both supported auth schemes
• percent-encode REST path parameters so reserved characters, Unicode, and exact dot segments cannot alter route structure
• document the path-encoding correction in the changelog

Independent Repository Fix

The REST URL builder previously inserted path parameter values verbatim. Values containing slashes could change path segments. Exact . and .. values could also be normalized by URL joining and change the requested route. The client now percent-encodes substituted values, explicitly encodes dot-only segments, and includes focused regression coverage for slashes, spaces, plus signs, Unicode, . and ...

Duplicate Check

• checked existing open and closed PRs in agoda-com/api-agent for Xquik and related package names

Validation

• Python 3.11 and 3.12
• uv lock --check
• uv run ruff check api_agent/ tests/
• uv run ruff format --check api_agent/ tests/
• uv run ty check
• uv run pytest tests/ -q - 344 passed on each Python version
• git diff --check

Xquik is an independent third-party service. Not affiliated with X Corp. "Twitter" and "X" are trademarks of X Corp.

[kriptoburak]

Re-audit cleanup is live at signed head 65bb954. It restores 6 unrelated README formatting lines to upstream wording, leaving the Xquik OpenAPI example and independent path-encoding fix focused. Python 3.11 and 3.12 each pass 344 tests, Ruff, formatting, type checks, lockfile validation, and git diff --check. GitHub run 30499699426 contains 0 jobs and awaits maintainer workflow approval.