Converge Templates and Recurring operator flows

[alexeygrigorev]

Converge Templates and Recurring operator flows

Status: accepted and committed locally — exact accepted commit 9d204d208820e3d842a3d3fc83493c230bcadaa5; not merged, pushed, deployed, shipped, or closed
Tags: enhancement, portal, frontend, testing, design, P1
Parent: #162 Wave A slice 2
Depends on: satisfied — accepted #218 commit 0c89588df809b2e84af02e796d1910a25eea0165, accepted #180 behavior foundation, and accepted #161 shell/Home foundation
Blocks: #162 integrated Wave A acceptance
Next owner: Orchestrator — when coordinated publication resumes, merge the accepted local Wave A chain in order, push main, then hand off to On-Call; no implementation or review rerun is pending for #219
Resume condition: local main is clean and the Orchestrator is ready to publish the accepted Wave A chain; #219 requires no rerun unless commit 9d204d208820e3d842a3d3fc83493c230bcadaa5 changes

Product outcome

Templates and Recurring feel like one safe operator workflow without changing their domain contracts:

• Templates remain read-only projections of reviewed Git-authored definitions. Operators can search, inspect source/revision and Task definitions, create a Card, and explicitly review/apply Template updates to selected existing Cards.
• Recurring remains the place to create and edit schedules that generate Tasks, clearly distinguish Active from Paused, and safely pause, resume, or delete a schedule.
• Editing a recurring schedule makes clean, changed, saving, validation, conflict, retry, and discard consequences explicit. A dismissal never silently loses changed values.
• On a phone, one schedule is readable before secondary actions; its Edit/Pause-or-Resume/Delete controls are available through an accessible row-owned disclosure instead of a dense three-button strip.
• Failed Template batch preview/apply and partial conflicts stay in the selected Template detail, announce the failure, preserve the reviewed selection/result context, and offer the next safe recovery action.

This is gap-only convergence over the canonical frontend. It does not create a Template editor, change Template/Card/Task semantics, alter recurring generation, or introduce a new API, data model, router, shell, or compatibility layer.

PM amendment — exact implementation blockers

The Software Engineer blocker report is substantiated against the accepted #218 containing baseline, the #159 durable evidence contract, and accepted held #164 commit 3e835a19017da18f2177d81fb7e084764970dee3. This amendment changes no product outcome, runtime/API contract, or production write boundary.

• Authorize backend/scripts/frontend-capabilities.test.mjs only to add the five already-groomed durable state suffixes to the existing Templates/Recurring expected-state lists and add exact admin role overrides for templates.batch-failure, recurring.editor-dirty, recurring.validation, recurring.saving, and recurring.conflict. Do not alter schema, collector, reporter, accepted evidence type, role semantics, route/API inventories, or any unrelated state.
• Authorize backend/e2e/issue-218-shared-primitives.spec.js only for one minimal mobile interaction that opens the row-owned “Schedule actions” disclosure before the existing Delete action. Preserve Converge Wave A surfaces on bounded shared UI primitives #218’s fixture, assertions, screenshot inventory, capability claims, and all other journey behavior.
• Correct the focused Playwright recipe to execute from backend/ with backend/playwright.config.js, so the configured server/base URL/workers apply.
• Exclude make test-sam-workspace-isolation from Converge Templates and Recurring operator flows #219. Its unchanged containing-baseline dependency-location failure is unrelated to Converge Templates and Recurring operator flows #219 and is already repaired, fully verified, PM-accepted, and committed in held Show signed-in identity and authorized teammates’ Task/Card work #164. Converge Templates and Recurring operator flows #219 must not duplicate or cherry-pick that repair. Normal SAM validation/build, source/build/SAM artifact identity, packaged runtime/frontend isolation exercised by make ci, and source/SAM browser parity remain mandatory.

Authorized refreeze sequence: make only the two newly authorized test/evidence edits; retain the seven existing bounded candidate paths; rerun focused frontend tests, corrected focused Playwright, the full browser suite with all 147 states, frontend parity, backend test/typecheck/build, SAM validation/build and artifact checks, make ci, and diff integrity; regenerate and inspect exactly the 12 issue screenshots; post new diff/status/content fingerprints; then repeat Designer, independent Tester, and PM review on that exact fingerprint. Earlier partial green runs are supporting diagnostics, not lifecycle verdicts.

Frozen baseline and dependency reconciliation

The PM inspected source and tests read-only at clean baseline 78e91223203aa54376a318fd1a3214ce0242e0c3.

That baseline contains:

• accepted Restore behavior-based browser coverage and fix canonical UI accessibility races #180 increments e684162 and b045739, including Recurring Active/Paused programmatic text, route-fresh mutation handling, row-owned pause failure/retry, deterministic real-browser behavior, and accessibility-race repairs;
• accepted Finalize the canonical scan-first Operations Home #161 Home/shared-shell work, finalized by 7d77632 and 64476d2; Converge Templates and Recurring operator flows #219 neither changes nor revalidates Home;
• the Restore canonical frontend behavior coverage and SAM parity gates #159 durable capability/source-SAM evidence contract;
• canonical Git-authored Template projection and recurring API behavior.

Accepted #218 commit 0c89588df809b2e84af02e796d1910a25eea0165 converges shared headers, action rows, forms, semantic statuses, honest states, and responsive rules and is the exact containing baseline for #219. The Software Engineer posted the required refreshed inventory before editing. #219 consumes those accepted primitives and must not revert, duplicate, absorb, or restyle them. If a later accepted integration changes an owned path before #219 freezes, reconstruct the candidate and repeat Designer, Tester, and PM review on the new fingerprint.

Held #158/#164 branches are not part of baseline 78e9122. If either is integrated first, preserve its accepted behavior and rerun the overlap inventory; do not resolve overlap by reverting or silently rewriting it.

Criterion-to-current-source/test inventory

Already compliant — preserve, do not rebuild

Canonical Template/Card/Task contract

• frontend/src/surfaces/tasks/templates.js renders a searchable, deep-linkable, read-only Git-authored Template list/detail with source path, revision, Task definitions, Create card, stale/not-found recovery, and intentional mobile list/detail return.
• Template definitions have no browser editor or Save/Delete action. backend/e2e/canonical-capability-behavior.spec.js proves POST/PUT/DELETE return 405 and both operator/admin roles inspect the same projection.
• Existing Card update behavior is explicit preview → checkbox selection → apply. Nothing is selected automatically; partial results identify applied Cards and conflicts without silent retry.
• backend/e2e/card-template-updates.spec.js, frontend/test/tasks-surface.test.mjs, and durable states templates.read-only, templates.source-revision, templates.create-card, templates.reviewed-card-batch, templates.method-not-allowed, templates.failure, and templates.stale-not-found cover the canonical contract.

There is no “dirty Template editor” to build. Clean/dirty/saving/validation/conflict editor criteria in this issue apply to the recurring schedule editor. Template mutation remains deployment-owned and read-only in the portal.

Accepted Recurring semantics

• frontend/src/surfaces/tasks/recurring.js exposes Active/Paused as real text without prohibited ARIA, renders honest unavailable/empty/ready summaries, and retains row identity across mutation recovery.
• Pause and Resume use the same authoritative PUT contract, disable only the initiating control while pending, reload server state, retain the schedule on failure, announce row-owned recovery, focus it, and leave the same action available for retry.
• Delete uses a destructive confirmation that states only the schedule is removed and generated Tasks remain. A referenced 409 retains the row and directs the operator to Pause; an unrelated failure remains retryable.
• frontend/src/surfaces/tasks/quick-create.js already provides labeled recurring create/edit fields, cadence preview, five-field cron validation, duplicate-submit prevention, aria-busy saving text, assertive failure/conflict feedback, retained values, and authoritative reload when Cancel follows a 409.
• Unit coverage in frontend/test/tasks-surface.test.mjs proves create/edit payloads, dialog naming/focus trap, validation mechanics, conflict Cancel reload, stale-route completion, failed pause focus, protected delete, and Active/Paused semantics.
• Real-server journeys in backend/e2e/canonical-capability-behavior.spec.js and backend/e2e/canonical-route-parity.spec.js prove empty/ready, persisted pause/resume, role denial, retryable 503, removable delete, referenced 409 guidance, mobile rendering, accessibility, and route behavior.
• Existing durable states are recurring.empty, recurring.ready, recurring.pause, recurring.resume, recurring.delete-unreferenced, recurring.delete-referenced-409, recurring.permission-denied, and recurring.failure.

These accepted #180 semantics are invariants, not implementation work.

Concrete unmet gaps owned by #219

1. Recurring drafts can be discarded silently. createQuickFormOverlay() closes immediately from Close, backdrop, or Escape. The recurring editor has no baseline snapshot, clean/dirty state, changed-state announcement, or discard confirmation. A changed create/edit draft can therefore disappear without an explicit decision.
2. Recurring mobile rows expose a dense action strip. At phone width the current CSS lays Edit, Pause/Resume, and Delete into three equal columns. There is no row-owned disclosure with an accessible expanded state, keyboard operation, or stable focus after rerender.
3. Template batch request failures use non-error feedback semantics. runtime-template-batch-message always has role="status"; preview/apply request failures and partial conflict recovery do not move focus to an assertive, selected-Template-owned message. Recovery copy exists but is not one coherent announced failure contract.
4. Durable evidence does not identify the editor lifecycle. The capability catalog has no exact runtime states for recurring changed draft, validation, saving, or conflict, and no exact Template batch request-failure state. Existing screenshots/source assertions cannot substitute for passed same-run browser evidence.

#218-owned or dependency-owned — preserve exactly

• Converge Wave A surfaces on bounded shared UI primitives #218: shared header, action-row, field/footer, semantic-status, honest-state, token, 44px target, and responsive presentation. A Converge Templates and Recurring operator flows #219 class may consume the accepted primitive but must not recreate it.
• Restore behavior-based browser coverage and fix canonical UI accessibility races #180: Recurring Active/Paused text, pause/resume server semantics, row failure focus/retry, route freshness, fixture isolation, diagnostics, and behavior-based browser boundaries.
• Finalize the canonical scan-first Operations Home #161: Home hierarchy, shell composition, route/history/focus behavior, and Home evidence.
• Restore canonical frontend behavior coverage and SAM parity gates #159: capability schema, collector/reporter, accepted same-run annotation evidence, and source/SAM parity machinery.
• Show signed-in identity and authorized teammates’ Task/Card work #164: identity, selected owner/team scope, permissions, actor attribution, and disabled/stale-user behavior.
• Make assistant output review safe and lifecycle-complete #158: Assistant/Artifact lifecycle and presentation.
• Backend Template/Recurring routes, validation, permissions, persistence, generation, and conflict meaning are authoritative and unchanged.

Bounded write ownership

After the required post-#218 inventory, implementation may edit only:

Production

• frontend/src/surfaces/tasks/quick-create.js — recurring-form dirty/discard lifecycle only; shared Task/Card quick forms must remain behaviorally unchanged.
• frontend/src/surfaces/tasks/recurring.js — mobile row disclosure and row-owned action/focus behavior only.
• frontend/src/surfaces/tasks/templates.js — Template batch failure/partial-conflict announcement and recovery only.
• frontend/src/styles.css — minimal Converge Templates and Recurring operator flows #219 layout/disclosure states consuming Converge Wave A surfaces on bounded shared UI primitives #218 primitives; no duplicate primitive declarations.

Tests and durable evidence

• frontend/test/tasks-surface.test.mjs
• backend/e2e/issue-219-templates-recurring.spec.js — one dedicated real-server behavior spec
• backend/e2e/frontend-capabilities.json — only the exact new behavior states below
• backend/scripts/frontend-capabilities.test.mjs — only the matching expected-state entries and exact admin role overrides for those five IDs
• backend/e2e/issue-218-shared-primitives.spec.js — only one mobile “Schedule actions” disclosure-opening step before its existing Delete action
• Existing backend/e2e/card-template-updates.spec.js, backend/e2e/canonical-capability-behavior.spec.js, or backend/e2e/canonical-route-parity.spec.js only if the post-Converge Wave A surfaces on bounded shared UI primitives #218 inventory proves a minimal pointer/fixture adjustment is required; no journey rewrite or ownership transfer

Add only these durable state identities if still absent after #218:

• templates.batch-failure
• recurring.editor-dirty
• recurring.validation
• recurring.saving
• recurring.conflict

Do not edit backend runtime/routes/tests beyond the two exact test/evidence exceptions above, API schemas, seed contracts, #159 schema/collector/reporter code, shell/runtime/Home/account/team files, or unrelated styles. Any newly required production path or backend contract requires another PM amendment before editing.

Acceptance criteria

Gap-only implementation

• Before editing, the engineer posts the exact starting SHA plus a criterion-to-current-source/test inventory classifying every item as already compliant, concrete gap, Converge Wave A surfaces on bounded shared UI primitives #218/dependency-owned, or out of scope.
• Only gaps still present after Converge Wave A surfaces on bounded shared UI primitives #218 are changed. Accepted shared primitives are consumed directly; obsolete Converge Templates and Recurring operator flows #219-owned declarations/markup are removed in the same change.
• Template definitions remain read-only Git projections. No Save/Delete Template control, portal Template editor, browser-only mutation, compatibility alias, legacy fallback, or dual behavior is introduced.
• Canonical Template → Card instantiation, reviewed Card-update selection, Card conflict handling, and Template/Card/Task vocabulary remain exact.
• Recurring API payloads, cron meaning, daily generation timing, permission behavior, generated-Task retention, and Restore behavior-based browser coverage and fix canonical UI accessibility races #180 pause/resume/delete semantics remain exact.

Recurring editor lifecycle

• A newly opened create/edit form is programmatically clean. Changing any persisted field makes it dirty; returning every persisted field to its baseline makes it clean again.
• Dirty state is communicated in concise visible text and a polite live state without changing the dialog title or pretending a save occurred.
• Clean Cancel, Close, backdrop, or Escape closes normally and restores focus to the connected opener.
• Dirty Cancel, Close, backdrop, or Escape opens one accessible discard confirmation that names the recurring schedule/draft. Keep editing returns to the same dialog, exact values, and useful field focus; Discard closes and restores focus to the opener.
• While saving, one submit causes at most one POST/PUT, submit is busy/disabled, dismissal cannot produce an ambiguous second mutation, and the pending state is announced.
• Validation keeps all entered values, associates errors to exact fields, focuses the first invalid field, and performs no request.
• A 409 keeps all entered values and dirty state, announces that server state changed, and offers exactly two safe choices: keep editing/retry with the current draft, or discard and reload authoritative schedules.
• A non-409 failure keeps values and dirty state, stays retryable, and never reports success. Successful save closes only after authoritative success and reloads without replacing a newer route.

Recurring list and mobile disclosure

• Desktop 1440×900 retains a readable schedule row with human description, Active/Paused text, cadence, next run or paused consequence, safe assignee label, and the existing state-valid actions.
• At 390×844, each schedule presents its identity/status/facts before one at-least-44×44 “Schedule actions” disclosure. Edit, Pause-or-Resume, and Delete appear in reading order only inside that row-owned disclosure; destructive Delete remains visually and semantically separated.
• Disclosure expanded/collapsed state is programmatically exposed, keyboard operable, and not inferred from an icon. Opening one row does not change another schedule.
• Pause/resume/delete success rerenders authoritative state and restores focus to the same surviving schedule/action context. Failure retains the expanded row, announces row-owned guidance, and focuses the recovery message/control.
• Referenced-delete 409 leaves the schedule visible and expanded, names Pause as the safe alternative, and states generated Tasks and notifications are preserved.
• Loading/unavailable never renders false zero counts; empty explains that New schedule creates the first schedule; a failed source remains unavailable with retry.

Template list/detail and batch recovery

• Templates remain searchable and deep-linkable with a readable desktop list/detail and intentional mobile one-pane detail plus canonical Back/Forward/return behavior.
• At 390×844 the selected Template detail, Back control, Create card action, definition, Tasks, and Card-update region remain reachable with 44×44 controls, no page-level horizontal scroll, clipping, overlap, or hidden recovery.
• Batch preview/apply pending state identifies the selected Template and prevents duplicate submission without clearing explicit Card selections.
• Preview/apply request failure is an assertive selected-Template-owned error, preserves the selected Template and usable context, receives useful focus after final render, and exposes one precisely named retry.
• Partial apply reports each applied Card and each conflict separately, never retries a conflict silently, and requires a fresh preview before a conflicted Card can be selected again.
• Routine operator copy uses human Template/Card/Task labels and does not expose raw IDs, internal tokens, private repository paths beyond the accepted public-safe projection, or provider/storage metadata.

Accessibility, responsive, and honest state

• Changed states retain one main/page-heading contract, nested headings, native labels/list/dialog/disclosure semantics, visible focus, logical keyboard order, focus containment/restoration, and text/programmatic status meaning.
• At 1440×900 there is one dominant decision region; at 390×844 fields are one column, every control is at least 44×44 CSS pixels, and there is no page-level horizontal scroll, clipping, overlap, or unreachable action.
• Light/dark tokens preserve hierarchy and semantic contrast. Reduced motion removes no state or focus cue. Zoom/reflow remains usable.
• Automated scans report zero critical or serious WCAG A/AA findings on every captured changed state.
• Synthetic fixtures, screenshots, logs, and issue evidence contain no operational corpus, real person/contact/provider data, private links, credentials, production identifiers, finance/sponsor facts, or generated operational artifacts.

Durable real-server behavior and parity

• Focused production-module tests cover clean↔dirty reversibility, every dismissal path, discard confirmation, duplicate-submit prevention, validation, 409/non-409 retention, mobile disclosure isolation, rerender focus, and Template batch error recovery.
• The normal local TypeScript server and persisted synthetic records drive the dedicated Playwright journey. Core behavior uses no request interception, fixed sleep, retry-as-synchronization, source-string assertion, incidental copy/whitespace pin, broad 404 swallowing, history-length arithmetic, test-order dependence, screenshot assertion, or pixel/byte golden.
• The successful full browser run emits same-run passing evidence for every existing Templates/Recurring state and the exact new states retained after post-Converge Wave A surfaces on bounded shared UI primitives #218 inventory, for every required role.
• Source, backend/dist, and packaged SAM frontend assets are identical for every changed asset; the normal source/SAM parity run accounts for every evidence record and proves the same route/state behavior.
• Screenshots are visual evidence only. They do not count as behavior, capability, accessibility, or parity proof.

Test scenarios

Dirty recurring draft dismissal

Given a clean edit dialog for a synthetic recurring schedule
When the operator changes description, cadence, assignee, or Active and attempts Close, Cancel, backdrop dismissal, or Escape
Then a discard confirmation appears without losing values
When Keep editing is selected
Then the same values and useful focus remain
When every field is restored to baseline or Discard is selected
Then the dialog closes through the clean/explicit path and focus returns to the connected opener

Validation, saving, conflict, and retry

Given a dirty recurring draft
When required description or cron is invalid
Then exact fields are announced/focused and no request occurs
When a valid draft is submitted twice while the first request is pending
Then one mutation occurs and saving is announced
When the server returns 409 or 503
Then values and dirty state remain, false success never appears, and the corresponding reload/discard or retry path is explicit

Mobile schedule actions and protected delete

Given active, paused, removable, and referenced synthetic schedules at 390×844
When each row disclosure is operated by keyboard/touch
Then only that row exposes Edit, Pause/Resume, and Delete in reading order
When referenced Delete returns authoritative 409
Then the same row remains expanded, generated work is preserved, and Pause guidance is announced and focused

Template batch failure and partial conflict

Given one read-only Template with multiple existing synthetic Cards
When preview fails, succeeds, selected Cards are applied, and one Card conflicts
Then the selected Template and explicit selections/results remain understandable, request failure is assertive/retryable, applied and conflicted Cards are distinct, and the conflict requires a fresh preview without silent retry

Route, responsive, and source/SAM identity

Given direct Templates and Recurring routes on source and clean packaged SAM servers
When the operator searches/selects a Template, uses mobile Back/Forward, opens recurring row actions, edits/discards/saves, and reloads
Then URL/entity/focus and authoritative state agree at 1440×900 and 390×844, and every changed frontend asset and durable evidence record matches across source and SAM

Synthetic screenshot inventory

Capture exactly these 12 untracked native-size PNGs under .tmp/screenshots/issue-219/; delete stale extras before review:

• 01-source-templates-batch-conflict-desktop-1440x900.png
• 02-sam-templates-batch-conflict-desktop-1440x900.png
• 03-source-templates-detail-mobile-390x844.png
• 04-sam-templates-detail-mobile-390x844.png
• 05-source-recurring-actions-mobile-390x844.png
• 06-sam-recurring-actions-mobile-390x844.png
• 07-source-recurring-dirty-editor-mobile-390x844.png
• 08-sam-recurring-dirty-editor-mobile-390x844.png
• 09-source-recurring-conflict-desktop-1440x900.png
• 10-sam-recurring-conflict-desktop-1440x900.png
• 11-source-recurring-delete-409-desktop-1440x900.png
• 12-sam-recurring-delete-409-desktop-1440x900.png

Source/SAM pairs use identical synthetic fixtures and show the same route, selected entity, expanded/dirty/conflict state, accessible-name summary, and console/page-error result. Designer and Tester inspect every image at native resolution for hierarchy, state/copy ownership, theme/contrast, touch target sizing, overflow, clipping, overlap, first-decision visibility, and public safety. Do not commit, publish, or attach these images to the public issue.

Exact verification

Engineer may run focused tests while iterating. make test-sam-workspace-isolation is explicitly excluded for this containing baseline under the PM amendment; do not edit its verifier in #219. Independent Tester runs the complete workflow on one frozen diff/status/content fingerprint and records each command, exit code, observed counts, changed behavior titles, capability-state accounting, and evidence paths:

node --test frontend/test/tasks-surface.test.mjs
npm run test:frontend:unit
npm run test:frontend:coverage
npm --prefix backend test
npm --prefix backend run typecheck
npm --prefix backend run build
node backend/scripts/verify-frontend-artifact.mjs --source frontend --artifact backend/dist
cd backend && npx playwright test e2e/issue-219-templates-recurring.spec.js e2e/card-template-updates.spec.js e2e/canonical-capability-behavior.spec.js e2e/canonical-route-parity.spec.js
npm --prefix backend run test:e2e
npm --prefix backend run test:e2e:frontend-parity
make sam-validate
make sam-build
node backend/scripts/verify-frontend-artifact.mjs --source frontend --artifact .aws-sam/build/BackendFunction
make ci
git diff --check

The dedicated #219 spec must run inside the normal full Playwright workflow and use its normal capability collector. Do not run raw import/export/migration/restore/data-movement tools, provider actions, AWS commands beyond local SAM validation/build, workflow dispatch, manual deploy, or production/private data checks.

Lifecycle gates

• PM baseline inventory completed read-only at 78e9122
• Accepted Restore behavior-based browser coverage and fix canonical UI accessibility races #180 Recurring semantics and accepted Finalize the canonical scan-first Operations Home #161 foundations reconciled
• PM-groomed Converge Wave A surfaces on bounded shared UI primitives #218 overlap and sequencing reconciled
• Converge Wave A surfaces on bounded shared UI primitives #218 received Designer/Tester/PM acceptance and exact commit 0c89588df809b2e84af02e796d1910a25eea0165
• Reviewed containing SHA 0c89588df809b2e84af02e796d1910a25eea0165 and project-local isolated writer order recorded
• Software Engineer posted refreshed criterion/source/test inventory before editing
• Software Engineer applies the two PM-authorized test/evidence adjustments, reruns the corrected complete gate, and posts new frozen diff/status/content fingerprints plus READY FOR DESIGN/TEST
• Designer inspects exactly 12 screenshots and posts DESIGN PASS on that fingerprint
• Independent Tester verifies every criterion and posts TESTER PASS on the same fingerprint
• PM performs operator-perspective acceptance and posts ACCEPTED on the same fingerprint
• Software Engineer commits only accepted Converge Templates and Recurring operator flows #219-owned paths with Closes #219
• Orchestrator merges locally in the coordinated Replace the transitional Tasks table with the final cardId schema #166-safe order and pushes main
• On-Call verifies CI/CD, deployment, source/SAM identity, and smoke evidence before Converge Templates and Recurring operator flows #219 is called shipped or closed
• Parent Converge canonical DataOps surfaces on one operator design system #162 records the accepted child result

No HUMAN gate is required for this local, synthetic, provider-free slice.

No-backcompat boundary

Make the final behavior atomic. Remove superseded #219-owned markup/selectors/tests in the same change. Do not add aliases, legacy fallbacks, hidden old controls beside new disclosure controls, dual event paths, old/new state readers, temporary feature flags, or version branches. If the accepted #218 primitive cannot express the required behavior, stop for PM amendment instead of creating a parallel primitive.

Explicit exclusions

• A Template editor or Template POST/PUT/DELETE; editing YAML, private knowledge, or source repositories.
• Any change to canonical Template/Card/Task contracts, Card instantiation, Card lifecycle, recurring cron/generation semantics, permission policy, persisted fields, APIs, backend routes, DynamoDB, migrations, imports, restores, exports, or infrastructure.
• Home, shell/navigation IA, account/team identity, Settings, notifications, mobile drawer, Show signed-in identity and authorized teammates’ Task/Card work #164 authorization/ownership/attribution, Inbox/Task/Card execution, Admin, or Users.
• Assistant/Artifact lifecycle or Make assistant output review safe and lifecycle-complete #158 work.
• Broad CSS rewrite, stylesheet splitting, framework/component library, router/runtime abstraction, second frontend, or new token vocabulary.
• Provider calls, production writes, AWS deployment, manual deploy, workflow dispatch, real external accounts, or HUMAN gates.
• Raw operational knowledge, private links/data, real identifiers, tracked screenshots, screenshot goldens, generated design boards, or public screenshot attachments.

[alexeygrigorev]

PM GROOMED — agent-ready Wave A Templates/Recurring slice, implementation serialized after #218

I completed a read-only source/test inventory at clean baseline 78e91223203aa54376a318fd1a3214ce0242e0c3 and reconciled parent #162, accepted #180 Recurring semantics, accepted #161 shell/Home foundations, #159 durable evidence, and PM-groomed #218.

The issue now preserves the already-canonical behavior instead of rebuilding it:

• Templates remain read-only Git-authored projections with search/detail, source/revision, Create card, reviewed existing-Card updates, method denial, stale recovery, and mobile list/detail.
• Recurring retains accepted validation, saving, conflict retention, route freshness, authoritative pause/resume, role denial, generated-Task retention, and safe referenced-delete 409 guidance.

Only four evidenced gaps remain in scope:

1. recurring dirty drafts can currently be discarded silently from Close/backdrop/Escape/Cancel;
2. phone rows currently show a dense three-button action strip instead of a row-owned accessible disclosure;
3. Template batch request failures use non-assertive status semantics and weak focus/retry ownership;
4. durable same-run capability evidence does not identify the changed editor lifecycle and batch-failure states.

The body defines exact bounded production/test paths, post-#218 reconstruction rules, desktop/mobile/accessibility/honest-state behavior, 12 synthetic source/SAM screenshot files, real-server browser and capability accounting, exact verification commands, Designer → Tester → PM → commit → merge/push → On-Call gates, atomic no-backcompat rules, and explicit exclusions for Home/shell/account/team identity, #164 authorization, #158 Assistant lifecycle, backend/data/provider work, broad CSS, and HUMAN gates.

Implementation is explicitly blocked until #218 receives Tester/PM acceptance and an exact commit because its styles, Templates/Recurring modules, tests, and browser fixtures overlap. The engineer must inventory the reviewed containing SHA and delete any gap already solved by #218 before editing.

Labels are finalized as enhancement, portal, frontend, testing, design, and P1; needs grooming was removed.

No repository file, worktree, commit, push, deployment, provider, production/private data, or HUMAN gate was touched.

Next owner: Orchestrator waits for #218's accepted commit, records the containing SHA/writer order, then assigns Software Engineer.

[alexeygrigorev]

SOFTWARE ENGINEER CURRENT-SOURCE/TEST INVENTORY — exact accepted #218 containing base

Starting SHA: 0c89588df809b2e84af02e796d1910a25eea0165 (Converge shared presentation primitives, Closes #218)
Branch/worktree: issue-219-templates-recurring at .tmp/worktrees/issue-219-templates-recurring
Preflight: clean worktree, zero staged/unmerged paths, no overlapping writer in this worktree. PM grooming is complete and needs grooming is absent.

Already compliant — preserve, do not rebuild

• Read-only Template/Card/Task contract: frontend/src/surfaces/tasks/templates.js still exposes search, deep-linked list/detail, public-safe source/revision, Task definitions, Create card, reviewed explicit Card selection, distinct apply/conflict results, fresh-preview recovery, stale/not-found recovery, and mobile return. There is no Template Save/Delete/editor. Existing focused and real-server coverage remains in frontend/test/tasks-surface.test.mjs, backend/e2e/card-template-updates.spec.js, backend/e2e/canonical-capability-behavior.spec.js, and backend/e2e/canonical-route-parity.spec.js; catalog states remain templates.read-only, .source-revision, .create-card, .reviewed-card-batch, .method-not-allowed, .failure, and .stale-not-found.
• Accepted Restore behavior-based browser coverage and fix canonical UI accessibility races #180 Recurring semantics: frontend/src/surfaces/tasks/quick-create.js retains labeled persisted fields, cron preview/five-field validation, one-request submit guard, busy announcement, retained values on 409/non-409, and route-fresh authoritative reload. frontend/src/surfaces/tasks/recurring.js retains honest loading/empty/ready state, Active/Paused text, authoritative pause/resume, generated-Task-safe delete confirmation, referenced-delete 409 Pause guidance, row-owned failure focus/retry, and stale-route protection. Existing catalog states remain recurring.empty, .ready, .pause, .resume, .delete-unreferenced, .delete-referenced-409, .permission-denied, and .failure.
• Converge Wave A surfaces on bounded shared UI primitives #218 shared presentation contract: accepted SHA 0c89588 supplies surface-page-header, surface-action-row, surface-form-grid, surface-form-footer, semantic status-label, and honest-state primitives plus scoped responsive/44px behavior. Current Templates/Recurring markup consumes those primitives. Converge Templates and Recurring operator flows #219 will add only behavior-specific selectors and will not recreate tokens or primitives.
• Existing durable machinery: Restore canonical frontend behavior coverage and SAM parity gates #159 capability schema/collector/reporter and source/dist/SAM parity machinery are present and unchanged. Existing canonical journeys remain pointers rather than being transferred into Converge Templates and Recurring operator flows #219.

Concrete gaps still present after #218 — #219 implementation

1. Recurring draft lifecycle: createQuickFormOverlay() still closes directly for Close, backdrop, and Escape; recurring Cancel also closes directly (except its old 409 reload branch). openRecurringForm() has no persisted-field baseline, reversible clean/dirty state, visible/polite changed announcement, discard confirmation, or dismissal lock while saving. The 409 path still overloads Cancel rather than exposing the required two explicit recovery choices. Existing tests prove immediate Escape close and conflict Cancel reload, so focused tests must be replaced/expanded for every dismissal path, reversibility, saving lock, validation retention/focus/no request, 409 choices, non-409 retry, and opener restoration. Shared Task/Card quick forms must remain unchanged.
2. Recurring mobile disclosure: each row still renders Edit, Pause/Resume, and Delete directly in .recurring-row-actions; phone CSS merely moves that dense strip into columns. There is no row-owned “Schedule actions” button, aria-expanded/aria-controls, isolated open state, expanded-state retention across failure, or surviving-row focus restoration after authoritative rerender. Add one disclosure per row while retaining readable desktop actions and all Restore behavior-based browser coverage and fix canonical UI accessibility races #180 mutation semantics.
3. Template batch recovery: .runtime-template-batch-message is always role="status"; preview/apply request failures are not typed as errors, are not assertive, do not receive post-render focus, and do not own one precisely named retry. Partial conflicts are visually listed and require reload already, but need one coherent selected-Template-owned assertive result/recovery contract while preserving selected Template, explicit review context, applied/conflicted separation, and no silent retry.
4. Durable evidence: backend/e2e/frontend-capabilities.json lacks exactly templates.batch-failure, recurring.editor-dirty, recurring.validation, recurring.saving, and recurring.conflict; backend/e2e/issue-219-templates-recurring.spec.js does not exist. Add only those states and one normal local TypeScript-server Playwright journey with persisted synthetic records, full collector annotations, source/SAM parity, and the exact 12 untracked .tmp/screenshots/issue-219/ images.

Dependency-owned — preserve exactly

• Converge Wave A surfaces on bounded shared UI primitives #218 shared presentation primitives and scoped palette; no parallel primitive or broad restyle.
• Restore behavior-based browser coverage and fix canonical UI accessibility races #180 recurring contracts, mutation semantics, route freshness, diagnostics, fixture isolation, and row-owned recovery.
• Finalize the canonical scan-first Operations Home #161 Home/shell composition and navigation; Restore canonical frontend behavior coverage and SAM parity gates #159 evidence infrastructure; held Show signed-in identity and authorized teammates’ Task/Card work #164 identity/authorization and Make assistant output review safe and lifecycle-complete #158 Assistant/Artifact work. Neither held branch is in this exact base.
• Backend Template/Recurring routes, payloads, validation, permissions, persistence, generation timing, conflict meaning, and data model.

Out of scope / forbidden write boundary

• No Template editor or Template mutation; no API/backend/schema/seed/data/infrastructure/provider/AWS deploy work; no compatibility alias, fallback, feature flag, or dual behavior.
• No Home, shell/navigation, account/team/identity, Admin, Users, Inbox/Task/Card execution, Show signed-in identity and authorized teammates’ Task/Card work #164, Make assistant output review safe and lifecycle-complete #158, operational corpus/private data, source-repository, or broad CSS work.
• Writes remain limited to the four authorized production files, frontend/test/tasks-surface.test.mjs, new dedicated Converge Templates and Recurring operator flows #219 spec, the five exact capability entries, and only a proven minimal pointer adjustment if required by full evidence. Screenshots/logs remain untracked under .tmp/.

Inventory outcome: all four concrete PM-groomed gaps remain after accepted #218 and are the complete implementation scope. No source file has been edited yet.

[alexeygrigorev]

SOFTWARE ENGINEER BLOCKED — PM amendment required

The bounded #219 implementation is complete in the assigned worktree, but the required frozen READY handoff cannot be posted while three exact-scope/verification contradictions remain.

1. The mandated new capability states cannot pass the mandated backend gate inside the allowed write set. The issue requires exactly templates.batch-failure, recurring.editor-dirty, recurring.validation, recurring.saving, and recurring.conflict in backend/e2e/frontend-capabilities.json, while backend/scripts/frontend-capabilities.test.mjs hard-codes the prior Templates/Recurring state lists and role overrides. npm --prefix backend test and make ci therefore fail exactly at templates state coverage drifted (1,089 passed, 5 skipped, 1 failed under the same audited process-only advancing clock accepted for Converge Wave A surfaces on bounded shared UI primitives #218). Converge Templates and Recurring operator flows #219 explicitly forbids editing that test/Restore canonical frontend behavior coverage and SAM parity gates #159 code. The full browser reporter independently accepts all 147 states.

2. Required collapsed mobile disclosure necessarily breaks an existing full-suite pointer that Converge Templates and Recurring operator flows #219 cannot edit. Full E2E is 94/95 passed and reports all 147 states complete. The only failure is backend/e2e/issue-218-shared-primitives.spec.js:348-350: after its mobile Template capture leaves the viewport at 390px, it waits three minutes for the now-hidden Delete action without first opening the required row-owned Schedule actions disclosure. Converge Templates and Recurring operator flows #219 requires every mobile row to start collapsed, but its write set does not authorize this Converge Wave A surfaces on bounded shared UI primitives #218 journey. The correctly configured focused four-spec run is 37/37 passed, including source and packaged SAM Converge Templates and Recurring operator flows #219 journeys.

3. Workspace isolation is an inherited known baseline failure. After clean npm ci, make test-sam-workspace-isolation still fails because the unchanged verifier requires root node_modules/js-yaml/package.json, while npm installs it under backend/node_modules. Converge Wave A surfaces on bounded shared UI primitives #218 PM explicitly excluded that verifier repair, but Converge Templates and Recurring operator flows #219 requires the gate and forbids the path.

There is also a command-recipe error: literal npm --prefix backend exec playwright test -- ... runs from the repository root, skips backend/playwright.config.js, uses four workers with no base URL, and fails existing specs with Invalid URL. Running the same four specs from backend/ passes 37/37.

Green evidence already obtained:

• focused Tasks 36/36; frontend unit/coverage 299/299;
• typecheck/build and 74-asset source/build/SAM identity;
• SAM validate/build;
• configured focused browser 37/37;
• full browser 94/95 with 147/147 durable states;
• frontend parity 40 records/40 screenshots;
• exact 12 Converge Templates and Recurring operator flows #219 screenshots regenerated, source/SAM checked, and natively inspected;
• git diff --check clean; seven authorized candidate paths only; staged/unmerged 0/0.

Requested PM amendment:

• authorize the minimal expected-state/role additions in backend/scripts/frontend-capabilities.test.mjs;
• authorize the minimal Schedule actions click in backend/e2e/issue-218-shared-primitives.spec.js;
• either exclude the inherited workspace-isolation gate as in accepted Converge Wave A surfaces on bounded shared UI primitives #218 or authorize its existing dependency-location repair;
• correct the focused Playwright recipe to run from backend/.

No forbidden path was edited. Nothing was staged, committed, merged, pushed, deployed, sent to a provider, or advanced through a HUMAN gate.

[alexeygrigorev]

PM AMENDMENT — exact #219 implementation blockers adjudicated

I reviewed the complete groomed issue and SWE blocker report against docs/PROCESS.md, the PM role contract, accepted #218 commit 0c89588df809b2e84af02e796d1910a25eea0165, the accepted #159 durable capability/evidence contract, and the accepted held #164 commit 3e835a19017da18f2177d81fb7e084764970dee3.

The evidence supports the requested narrow amendment. The product outcome, production write boundary, runtime/API behavior, five durable state identities, #180 Recurring semantics, and #218 shared presentation contract remain unchanged.

Authorized exact adjustments

1. Capability contract expectations

   • Add only the five already-groomed state suffixes to the existing Templates/Recurring expected-state lists in backend/scripts/frontend-capabilities.test.mjs.
   • Add only exact admin role overrides for:
     • templates.batch-failure
     • recurring.editor-dirty
     • recurring.validation
     • recurring.saving
     • recurring.conflict
   • Do not alter the Restore canonical frontend behavior coverage and SAM parity gates #159 schema, collector, reporter, evidence policy/type, role semantics, routes/APIs, or unrelated states.

2. Accepted Converge Wave A surfaces on bounded shared UI primitives #218 evidence adaptation

   • In backend/e2e/issue-218-shared-primitives.spec.js, add only one mobile step that opens the row-owned Schedule actions disclosure before its existing Delete action.
   • Preserve the fixture, assertions, screenshots, capability claims, and every other Converge Wave A surfaces on bounded shared UI primitives #218 journey behavior.

3. Correct focused Playwright command

   • Run from the backend package so backend/playwright.config.js, its server/base URL, and worker settings apply:

     cd backend && npx playwright test e2e/issue-219-templates-recurring.spec.js e2e/card-template-updates.spec.js e2e/canonical-capability-behavior.spec.js e2e/canonical-route-parity.spec.js

4. Workspace-isolation gate

   • make test-sam-workspace-isolation is excluded from Converge Templates and Recurring operator flows #219.
   • Its failure is unchanged in Converge Templates and Recurring operator flows #219’s exact containing baseline and unrelated to this product slice. The dependency-location repair is already implemented, independently verified, PM-accepted, and committed in held Show signed-in identity and authorized teammates’ Task/Card work #164; Converge Templates and Recurring operator flows #219 must not duplicate or cherry-pick it.
   • Normal backend test/typecheck/build, source/build/SAM asset identity, source/SAM browser parity, SAM validation/build, packaged runtime/frontend isolation through make ci, and make ci itself remain mandatory.

Authorized refreeze

Software Engineer now owns exactly these steps:

• apply only the two newly authorized test/evidence edits while retaining the seven existing bounded candidate paths;
• rerun focused frontend checks, the corrected focused Playwright command, full E2E with all 147 states, frontend parity, backend test/typecheck/build, SAM validation/build and artifact checks, make ci, and diff integrity;
• regenerate and inspect exactly the 12 required Converge Templates and Recurring operator flows #219 screenshots;
• post new diff/status/content fingerprints and READY FOR DESIGN/TEST;
• repeat Designer → independent Tester → PM review on that exact frozen fingerprint.

The earlier partial green runs remain useful diagnostics but are not lifecycle verdicts. Any additional path or broader change requires another PM amendment.

Issue status, dependency resolution, write ownership, verification recipe, and lifecycle metadata have been updated accordingly.

Verdict: PM AMENDMENT APPROVED. Next owner: Software Engineer for the bounded repair and refreeze.

No repository/worktree file, issue other than #219, issue label, commit, push, merge, deployment, provider, production/private data, or HUMAN gate was changed.

[alexeygrigorev]

READY FOR DESIGN/TEST — PM-amended frozen candidate

Implemented and refrozen #219 on exact accepted #218 base 0c89588df809b2e84af02e796d1910a25eea0165, including the authorized PM amendment at #219 (comment).

Bounded implementation

• Recurring create/edit drafts now track reversible clean/dirty state and protect Cancel, Close, backdrop, and Escape dismissal with the shared accessible discard decision.
• Saving owns one mutation and blocks ambiguous dismissal; validation retains values and focuses exact fields; 409 and non-409 outcomes retain the dirty draft with explicit retry/reload ownership.
• Mobile Recurring rows start with one row-owned Schedule actions disclosure, preserve per-row expanded state through rerenders, expose Edit → Pause/Resume → Delete in order, and restore row/failure focus.
• Template batch preview/apply failures and partial conflicts are assertive, focused, selected-Template-owned states with exactly one correctly named retry.
• Added only the five groomed durable IDs: templates.batch-failure, recurring.editor-dirty, recurring.validation, recurring.saving, and recurring.conflict, all admin-scoped.
• Preserved read-only Git-authored Templates, accepted Restore behavior-based browser coverage and fix canonical UI accessibility races #180 recurring API/pause/resume/delete semantics, the Converge Wave A surfaces on bounded shared UI primitives #218 shared presentation contract, and all excluded backend/provider/Home/shell/account/team/Make assistant output review safe and lifecycle-complete #158/Show signed-in identity and authorized teammates’ Task/Card work #164 behavior.

PM-amendment adjustments

• backend/scripts/frontend-capabilities.test.mjs adds only the five expected suffixes and their exact admin role overrides. Schema, collector, reporter, routes, APIs, evidence policy, and unrelated states are unchanged.
• backend/e2e/issue-218-shared-primitives.spec.js opens Schedule actions before the existing mobile Delete interaction. Its desktop evidence remains expanded; its mobile capture explicitly collapses that same disclosure so the existing protected-delete guidance remains inside the 390x844 evidence frame. Fixtures, assertions, screenshot names, and capability ownership remain unchanged.
• The focused Playwright workflow ran from backend/, using the configured owned server, base URL, and one-worker contract.
• Per amendment, workspace isolation is excluded from the amended rerun and is not claimed.

Terminal verification

All authoritative amended commands exited 0:

• node --test frontend/test/tasks-surface.test.mjs: 36/36 passed.
• npm run test:frontend:unit: 299/299 passed, 25 suites.
• npm run test:frontend:coverage: 299/299 passed; 76.39% statements/lines, 72.35% branches, 74.72% functions.
• npm --prefix backend test: 1,090 passed, 5 intentional skips, 0 failed, 1,095 total and 166 suites.
• npm --prefix backend run typecheck: passed.
• npm --prefix backend run build: passed; runtime boundary verified.
• Source/build frontend identity: 74/74 assets byte-identical.
• Corrected configured focused Playwright run: 37/37 passed.
• Isolated amended Converge Wave A surfaces on bounded shared UI primitives #218 journey: 1/1 passed.
• npm --prefix backend run test:e2e: 95/95 passed; reporter completed 147/147 stable capability states.
• npm --prefix backend run test:e2e:frontend-parity: PASS with 40 evidence records and 40 screenshots.
• make sam-validate: passed.
• make sam-build: passed for all six functions.
• Source/SAM frontend identity: 74/74 assets byte-identical.
• make ci: terminal exit 0; frontend/backend checks, all seven real DynamoDB transaction suites (51/51), typecheck/build/SAM/runtime boundary, and packaged frontend isolation (13/13) passed.
• git diff --check: passed.

The unchanged conversational fixture crossed its July 30 30-day wall-clock boundary. Backend tests and make ci used the same process-limited advancing Date preload pattern audited and accepted for #218, anchored at 2026-08-29T11:59:00Z. Preload source SHA-256: 88ec58aa0be084e5fbe67ee3196427fae8abb0321f664ea1cdd87d6ff884df88. It activates only for /backend/tests/*.test.ts, was never written to the candidate, leaves browser/build/SAM/script workers on wall time, and NODE_OPTIONS is unset at freeze.

Exact screenshot evidence

.tmp/screenshots/issue-219/ contains exactly 12 ignored PNGs and no extras:

1. 01-source-templates-batch-conflict-desktop-1440x900.png
2. 02-sam-templates-batch-conflict-desktop-1440x900.png
3. 03-source-templates-detail-mobile-390x844.png
4. 04-sam-templates-detail-mobile-390x844.png
5. 05-source-recurring-actions-mobile-390x844.png
6. 06-sam-recurring-actions-mobile-390x844.png
7. 07-source-recurring-dirty-editor-mobile-390x844.png
8. 08-sam-recurring-dirty-editor-mobile-390x844.png
9. 09-source-recurring-conflict-desktop-1440x900.png
10. 10-sam-recurring-conflict-desktop-1440x900.png
11. 11-source-recurring-delete-409-desktop-1440x900.png
12. 12-sam-recurring-delete-409-desktop-1440x900.png

Every desktop image is 1440x900 sRGB and every mobile image is 390x844 sRGB. All six source/SAM pairs are byte-identical. I opened all 12 independently at original resolution: intended state and next decision are visible, mobile hierarchy and controls are readable, no evidence is clipped or overlapping, and all content is synthetic/public-safe. Screenshot content-manifest SHA-256: 064f994210d653aeb10c29d94418442653144532af15b9ee71f892e7e51fd77c.

Generated test-results, failure traces, Playwright reports, and non-#219 screenshot artifacts are absent before freeze.

Frozen candidate fingerprints

• Branch: issue-219-templates-recurring
• HEAD/base/merge-base: 0c89588df809b2e84af02e796d1910a25eea0165
• Candidate paths: 9 — 8 tracked modifications plus 1 untracked issue-owned E2E spec
• Staged paths: 0
• Unmerged paths: 0
• Tracked binary diff SHA-256: 5cba5e8702df3fbc347c37ebafb13754461a79b970875a18f9e6c53f7ef0ae34
• Porcelain-v1 NUL status SHA-256: 10318348cb9aaec56f5a38a7530ddf36133fdb7435d3c53e9f4a457ed7188f48
• Candidate content manifest SHA-256: 0cd25da62f2133ccf63e3334e5eba100f75d60e9479417551a94f97b50a61d49

Nothing was staged, committed, merged, pushed, deployed, sent to an external provider, or advanced through a HUMAN gate.

READY FOR DESIGN/TEST

[alexeygrigorev]

DESIGN FINDINGS — PM-amended frozen candidate

Reviewed read-only as Product Designer against AGENTS.md, complete docs/PROCESS.md, .claude/agents/designer.md, frontend/DESIGN.md, frontend/DESIGN_SYSTEM.md, complete #219/#162/#218 history, the #219 PM amendment, the frozen implementation diff, and exactly all 12 native screenshots.

Frozen candidate verified

• HEAD/base/merge-base: 0c89588df809b2e84af02e796d1910a25eea0165
• Candidate paths: 9 (8 tracked modifications + 1 untracked issue-owned E2E spec)
• Tracked binary diff SHA-256: 5cba5e8702df3fbc347c37ebafb13754461a79b970875a18f9e6c53f7ef0ae34
• NUL-delimited porcelain SHA-256: 10318348cb9aaec56f5a38a7530ddf36133fdb7435d3c53e9f4a457ed7188f48
• Candidate content manifest SHA-256: 0cd25da62f2133ccf63e3334e5eba100f75d60e9479417551a94f97b50a61d49
• Screenshot manifest SHA-256: 064f994210d653aeb10c29d94418442653144532af15b9ee71f892e7e51fd77c
• Staged/unmerged paths: 0/0

The identity remained exact after review.

Native screenshot review

Exactly the required 12 PNGs exist under .tmp/screenshots/issue-219/, with no extras. I opened every file independently at original resolution: four 1440×900 desktop source/SAM pairs and two 390×844 mobile source/SAM pairs. All six pairs are byte-identical.

Inspected states:

• Template batch partial conflict: 01, 02
• Template mobile detail: 03, 04
• Recurring mobile row disclosure: 05, 06
• Recurring dirty editor: 07, 08
• Recurring conflict: 09, 10
• Recurring protected delete: 11, 12

Template detail and partial-conflict hierarchy are readable; applied and conflicted Cards remain distinct, and fresh-preview recovery is clear. The dirty editor retains values and context, the conflict dialog retains its decisions, and protected delete leaves the schedule visible with safe Pause guidance. Mobile controls are at least 44px, disclosure order is understandable, focus cues are visible, and I found no page-level overflow, evidence-obscuring clipping/overlap, broken route, false success, private data, real contact/provider payload, credential, or production identifier. New style declarations use the accepted #218 semantic tokens, so they do not introduce a separate light/dark palette.

Blocking findings

1. Mobile Delete is not visually separated from routine actions. In 05 and 06, Edit, Pause, and Delete render as three identical neutral full-width controls with equal spacing. The candidate attempts separation at frontend/src/styles.css:3745, but the later, more-specific Tasks rule at frontend/src/styles.css:8891 resets the danger-text-button border, background, and text to neutral; the mobile rule at frontend/src/styles.css:9541 then makes every action the same full-width shape. The explicit Converge Templates and Recurring operator flows #219 criterion and the design-system contract require destructive Delete to remain visually separated from Edit/Pause. Preserve the explicit label/ARIA semantics, but restore an unmistakable token-based destructive treatment and/or stronger grouping separation in both light and dark themes, then regenerate the exact evidence.

2. Failure/conflict copy exposes raw route messages and HTTP state codes. 09 and 10 visibly say Synthetic route failure (409). frontend/src/surfaces/tasks/quick-create.js:648-656 directly interpolates err.message, and Template preview/apply does the same at frontend/src/surfaces/tasks/templates.js:468-470 and :506-507; the dedicated browser journey explicitly requires Synthetic route failure (503) at backend/e2e/issue-219-templates-recurring.spec.js:228. This conflicts with Converge Templates and Recurring operator flows #219's human-label/privacy copy criterion and frontend/DESIGN_SYSTEM.md's rule to avoid API/state codes and raw provider/internal failure payloads. Keep the useful human consequences and choices, but map these to stable operator-safe copy without status codes or raw backend messages; update behavior coverage and regenerate affected evidence.

Everything else in the requested Template/Recurring hierarchy, dirty-state protection, focus ownership, source/SAM consistency, target sizing, responsive layout, accessibility presentation, and public-safe evidence passes design review.

Verdict: DESIGN FINDINGS. Re-freeze after both blockers are repaired, regenerate and inspect exactly the 12 required files with no extras, and request a fresh Designer review on the new fingerprint.

No repository file was edited, staged, committed, merged, pushed, deployed, sent to a provider, or advanced through a HUMAN gate during this review.