[armando-rodriguez-cko]

Summary

Security hardening of path parameters.

Changes

• Path parameters containing /, \ or ASCII control characters are now rejected with a ValueError before any request is sent, instead of being percent-encoded.
• Valid ids are unchanged on the wire.

API Reference

None.

Breaking changes

None. Values that could not reach a valid endpoint are now rejected before the request is sent.

Tests

Unit tests for the path helper and for every endpoint that takes a path parameter.

Related

Reported internally.

[agent-wall-e]

🟢 Risk Classification: LOW

Approval route: AI Auto-Approval
Rollback controls: Automated Instant Rollback + feature flags

Classification reasons

• no_low_class_matched
• prod_source_modified
• 2.2.6_logical_extension:This change only tightens input validation in an existing path-encoding helper by rejecting additional invalid characters before encoding, without changing the function signature, adding new endpoints, persisting data, or crossing any trust boundary.

Operational gates

• ✅ jira_ticket (INT-1827)
• ✅ independent_review

Files analysed: 3

---

_{wall-e 2026.06.19-02 · policy 6b4ce2b3b45a…}

[agent-wall-e]

🔬 Debug — why this classification?

Each reason code emitted by the classifier, its source clause in the AI in SDLC Control Framework, and what it means.

Reason code	Kind	Clause	Meaning
no_low_class_matched	informational	§2.2 (fall-through)	None of the deterministic Low classes (§2.2.3, §2.2.4, §2.2.7, docs-only) applied; classifier fell through to LLM evaluation.
prod_source_modified	informational	§2.1 M7 (informational)	At least one file is non-doc, non-test, non-IaC — i.e. application source code was modified.
2.2.6_logical_extension — This change only tightens input validation in an existing path-encoding helper by rejecting additional invalid characters before encoding, without changing the function signature, adding new endpoints, persisting data, or crossing any trust boundary.	classifying	§2.2.6	Sonnet 4.6 evaluator promoted minor → low: the change reuses existing code paths and does not cross a trust boundary.

Kinds:

• classifying — this rule contributed to the chosen tier.
• informational — context only; did not by itself decide the tier.

See issue #3 for the proposal to formalise this map as Appendix A of the standards doc.

_{wall-e 2026.06.19-02 · debug}

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[agent-wall-e]

✅ Auto-approved — this PR meets all Low-risk criteria.

All checks passed, no unresolved comments, and the change classification is:

• no_low_class_matched
• prod_source_modified
• 2.2.6_logical_extension:This change only tightens input validation in an existing path-encoding helper by rejecting additional character classes before encoding, without modifying any endpoint, data model, auth logic, or external integration.

_{wall-e 2026.06.19-02 · policy 6b4ce2b3b45a…}