# noCV engineering task library Content version 5 Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs. Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence. ## CSEARCH — A catalog search that survives interruption Fictional workshop directory Cedar lists tools and spare parts using a local search adapter. **Field:** Frontend. **Suggested stack:** React, TypeScript, CSS Modules, Testing Library. **Engineer value:** Practice URL contracts and request ownership. **Company value:** Inspect whether discovery intent survives changing results. **Delivery agreement:** Use local fixtures; external search services are excluded. ### Setup prerequisites - Create synthetic items with stable identifiers. - Stub cursor pages, facets, delayed responses and missing items. ### Specify search state Make queries shareable. #### CSEARCH-101 — Normalize directory whitespace without changing part codes **Task · Medium priority · Foundational** noCV practice brief v5 · CSEARCH-101 · A catalog search that survives interruption Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Specify search state. Depends on: No preceding ticket. Difficulty: Foundational. Estimated focused work: 60 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 100%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Repeated spaces create separate search requests. Define normalization without altering case-sensitive part codes. Acceptance criteria - Outer spaces trim - Internal-space policy is documented - Input preserves edits until submit Implementation constraints - Do not silently lowercase identifiers. Verification - Submit padded code - Submit whitespace only Deliverables - Query parser and examples Rollout and recovery: Revert normalization while accepting old links. Project prerequisites: Create synthetic items with stable identifiers. Stub cursor pages, facets, delayed responses and missing items. Engineer value: Practice URL contracts and request ownership. Company value: Inspect whether discovery intent survives changing results. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CSEARCH-102 — Expose selected directory facets in shared links **Story · Medium priority · Intermediate** noCV practice brief v5 · CSEARCH-102 · A catalog search that survives interruption Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Specify search state. Depends on: CSEARCH-101. Difficulty: Intermediate. Estimated focused work: 105 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 100%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Shared search links conceal which filters excluded parts. Render removable facets from validated URL values. Acceptance criteria - Active facets have labels - Unknown facets use visible fallback - Removal resets pagination Implementation constraints - Resolve labels from trusted metadata. Verification - Open two selected facets - Use unknown facet ID Deliverables - Facet controls and URL cases Rollout and recovery: Disable facet writes while retaining parsing. Project prerequisites: Create synthetic items with stable identifiers. Stub cursor pages, facets, delayed responses and missing items. Engineer value: Practice URL contracts and request ownership. Company value: Inspect whether discovery intent survives changing results. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CSEARCH-103 — Announce completed directory searches once **Bug · Medium priority · Foundational** noCV practice brief v5 · CSEARCH-103 · A catalog search that survives interruption Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Specify search state. Depends on: CSEARCH-101. Difficulty: Foundational. Estimated focused work: 75 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 70% · Frontend 30%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. A live region reads counts after every keystroke. Announce committed search outcomes without moving focus. Acceptance criteria - Count announces on completion - Loading has one status - Errors explain retry Implementation constraints - Do not focus status updates. Verification - Submit and inspect announcement - Reject search and inspect error Deliverables - Status component and manual protocol Rollout and recovery: Use submit-only announcements if updates repeat. Project prerequisites: Create synthetic items with stable identifiers. Stub cursor pages, facets, delayed responses and missing items. Engineer value: Practice URL contracts and request ownership. Company value: Inspect whether discovery intent survives changing results. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. ### Handle changing results Keep feedback attached to active queries. #### CSEARCH-104 — Bind directory page cursors to their originating query **Bug · High priority · Advanced** noCV practice brief v5 · CSEARCH-104 · A catalog search that survives interruption Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Handle changing results. Depends on: CSEARCH-102. Difficulty: Advanced. Estimated focused work: 165 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 80% · API design 20%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. More results races with facet changes and appends unrelated products. Scope pages to query identity. Acceptance criteria - Matching pages alone append - Facet changes invalidate cursors - IDs deduplicate repeated results Implementation constraints - Cancellation alone is insufficient. Verification - Append matching page - Resolve old page after new query Deliverables - Query-scoped pager and race test Rollout and recovery: Disable incremental paging on ownership failure. Project prerequisites: Create synthetic items with stable identifiers. Stub cursor pages, facets, delayed responses and missing items. Engineer value: Practice URL contracts and request ownership. Company value: Inspect whether discovery intent survives changing results. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CSEARCH-105 — Restore a directory result anchor after detail navigation **Story · Medium priority · Intermediate** noCV practice brief v5 · CSEARCH-105 · A catalog search that survives interruption Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Handle changing results. Depends on: CSEARCH-104. Difficulty: Intermediate. Estimated focused work: 150 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 60% · Accessibility 40%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Returning from a part detail resets a long search to the top. Restore the visited item. Acceptance criteria - Back restores query and anchor - Missing item has fallback - Focus returns to originating link Implementation constraints - Do not identify anchors only by pixels. Verification - Visit later result and return - Remove it before Back Deliverables - History restoration and browser case Rollout and recovery: Disable anchoring while retaining query history. Project prerequisites: Create synthetic items with stable identifiers. Stub cursor pages, facets, delayed responses and missing items. Engineer value: Practice URL contracts and request ownership. Company value: Inspect whether discovery intent survives changing results. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CSEARCH-106 — Explain unavailable parts in bookmarked directory links **Story · Medium priority · Intermediate** noCV practice brief v5 · CSEARCH-106 · A catalog search that survives interruption Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Handle changing results. Depends on: CSEARCH-101. Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 70% · Security 30%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. An old part bookmark renders a blank page. Distinguish removal from failed loading. Acceptance criteria - Missing and failed reads differ - Return preserves valid search - External return targets are rejected Implementation constraints - Allowlist internal return routes. Verification - Open removed part - Inject external return URL Deliverables - Unavailable state and route tests Rollout and recovery: Restore static unavailable page if navigation breaks. Project prerequisites: Create synthetic items with stable identifiers. Stub cursor pages, facets, delayed responses and missing items. Engineer value: Practice URL contracts and request ownership. Company value: Inspect whether discovery intent survives changing results. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CSEARCH-107 — Keep zero-count directory facets removable **Bug · Medium priority · Advanced** noCV practice brief v5 · CSEARCH-107 · A catalog search that survives interruption Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Handle changing results. Depends on: CSEARCH-102, CSEARCH-104. Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 100%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Selected filters disappear when counts reach zero, trapping the query. Separate selection from availability. Acceptance criteria - Selected zero-count facets remain - Stale counts are labeled - Count failure preserves selection Implementation constraints - Count refresh cannot rewrite selections. Verification - Select zero-result facet - Reject facet-count refresh Deliverables - Facet reconciliation and cases Rollout and recovery: Freeze counts while preserving removal. Project prerequisites: Create synthetic items with stable identifiers. Stub cursor pages, facets, delayed responses and missing items. Engineer value: Practice URL contracts and request ownership. Company value: Inspect whether discovery intent survives changing results. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. ### Prepare recovery Bound caching and support diagnosis. #### CSEARCH-108 — Bound the directory query cache **Task · Medium priority · Expert** noCV practice brief v5 · CSEARCH-108 · A catalog search that survives interruption Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Prepare recovery. Depends on: CSEARCH-104, CSEARCH-107. Difficulty: Expert. Estimated focused work: 240 minutes; setup and prerequisite tickets are additional. Estimated field mix: Performance engineering 60% · Frontend 40%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Browsing many searches grows memory indefinitely. Introduce capacity and expiry with deterministic eviction. Acceptance criteria - Capacity is configurable - Keys contain all query dimensions - Expired entries refresh visibly Implementation constraints - Cache public directory records only. Verification - Revisit retained query - Exceed capacity and inspect eviction Deliverables - Cache policy and clock tests Rollout and recovery: Disable cache and fetch committed queries. Project prerequisites: Create synthetic items with stable identifiers. Stub cursor pages, facets, delayed responses and missing items. Engineer value: Practice URL contracts and request ownership. Company value: Inspect whether discovery intent survives changing results. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CSEARCH-109 — Print a directory shortlist from current item identities **Story · Medium priority · Intermediate** noCV practice brief v5 · CSEARCH-109 · A catalog search that survives interruption Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Prepare recovery. Depends on: CSEARCH-105, CSEARCH-106. Difficulty: Intermediate. Estimated focused work: 135 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 100%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Printed shortlists include removed entries. Use a dedicated projection resolved by current item IDs. Acceptance criteria - Missing items are identified - Removal updates print - Controls are hidden in print Implementation constraints - Use the local directory adapter. Verification - Print two entries - Remove one before printing Deliverables - Print view and media checks Rollout and recovery: Hide printing if projections diverge. Project prerequisites: Create synthetic items with stable identifiers. Stub cursor pages, facets, delayed responses and missing items. Engineer value: Practice URL contracts and request ownership. Company value: Inspect whether discovery intent survives changing results. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CSEARCH-110 — Instrument directory search without capturing query text **Chore · Low priority · Advanced** noCV practice brief v5 · CSEARCH-110 · A catalog search that survives interruption Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Prepare recovery. Depends on: CSEARCH-103, CSEARCH-108. Difficulty: Advanced. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Privacy engineering 60% · Frontend 40%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Search failure metrics currently include potentially sensitive part queries. Add bounded operational events. Acceptance criteria - Includes outcome and duration bucket - Omits queries and item names - Retries retain correlation token Implementation constraints - Verify through a local event collector. Verification - Complete search and inspect event - Fail secret-like query and check exclusion Deliverables - Event allowlist and samples Rollout and recovery: Disable event sink if unexpected fields appear. Project prerequisites: Create synthetic items with stable identifiers. Stub cursor pages, facets, delayed responses and missing items. Engineer value: Practice URL contracts and request ownership. Company value: Inspect whether discovery intent survives changing results. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence.