Normalize directory whitespace without changing part codes
Repeated spaces create separate search requests. Define normalization without altering case-sensitive part codes.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- URL state · Parsing
Estimated field mix
- Frontend100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
Fictional workshop directory Cedar lists tools and spare parts using a local search adapter.
Setup prerequisites
- Create synthetic items with stable identifiers.
- Stub cursor pages, facets, delayed responses and missing items.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Outer spaces trim
- Internal-space policy is documented
- Input preserves edits until submit
Implementation constraints
- Do not silently lowercase identifiers.
Verification to include
- Submit padded code
- Submit whitespace only
Deliverables
- Query parser and examples
Rollout and recovery
Revert normalization while accepting old links.
Value of the work
For the engineer: Practice URL contracts and request ownership.
For the team: Inspect whether discovery intent survives changing results.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.