# 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. ## CMODAL — Accessible overlays and notifications in a team portal Fictional membership portal Juniper manages synthetic team settings. Use locally owned components and a local settings adapter. **Field:** Accessibility. **Suggested stack:** React, TypeScript, Base UI, CSS Modules. **Engineer value:** Practice focus containment, dismissal and asynchronous feedback. **Company value:** Inspect whether shared UI primitives protect users across many product flows. **Delivery agreement:** Change one owned primitive at a time and record affected portal consumers. ### Setup prerequisites - Create synthetic settings forms and destructive-action stubs. - Provide delayed success, rejection and removed-trigger cases. ### Specify overlay contracts Name dialogs and define dismissal. #### CMODAL-101 — Name team-setting dialogs from visible headings **Bug · High priority · Foundational** noCV practice brief v5 · CMODAL-101 · Accessible overlays and notifications in a team portal Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Specify overlay contracts. Depends on: No preceding ticket. Difficulty: Foundational. Estimated focused work: 60 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 80% · Frontend 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. Screen readers announce Dialog without a purpose. Connect each settings dialog to its visible heading. Acceptance criteria - Dialog has a meaningful name - Description excludes the entire form - Heading IDs remain unique Implementation constraints - Use the owned primitive's naming API. Verification - Open two dialog types - Mount repeated instances Deliverables - Dialog naming fix and checks Rollout and recovery: Revert consumer composition if names collide. Project prerequisites: Create synthetic settings forms and destructive-action stubs. Provide delayed success, rejection and removed-trigger cases. Engineer value: Practice focus containment, dismissal and asynchronous feedback. Company value: Inspect whether shared UI primitives protect users across many product flows. 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. #### CMODAL-102 — Make portal notification dismissal keyboard operable **Story · Medium priority · Foundational** noCV practice brief v5 · CMODAL-102 · Accessible overlays and notifications in a team portal Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Specify overlay contracts. Depends on: No preceding ticket. 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. Toast close icons have no accessible name and cannot receive focus. Add an explicit dismissal control. Acceptance criteria - Close has an action name - Keyboard activation dismisses - Dismissal preserves sensible focus Implementation constraints - Notifications cannot trap focus. Verification - Dismiss via keyboard - Dismiss notification whose trigger disappeared Deliverables - Dismiss control and focus cases Rollout and recovery: Keep notifications persistent if dismissal becomes unreachable. Project prerequisites: Create synthetic settings forms and destructive-action stubs. Provide delayed success, rejection and removed-trigger cases. Engineer value: Practice focus containment, dismissal and asynchronous feedback. Company value: Inspect whether shared UI primitives protect users across many product flows. 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. #### CMODAL-103 — Define when unsaved settings dialogs may close **Task · High priority · Intermediate** noCV practice brief v5 · CMODAL-103 · Accessible overlays and notifications in a team portal Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Specify overlay contracts. Depends on: CMODAL-101. Difficulty: Intermediate. Estimated focused work: 120 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. Escape silently discards edited settings. Add a dirty-state close contract shared by close button and outside interaction. Acceptance criteria - Clean dialogs close normally - Dirty close requests confirmation - Cancel keeps draft and focus Implementation constraints - Avoid browser-wide beforeunload for local overlay changes. Verification - Close clean dialog - Cancel dirty dismissal Deliverables - Close policy and interaction cases Rollout and recovery: Disable outside dismissal while correcting the policy. Project prerequisites: Create synthetic settings forms and destructive-action stubs. Provide delayed success, rejection and removed-trigger cases. Engineer value: Practice focus containment, dismissal and asynchronous feedback. Company value: Inspect whether shared UI primitives protect users across many product flows. 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 nested interactions Preserve focus and pending user work. #### CMODAL-104 — Return focus when a portal dialog trigger disappears **Bug · High priority · Advanced** noCV practice brief v5 · CMODAL-104 · Accessible overlays and notifications in a team portal Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Handle nested interactions. Depends on: CMODAL-103. Difficulty: Advanced. Estimated focused work: 165 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. After deleting a row through its dialog, the original trigger no longer exists. Provide a surviving fallback target. Acceptance criteria - Existing trigger regains focus - Deleted trigger uses nearest contextual control - Failure keeps focus inside dialog Implementation constraints - Resolve fallback after committed row removal. Verification - Save without deleting trigger - Delete the trigger's row Deliverables - Focus-return resolver and cases Rollout and recovery: Keep an action-result placeholder if no valid target exists. Project prerequisites: Create synthetic settings forms and destructive-action stubs. Provide delayed success, rejection and removed-trigger cases. Engineer value: Practice focus containment, dismissal and asynchronous feedback. Company value: Inspect whether shared UI primitives protect users across many product flows. 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. #### CMODAL-105 — Keep parent settings inert while a nested confirmation is open **Bug · High priority · Advanced** noCV practice brief v5 · CMODAL-105 · Accessible overlays and notifications in a team portal Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Handle nested interactions. Depends on: CMODAL-103, CMODAL-104. Difficulty: Advanced. Estimated focused work: 180 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. Tab reaches the parent form behind a confirmation dialog. Compose modal ownership across one nested level. Acceptance criteria - Tab stays in active confirmation - Escape closes only top layer - Parent state survives confirmation cancellation Implementation constraints - Use the accessible primitive rather than manual document-wide traps. Verification - Cycle Tab through nested dialog - Cancel then resume parent form Deliverables - Nested-dialog composition tests Rollout and recovery: Replace nested confirmation with an inline confirmation step. Project prerequisites: Create synthetic settings forms and destructive-action stubs. Provide delayed success, rejection and removed-trigger cases. Engineer value: Practice focus containment, dismissal and asynchronous feedback. Company value: Inspect whether shared UI primitives protect users across many product flows. 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. #### CMODAL-106 — Prevent menu dismissal from swallowing a settings action **Bug · Medium priority · Intermediate** noCV practice brief v5 · CMODAL-106 · Accessible overlays and notifications in a team portal Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Handle nested interactions. Depends on: CMODAL-104. Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 80% · Accessibility 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. Choosing Rename closes the menu before its dialog receives the intended row. Make the action payload stable through dismissal. Acceptance criteria - Rename targets selected row - Keyboard and pointer match - Removed rows show unavailable state Implementation constraints - Capture immutable row identity at activation. Verification - Rename from keyboard menu - Remove row before dialog load Deliverables - Menu-to-dialog handoff Rollout and recovery: Disable the menu action if identity is unresolved. Project prerequisites: Create synthetic settings forms and destructive-action stubs. Provide delayed success, rejection and removed-trigger cases. Engineer value: Practice focus containment, dismissal and asynchronous feedback. Company value: Inspect whether shared UI primitives protect users across many product flows. 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. #### CMODAL-107 — Keep pending portal dialog saves cancellable without duplicate writes **Story · High priority · Expert** noCV practice brief v5 · CMODAL-107 · Accessible overlays and notifications in a team portal Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Handle nested interactions. Depends on: CMODAL-105, CMODAL-106. Difficulty: Expert. Estimated focused work: 240 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. A slow save invites repeated clicks and users cannot tell whether closing cancels the write. Specify operation and view lifecycles separately. Acceptance criteria - One pending write per revision - Closing does not claim server cancellation - Reopen reconciles operation status Implementation constraints - Adapter cancellation may be advisory only. Verification - Close after accepted save - Timeout then reopen same operation Deliverables - Pending-operation model and races Rollout and recovery: Disable closing during unresolved operations with an explicit explanation. Project prerequisites: Create synthetic settings forms and destructive-action stubs. Provide delayed success, rejection and removed-trigger cases. Engineer value: Practice focus containment, dismissal and asynchronous feedback. Company value: Inspect whether shared UI primitives protect users across many product flows. 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. ### Make feedback durable Support zoom and verify reusable behavior. #### CMODAL-108 — Reflow portal dialogs without hiding their confirmation actions **Bug · Medium priority · Intermediate** noCV practice brief v5 · CMODAL-108 · Accessible overlays and notifications in a team portal Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Make feedback durable. Depends on: CMODAL-105. Difficulty: Intermediate. Estimated focused work: 120 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. Magnified text pushes Save below a fixed-height dialog with no reachable scroll path. Reflow the dialog shell. Acceptance criteria - Content scrolls inside labeled region - Actions stay reachable - Document background remains inert Implementation constraints - Avoid fixed pixel heights for text containers. Verification - Check 200 percent text sizing - Use long error descriptions Deliverables - Responsive dialog styles Rollout and recovery: Use full-page forms if actions cannot remain reachable. Project prerequisites: Create synthetic settings forms and destructive-action stubs. Provide delayed success, rejection and removed-trigger cases. Engineer value: Practice focus containment, dismissal and asynchronous feedback. Company value: Inspect whether shared UI primitives protect users across many product flows. 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. #### CMODAL-109 — Make critical portal notifications persistent until acknowledged **Story · Medium priority · Intermediate** noCV practice brief v5 · CMODAL-109 · Accessible overlays and notifications in a team portal Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Make feedback durable. Depends on: CMODAL-102, CMODAL-107. Difficulty: Intermediate. Estimated focused work: 105 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. A failed permission change disappears after four seconds. Separate persistent actionable failures from transient informational status. Acceptance criteria - Failed changes remain visible - Acknowledgement is explicit - Repeated same failure coalesces without losing action Implementation constraints - Do not use urgency announcements for every toast. Verification - Reject permission change - Repeat rejection and inspect coalescing Deliverables - Notification priority contract Rollout and recovery: Disable auto-dismiss for all actionable messages if classification fails. Project prerequisites: Create synthetic settings forms and destructive-action stubs. Provide delayed success, rejection and removed-trigger cases. Engineer value: Practice focus containment, dismissal and asynchronous feedback. Company value: Inspect whether shared UI primitives protect users across many product flows. 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. #### CMODAL-110 — Audit shared portal overlays across input and theme settings **Chore · Medium priority · Advanced** noCV practice brief v5 · CMODAL-110 · Accessible overlays and notifications in a team portal Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Make feedback durable. Depends on: CMODAL-108, CMODAL-109. Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 60% · Quality engineering 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. Primitive fixes may regress different consumers. Run a bounded matrix on settings, rename and deletion flows. Acceptance criteria - Matrix covers keyboard and pointer - Light dark and forced colors are recorded - Failures include minimal reproduction Implementation constraints - Report actual local observations and remaining gaps. Verification - Complete rename flow - Exercise rejected delete in constrained display Deliverables - Overlay audit record Rollout and recovery: Keep affected consumer disabled until its blocking regression is fixed. Project prerequisites: Create synthetic settings forms and destructive-action stubs. Provide delayed success, rejection and removed-trigger cases. Engineer value: Practice focus containment, dismissal and asynchronous feedback. Company value: Inspect whether shared UI primitives protect users across many product flows. 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.