Attach process instructions to seeded recurring tasks

[alexeygrigorev]

Attach process instructions to seeded recurring tasks

Status: in progress
Tags: bug, work-engine, portal, process-docs, P0
Depends on: #70, #73
Blocks: #71 final V1 cutover acceptance

Scope

Seeded production recurring tasks must be actionable with process context. The two Sunday/daily launch tasks are visible in Operations Home after #73, but they still show as blocking process-quality findings because generated tasks have neither instructionDocId nor instructionsUrl.

This issue updates the recurring seed/generation path so:

• Baseline recurring configs can carry task instruction context such as instructionDocId, instructionsUrl, systems, and proof metadata where appropriate.
• Future recurring task generation copies those fields into generated task records.
• The production deploy seed step repairs already-generated recurring tasks for existing configs, idempotently, so today’s tasks stop showing as missing-instruction blockers after deploy.

Use in-repo process docs where available. For the current launch tasks:

• Invite people to Slack from Airtable should point to sop.community.book-of-the-week.invite-people-to-slack-from-the-airtable-form.
• Create new Trello cards and review existing ones should at minimum point to a relevant Trello SOP or fallback instructionsUrl so the operator can open process context. If no exact SOP exists, use the closest existing Trello process doc and leave a clear comment/test expectation that this is a V1 launch fallback.

Acceptance Criteria

• Baseline recurring configs include process instruction context for the two currently generated production tasks.
• generateRecurringTasks copies recurring config instruction context into newly generated tasks.
• Re-running seed-recurring.ts repairs existing generated recurring tasks that are missing instruction context, without creating duplicates or overwriting unrelated operator-created tasks.
• Seed/cron tests prove generated recurring tasks have instruction context and that repair is idempotent.
• Production smoke after deploy verifies the two seeded Today tasks are visible and no longer appear as missing-instruction process blockers.

Test Scenarios

Scenario: Future recurring tasks inherit process docs

Given: baseline recurring configs are seeded.
When: cron generates due recurring tasks.
Then: generated tasks for Slack invites and Trello review have instructionDocId or instructionsUrl plus relevant systems metadata.

Scenario: Existing production tasks are repaired

Given: recurring tasks already exist for a seeded config and are missing process instruction fields.
When: seed-recurring.ts runs again during deploy.
Then: those existing recurring tasks receive the config instruction context and no duplicate tasks are created.

Scenario: Process quality remains honest

Given: a task still lacks instructions.
When: Operations Home builds process-quality findings.
Then: it can still report that blocker. This issue should fix the seeded recurring tasks, not disable process-quality checks.

Required Verification

• NODE_ENV=test SKIP_AUTH=true node --import tsx --test tests/seed-recurring.test.ts
• npm --prefix work-engine run typecheck
• Focused frontend/process-quality test if needed to prove blocker removal logic.
• After push/deploy, production browser/API smoke for /work Today and Process Quality.

Out of Scope

• Curating perfect long-term SOPs for every recurring task.
• Removing process-quality blockers globally.
• Real Trello import or Telegram/assistant human gates.

[alexeygrigorev]

Implemented and pushed in 622dd85.\n\nLocal gates passed before push:\n- git diff --check\n- NODE_ENV=test SKIP_AUTH=true node --import tsx --test tests/seed-recurring.test.ts\n- NODE_ENV=test SKIP_AUTH=true node --import tsx --test tests/export-portable.test.ts\n- npm --prefix work-engine run typecheck\n- npm --prefix work-engine test -- --runInBand\n- uv run --project lambda-functions --extra search --with pytest python -m pytest tests/docs_app/test_process_quality.py tests/docs_app/test_work_api_integration.py tests/docs_app/test_frontend_routes_and_links.py -q\n\nTester gate passed and PM accepted. On-Call is now responsible for the Deploy DataOps V1 Lambda run and production /work smoke for the two seeded Today tasks and missing-instruction Process Quality blockers.

[alexeygrigorev]

On-call CI/CD and production smoke for commit 622dd85aac0a7e3f11c716a34ea6f14cddbe2200 completed.

CI/CD:

• Workflow: Deploy DataOps V1 Lambda
• Run: https://github.com/DataTalksClub/dataops/actions/runs/28332381105
• Result: success
• Expected jobs both passed:
  • Check DataOps v1 app
  • Deploy DataOps v1 app
• Deploy job passed OIDC/AWS credential setup, SAM deploy, runtime seeding, deployed docs smoke, workflow-template smoke, and private work-engine Lambda smoke.

Production smoke for https://ops.dtcdev.click/work on 2026-06-28:

• Authenticated public API GET /work/api/tasks?date=2026-06-28 returned exactly 2 tasks.
• Create new Trello cards and review existing ones has instructionDocId: sop.internal-admin.trello.how-to-create-an-event-through-trello and systems: [trello].
• Invite people to Slack from Airtable has instructionDocId: sop.community.book-of-the-week.invite-people-to-slack-from-the-airtable-form and systems: [airtable, slack].
• Operations Home rendered both seeded recurring tasks in the browser.
• Process Quality no longer reports missing-instruction blockers for either target task. The deterministic report summary has blocking: 0 and missing-proof-instructions: 0; target missing-instruction count is 0.

Residual observation:

• Process Quality still shows 2 active blockers for those same task docs, but they are broken-asset-reference findings for missing screenshots/images, not missing-instruction blockers. This appears to be a separate process-doc asset cleanup issue, not a deploy or issue Attach process instructions to seeded recurring tasks #74 regression.

Evidence captured locally under .tmp/issue-74-oncall/:

• tasks-summary.json
• process-quality-summary.json
• ui-evidence.json
• operations-home.png
• process-quality-section.png
• process-quality-drilldown.png