# 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. ## CGRID — An inventory grid with trustworthy edits Fictional supplier Reedworks uses a browser inventory table. Quantities are planning records, not live warehouse instructions. **Field:** Frontend. **Suggested stack:** React, TypeScript, CSS Modules, Playwright. **Engineer value:** Practice grid interaction and concurrent edit recovery. **Company value:** Inspect how changes protect operator intent during partial failures. **Delivery agreement:** Deliver separate pull requests using synthetic stock. ### Setup prerequisites - Create synthetic SKUs with revisions and nullable quantities. - Implement a local paginated adapter with conditional updates. ### Understand cells Define value and edit contracts. #### CGRID-101 — Render unknown stock separately from zero **Bug · High priority · Foundational** noCV practice brief v5 · CGRID-101 · An inventory grid with trustworthy edits Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Understand cells. Depends on: No preceding ticket. Difficulty: Foundational. Estimated focused work: 60 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. Buyers mistake missing quantities for zero because the grid coerces null. Preserve the API distinction. Acceptance criteria - Null displays Unknown - Zero displays 0 - Unknown values sort last Implementation constraints - Do not mutate stored quantities. Verification - Render null beside zero - Reject nonnumeric values without showing NaN Deliverables - Quantity renderer and cases Rollout and recovery: Revert the renderer without migration. Project prerequisites: Create synthetic SKUs with revisions and nullable quantities. Implement a local paginated adapter with conditional updates. Engineer value: Practice grid interaction and concurrent edit recovery. Company value: Inspect how changes protect operator intent during partial failures. 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. #### CGRID-102 — Keep inventory column widths after reload **Story · Medium priority · Foundational** noCV practice brief v5 · CGRID-102 · An inventory grid with trustworthy edits Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Understand cells. Depends on: No preceding ticket. Difficulty: Foundational. Estimated focused work: 75 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. Operators resize the SKU column every morning. Save bounded widths per grid version. Acceptance criteria - Widths restore after reload - Limits prevent hidden controls - Reset removes overrides Implementation constraints - Persist layout only. Verification - Restore two widths - Corrupt saved JSON and verify defaults Deliverables - Width persistence and reset control Rollout and recovery: Disable persistence if controls disappear. Project prerequisites: Create synthetic SKUs with revisions and nullable quantities. Implement a local paginated adapter with conditional updates. Engineer value: Practice grid interaction and concurrent edit recovery. Company value: Inspect how changes protect operator intent during partial failures. 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. #### CGRID-103 — Validate stock edits before saving **Task · High priority · Intermediate** noCV practice brief v5 · CGRID-103 · An inventory grid with trustworthy edits Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Understand cells. Depends on: CGRID-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. Pasting a decimal quantity sends an invalid stock update. Add recoverable field validation. Acceptance criteria - Nonnegative integers save - Decimals and negatives remain editable - Errors identify the cell Implementation constraints - Follow the local adapter contract. Verification - Save quantity 12 - Paste -1 and verify no request Deliverables - Cell validator and interaction cases Rollout and recovery: Restore read-only quantities if valid saves fail. Project prerequisites: Create synthetic SKUs with revisions and nullable quantities. Implement a local paginated adapter with conditional updates. Engineer value: Practice grid interaction and concurrent edit recovery. Company value: Inspect how changes protect operator intent during partial failures. 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. ### Protect edits Preserve selection and drafts. #### CGRID-104 — Maintain inventory selection while sorted rows update **Bug · High priority · Advanced** noCV practice brief v5 · CGRID-104 · An inventory grid with trustworthy edits Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Protect edits. Depends on: CGRID-101. 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. A background refresh reorders rows and moves the editing highlight to another SKU. Anchor selection to identity. Acceptance criteria - Selected SKU remains selected - Deleted selection clears explicitly - Sorting cannot change edit target Implementation constraints - Array indices cannot identify rows. Verification - Refresh reordered rows - Delete the selected SKU mid-edit Deliverables - Identity-based selection coordinator Rollout and recovery: Disable background refresh if selection diverges. Project prerequisites: Create synthetic SKUs with revisions and nullable quantities. Implement a local paginated adapter with conditional updates. Engineer value: Practice grid interaction and concurrent edit recovery. Company value: Inspect how changes protect operator intent during partial failures. 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. #### CGRID-105 — Reject stale stock updates without losing drafts **Bug · High priority · Advanced** noCV practice brief v5 · CGRID-105 · An inventory grid with trustworthy edits Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Protect edits. Depends on: CGRID-103. Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 60% · API design 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. Two buyers edit the same row and the second overwrites the first. Handle revision conflicts. Acceptance criteria - Saves include expected revision - Conflict preserves draft and current value - Resubmission requires reconciliation Implementation constraints - Never blindly retry conflicts. Verification - Accept matching revision - Reject stale revision and inspect draft Deliverables - Conflict panel and adapter cases Rollout and recovery: Gate editing while conflict handling is repaired. Project prerequisites: Create synthetic SKUs with revisions and nullable quantities. Implement a local paginated adapter with conditional updates. Engineer value: Practice grid interaction and concurrent edit recovery. Company value: Inspect how changes protect operator intent during partial failures. 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. #### CGRID-106 — Define keyboard entry and escape for inventory cells **Story · Medium priority · Intermediate** noCV practice brief v5 · CGRID-106 · An inventory grid with trustworthy edits Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Protect edits. Depends on: CGRID-103, CGRID-104. Difficulty: Intermediate. Estimated focused work: 150 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 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. Arrow keys sometimes move cells while users edit text. Introduce explicit navigation and editing states. Acceptance criteria - Enter starts editing - Escape restores committed value - Editor arrows retain native behavior Implementation constraints - Provide semantic controls and visible focus. Verification - Edit without a pointer - Escape an invalid draft Deliverables - Keyboard contract and checks Rollout and recovery: Fall back to ordinary row forms. Project prerequisites: Create synthetic SKUs with revisions and nullable quantities. Implement a local paginated adapter with conditional updates. Engineer value: Practice grid interaction and concurrent edit recovery. Company value: Inspect how changes protect operator intent during partial failures. 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. #### CGRID-107 — Undo only an uncontested stock change **Story · Medium priority · Expert** noCV practice brief v5 · CGRID-107 · An inventory grid with trustworthy edits Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Protect edits. Depends on: CGRID-105. Difficulty: Expert. Estimated focused work: 240 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 50% · API design 50%. 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 blind Undo would erase a colleague's newer stock value. Add one guarded inverse update. Acceptance criteria - Undo uses resulting revision - Newer revisions reject undo - Failure preserves current row Implementation constraints - Undo must be a conditional write. Verification - Undo an uncontested save - Advance revision before undo Deliverables - Guarded undo and race case Rollout and recovery: Hide Undo while retaining ordinary edits. Project prerequisites: Create synthetic SKUs with revisions and nullable quantities. Implement a local paginated adapter with conditional updates. Engineer value: Practice grid interaction and concurrent edit recovery. Company value: Inspect how changes protect operator intent during partial failures. 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 interruption Recover from partial writes. #### CGRID-108 — Preview pasted stock ranges before applying them **Story · High priority · Advanced** noCV practice brief v5 · CGRID-108 · An inventory grid with trustworthy edits Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Handle interruption. Depends on: CGRID-103, CGRID-106. Difficulty: Advanced. Estimated focused work: 210 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. A spreadsheet paste includes headers and an extra column. Show its target mapping before writing. Acceptance criteria - Preview names target SKUs - Malformed rows show errors - Confirm sends selected valid rows only Implementation constraints - Bound paste size and treat text as untrusted. Verification - Preview three rows - Reject oversized formula-like input safely Deliverables - Paste parser and confirmation preview Rollout and recovery: Disable paste while preserving manual edits. Project prerequisites: Create synthetic SKUs with revisions and nullable quantities. Implement a local paginated adapter with conditional updates. Engineer value: Practice grid interaction and concurrent edit recovery. Company value: Inspect how changes protect operator intent during partial failures. 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. #### CGRID-109 — Report individual results for a partial stock save **Task · High priority · Intermediate** noCV practice brief v5 · CGRID-109 · An inventory grid with trustworthy edits Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Handle interruption. Depends on: CGRID-105, CGRID-108. Difficulty: Intermediate. Estimated focused work: 150 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 70% · API design 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. Bulk edit says Saved when one row failed. Return stable per-row outcomes. Acceptance criteria - Success shows committed revision - Failure retains draft - Retry selects failed rows only Implementation constraints - Timeouts remain unresolved until reconciled. Verification - Save mixed valid and invalid rows - Timeout one row and inspect uncertainty Deliverables - Result summary and retry controls Rollout and recovery: Disable bulk save if result mapping fails. Project prerequisites: Create synthetic SKUs with revisions and nullable quantities. Implement a local paginated adapter with conditional updates. Engineer value: Practice grid interaction and concurrent edit recovery. Company value: Inspect how changes protect operator intent during partial failures. 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. #### CGRID-110 — Export inventory-grid diagnostics without stock data **Chore · Low priority · Intermediate** noCV practice brief v5 · CGRID-110 · An inventory grid with trustworthy edits Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Handle interruption. Depends on: CGRID-104, CGRID-109. Difficulty: Intermediate. Estimated focused work: 90 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. Support needs grid state but copying rows exposes inventory. Add an opt-in diagnostic download. Acceptance criteria - Includes grid version and flags - Omits quantities and SKU labels - User previews the report Implementation constraints - Allowlist diagnostic fields. Verification - Export populated grid - Verify secret-like fixture values are absent Deliverables - Exporter and exclusion checks Rollout and recovery: Remove export if unexpected fields appear. Project prerequisites: Create synthetic SKUs with revisions and nullable quantities. Implement a local paginated adapter with conditional updates. Engineer value: Practice grid interaction and concurrent edit recovery. Company value: Inspect how changes protect operator intent during partial failures. 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.